HestiaCP on Ubuntu server 20.04 offline for several hours

Community Support
1

Hi,
I have a WordPress site running on a virtual server with Ubuntu 20.04, on HestiaCP (1.4.17) with LEMP stack (MariaDB 10.6, Nginx 1.21, PHP-FPM 7.4).
Yesterday at 23:42 the site went offline until this morning at 10:41… I’ve been checking all system logs but I haven’t found yet which was the root cause…
The only unusual entries so far, are the following ones I found on syslog file:

Oct 30 23:46:48 server systemd[1]: Stopping User Manager for UID 1000...
Oct 30 23:46:48 server systemd[308244]: Stopped target Main User Target.
Oct 30 23:46:48 server systemd[308244]: Stopped target Basic System.
Oct 30 23:46:48 server systemd[308244]: Stopped target Paths.
Oct 30 23:46:48 server systemd[308244]: Stopped target Sockets.
Oct 30 23:46:48 server systemd[308244]: Stopped target Timers.
Oct 30 23:46:48 server systemd[308244]: dbus.socket: Succeeded.
Oct 30 23:46:48 server systemd[308244]: Closed D-Bus User Message Bus Socket.
Oct 30 23:46:48 server systemd[308244]: dirmngr.socket: Succeeded.
Oct 30 23:46:48 server systemd[308244]: Closed GnuPG network certificate management daemon.
Oct 30 23:46:48 server systemd[308244]: gpg-agent-browser.socket: Succeeded.
Oct 30 23:46:48 server systemd[308244]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Oct 30 23:46:48 server systemd[308244]: gpg-agent-extra.socket: Succeeded.
Oct 30 23:46:48 server systemd[308244]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Oct 30 23:46:48 server systemd[308244]: gpg-agent-ssh.socket: Succeeded.
Oct 30 23:46:48 server systemd[308244]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Oct 30 23:46:48 server systemd[308244]: gpg-agent.socket: Succeeded.
Oct 30 23:46:48 server systemd[308244]: Closed GnuPG cryptographic agent and passphrase cache.
Oct 30 23:46:48 server systemd[308244]: pk-debconf-helper.socket: Succeeded.
Oct 30 23:46:48 server systemd[308244]: Closed debconf communication socket.
Oct 30 23:46:48 server systemd[308244]: Reached target Shutdown.
Oct 30 23:46:48 server systemd[308244]: systemd-exit.service: Succeeded.
Oct 30 23:46:48 server systemd[308244]: Finished Exit the Session.
Oct 30 23:46:48 server systemd[308244]: Reached target Exit the Session.
Oct 30 23:46:48 server systemd[1]: [email protected]: Succeeded.
Oct 30 23:46:48 server systemd[1]: Stopped User Manager for UID 1000.
Oct 30 23:46:48 server systemd[1]: Stopping User Runtime Directory /run/user/1000...
Oct 30 23:46:48 server systemd[1]: run-user-1000.mount: Succeeded.
Oct 30 23:46:48 server systemd[1]: [email protected]: Succeeded.
Oct 30 23:46:48 server systemd[1]: Stopped User Runtime Directory /run/user/1000.
Oct 30 23:46:48 server systemd[1]: Removed slice User Slice of UID 1000.

I don’t know how to read this. I’m still investigating looking up on the Internet, but haven’t found anything relevant so far.
Any ideas?

2

Have you made anything that the server came back online? The log messages above arent indicating much.

3

No, the server came back online by itself…

syslog entries:

Oct 31 10:41:30 server systemd[1]: Created slice User Slice of UID 1000.
Oct 31 10:41:30 server systemd[1]: Starting User Runtime Directory /run/user/1000...
Oct 31 10:41:30 server systemd[1]: Finished User Runtime Directory /run/user/1000.
Oct 31 10:41:30 server systemd[1]: Starting User Manager for UID 1000...
Oct 31 10:41:30 server systemd[373563]: Reached target Paths.
Oct 31 10:41:30 server systemd[373563]: Reached target Timers.
Oct 31 10:41:30 server systemd[373563]: Starting D-Bus User Message Bus Socket.
Oct 31 10:41:30 server systemd[373563]: Listening on GnuPG network certificate management daemon.
Oct 31 10:41:30 server systemd[373563]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Oct 31 10:41:30 server systemd[373563]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Oct 31 10:41:30 server systemd[373563]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Oct 31 10:41:30 server systemd[373563]: Listening on GnuPG cryptographic agent and passphrase cache.
Oct 31 10:41:30 server systemd[373563]: Listening on debconf communication socket.
Oct 31 10:41:30 server systemd[373563]: Listening on D-Bus User Message Bus Socket.
Oct 31 10:41:30 server systemd[373563]: Reached target Sockets.
Oct 31 10:41:30 server systemd[373563]: Reached target Basic System.
Oct 31 10:41:30 server systemd[373563]: Reached target Main User Target.
Oct 31 10:41:30 server systemd[373563]: Startup finished in 87ms.
Oct 31 10:41:30 server systemd[1]: Started User Manager for UID 1000.

I suspect that this could be something related to a cloud provider issue (I opened a ticket with their technical support)… let’s see if something comes out from there…

Anyway, this is quite weird…

4

I also would say, that it looks more like a provider sided issue - let them answer first.

1 Like