┌──(root⌁neo)-[~] └─# apt upgrade -y Reading package lists… Done
*Building dependency tree * Reading state information… Done Calculating upgrade… Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up hestia-nginx (1.19.8) … /usr/local/hestia/bin/v-change-sys-port: line 19: /func/main.sh: No such file or directory /usr/local/hestia/bin/v-change-sys-port: line 20: /conf/hestia.conf: No such file or directory /usr/local/hestia/bin/v-change-sys-port: line 45: check_args: command not found Port is already used by Hestia, please set anotherone! /usr/local/hestia/bin/v-change-sys-port: line 35: log_event: command not found dpkg: error processing package hestia-nginx (–configure):
installed hestia-nginx package post-installation script subprocess returned error exit status 127* Errors were encountered while processing:
hestia-nginx* E: Sub-process /usr/bin/dpkg returned an error code (1)
*
┌──(root⌁neo)-[~] └─# dpkg --configure -a 100 ⨯ Setting up hestia-nginx (1.19.8) … /usr/local/hestia/bin/v-change-sys-port: line 19: /func/main.sh: No such file or directory /usr/local/hestia/bin/v-change-sys-port: line 20: /conf/hestia.conf: No such file or directory /usr/local/hestia/bin/v-change-sys-port: line 45: check_args: command not found Port is already used by Hestia, please set anotherone! /usr/local/hestia/bin/v-change-sys-port: line 35: log_event: command not found dpkg: error processing package hestia-nginx (–configure):
installed hestia-nginx package post-installation script subprocess returned error exit status 127* Errors were encountered while processing:
hestia-nginx*
P.S. on this server I am using only apache (without nginx reverse proxy).
hey magnus, this seems a bit weird especially the part where it complains about the blocked port. maybe check, if hestia-nginx could not be stopped/killed properly and is still running? I’d remove hestia-nginx via apt remove and then check and kill the hestia-nginx.
also check via netstat if something else occupied the port 8083 … if you find that free please try to run apt install hestia-nginx again.
PS: after you enncountered the error, what’s the output of journalctl -xe ?
After unistalling hestia-nginx there is still the process hestia.service displayed but with following status:
┌──(root⌁sam)-[/usr/local/hestia/func]
*└─# systemctl status hestia.service * ● hestia.service
Loaded: not-found (Reason: Unit hestia.service not found.)*
Active: active (running) since Tue 2021-03-16 21:59:58 CET; 5min ago*
CGroup: /system.slice/hestia.service*
├─1092 nginx: master process /usr/local/hestia/nginx/sbin/hestia-nginx*
├─1098 nginx: worker process*
└─1154 php-fpm: master process (/usr/local/hestia/php/etc/php-fpm.conf)*
Mar 16 21:59:58 myhostname systemd[1]: Starting LSB: starts the hestia control panel… Mar 16 21:59:58 myhostname hestia[1028]: Starting hestia-nginx: hestia-nginxnginx: [warn] “ssl_stapling” ignored, issuer certificate not found for certificate “/usr/local/hestia/ssl/certificate.crt” Mar 16 21:59:58 myhostname hestia[1028]: . Mar 16 21:59:58 myhostname hestia[1028]: Starting hestia-php: hestia-php. Mar 16 21:59:58 myhostname systemd[1]: Started LSB: starts the hestia control panel.
Therefore I cannot kill it. I removed it from the list with “systemctl disable hestia” instead
netstat showed no occupancy of port 8083
Re-Installing hestia-nginx results in the same error as before
journalctl -xe shows no errors:
Mar 16 22:12:34 myhostname systemd[1]: Reloading. Mar 16 22:12:34 myhostname systemd[1]: /lib/systemd/system/spamassassin.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/spamd.pid → /run/spamd.pid; please update the unit file ac Mar 16 22:12:34 myhostname systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please up Mar 16 22:12:34 myhostname systemd[1]: /lib/systemd/system/dovecot.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/dovecot/master.pid → /run/dovecot/master.pid; please update the Mar 16 22:12:34 myhostname systemd[1]: Reloading. Mar 16 22:12:34 myhostname systemd[1]: /lib/systemd/system/spamassassin.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/spamd.pid → /run/spamd.pid; please update the unit file ac Mar 16 22:12:34 myhostname systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please up Mar 16 22:12:34 myhostname systemd[1]: /lib/systemd/system/dovecot.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/dovecot/master.pid → /run/dovecot/master.pid; please update the Mar 16 22:12:34 myhostname systemd[1]: Starting LSB: starts the hestia control panel… – Subject: A start job for unit hestia.service has begun execution – Defined-By: systemd – Support: Debian -- Support
*-- * – A start job for unit hestia.service has begun execution.
*-- * – The job identifier is 580. Mar 16 22:12:34 myhostname hestia[6848]: Starting hestia-nginx: hestia-nginxnginx: [warn] “ssl_stapling” ignored, issuer certificate not found for certificate “/usr/local/hestia/ssl/certificate.crt” Mar 16 22:12:34 myhostname hestia[6848]: . Mar 16 22:12:34 myhostname hestia[6848]: Starting hestia-php: hestia-php. Mar 16 22:12:34 myhostname systemd[1]: Started LSB: starts the hestia control panel. – Subject: A start job for unit hestia.service has finished successfully – Defined-By: systemd – Support: Debian -- Support
*-- * – A start job for unit hestia.service has finished successfully.
*-- * – The job identifier is 580.
I am focussing now on the lines: /usr/local/hestia/bin/v-change-sys-port: line 19: /func/main.sh: No such file or directory /usr/local/hestia/bin/v-change-sys-port: line 20: /conf/hestia.conf: No such file or directory /usr/local/hestia/bin/v-change-sys-port: line 45: check_args: command not found
Even other v-commands lead to not finding the specified files.
I did not change any ownership or permissions.
I could execute ./main.sh for example in its directory.
So I am wondering if the $HESTIA variable is mis-set somewhere?!
I could solve the first error by deleting those files:
-rw-r–r-- 1 root root 1346 Mar 15 13:49 hestia-nginx.copyright -rw-r–r-- 1 root root 1025 Mar 16 19:31 hestia-nginx.list -rw-r–r-- 1 root root 1491 Mar 16 19:31 hestia-nginx.md5sums -rwxr-xr-x 1 root root 62 Mar 15 13:49 hestia-nginx.portrm -rwxr-xr-x 1 root root 594 Mar 15 13:49 hestia-nginx.postinst
but still the v-commands cant find the linked .confs and .shs
