Hestia-php update failed

Hello.

Recieved a message:

Error: hestia-php update failed
Error: hestia-php update failed
Error: hestia-php update failed

Try to run command in console

$ sudo /usr/local/hestia/bin/v-update-sys-hestia hestia-php
Error: hestia-php update failed

Another command

$ sudo apt install hestia-php
Reading package lists... Done
Building dependency tree       
Reading state information... Done
hestia-php is already the newest version (8.1.11).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up hestia-php (8.1.11) ...
dpkg: error processing package hestia-php (--configure):
 installed hestia-php package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 hestia-php
E: Sub-process /usr/bin/dpkg returned an error code (1)

Hestia version: v1.6.8
OS version: Ubuntu 20.04.5 LTS

What happens when remove hestia-php and then reinstall it?

it’s on production. It’s scary removing php :slight_smile: May by there is another solution?

It is not “php” used for the website in production but for the panel only.

What do you see when you run:
systemctl restart hestia

$ sudo systemctl restart hestia
Job for hestia.service failed because the control process exited with error code.
See "systemctl status hestia.service" and "journalctl -xe" for details.

$ sudo systemctl  status hestia.service
ߨestia.service - LSB: starts the hestia control panel
     Loaded: loaded (/etc/init.d/hestia; generated)
     Active: failed (Result: exit-code) since Fri 2022-10-07 21:55:03 EEST; 10s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 2906738 ExecStart=/etc/init.d/hestia start (code=exited, status=70)
      Tasks: 3 (limit: 19660)
     Memory: 23.6M
     CGroup: /system.slice/hestia.service
             㠱132470 php-fpm: master process (/usr/local/hestia/php/etc/php-fpm.conf)
             㠲679125 nginx: master process /usr/local/hestia/nginx/sbin/hestia-nginx
             㠲679126 nginx: worker process

Oct 07 21:55:03  systemd[1]: Starting LSB: starts the hestia control panel...
Oct 07 21:55:03  hestia[2906738]:  * Starting hestia-nginx hestia-nginx
Oct 07 21:55:03  hestia[2906738]:    ...done.
Oct 07 21:55:03  hestia[2906738]:  * Starting hestia-php hestia-php
Oct 07 21:55:03  hestia[2906743]: [07-Oct-2022 21:55:03] ERROR: Another FPM instance seems to already listen on /var/run/hestia-php.sock
Oct 07 21:55:03  hestia[2906743]: [07-Oct-2022 21:55:03] ERROR: FPM initialization failed
Oct 07 21:55:03  systemd[1]: hestia.service: Control process exited, code=exited, status=70/SOFTWARE
Oct 07 21:55:03 systemd[1]: hestia.service: Failed with result 'exit-code'.
Oct 07 21:55:03 systemd[1]: Failed to start LSB: starts the hestia control panel.

have you upgraded OS ? I get this error after upgrading from ubuntu 20.04 to 22.04 jummy.

rm /var/run/hestia-php.sock

And then restart again

Same for you also delete libonig5 and reinstall hestia-php agin it should now also downgrade to libonig4

reinstalling delete all users and configurations. and how to downgrade libonig4?

apt remove libonig5
apt install libonig4
And apt reinstall hestia-php

I get this error

apt install libonig4
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package libonig4 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libonig4' has no installation candidate

apt reinstall hestia-php -f

Should reinstall it

I do this but I get error again.

[email protected]:~# sudo systemctl restart hestia

Warning: The unit file, source configuration file or drop-ins of hestia.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Job for hestia.service failed because the control process exited with error code.
See "systemctl status hestia.service" and "journalctl -xeu hestia.service" for details.
[email protected]:~# systemctl status hestia.service
Warning: The unit file, source configuration file or drop-ins of hestia.service changed on disk. Run 'systemctl daemon-reload' to reload units.
× hestia.service - LSB: starts the hestia control panel
     Loaded: loaded (/etc/init.d/hestia; generated)
     Active: failed (Result: exit-code) since Mon 2022-10-10 12:24:13 +03; 11s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 11424 ExecStart=/etc/init.d/hestia start (code=exited, status=203/EXEC)
      Tasks: 2 (limit: 4506)
     Memory: 9.6M
        CPU: 657us
     CGroup: /system.slice/hestia.service
             ├─809 "nginx: master process /usr/local/hestia/nginx/sbin/hestia-nginx"
             └─810 "nginx: worker process" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ""

