CentOS errors
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: CentOS errors
check_snmp is included with 1.5. Did you compile properly? Did you see any errors?
Re: CentOS errors
I follow the instruction "Installing Nagios Core From Source" no errors was found ... should i do it again ?
Re: CentOS errors
Download and build an older version of the plugins. Once built, only copy over those plugins that you are missing into your libexec folder.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: CentOS errors
Do you have locate installed on your system?:
If you do not find it, you can re-compile, just make sure you follow the commands completely, including configure, make, make all.
Code: Select all
yum install mlocateCode: Select all
updatedb
Code: Select all
locate check_snmpRe: CentOS errors
So i download the last version of the plugins and i follow the "Installing Nagios Core From Source" and i execute the following commands ....
after restart the nagios i have this error:
Code: Select all
./configure --with-nagios-user=nagios --with-nagios-group=nagios
make
make install
chkconfig --add nagios
chkconfig --level 35 nagios on
chkconfig --add httpd
chkconfig --level 35 httpd onWhoops!
Error: Could not read host and service status information!
The most common cause of this error message (especially for new users), is the fact that Nagios is not actually running. If Nagios is indeed not running, this is a normal error message. It simply indicates that the CGIs could not obtain the current status of hosts and services that are being monitored. If you've just installed things, make sure you read the documentation on starting Nagios.
Some other things you should check in order to resolve this error include:
Check the Nagios log file for messages relating to startup or status data errors.
Always verify configuration options using the -v command-line option before starting or restarting Nagios!
Make sure you read the documentation on installing, configuring and running Nagios thoroughly before continuing. If all else fails, try sending a message to one of the mailing lists. More information can be found at http://www.nagios.org.
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: CentOS errors
Was this verified?The most common cause of this error message (especially for new users), is the fact that Nagios is not actually running
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: CentOS errors
Hmm, can you run the following:
service nagios stop
killall -9 nagios
service nagios start
Do you still receive the error? If so please run and show the output of:
ll -la /usr/local/nagios/sbin/
service nagios stop
killall -9 nagios
service nagios start
Do you still receive the error? If so please run and show the output of:
ll -la /usr/local/nagios/sbin/
Re: CentOS errors
Here it is the output
still the same error[root@mpnagios ~]# service nagios stop
nagios is stopped
[root@mpnagios ~]# killall -9 nagios
nagios: no process killed
[root@mpnagios ~]# service nagios start
nagios is stopped
Nagios Core 4.0.1
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 10-15-2013
License: GPL
Website: http://www.nagios.org
Reading configuration data...
Read main config file okay...
Read object config files okay...
Running pre-flight check on configuration data...
Checking objects...
Checked 12 services.
Warning: Host 'Router001' has no default contacts or contactgroups defined!
Checked 3 hosts.
Checked 3 host groups.
Checked 0 service groups.
Checked 1 contacts.
Checked 1 contact groups.
Checked 25 commands.
Checked 5 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 3 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 5 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...
Total Warnings: 1
Total Errors: 0
Things look okay - No serious problems were detected during the pre-flight check
Object precache file created:
/usr/local/nagios/var/objects.precache
[root@mpnagios ~]# ll -la /usr/local/nagios/sbin/
total 4024
drwxrwxr-x. 2 nagios nagios 4096 Oct 22 18:58 .
drwxr-xr-x. 8 root root 4096 Oct 22 18:59 ..
-rwxrwxr-x. 1 nagios nagios 288008 Oct 22 18:58 avail.cgi
-rwxrwxr-x. 1 nagios nagios 285064 Oct 22 18:58 cmd.cgi
-rwxrwxr-x. 1 nagios nagios 255176 Oct 22 18:58 config.cgi
-rwxrwxr-x. 1 nagios nagios 300264 Oct 22 18:58 extinfo.cgi
-rwxrwxr-x. 1 nagios nagios 255432 Oct 22 18:58 histogram.cgi
-rwxrwxr-x. 1 nagios nagios 230632 Oct 22 18:58 history.cgi
-rwxrwxr-x. 1 nagios nagios 230600 Oct 22 18:58 notifications.cgi
-rwxrwxr-x. 1 nagios nagios 226472 Oct 22 18:58 outages.cgi
-rwxrwxr-x. 1 nagios nagios 226760 Oct 22 18:58 showlog.cgi
-rwxrwxr-x. 1 nagios nagios 296200 Oct 22 18:58 status.cgi
-rwxrwxr-x. 1 nagios nagios 248712 Oct 22 18:58 statusmap.cgi
-rwxrwxr-x. 1 nagios nagios 242952 Oct 22 18:58 statuswml.cgi
-rwxrwxr-x. 1 nagios nagios 230664 Oct 22 18:58 statuswrl.cgi
-rwxrwxr-x. 1 nagios nagios 251144 Oct 22 18:58 summary.cgi
-rwxrwxr-x. 1 nagios nagios 242952 Oct 22 18:58 tac.cgi
-rwxrwxr-x. 1 nagios nagios 259528 Oct 22 18:58 trends.cgi
[root@mpnagios ~]#
Re: CentOS errors
Which error is the same? It looks like nagios restarted successfully in your last post.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.