Page 1 of 2
Can't get Nagios to display
Posted: Tue Nov 22, 2016 3:00 pm
by psrch
I am having trouble getting Nagios running. I know the service is running, but if I go to the nagios application in the browser and log in, I get a black screen. If, however, you "highlight" the words, I see "Not supported" displayed.
I am running Nagios core, version 4.1.1 (or latest when I installed it) running on CentOS 7. I followed the directions located here:
https://assets.nagios.com/downloads/nag ... entos7.pdf - with no error messages.
What am I doing wrong?
Re: Can't get Nagios to display
Posted: Tue Nov 22, 2016 3:10 pm
by avandemore
First, it's probably better to use Core 4.2.2:
https://assets.nagios.com/downloads/nag ... 2.2.tar.gz
Can you attach a screenshot of this:
nagios application in the browser and log in, I get a black screen. If, however, you "highlight" the words, I see "Not supported" displayed.
Re: Can't get Nagios to display
Posted: Tue Nov 22, 2016 3:19 pm
by psrch
I've attached a screen shot. And I double checked - I am using version 4.2.2, with plugins version 2.1.2.
Re: Can't get Nagios to display
Posted: Tue Nov 22, 2016 4:02 pm
by avandemore
Maybe you have some kind of plugin or other issue with your web browser. I can pull up the login from here.
Nagios is developed against vanilla Firefox and Chrome installs.
Re: Can't get Nagios to display
Posted: Tue Nov 22, 2016 4:06 pm
by psrch
I can pull up the login just fine - this screen is what happens immediately after logging in.
Re: Can't get Nagios to display
Posted: Tue Nov 22, 2016 4:08 pm
by dwhitfield
Re: Can't get Nagios to display
Posted: Tue Nov 22, 2016 4:17 pm
by psrch
Same thing, except the CSS seems to be working... see image attached.
Re: Can't get Nagios to display
Posted: Tue Nov 22, 2016 4:31 pm
by dwhitfield
Can you post the following:
Code: Select all
/usr/local/nagios/var/nagios.log
/var/log/messages
/var/log/httpd/error_log
/var/log/httpd/access_log
If you have security concerns, please scrub the files as needed. Thanks!
Re: Can't get Nagios to display
Posted: Tue Nov 22, 2016 4:47 pm
by psrch
I dug through the /var/log/messages, /var/log/httpd/error_log, and /var/log/httpd/access_log files, and didn't see anything related to Nagios there.
However, here are the messages from the nagios log since the last start:
Code: Select all
[1479845816] Nagios 4.2.2 starting... (PID=16002)
[1479845816] Local time is Tue Nov 22 14:16:56 CST 2016
[1479845816] LOG VERSION: 2.0
[1479845816] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
[1479845816] qh: core query handler registered
[1479845816] nerd: Channel hostchecks registered successfully
[1479845816] nerd: Channel servicechecks registered successfully
[1479845816] nerd: Channel opathchecks registered successfully
[1479845816] nerd: Fully initialized and ready to rock!
[1479845816] wproc: Successfully registered manager as @wproc with query handler
[1479845816] wproc: Registry request: name=Core Worker 16007;pid=16007
[1479845816] wproc: Registry request: name=Core Worker 16004;pid=16004
[1479845816] wproc: Registry request: name=Core Worker 16006;pid=16006
[1479845816] wproc: Registry request: name=Core Worker 16008;pid=16008
[1479845816] wproc: Registry request: name=Core Worker 16005;pid=16005
[1479845816] wproc: Registry request: name=Core Worker 16009;pid=16009
[1479845816] wproc: Registry request: name=Core Worker 16010;pid=16010
[1479845816] wproc: Registry request: name=Core Worker 16011;pid=16011
[1479845816] wproc: Registry request: name=Core Worker 16012;pid=16012
[1479845816] wproc: Registry request: name=Core Worker 16013;pid=16013
[1479845816] wproc: Registry request: name=Core Worker 16015;pid=16015
[1479845816] wproc: Registry request: name=Core Worker 16014;pid=16014
[1479845816] wproc: Registry request: name=Core Worker 16017;pid=16017
[1479845816] wproc: Registry request: name=Core Worker 16016;pid=16016
[1479845816] wproc: Registry request: name=Core Worker 16018;pid=16018
[1479845816] wproc: Registry request: name=Core Worker 16019;pid=16019
[1479845816] wproc: Registry request: name=Core Worker 16020;pid=16020
[1479845816] wproc: Registry request: name=Core Worker 16021;pid=16021
[1479845816] wproc: Registry request: name=Core Worker 16022;pid=16022
[1479845816] wproc: Registry request: name=Core Worker 16023;pid=16023
[1479845816] wproc: Registry request: name=Core Worker 16024;pid=16024
[1479845816] wproc: Registry request: name=Core Worker 16027;pid=16027
[1479845816] wproc: Registry request: name=Core Worker 16029;pid=16029
[1479845816] wproc: Registry request: name=Core Worker 16030;pid=16030
[1479845816] wproc: Registry request: name=Core Worker 16026;pid=16026
[1479845816] wproc: Registry request: name=Core Worker 16028;pid=16028
[1479845816] wproc: Registry request: name=Core Worker 16031;pid=16031
[1479845816] wproc: Registry request: name=Core Worker 16032;pid=16032
[1479845816] wproc: Registry request: name=Core Worker 16033;pid=16033
[1479845816] wproc: Registry request: name=Core Worker 16034;pid=16034
[1479845816] wproc: Registry request: name=Core Worker 16035;pid=16035
[1479845816] wproc: Registry request: name=Core Worker 16036;pid=16036
[1479845816] wproc: Registry request: name=Core Worker 16037;pid=16037
[1479845816] wproc: Registry request: name=Core Worker 16038;pid=16038
[1479845816] wproc: Registry request: name=Core Worker 16039;pid=16039
[1479845816] wproc: Registry request: name=Core Worker 16040;pid=16040
[1479845816] wproc: Registry request: name=Core Worker 16041;pid=16041
[1479845816] wproc: Registry request: name=Core Worker 16042;pid=16042
[1479845816] wproc: Registry request: name=Core Worker 16043;pid=16043
[1479845816] wproc: Registry request: name=Core Worker 16044;pid=16044
[1479845816] wproc: Registry request: name=Core Worker 16045;pid=16045
[1479845816] wproc: Registry request: name=Core Worker 16046;pid=16046
[1479845816] wproc: Registry request: name=Core Worker 16047;pid=16047
[1479845816] wproc: Registry request: name=Core Worker 16048;pid=16048
[1479845816] wproc: Registry request: name=Core Worker 16049;pid=16049
[1479845816] wproc: Registry request: name=Core Worker 16050;pid=16050
[1479845816] wproc: Registry request: name=Core Worker 16051;pid=16051
[1479845816] wproc: Registry request: name=Core Worker 16052;pid=16052
[1479845816] Successfully launched command file worker with pid 16053
[1479846041] SERVICE ALERT: localhost;SSH;CRITICAL;SOFT;1;connect to address 127.0.0.1 and port 22: Connection refused
[1479846101] SERVICE ALERT: localhost;SSH;CRITICAL;SOFT;2;connect to address 127.0.0.1 and port 22: Connection refused
[1479846116] SERVICE ALERT: localhost;Total Processes;WARNING;SOFT;1;PROCS WARNING: 340 processes with STATE = RSZDT
[1479846161] SERVICE ALERT: localhost;SSH;CRITICAL;SOFT;3;connect to address 127.0.0.1 and port 22: Connection refused
[1479846176] SERVICE ALERT: localhost;Total Processes;WARNING;SOFT;2;PROCS WARNING: 334 processes with STATE = RSZDT
[1479846221] SERVICE ALERT: localhost;SSH;CRITICAL;HARD;4;connect to address 127.0.0.1 and port 22: Connection refused
[1479846236] SERVICE ALERT: localhost;Total Processes;WARNING;SOFT;3;PROCS WARNING: 340 processes with STATE = RSZDT
[1479846296] SERVICE ALERT: localhost;Total Processes;WARNING;HARD;4;PROCS WARNING: 340 processes with STATE = RSZDT
[1479846296] SERVICE NOTIFICATION: nagiosadmin;localhost;Total Processes;WARNING;notify-service-by-email;PROCS WARNING: 340 processes with STATE = RSZDT
[1479849415] Auto-save of retention data completed successfully.
[1479849896] SERVICE NOTIFICATION: nagiosadmin;localhost;Total Processes;WARNING;notify-service-by-email;PROCS WARNING: 340 processes with STATE = RSZDT
Re: Can't get Nagios to display
Posted: Tue Nov 22, 2016 5:04 pm
by dwhitfield
Are you ok PMing me the files I requested? You can still scrub them as needed.
It sounds like you have apache serving other things. If this is the case, in particular I'd like to take a look at /var/log/httpd/error_log.
Have you tried opening Nagios in a different browser? Same error message?
Please be aware that our office will be closed Thursday and Friday.