The instance is likely offline, please check and try again

[floki]

Hi,

Sorry for late reply, spent some sick leave anyway, this is what the command subsystem look like when I reset them:

https://drive.google.com/file/d/1wTYKNd ... sp=sharing

Still can't apply configuration. Tested other servers and they got the same message:

Code: Select all

The apply command hasn't started yet. The instance may not be online or is unreachable

[scottwilkerson]

The the Job Status remain in a waiting state like in your image?

[floki]

Yes, that's after I reset the jobs. I don't totally understand why it appears offline even though its applying the configuration to itself. I'm losing hope with this one
I just don't want the next person who will handle the nagios log server to restart logstash every time a configuration change.

[scottwilkerson]

If it is sticking at Waiting, it leads me to believe the cron isn't running

Can you show the output of the following

Code: Select all

service crond status
chage -l nagios
ps -ef|grep php

[floki]

Thanks for the response!

hmmm so here's the result of each command you posted:
https://drive.google.com/file/d/14Slg48 ... sp=sharing

That's from a test server but our licensed servers has also has the same results

[scottwilkerson]

Ok, it looks like the nagios user's password is expired.

Please run the following to set the password to not expire

Code: Select all

chage -m 0 -M 99999 -I -1 -E -1 nagios

[floki]

WOW! Thanks a lot! That syntax solved the problem. Thanks!

[cdienger]

Glad to hear!