Oct 10 12:24:13 serve.domain.com systemd[1]: hestia.service: Found left-over process 810 (hestia-nginx) in control group while starting unit. Ignoring.
Oct 10 12:24:13 serve.domain.com systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 10 12:24:13 serve.domain.com systemd[11424]: hestia.service: Failed to locate executable /etc/init.d/hestia: No such file or directory
Oct 10 12:24:13 serve.domain.com systemd[11424]: hestia.service: Failed at step EXEC spawning /etc/init.d/hestia: No such file or directory
Oct 10 12:24:13 serve.domain.com systemd[1]: Starting LSB: starts the hestia control panel...
Oct 10 12:24:13 serve.domain.com systemd[1]: hestia.service: Control process exited, code=exited, status=203/EXEC
Oct 10 12:24:13 serve.domain.com systemd[1]: hestia.service: Failed with result 'exit-code'.
Oct 10 12:24:13 serve.domain.com systemd[1]: hestia.service: Unit process 809 (hestia-nginx) remains running after unit stopped.
Oct 10 12:24:13 serve.domain.com systemd[1]: hestia.service: Unit process 810 (hestia-nginx) remains running after unit stopped.
Oct 10 12:24:13 serve.domain.com systemd[1]: Failed to start LSB: starts the hestia control panel.

apt reinstall -f hestia-nginx

1 Like

Yes We have succeeded :smiley: , Yesterday I consumed my all time to solve this problem. I rollback to 20.04 when I failed and today I tried again and I solved this thanks to you ( king )

Does not work for me

$ sudo apt reinstall -f hestia-nginx
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
Need to get 0 B/6216 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 48052 files and directories currently installed.)
Preparing to unpack .../hestia-nginx_1.23.1_amd64.deb ...
Unpacking hestia-nginx (1.23.1) over (1.23.1) ...
Setting up hestia-php (8.1.11) ...
dpkg: error processing package hestia-php (--configure):
 installed hestia-php package post-installation script subprocess returned error exit status 1
Setting up hestia-nginx (1.23.1) ...
Job for hestia.service failed because the control process exited with error code.
See "systemctl status hestia.service" and "journalctl -xe" for details.
invoke-rc.d: initscript hestia, action "start" failed.
 hestia.service - LSB: starts the hestia control panel
    Loaded: loaded (/etc/init.d/hestia; generated)
    Active: failed (Result: exit-code) since Tue 2022-10-11 22:02:07 EEST; 10ms ago
      Docs: man:systemd-sysv-generator(8)
   Process: 511415 ExecStart=/etc/init.d/hestia start (code=exited, status=1/FAILURE)
     Tasks: 3 (limit: 19660)
    Memory: 9.7M
    CGroup: /system.slice/hestia.service
            㠱132470 php-fpm: master process (/usr/local/hestia/php/etc/php-fpm.conf)
           㠲679125 nginx: master process /usr/local/hestia/nginx/sbin/hestia-nginx
          㠲679126 nginx: worker process

