"Waiting for Database Startup" after 2.0.5 upgrade

This support forum board is for support questions relating to Nagios Log Server, our solution for managing and monitoring critical log data.
Locked
jvestrum
Posts: 46
Joined: Tue Mar 03, 2015 10:45 am

"Waiting for Database Startup" after 2.0.5 upgrade

Post by jvestrum »

I ran the upgrade script for 2.0.5 and after 15 minutes the web interface is still displaying "Waiting for Database Startup", refreshing every 5 seconds. I've restarted httpd. My php.ini already has memory_limit = 512M. The elasticsearch process is running, but doesn't seem to be doing anything. No files have been modified in the data dir since the restart. Looking at the elasticsearch log, after the restart it only logged these three lines:

Code: Select all

[2018-09-14 13:18:22,005][INFO ][node                     ] [a6a1ee31-789f-4927-8680-25814f651b54] version[1.7.6], pid[12315], build[c730b59/2016-11-18T15:21:16Z]
[2018-09-14 13:18:22,006][INFO ][node                     ] [a6a1ee31-789f-4927-8680-25814f651b54] initializing ...
[2018-09-14 13:18:22,130][INFO ][plugins                  ] [a6a1ee31-789f-4927-8680-25814f651b54] loaded [knapsack-1.7.3.0-d0ea246], sites []
Based on past restarts, those lines should immediately be followed by "using [1] data paths, mounts [[/srv ...." but it never happens. The process correctly has -Des.default.path.data=/srv/nagioslogserver/elasticsearch/data, which is where the data is and the permissions look correct.. I'm stumped.
jvestrum
Posts: 46
Joined: Tue Mar 03, 2015 10:45 am

Re: "Waiting for Database Startup" after 2.0.5 upgrade

Post by jvestrum »

Okay nevermind. This system had a hung NFS mount that was completely unrelated to the Elasticsearch install, but Elasticsearch was trying to do a df (or something similar) and hanging on that. As soon as I unmounted it, things got rolling again.
User avatar
cdienger
Support Tech
Posts: 5045
Joined: Tue Feb 07, 2017 11:26 am

Re: "Waiting for Database Startup" after 2.0.5 upgrade

Post by cdienger »

Glad to hear it got sorted out!
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Locked