Description of problem: add crane logs in foreman-debug Version-Release number of selected component (if applicable): sos-3.2-15 Actual results: sos_commands/foreman/foreman-debug/var/log/httpd is missing crane logs. Expected results: crane logs included. Additional info:
Since these logs are expected to be collected by external command foreman-debug, changing product to Sat6.
Can you guys specify what filename pattern are we supposed to add?
michael, can you please see comment 4.
Crane logs direct to stderr. Apache should be putting that output in its error log.
Michael, can you please give me an example of some logs that crane record? I can't grep a single message containing "crane" in a satellite6 system. Ideally with some simple action I need to perform to get such a log(s). Thanks!
When crane starts, it logs one of three messages about loading a config file. You can see them here: https://github.com/pulp/crane/blob/1c5e817/crane/config.py#L60-L67
Chris, I've doublechecked and we currently add the following file pattern into foreman-debug: add_files /var/log/{httpd,apache2}/*error_log* We do not collect access_logs because these contain lot of entries but the error_log should be sufficient (should contain logs from all WSGI apps). The crane component in Satellite 6 is configured with default apache logging setting: https://github.com/Katello/puppet-crane/blob/master/manifests/apache.pp Check the error_log once again, your messages should be there.
perfect, thx Lukas
Moving 6.2 bugs out to sat-backlog.
Created redmine issue http://projects.theforeman.org/issues/15968 from this bug
Upstream bug component is Content Management
Upstream bug component is Infrastructure
Upstream bug assigned to lzap
An upstream issue has been opened for this. When this is fixed, the next version of satellite will contain the fix. We will no longer be tracking this downstream. If you feel this was closed in error, please feel free to re-open with additional information.