MySQL service randomly crashes inside Virtuozzo container

Created:

2016-11-16 12:50:52 UTC

Modified:

2017-04-24 11:18:11 UTC

0

Was this article helpful?


Have more questions?

Submit a request

MySQL service randomly crashes inside Virtuozzo container

Applicable to:

  • Plesk 12.0 for Windows
  • Plesk 12.5 for Windows

Symptoms

  1. Mysql process in container randomly crashes with the following error message written to MySQL log:

    InnoDB: Operating system error number 6 in a file operation.
  2. MySQL backups crash with the similar error messages written to MySQL error log:

    140310 9:19:48 InnoDB: Operating system error number 6 in a file operation.
    InnoDB: Some operating system error numbers are described at
    InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
    InnoDB: File operation call: 'flush'.
    InnoDB: Cannot continue operation.
    Result you expected : Backup should have completed
    Specific error and keywords : mysql backup fails
    140310 9:19:48 InnoDB: Operating system error number 6 in a file operation.
    InnoDB: Some operating system error numbers are described at
    InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
    InnoDB: File operation call: 'flush'.
    InnoDB: Cannot continue operation.

Cause

Error 6 is ERROR_INVALID_HANDLE . There is no definite way to reproduce the problem, it is caused by the combination of Antivirus scanner activity, sharing of the volume, filesystem backup running simultaneously with mysqld and indexing services activity.

Resolution

  1. Make sure there is no antivirus/antimalware software installed inside the container.

Antivirus installation inside containers is not supported. For antivirus solutions compatible with Virtuozzo containers for Windows please check this article;

  1. Confirm that the affected container is not under DDoS attack. To check this use Resolution and Additional Information sections of this article;

  2. Check the affected container's disk fragmentation level using instructions from this article and perform the defragmentation is necessary;

  3. Check the System log in the EventViewer of the hardware node for the presence of Events with ID 57: An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): ****

If such events are present, check the virtual disk of the container for NTFS corruption using instructions from this article.

Have more questions? Submit a request
Please sign in to leave a comment.