• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

plesk sql (mysql) always hangs :( help!

P

phyto

Guest
plesk sql (mysql) always hangs once or twice a day or two. and can't be restarted. i have to reboot to have it back. but after a few hours or a day, it hangs again. i don't see any other relevant info in event viewer except the following.

is there any other people having same problem? could someone point me to the right direction?

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 2004-11-13
Time: 14:48:28
User: N/A
Computer: SM11
Description:
The Plesk SQL Server service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
 
and following is what i found from the error log:

041114 15:02:07 InnoDB: Started
MySql: ready for connections.
Version: '4.0.20a-nt' socket: '' port: 3306
041114 22:51:00 InnoDB: Operating system error number 1450 in a file operation.
InnoDB: See http://www.innodb.com/ibman.php for installation help.
InnoDB: See section 13.2 at http://www.innodb.com/ibman.php
InnoDB: about operating system error numbers.
InnoDB: File name .\ibdata1
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
041114 22:52:01 InnoDB: Operating system error number 1450 in a file operation.
InnoDB: See http://www.innodb.com/ibman.php for installation help.
InnoDB: See section 13.2 at http://www.innodb.com/ibman.php
InnoDB: about operating system error numbers.
InnoDB: File name .\ibdata1
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
041114 22:53:01 InnoDB: Operating system error number 1450 in a file operation.
InnoDB: See http://www.innodb.com/ibman.php for installation help.
InnoDB: See section 13.2 at http://www.innodb.com/ibman.php
InnoDB: about operating system error numbers.
InnoDB: File name .\ibdata1
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
041114 22:57:05 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 25665779
InnoDB: Doing recovery: scanned up to log sequence number 0 25670705
041114 22:57:06 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
041114 22:57:07 InnoDB: Flushing modified pages from the buffer pool...
041114 22:57:07 InnoDB: Started
MySql: ready for connections.
Version: '4.0.20a-nt' socket: '' port: 3306
 
System error code 1450 means "Insufficient system resources exist to complete the requested service."
Please, check disk space on your server.
 
nope...:(

2x200gb raid1 hard disks
160gb remaining free
:(

this really bugs me everyday!

thanks for your help.
 
Back
Top