Oct 11 22:02:04 alg.com.ua hestia[511415]:  * Starting hestia-nginx hestia-nginx
Oct 11 22:02:04 alg.com.ua hestia[511418]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use)
Oct 11 22:02:05 alg.com.ua hestia[511418]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use)
Oct 11 22:02:05 alg.com.ua hestia[511418]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use)
Oct 11 22:02:06 alg.com.ua hestia[511418]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use)
Oct 11 22:02:06 alg.com.ua hestia[511418]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use)
Oct 11 22:02:07 alg.com.ua hestia[511418]: nginx: [emerg] still could not bind()
Oct 11 22:02:07 alg.com.ua systemd[1]: hestia.service: Control process exited, code=exited, status=1/FAILURE
Oct 11 22:02:07 alg.com.ua systemd[1]: hestia.service: Failed with result 'exit-code'.
Oct 11 22:02:07 alg.com.ua systemd[1]: Failed to start LSB: starts the hestia control panel.
dpkg: error processing package hestia-nginx (--configure):
 installed hestia-nginx package post-installation script subprocess returned error exit status 1
Processing triggers for systemd (245.4-4ubuntu3.17) ...
Errors were encountered while processing:
 hestia-php
 hestia-nginx
E: Sub-process /usr/bin/dpkg returned an error code (1)

bind() to 0.0.0.0:8083

Some service is allready bound to 8083

Stop hestia service or check what service is using port 8083

I rebooted server

~$ netstat -a |grep 8083
tcp        0      0 0.0.0.0:8083            0.0.0.0:*               LISTEN     
~$ sudo systemctl stop hestia
~$ netstat -a |grep 8083
~$ sudo apt reinstall -f hestia-ngnix -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package hestia-ngnix

apt install hestia-nginx

~$ sudo systemctl stop hestia
~$ sudo apt install hestia-nginx
Reading package lists... Done
Building dependency tree       
Reading state information... Done
hestia-nginx is already the newest version (1.23.1).
0 upgraded, 0 newly installed, 0 to remove and 189 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up hestia-php (8.1.11) ...
dpkg: error processing package hestia-php (--configure):
 installed hestia-php package post-installation script subprocess returned error exit status 1
Setting up hestia-nginx (1.23.1) ...
Job for hestia.service failed because the control process exited with error code.
See "systemctl status hestia.service" and "journalctl -xe" for details.
invoke-rc.d: initscript hestia, action "start" failed.
ߨestia.service - LSB: starts the hestia control panel
     Loaded: loaded (/etc/init.d/hestia; generated)
     Active: failed (Result: exit-code) since Wed 2022-10-12 00:14:43 EEST; 13ms ago
       Docs: man:systemd-sysv-generator(8)
    Process: 46943 ExecStart=/etc/init.d/hestia start (code=exited, status=1/FAILURE)
      Tasks: 3 (limit: 19660)
     Memory: 12.5M
     CGroup: /system.slice/hestia.service
             㠲4264 nginx: master process /usr/local/hestia/nginx/sbin/hestia-nginx
             㠲4265 nginx: worker process
             㠲4267 php-fpm: master process (/usr/local/hestia/php/etc/php-fpm.conf)

Oct 12 00:14:40 example.com hestia[46943]:  * Starting hestia-nginx hestia-nginx
Oct 12 00:14:40 example.com hestia[46946]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use)
Oct 12 00:14:41 example.com hestia[46946]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use)
Oct 12 00:14:41 example.com hestia[46946]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use)
Oct 12 00:14:42 example.com hestia[46946]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use)
Oct 12 00:14:42 example.com hestia[46946]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use)
Oct 12 00:14:43 example.com hestia[46946]: nginx: [emerg] still could not bind()
Oct 12 00:14:43 example.com systemd[1]: hestia.service: Control process exited, code=exited, status=1/FAILURE
Oct 12 00:14:43 example.com systemd[1]: hestia.service: Failed with result 'exit-code'.
Oct 12 00:14:43 example.com systemd[1]: Failed to start LSB: starts the hestia control panel.
Sep 21 21:53:40 example.com sudo[799903]: pam_unix(sudo:auth): conversation failed
Sep 21 21:53:40 example.com sudo[799903]: pam_unix(sudo:auth): auth could not identify password for [admin]
Sep 21 21:53:42 example.com sudo[799973]: pam_unix(sudo:auth): conversation failed