FAILED: Temporary failure INFO Runner: RESULT: 8/10 passed

Support
1

Problem Description - After recent updates I’m receiving the following error messages.

Any Error Messages

Started Sympl service monitor.
  INFO Runner: mysqld: Checking service is enabled
  INFO Runner: mysqld: Checking process
  INFO Runner: mysqld: Attempting to start mysqld
  INFO Runner: mysqld: Trying to ping mysql
  INFO Runner: mysqld: Testing connection with a ping
  INFO Runner: mysqld:  /usr/bin/mysqladmin: connect to server at 'localhost' failed
  INFO Runner: mysqld: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)'
  INFO Runner: mysqld: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
  INFO Runner: mysqld: Connection test failed.
  INFO Runner: mysqld: Attempting to stop mysqld
  INFO Runner: mysqld: Attempting to start mysqld
  WARN Runner: mysqld: RETRYING (following Temporary failure)
  INFO Runner: mysqld: Checking service is enabled
  INFO Runner: mysqld: Checking process
  INFO Runner: mysqld: Attempting to start mysqld
  INFO Runner: mysqld: Trying to ping mysql
  INFO Runner: mysqld: Testing connection with a ping
  INFO Runner: mysqld:  /usr/bin/mysqladmin: connect to server at 'localhost' failed
  INFO Runner: mysqld: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)'
  INFO Runner: mysqld: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
  INFO Runner: mysqld: Connection test failed.
  INFO Runner: mysqld: Attempting to stop mysqld
  INFO Runner: mysqld: Attempting to start mysqld
  WARN Runner: mysqld: FAILED: Temporary failure
  INFO Runner: pure-ftpd: Checking service is enabled
  INFO Runner: pure-ftpd: Checking process
  INFO Runner: pure-ftpd: Attempting to start pure-ftpd
  INFO Runner: pure-ftpd: Testing connection to localhost:ftp
  INFO Runner: pure-ftpd: Connection test temporarily failed: Connection refused - connect(2) for "localhost" port ftp  
  INFO Runner: pure-ftpd: Attempting to stop pure-ftpd
  INFO Runner: pure-ftpd: Attempting to start pure-ftpd
  WARN Runner: pure-ftpd: RETRYING (following Temporary failure)
  INFO Runner: pure-ftpd: Checking service is enabled
  INFO Runner: pure-ftpd: Checking process
  INFO Runner: pure-ftpd: Attempting to start pure-ftpd
  INFO Runner: pure-ftpd: Testing connection to localhost:ftp
  INFO Runner: pure-ftpd: Connection test temporarily failed: Connection refused - connect(2) for "localhost" port ftp
  INFO Runner: pure-ftpd: Attempting to stop pure-ftpd
  INFO Runner: pure-ftpd: Attempting to start pure-ftpd
  WARN Runner: pure-ftpd: FAILED: Temporary failure
  INFO Runner: RESULT: 8/10 passed.
sympl-monit.service: Main process exited, code=exited, status=1/FAILURE
sympl-monit.service: Failed with result 'exit-code'.
sympl-monit.service: Triggering OnFailure= dependencies.

Environment

  • Sympl Version [9.0/10.0]:
  • Sympl Testing Version? [Yes/No] - No
  • Debian Version [Buster/Stretch]: - Buster
  • Hardware Type? [Dedicated/Virtual/Pi]
  • Hosted On? [name of hosting co] - Bytemark

Anyone else seeing this?
Rgds Pete

2

(Formatting fixed in top post)

It’s reporting that both MySQL/MariaDB and PureFTP are down for some reason, and is unable to start.

Check how much free RAM there is with free, as you may be running out and triggering the OOM killer, which is then killing things and leaving you without enough memory to start them again.

Also, please confirm hardware and what version of Sympl is being used, and if it was upgraded from Symbiosis, or a previous version of Sympl.

3

The Bytemark VM is running a couple of WP and Avada sites which are quite resource heavy. A reboot seems to have temporarily fixed the issue which was consuming a lot of memory in view of the fact that the VM is a low spec entry level machine. So I think you’re entirely correct about the lack of RAM triggering the problem.

Machine is an entry level Bytemark VM
Running Debian Buster version 10.9
Sympl was installed directly to a Bytemark VM - so not upgraded from Symbiosis.

Let’s just assume this one’s resolved for now. I’ll upgrade the vm should the issue manifest again.