Command not processed in a timely manner
-
hotdealdave
- Posts: 8
- Joined: Fri Sep 07, 2012 10:36 am
Command not processed in a timely manner
Our server is currently "stuck" with some services down, and will not respond to any commands from the GUI. It states that "the command was not processed in a timely manner..." I will probably just restart the server for now, but what is the proper way to try to resolve issues similar to that in the screenshot, from the command line?
You do not have the required permissions to view the files attached to this post.
-
hotdealdave
- Posts: 8
- Joined: Fri Sep 07, 2012 10:36 am
Re: Command not processed in a timely manner
I should also mention that I enabled DNX this morning, and it seems to be working. The load on the slave server does seem significantly increased, and the load on the master decreased somewhat. But as seen above, the master is no longer responding to commands from the GUI. The last thing I did was add two checks of shares on one of our hosts.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Command not processed in a timely manner
The red items you show makes me believe some of the crond processes aren't running.
Can you run the following to try a restart of crond
If that is running fine, we should be able to see the processes running with the following
If you see several processes running lets run the following to see if we can spot any errors
Can you run the following to try a restart of crond
Code: Select all
service crond restartCode: Select all
ps -ef|grep /cron/Code: Select all
tail -f /usr/local/nagiosxi/var/cmdsubsys.log
-
hotdealdave
- Posts: 8
- Joined: Fri Sep 07, 2012 10:36 am
Re: Command not processed in a timely manner
Thank you. I did just restart the server and that resolved it, but I will bookmark this response and try these commands next time we have a similar issue, which seems to be once or twice a week.
Re: Command not processed in a timely manner
Also, make sure the crond is added to the chkconfig for the proper run levels:
Let us know if you have any more questions.
Code: Select all
chkconfig --list | grep crondBe sure to check out our Knowledgebase for helpful articles and solutions!