Nagios crashed. Re-building again.
-
prateekagr1988
- Posts: 62
- Joined: Fri Sep 26, 2014 7:21 pm
Re: Nagios crashed. Re-building again.
It's 2012R1.2, same as the earlier one.
We did not do a fresh install. We just restored the files.
We are unable to open CCM, and it says page not found.
We did not do a fresh install. We just restored the files.
We are unable to open CCM, and it says page not found.
-
prateekagr1988
- Posts: 62
- Joined: Fri Sep 26, 2014 7:21 pm
Re: Nagios crashed. Re-building again.
I get the below error when running the reconfigure script:
# ./reconfigure_nagios.sh
URL: http://localhost/nagiosql/index.php
CMDLINE
/usr/bin/wget --save-cookies nagiosql.cookies --keep-session-cookies http://localhost/nagiosql/index.php --no-check-certificate --post-data 'Submit=Login&tfUsername=nagiosxi&tfPassword=************************' -O nagiosql.login--2015-03-18 22:39:00-- http://localhost/nagiosql/index.php
Resolving localhost... ::1, 127.0.0.1
Connecting to localhost|::1|:80... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2015-03-18 22:39:00 ERROR 500: Internal Server Error.
NAGIOSQL LOGIN FAILED!
Please suggest.
# ./reconfigure_nagios.sh
URL: http://localhost/nagiosql/index.php
CMDLINE
/usr/bin/wget --save-cookies nagiosql.cookies --keep-session-cookies http://localhost/nagiosql/index.php --no-check-certificate --post-data 'Submit=Login&tfUsername=nagiosxi&tfPassword=************************' -O nagiosql.login--2015-03-18 22:39:00-- http://localhost/nagiosql/index.php
Resolving localhost... ::1, 127.0.0.1
Connecting to localhost|::1|:80... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2015-03-18 22:39:00 ERROR 500: Internal Server Error.
NAGIOSQL LOGIN FAILED!
Please suggest.
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: Nagios crashed. Re-building again.
Try to access CCM and then run the following commands:
Send us these files:
/tmp/mysqld_log.txt
/tmp/httpd_log.txt
Code: Select all
tail /var/log/mysqld.log -n 100 > /tmp/mysqld_log.txt
tail /var/log/httpd/error_log -n 100 > /tmp/httpd_log.txt/tmp/mysqld_log.txt
/tmp/httpd_log.txt
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
-
prateekagr1988
- Posts: 62
- Joined: Fri Sep 26, 2014 7:21 pm
Re: Nagios crashed. Re-building again.
httpd:
[Wed Mar 18 22:44:54 2015] [error] [client 10.65.13.89] PHP Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /usr/local/nagiosxi/html/includes/utilsl.inc.php on line 381, referer: http://sr1pmonpe10.cioio.net/nagiosxi/i ... ustypes=28
[Wed Mar 18 22:44:54 2015] [error] [client 10.65.13.89] PHP Warning: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /usr/local/nagiosxi/html/includes/components/xicore/ajaxhelpers-servicestatus.inc.php on line 577, referer: http://sr1pmonpe10.cioio.net/nagiosxi/i ... ustypes=28
[Wed Mar 18 22:44:54 2015] [error] [client 10.65.13.89] PHP Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /usr/local/nagiosxi/html/includes/utilsl.inc.php on line 381, referer: http://sr1pmonpe10.cioio.net/nagiosxi/i ... ustypes=28
mysqld:
150318 16:59:32 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150318 17:00:37 mysqld_safe Starting mysqld daemon with databases from /u01/appl/mysql
150318 17:00:39 [Note] Plugin 'InnoDB' is disabled.
150318 17:00:39 [Note] Event Scheduler: Loaded 0 events
150318 17:00:39 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
150318 21:59:53 [Note] /usr/libexec/mysqld: Normal shutdown
150318 21:59:53 [Note] Event Scheduler: Purging the queue. 0 events
150318 21:59:55 [Note] /usr/libexec/mysqld: Shutdown complete
150318 21:59:55 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150318 21:59:56 mysqld_safe Starting mysqld daemon with databases from /u01/appl/mysql
150318 21:59:56 [Note] Plugin 'InnoDB' is disabled.
150318 21:59:56 [Note] Event Scheduler: Loaded 0 events
150318 21:59:56 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
150318 22:13:34 [Note] /usr/libexec/mysqld: Normal shutdown
150318 22:13:34 [Note] Event Scheduler: Purging the queue. 0 events
150318 22:13:36 [Note] /usr/libexec/mysqld: Shutdown complete
150318 22:13:36 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150318 22:13:37 mysqld_safe Starting mysqld daemon with databases from /u01/appl/mysql
150318 22:13:37 [Note] Plugin 'InnoDB' is disabled.
150318 22:13:37 [Note] Event Scheduler: Loaded 0 events
150318 22:13:37 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
[Wed Mar 18 22:44:54 2015] [error] [client 10.65.13.89] PHP Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /usr/local/nagiosxi/html/includes/utilsl.inc.php on line 381, referer: http://sr1pmonpe10.cioio.net/nagiosxi/i ... ustypes=28
[Wed Mar 18 22:44:54 2015] [error] [client 10.65.13.89] PHP Warning: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /usr/local/nagiosxi/html/includes/components/xicore/ajaxhelpers-servicestatus.inc.php on line 577, referer: http://sr1pmonpe10.cioio.net/nagiosxi/i ... ustypes=28
[Wed Mar 18 22:44:54 2015] [error] [client 10.65.13.89] PHP Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /usr/local/nagiosxi/html/includes/utilsl.inc.php on line 381, referer: http://sr1pmonpe10.cioio.net/nagiosxi/i ... ustypes=28
mysqld:
150318 16:59:32 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150318 17:00:37 mysqld_safe Starting mysqld daemon with databases from /u01/appl/mysql
150318 17:00:39 [Note] Plugin 'InnoDB' is disabled.
150318 17:00:39 [Note] Event Scheduler: Loaded 0 events
150318 17:00:39 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
150318 21:59:53 [Note] /usr/libexec/mysqld: Normal shutdown
150318 21:59:53 [Note] Event Scheduler: Purging the queue. 0 events
150318 21:59:55 [Note] /usr/libexec/mysqld: Shutdown complete
150318 21:59:55 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150318 21:59:56 mysqld_safe Starting mysqld daemon with databases from /u01/appl/mysql
150318 21:59:56 [Note] Plugin 'InnoDB' is disabled.
150318 21:59:56 [Note] Event Scheduler: Loaded 0 events
150318 21:59:56 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
150318 22:13:34 [Note] /usr/libexec/mysqld: Normal shutdown
150318 22:13:34 [Note] Event Scheduler: Purging the queue. 0 events
150318 22:13:36 [Note] /usr/libexec/mysqld: Shutdown complete
150318 22:13:36 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150318 22:13:37 mysqld_safe Starting mysqld daemon with databases from /u01/appl/mysql
150318 22:13:37 [Note] Plugin 'InnoDB' is disabled.
150318 22:13:37 [Note] Event Scheduler: Loaded 0 events
150318 22:13:37 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: Nagios crashed. Re-building again.
Lets start off by fixing the timezone issues.
http://assets.nagios.com/downloads/nagi ... m_Time.pdf
http://assets.nagios.com/downloads/nagi ... m_Time.pdf
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
-
prateekagr1988
- Posts: 62
- Joined: Fri Sep 26, 2014 7:21 pm
Re: Nagios crashed. Re-building again.
I already updated /etc/php.ini and restarted apache, but that didn't help.
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: Nagios crashed. Re-building again.
So have the timezone errors stopped appearing in /var/log/httpd/error_log?
I would also re-run the nagios XI ./upgrade of the current version to see if that helps.
I would also re-run the nagios XI ./upgrade of the current version to see if that helps.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
-
prateekagr1988
- Posts: 62
- Joined: Fri Sep 26, 2014 7:21 pm
Re: Nagios crashed. Re-building again.
I still get timezone errors in /var/log/httpd/error_log.
However, I noticed that the error says "We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead", where I am using Europe/Amsterdam.
Upgrade is a risky option, as it might impact the compatibility of our existing personalized configurations.
Would you know why I get the below?
# ./reconfigure_nagios.sh
URL: http://localhost/nagiosql/index.php
CMDLINE
/usr/bin/wget --save-cookies nagiosql.cookies --keep-session-cookies http://localhost/nagiosql/index.php --no-check-certificate --post-data 'Submit=Login&tfUsername=nagiosxi&tfPassword=************************' -O nagiosql.login--2015-03-18 22:39:00-- http://localhost/nagiosql/index.php
Resolving localhost... ::1, 127.0.0.1
Connecting to localhost|::1|:80... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2015-03-18 22:39:00 ERROR 500: Internal Server Error.
NAGIOSQL LOGIN FAILED!
However, I noticed that the error says "We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead", where I am using Europe/Amsterdam.
Upgrade is a risky option, as it might impact the compatibility of our existing personalized configurations.
Would you know why I get the below?
# ./reconfigure_nagios.sh
URL: http://localhost/nagiosql/index.php
CMDLINE
/usr/bin/wget --save-cookies nagiosql.cookies --keep-session-cookies http://localhost/nagiosql/index.php --no-check-certificate --post-data 'Submit=Login&tfUsername=nagiosxi&tfPassword=************************' -O nagiosql.login--2015-03-18 22:39:00-- http://localhost/nagiosql/index.php
Resolving localhost... ::1, 127.0.0.1
Connecting to localhost|::1|:80... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2015-03-18 22:39:00 ERROR 500: Internal Server Error.
NAGIOSQL LOGIN FAILED!
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: Nagios crashed. Re-building again.
Can you please post your /etc/php.iniprateekagr1988 wrote:I still get timezone errors in /var/log/httpd/error_log.
However, I noticed that the error says "We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead", where I am using Europe/Amsterdam.
Also, what is the output of:
Code: Select all
ls -al /etc/localtimeDo you use a proxy server?prateekagr1988 wrote:Would you know why I get the below?
# ./reconfigure_nagios.sh
URL: http://localhost/nagiosql/index.php
CMDLINE
/usr/bin/wget --save-cookies nagiosql.cookies --keep-session-cookies http://localhost/nagiosql/index.php --no-check-certificate --post-data 'Submit=Login&tfUsername=nagiosxi&tfPassword=************************' -O nagiosql.login--2015-03-18 22:39:00-- http://localhost/nagiosql/index.php
Resolving localhost... ::1, 127.0.0.1
Connecting to localhost|::1|:80... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2015-03-18 22:39:00 ERROR 500: Internal Server Error.
NAGIOSQL LOGIN FAILED!
Another thing to look at is proxy related, specifically needing a no_proxy entry in /etc/wgetrc. This article shows you the required steps:
http://support.nagios.com/wiki/index.ph ... th_Proxies
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: Nagios crashed. Re-building again.
If it's a VM then take a snapshot before trying.prateekagr1988 wrote:Upgrade is a risky option, as it might impact the compatibility of our existing personalized configurations.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.