Bug 1044676 - 2.2. Configuration and Log Files for OpenShift Components
Summary: 2.2. Configuration and Log Files for OpenShift Components
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 2.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: brice
QA Contact: ecs-bugs
URL:
Whiteboard:
: 1045148 1091951 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 19:38 UTC by Luke Meyer
Modified: 2015-07-20 00:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-07 00:38:01 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Luke Meyer 2013-12-18 19:38:50 UTC
Some of the log files have moved. Most of this actually goes back to OSE 1.2 (exception: ruby193-mcollective logs)

2.2.2. Broker Host Failures
Everything broker-related is now under /var/log/openshift/broker.

/var/www/openshift/broker/httpd/logs/ directory has become /var/log/openshift/broker/httpd/

/var/www/openshift/broker/log/production.log is now /var/log/openshift/broker/production.log

/var/log/openshift/user_action.log is now /var/log/openshift/broker/user_action.log


2.2.3. MCollective
/var/log/ruby193-mcollective.log on node hosts is now /var/log/openshift/node/ruby193-mcollective.log

/var/log/ruby193-mcollective-client.log on broker hosts is now /var/log/openshift/broker/ruby193-mcollective-client.log

We should also mention that actions taken by mcollective on the node also log into /var/log/openshift/node/platform.log and /var/log/openshift/node/platform-trace.log

2.2.4. Gears
/var/lib/openshift/.httpd.d looks as described if using the apache-vhost web front end on the node (which wasn't an option in OSE 1.2, these docs are from 1.1). With the standard mod-rewrite web front end, there are no per-gear files/directories; instead everything is collected into several files like this:

ls /var/lib/openshift/.httpd.d/
aliases.db   frontend-mod-rewrite-https-template.erb  idler.db   nodes.db   routes.json  sts.txt
aliases.txt  geardb.json                              idler.txt  nodes.txt  sts.db

Comment 2 brice 2013-12-19 02:04:31 UTC
2.2.2

Done for 1.2 and 2.0 guides.

2.2.3

Done for 1.2 and 2.0 guides. Had to add condition, so the final bit you mentioned about the platform.log and platform-trace.log is in there, and the ruby193-mcollective and oo-mco ping stuff should only be in the 2.0 guide.

2.2.4

Done, but I'm not sure if I've done exactly as needed. I pretty much replaced the file output and some rewording so it makes sense in context. Let me know if anything more needs to be done. 

Also, I should mention that in Alex's test machine (which he kindly lets us use for testing), the files were different. His didn't have the frontend-mod-rewrite-https-template.erb file and he a nodes.db.romnew file. Probably not a big deal, but worth mentioning.

Comment 4 Luke Meyer 2013-12-19 23:10:47 UTC
Under 2.2.3 MCollective:

I would not say "Any MCollective actions performed on the node are also logged in /var/log/openshift/node/platform.log and /var/log/openshift/node/platform-trace.log." as that sounds like they are redundant logs, and the info that goes there is quite different and there may/not be any for a given call. So I might reword to:

"MCollective actions performed on the node may also log more details in /var/log/openshift/node/platform.log and /var/log/openshift/node/platform-trace.log."


Otherwise, looks good, thanks!

Comment 5 brice 2013-12-20 00:30:00 UTC
We're trying to shy away from using the word 'may', so I changed that to can. Other than that, I implemented the suggestion. 

Thanks, Luke. Putting this on QA. 

The above links will still work.

Comment 6 brice 2013-12-20 00:48:03 UTC
*** Bug 1045148 has been marked as a duplicate of this bug. ***

Comment 8 brice 2014-05-01 00:37:56 UTC
*** Bug 1091951 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.