Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[dev.icinga.com #12935] disabled show_stacktraces has no effect #2595

Closed
icinga-migration opened this issue Oct 16, 2016 · 2 comments
Closed

[dev.icinga.com #12935] disabled show_stacktraces has no effect #2595

icinga-migration opened this issue Oct 16, 2016 · 2 comments
Labels
bug Something isn't working
Milestone
2.5.0

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12935

Created by mfriedrich on 2016-10-16 14:52:06 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-10-18 15:53:01 +00:00 (in Redmine)

Explicitly disabling the setting in user preferences including a logout/login has no effect. Still getting those stack traces.

icingaweb2_preferences_show_stacktraces_bug_01.png

icingaweb2_preferences_show_stacktraces_bug_02.png

[root@icinga2 icingaadmin]# cat /etc/icingaweb2/preferences/icingaadmin/config.ini
[icingaweb]
show_stacktraces = "0"
show_benchmark = "0"
auto_refresh = "1"

Can be reproduced using the latest "icinga2x" Vagrant box.

Attachments
@icinga-migration
Copy link
Author

Updated by aklimov on 2016-10-18 15:53:01 +00:00

Hint: this was introduced with 2ec3666

@icinga-migration icinga-migration added the bug Something isn't working label Jan 17, 2017
@b1zzu
Copy link

b1zzu commented Apr 10, 2017 •
edited

++ (still happens with latest master)

@lippserd lippserd added this to the 2.5.0 milestone Oct 16, 2017
lippserd added a commit that referenced this issue Nov 15, 2017
@lippserd
Fix that disabled stack straces via user prefs had no effect
af64ca8 
Web::setupFrontController() took the user object into account when checking for disabled stacktraces.
But we changed our bootstrap order some time ago so we did not have a user in this method anymore.
Now, Web::setupUser() checks for disabled stacktaces in the user prefs instead.

refs #2595
@lippserd lippserd mentioned this issue Nov 15, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
2.5.0
Development

No branches or pull requests
3 participants
@lippserd @b1zzu @icinga-migration