Bug #24185
closed
No debug logging with Foreman 1.18 RC3
Description
I enabled debug logging and get only information messages in production.log. I touched restart.txt several times and still the logging is not taking effect.
:logging:
:level: debug
:production:
:type: file
:layout: pattern
# Individual logging types can be toggled on/off here
:loggers:
:app:
:enabled: true
:sql:
:enabled: true
2018-07-06T09:37:16 [I|app|] Started GET "/node/foreman-test.DOMAIN?format=yml" for 10.20.0.26 at 2018-07-06 09:37:16 -0400
2018-07-06T09:37:16 [I|app|ec21f] Processing by HostsController#externalNodes as YML
2018-07-06T09:37:16 [I|app|ec21f] Parameters: {"name"=>"foreman-test.DOMAIN"}
2018-07-06T09:37:16 [I|app|ec21f] Current user: foreman_api_admin (administrator)
2018-07-06T09:37:17 [I|app|ec21f] Rendering text template
2018-07-06T09:37:17 [I|app|ec21f] Rendered text template (0.0ms)
2018-07-06T09:37:17 [I|app|ec21f] Completed 200 OK in 1467ms (Views: 1.2ms | ActiveRecord: 867.0ms)
Updated by Tomer Brisker almost 6 years ago
- Category set to Logging
- translation missing: en.field_release set to 330
Updated by Lukas Zapletal almost 6 years ago
- Related to Feature #16218: Add possibility to override log configuration for test environment added
Updated by The Foreman Bot almost 6 years ago
- Status changed from New to Ready For Testing
- Assignee set to Lukas Zapletal
- Pull request https://github.com/theforeman/foreman/pull/5792 added
Updated by Marek Hulán almost 6 years ago
Which file are you changing? Also could you try restarting the whole httpd service? Also note it should be tmp/restart.txt which is touched (not sure if that still works though)
Updated by Marek Hulán almost 6 years ago
Oh I see it has been already reproduced, please ignore my comment.
Updated by Lukas Zapletal almost 6 years ago
- Triaged changed from No to Yes
Yeah, bot could have set Triaged as well perhaps.
Updated by Marek Hulán almost 6 years ago
This does not seem to be 1.18 regression, the introducing commit was merged in 1.14. It should be possible to just move production configuration to one level above under :logging and it should work just fine.
Updated by Trey Dockendorf almost 6 years ago
Using the documented method for debug logging works just fine:
:logging: :level: debug
I don't know where I got the idea to use the production key, maybe something from older version of Foreman that's no longer valid.
Updated by Ondřej Pražák almost 6 years ago
- Target version changed from 1.18.0 to 1.18.1
Updated by Lukas Zapletal almost 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset b0b46844626a27b6d67f6aef1f67695af103b47a.
Updated by Lukas Zapletal almost 6 years ago
I think it was in example (commented), it is supposed to work and it had a bug. Fixed.