HestiaCP 1.6.10 causes server to become inaccessible?

1

Hi there,

I just updated HestiaCP from 1.6.9 to 1.6.10 with sudo apt update and sudo apt upgrade on Ubuntu 22.04. The update process worked without any errors but after rebooting, the server became completely inaccessible…
The port monitoring of my VPS provider only shows that IMAP4 port is not working.
All other ports are fine. I can’t do anything because I can’t reach my server through SSH either…
I had to restore a backup from earlier today but I would like to understand what went wrong before trying to update/upgrade again.

Thanks in advance.

2

Our update only patched an security issue. Have no idea what went wrong then…

3

Yes… it’s strange. I’ll do another manual update/upgrade tonight.

4

Just reporting back: I tried again, successfully. It will stay a mystery what caused the crash earlier today…

5

On Debian 10 the same, admin panel not working after update
after new install too

6

Check /var/log/hestia/ and systemctl status hestia

7 
systemctl status hestia
● hestia.service - LSB: starts the hestia control panel
   Loaded: loaded (/etc/init.d/hestia; generated)
   Active: active (running) since Mon 2022-10-10 23:35:15 UTC; 1min 25s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 3222 ExecStart=/etc/init.d/hestia start (code=exited, status=0/SUCCESS)
    Tasks: 3 (limit: 2318)
   Memory: 22.8M
   CGroup: /system.slice/hestia.service
           ├─3226 nginx: master process /usr/local/hestia/nginx/sbin/hestia-nginx
           ├─3228 nginx: worker process
           └─3229 php-fpm: master process (/usr/local/hestia/php/etc/php-fpm.conf)

Oct 10 23:35:15 vps.ovh.ca hestia[3217]: Stopping hestia-php: hestia-php.
Oct 10 23:35:15 vps.ovh.ca systemd[1]: hestia.service: Succeeded.
Oct 10 23:35:15 vps.ovh.ca systemd[1]: Stopped LSB: starts the hestia control panel.
Oct 10 23:35:15 vps.ovh.ca systemd[1]: hestia.service: Found left-over process 817 (hestia-php) in control group while starting unit. Ignoring.
Oct 10 23:35:15 vps.ovh.ca systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 10 23:35:15 vps.ovh.ca systemd[1]: Starting LSB: starts the hestia control panel...
Oct 10 23:35:15 vps.ovh.ca hestia[3222]: Starting hestia-nginx: hestia-nginx.
Oct 10 23:35:15 vps.ovh.ca hestia[3222]: Starting hestia-php: hestia-php.
Oct 10 23:35:15 vps.ovh.ca systemd[1]: Started LSB: starts the hestia control panel.

in error.log:

2022-10-10 23:33:57 v-list-web-domain  'admin' '.vps.ovh.ca' 'plain' [Error 3]
2022-10-10 23:33:58 v-list-web-domain  'admin' '.vps.ovh.ca' 'plain' [Error 3]
2022-10-10 23:33:58 v-add-web-domain  'admin' '.vps.ovh.ca' [Error 2]
2022-10-10 23:34:53 v-list-dns-records  'admin' '.vps.ovh.ca' [Error 3]
2022-10-11 02:14:03 v-update-sys-hestia  'hestia' [Error 19]
2022-10-11 02:14:05 v-update-sys-hestia  'hestia-nginx' [Error 19]
2022-10-11 02:14:07 v-update-sys-hestia  'hestia-php' [Error 19]
2022-10-11 07:58:10 v-start-service  [Error 1]
8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.