• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Suse Linux 10.2 server is "frozzen" !

J

j Zim

Guest
I'm running Linux Suse 10.2 SLES with Plesk 8.6 on a Dell server.

The problem occured twice in one week:

Suddenly, the server seems to be totally frozzen. The different services (web, email, ftp) are not available anymore. I also cannot get the login screen on the console!

At the time the server stopped to work, I can always find the same entry in the /var/log/messages file:

Apr 14 11:48:30 linux-1 pop3d: Connection, ip=[83.68.211.148]
Apr 14 11:48:30 linux-1 pop3d: IMAP connect from @ [83.68.211.148]DEBUG: Connection, ip=[83.68.211.148]
Apr 14 11:48:30 linux-1 pop3d: IMAP connect from @ [83.68.211.148]Unable to connect to Plesk Database: Too many connections
Apr 14 11:48:30 linux-1 pop3d: smtp_lock_mysql: Unable to connect to the mysql database, smtp-lock will not workINFO: LOGIN, [email protected], ip=[83.68.211.148]

The only "choice" I have is to reset the box hoping that nothing in the databases get corrupted.

Is there a known problem on that OS?
Is it caused by an attack?
Where can I find more information about the problem (file /var/log/mysqld.log is almost empty 2-3 lines only)?
Error message is "Too many connections", how can I increase the amount of accepted connections? Is it a good idea?

Thank you in advance for your help.
Regards,
JZ
 
Hi

Not a problem with the BOX rather you need to tweak your mysql. go to your MY.cnf and increase timeout values and connections.

what you actually need to do is check which site is causing the bottle neck and freezing mysql.. try the mysqladmin proc and it will list you the DB's running and the process then suspend that user.. You can only keep increasing resources :) but nip the problem in the bud. Its probally bad code on a site which is not closing connections or do a netstat on the mysql port of 3306 see which IP is hitting it the most can be a hack attemp to :)
 
Actually, I think/hope I localized the problem. Problem on the Plesk box is caused by a Mysql server down and then everything is going bad.
It seems that the Joomla component/module Eventlist is causing the crash of Mysql. Does someone already know problem with that stuff?
Rgd.
 
Back
Top