httpd stopping

[Troy McClure]

Last week I had the httpd service stop twice. I'm not sure what has caused it, and haven't found anything in the logs yet, but I have a question. Doesn't asl use psmon to restart stopped services? If so, should httpd be restarted when it is stopped? I see it in the psmon config file. It was down for at least 1 hour once until I manually restarted it. I am on CentOS 5.

[scott]

It should, but we're still improving its detection capabilities. Its possible that it wasn't monitoring it

[benji]

Had same issue,

Apache kept on stpoing every 10 hours more or less...

I had to tur on Plesk watchdog to put it back on as son as it goes down.

With the recent update i have the following problem, like 10 mails per minute are being sent to my account with the following text:

Code: Select all

Subject: [psmon/s1.mydomain.net] Failed to spawn 'pop3d-ssl' with '/sbin/service pop3d-ssl restart'

Command executed: /sbin/service pop3d-ssl restart
Exit value: 1
Signal number: 0
Dumped core?: 0

pop3d-ssl: unrecognized service

I tried to disable psmon on /etc/asl/config to stop this... but i'm still receiving those messages.

And, its NOT true that pop3d-ssl has a problem, its just working perfect... ¿?

[scott]

Take a look at /etc/psmon.conf, if you see anything referencing that service just delete it.

[benji]

I've commented with #, how do I restart psmon so it read changes on config file?
changes done:

Code: Select all

#<Process pop3d-ssl>
#  spawncmd /sbin/service pop3d-ssl restart
#  pidfile /var/run/pop3d-ssl.pid
#</Process>
#<Process imapd-ssl>
#  spawncmd /sbin/service imapd-ssl restart
#  pidfile /var/run/imapd-ssl.pid
#</Process>
#<Process imapd>
#  spawncmd /sbin/service imapd restart
#  pidfile /var/run/imapd.pid
#</Process>

Actually it sends 3 diferent mails: one for imapd, one for imapd-ssl, other for pop3-ssl.

[benji]

I received 11.000 messages this weekend...

Any help on this? Psmon is going crazy!.

[scott]

just kill it (killall psmon), there is a cron job to check if its running. No need to restart it

[benji]

That did work!

Thanks!.

[outrage]

I have had problems since the latest yum update a few days ago.
I'm running Plesk 8.3 on Centos 4.3.

The first I notice is a customer will complain of error 500 when viewing their sites. This seems to be happening once a day but no particular time.

After logging into Plesk, service manager shows Apache is running but a simple restart will bring the sites back up.

I don't see anything in the error logs that may help and the server was up for 237 days before the update with no problems at all.

Any ideas?

Edit:
Update
I have just found there is a Plesk update that I need to install.


I found I couldn't use the standard Plesk updater and after clicking on the update it was saying something about my License key. I found this:
http://kb.swsoft.com/en/3543

I've installed the new udater and will get back if this original problem continues.

[outrage]

I installed the further 8.3 Plesk updates as stated above but the problem is persisting.
I didn't think it was the Plesk update because I had been running that for a week or so with no problems.
It only started since the last yum update.

[outrage]

Well I think I've found the problem quite by accident after reading other threads on this great site:

http://atomicrocketturtle.com/forum/vie ... highlight=

It seems this may also be related:

http://atomicrocketturtle.com/forum/vie ... highlight=

Thanks