Hi!
After upgrading from Ubuntu 18.04 LTS to 20.04 LTS hestiacp does not start.
[email protected]:/var/log# systemctl status hestia.service
● hestia.service - LSB: starts the hestia control panel
Loaded: loaded (/etc/init.d/hestia; generated)
Active: failed (Result: exit-code) since Sun 2021-06-27 05:15:36 -03; 10s ago
Docs: man:systemd-sysv-generator(8)
Process: 69217 ExecStart=/etc/init.d/hestia start (code=exited, status=127)
Tasks: 2 (limit: 4617)
Memory: 3.9M
CGroup: /system.slice/hestia.service
├─797 nginx: master process /usr/local/hestia/nginx/sbin/hestia-nginx
└─798 nginx: worker process
Jun 27 05:15:36 domain.example systemd[1]: hestia.service: Found left-over process 798 (hestia-nginx) in control group while starting unit. Ignoring.
Jun 27 05:15:36 domain.example systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 27 05:15:36 systemd[1]: Starting LSB: starts the hestia control panel…
Jun 27 05:15:36 domain.example hestia[69217]: * Starting hestia-nginx hestia-nginx
Jun 27 05:15:36 domain.example hestia[69217]: …done.
Jun 27 05:15:36 domain.example hestia[69217]: * Starting hestia-php hestia-php
Jun 27 05:15:36 domain.example hestia[69222]: /usr/local/hestia/php/sbin/hestia-php: error while loading shared libraries: libonig.so.4: cannot open shared object file: No such file or directory
Jun 27 05:15:36 domain.example systemd[1]: hestia.service: Control process exited, code=exited, status=127/n/a
Jun 27 05:15:36 domain.example systemd[1]: hestia.service: Failed with result ‘exit-code’.
Jun 27 05:15:36 domain.example systemd[1]: Failed to start LSB: starts the hestia control panel.
Please help me!.
