Plesk Stop all network service by itself

[Alexey_Shpak]

Hello.

We use Plesk 10.4 on Centos 6.

And we decide to upgrade Centos to cloud linux

2.6.32-379.19.1.lve1.2.7.el6.x86_64

CloudLinux Server release 6.3


It worked correctly, but sometimes (2 incedents) plesk stopped all network services (ssh,apache, postfix, etc).

Where I could find problem?

 

[IgorG]

Try to use it for troubleshooting - http://kb.parallels.com/111283

 

[Alexey_Shpak]

/var/log/secure
Feb 21 20:25:43 plesk2 sshd[360305]: Received signal 15; terminating.


/var/log/sw-cp-server/error_log
2013-02-21 20:25:43: (log.c.135) server stopped


/var/log/messages
Feb 21 20:25:43 plesk2 kernel: [1138938.292872] type=1701 audit(1361471143.240:54978): auid=0 uid=502 gid=503
ses=7147 pid=287437 comm="httpd" sig=11
Feb 21 20:25:43 plesk2 xinetd[424817]: Exiting...
Feb 21 20:25:44 plesk2 kernel: Kernel logging (proc) stopped.
Feb 21 20:25:44 plesk2 rsyslogd: [origin software="rsyslogd" swVersion="4.6.2" x-pid="376734" x-info="http://w
ww.rsyslog.com"] exiting on signal 15.


apache:x:502:503:Apache server:/:/sbin/nologin


/usr/local/psa/var/log/maillog
Feb 21 20:25:42 plesk2 postfix/smtpd[288156]: lost connection after RCPT from unknown[********]
Feb 21 20:25:42 plesk2 postfix/smtpd[288156]: disconnect from unknown[*********]
Feb 21 20:25:42 plesk2 /usr/lib64/plesk-9.0/psa-pc-remote[373780]: Message aborted.
Feb 21 20:25:42 plesk2 /usr/lib64/plesk-9.0/psa-pc-remote[373780]: Message aborted.
Feb 21 20:25:43 plesk2 postfix/master[287971]: terminating on signal 15

 

[IgorG]

Is it VPS? Virtuozzo?

 

[Alexey_Shpak]

VmWare ESXi 5.0 (licensed)


But we have another plesk-server with plesk-cloud-linux on physical server. And we haven't this problem.

Is it virtualization problem?

 

[IgorG]

I'm not sure about VmWare ESXi 5.0 but I saw this on Virtuozzo VPSses when kernel sent graceful SIGTERM (Signal 15) to processes in VPS due to lack of resources for all VPSes on hardware node.
In your case it should be seriously investigated directly on your server. I suggest you contact Support Team if you can't find a reason by yourself. Experienced supporters will perform detailed investigation directly on your server.