Hello,
I had some users complaining they could not log into Nagios anymore. After some testing, it seemed they entered the wrong password. It does not seem normal users get a 500 server error. Is this a bug? Could someone test this on 2014 R1.4? There should be a message a wrong pasword is entered, not an internal server error.
Grtz
Willem
Error http internal server error when entering wrong passwor
Re: Error http internal server error when entering wrong pas
I'm not seeing the same behavior. Can you test this on a different XI server if you have one? Is there anything in the /var/log/httpd/error_log file?
Former Nagios employee
Re: Error http internal server error when entering wrong pas
I did a test with my QA XI server and there I do get 'wrong password' message. After trying again on my production resulting again in a server error with http status code 500, this is an extract of the errorlog:
I would think it has something to do with "[Fri Sep 05 09:18:08 2014] [error] [client 172.19.4.245] PHP Fatal error: Call to a member function authenticate() on a non-object in /usr/local/nagiosxi/html/includes/components/active_direct$"
So I checked the ad integration components, which should be disabled and it was in fact disabled. Any idea what might be the issue?
Grtz
Willem
Code: Select all
[Fri Sep 05 08:59:34 2014] [error] [client 172.19.4.245] PHP Notice: Undefined variable: ac_needed_js_inject in /usr/local/nagiosxi/html/includes/components/ccm/page_templates/ccm_table.php on$
[Fri Sep 05 08:59:38 2014] [error] [client 172.19.4.245] PHP Notice: Undefined variable: ac_needed_js_inject in /usr/local/nagiosxi/html/includes/components/ccm/page_templates/ccm_table.php on$
[Fri Sep 05 09:00:31 2014] [error] [client 172.19.4.245] PHP Notice: Undefined variable: ac_needed_js_inject in /usr/local/nagiosxi/html/includes/components/ccm/page_templates/ccm_table.php on$
[Fri Sep 05 09:00:38 2014] [error] [client 172.19.4.245] PHP Notice: Undefined variable: ac_needed_js_inject in /usr/local/nagiosxi/html/includes/components/ccm/page_templates/ccm_table.php on$
[Fri Sep 05 09:16:10 2014] [error] [client 172.19.4.245] PHP Fatal error: Call to a member function authenticate() on a non-object in /usr/local/nagiosxi/html/includes/components/active_direct$
[Fri Sep 05 09:18:08 2014] [error] [client 172.19.4.245] PHP Fatal error: Call to a member function authenticate() on a non-object in /usr/local/nagiosxi/html/includes/components/active_direct$
[Fri Sep 05 09:18:08 2014] [error] [client 172.19.4.245] File does not exist: /var/www/html/favicon.ico
[Fri Sep 05 09:18:08 2014] [error] [client 172.19.4.245] File does not exist: /var/www/html/favicon.ico
So I checked the ad integration components, which should be disabled and it was in fact disabled. Any idea what might be the issue?
Grtz
Willem
Nagios XI 5.8.1
https://outsideit.net
https://outsideit.net
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: Error http internal server error when entering wrong pas
I would\will have to take a look to see what might be going on there. I do know that AD has not had changes for 2014, but whether they are needed or not is the question. If you are not using the ad component, I would highly suggest removing it and seeing if that resolves the issues you are seeing.
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
Re: Error http internal server error when entering wrong pas
Spenser,
The problem has been solved by removing the Active Directory Inegration component. A bit strange, as it was not enabled.
I guess this thread can be closed.
Grtz
Willem
The problem has been solved by removing the Active Directory Inegration component. A bit strange, as it was not enabled.
I guess this thread can be closed.
Grtz
Willem
Nagios XI 5.8.1
https://outsideit.net
https://outsideit.net
Re: Error http internal server error when entering wrong pas
Could be that it was "disabled" but still in use. I saw a few bugs recently where the web interface did not reflect the true state of a flatfile or database entry.
Either way, glad it was resolved. Closing up.
Either way, glad it was resolved. Closing up.
Former Nagios employee