Hi,
My server has around 15 sites on it, 8gb of memory and only a handful of users at any one time. Yet every time it does backups, it seems to kill MySQL.
I can never restart mysql, I have to go into terminal and stop it dead entirely before it will come back up, as well as kill all backup processes 'pkgacct'.
The backups are not huge, and there is plenty of space on the disk.
This happens more and more often and now it is happening every time backups run.
This is the 'failed' error cPanel sends when I kill mysql:
I have had to disable backups as it seems to be the cause based on the times and the fact they seem to be running whenever this happens.
When MySQL hits this issue, it just locks up and no sites are able to connect to it, sending all of my clients sites down.
There are no other heavy use processes going on, MySQL is at the top using 5% CPU and 3.4gb of memory - nothing the server cannot handle.
Why do the backups keep killing my databases?
When it restarts, almost every database the backups touch have tables which need repairing - not uncommon, but when mysql has been up for only 2 days since it last crashed, I wouldn't expect that.
My clients are very concerned and I need to know why backups are doing this - or why something else in cPanel is causing this.
Datacenter checked hardware and it is all ok.
My server has around 15 sites on it, 8gb of memory and only a handful of users at any one time. Yet every time it does backups, it seems to kill MySQL.
I can never restart mysql, I have to go into terminal and stop it dead entirely before it will come back up, as well as kill all backup processes 'pkgacct'.
The backups are not huge, and there is plenty of space on the disk.
This happens more and more often and now it is happening every time backups run.
This is the 'failed' error cPanel sends when I kill mysql:
Code:
Cpanel::Exception::Timeout/(XID uhdf6d) The system failed to lock the file “/var/run/restartsrv_mysql” after 197 seconds.
at /usr/local/cpanel/Cpanel/Exception/CORE.pm line 336.
Cpanel::Exception::create("Timeout", "The system failed to lock the file \x{e2}\x{80}\x{9c}[_1]\x{e2}\x{80}\x{9d} after [quant,_2"..., ARRAY(0x247b700)) called at /usr/local/cpanel/Cpanel/Exception.pm line 61
Cpanel::Exception::__ANON__(__CPANEL_HIDDEN__, __CPANEL_HIDDEN__..., ARRAY(0x247b700)) called at /usr/local/cpanel/Cpanel/SafeFile.pm line 729
Cpanel::SafeFile::_timeout_exception("/var/run/restartsrv_mysql", 197) called at /usr/local/cpanel/Cpanel/SafeFile.pm line 761
Cpanel::SafeFile::_die_if_file_is_flocked_cuz_already_waited_a_while("/var/run/restartsrv_mysql", 197) called at /usr/local/cpanel/Cpanel/SafeFile.pm line 829
Cpanel::SafeFile::_lock_wait("/var/run/restartsrv_mysql") called at /usr/local/cpanel/Cpanel/SafeFile.pm line 355
Cpanel::SafeFile::_safelock("/var/run/restartsrv_mysql") called at /usr/local/cpanel/Cpanel/SafeFile.pm line 558
Cpanel::SafeFile::_safe_open(undef, ">>", "/var/run/restartsrv_mysql", CODE(0xb8ee48), "safeopen") called at /usr/local/cpanel/Cpanel/SafeFile.pm line 115
Cpanel::SafeFile::safeopen(undef, ">>", "/var/run/restartsrv_mysql") called at /usr/local/cpanel/Cpanel/RestartSrv/Lock.pm line 25
Cpanel::RestartSrv::Lock::new("Cpanel::RestartSrv::Lock", "mysql") called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 183
Cpanel::ServiceManager::Base::lock(Cpanel::ServiceManager::Services::Mysql=HASH(0x2137ae8)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 459
Cpanel::ServiceManager::Base::BUILD(Cpanel::ServiceManager::Services::Mysql=HASH(0x2137ae8), HASH(0xbac398)) called at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/x86_64-linux-64int/Cpanel/Class/Object.pm line 49
Cpanel::Class::Object::BUILDALL(Cpanel::ServiceManager::Services::Mysql=HASH(0x2137ae8), HASH(0xbac398)) called at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/x86_64-linux-64int/Cpanel/Class/Object.pm line 41
Cpanel::Class::Object::new("Cpanel::ServiceManager::Services::Mysql", "service", "mysql") called at /usr/local/cpanel/Cpanel/ServiceManager.pm line 99
Cpanel::ServiceManager::new("Cpanel::ServiceManager", "service", "mysql") called at bin/restartsrv_base.pl line 79
scripts::restartsrv_base::__ANON__() called at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/Try/Tiny.pm line 99
eval {...} called at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/Try/Tiny.pm line 90
Try::Tiny::try(CODE(0xb6f018), Try::Tiny::Catch=REF(0xb43fb0)) called at bin/restartsrv_base.pl line 125
scripts::restartsrv_base::run("--check", "--notconfigured-ok") called at bin/restartsrv_base.pl line 33
The subprocess “/usr/local/cpanel/scripts/restartsrv_mysql” reported error number 255 when it ended.When MySQL hits this issue, it just locks up and no sites are able to connect to it, sending all of my clients sites down.
There are no other heavy use processes going on, MySQL is at the top using 5% CPU and 3.4gb of memory - nothing the server cannot handle.
Why do the backups keep killing my databases?
When it restarts, almost every database the backups touch have tables which need repairing - not uncommon, but when mysql has been up for only 2 days since it last crashed, I wouldn't expect that.
My clients are very concerned and I need to know why backups are doing this - or why something else in cPanel is causing this.
Datacenter checked hardware and it is all ok.
Last edited by a moderator:
