Page 2 of 5

Re: Sorry Dave, I can't let you do that error

Posted: Mon Mar 14, 2011 3:37 pm
by lamin
what do you mean terminal window. I onnect via putty run date command i AM GETTING THE same dtae and time. How about data not populating in the table I mentioned before.

Re: Sorry Dave, I can't let you do that error

Posted: Mon Mar 14, 2011 3:42 pm
by mguthrie
Try restarting both msql and postgresql

service mysqld restart
service postgresql restart

Re: Sorry Dave, I can't let you do that error

Posted: Tue Mar 15, 2011 9:48 am
by lamin
It seems like nagios is not storing data in nagios_servicechecks table because it is the only table empty. Please verify that and let me know because after following all your instructions and directions i am still get no data in that table. In addition, that silly message Dave is still there.

Thanks

Re: Sorry Dave, I can't let you do that error

Posted: Tue Mar 15, 2011 10:22 am
by rdedon
To get back to the "time change" that was done. How did you synchronize it via putty? I would suggest something of this nature if you haven't already:

Managing Nagios Time

The correct time on a server is critical, especially for Nagios. Synchronized time with other servers is important to
coordinate tasks and discover problems. One easy way to perform this task is to install ntp (Network Time Protocol)
and then manually have the system check time once a day in order to manage time.

yum install ­y ntp

Manually update your time. Here you can see the system is off by 12 seconds so it will be corrected gradually with
each check.

 ntpdate pool.ntp.org
11 Mar 12:09:55 ntpdate[24725]: step time server 192.168.*.* offset 10900.806712 sec
12 sec

Create a cron entry so that each day your system is brought up to date.
crontab ­e

45 23 * * * /usr/sbin/ntpdate pool.ntp.org

Re: Sorry Dave, I can't let you do that error

Posted: Tue Mar 15, 2011 10:44 am
by lamin
I am getting this error after the upgrade.

Re: Sorry Dave, I can't let you do that error

Posted: Tue Mar 15, 2011 2:23 pm
by mguthrie
Lets focus on a single issue at a time. Lets check the PHP timezone settings in your /etc/php.ini file. It's possible the UTC offset is incorrect for PHP.
http://support.nagios.com/wiki/index.ph ... e.22_Error


Try running the following scripts as well to make sure your backend is functioning properly.
/usr/local/nagiosxi/scripts/repairmysql.sh nagios *
/usr/local/nagiosxi/tools/fix_postgres_sequences.sh

Re: Sorry Dave, I can't let you do that error

Posted: Tue Mar 15, 2011 3:08 pm
by lamin
I have changed the date.timezone since last week.

Re: Sorry Dave, I can't let you do that error

Posted: Tue Mar 15, 2011 3:34 pm
by rdedon
It looks like the servers were busy, please try again for that to be sure. It should look like this:
ntp.jpg
This is also a VM.

Re: Sorry Dave, I can't let you do that error

Posted: Wed Mar 16, 2011 7:59 am
by lamin
I havr tried again but no luck

Re: Sorry Dave, I can't let you do that error

Posted: Wed Mar 16, 2011 9:24 am
by mguthrie
Does your company have a firewall or proxy setup that might be preventing the use of yum? It would appear it's not making contact with the outside world.

Once yum is working, you can run the following commands.

Try:

Code: Select all

yum install ntp
Once installed, run

Code: Select all

ntpdate time.nist.gov