Error on installation (Debian 10)

Hi,

Been doing dozens of Hestia installations.

For the first time, a bunch of errors are showing up:

cp: cannot stat ‘/usr/local/hestia/install/deb/sudo/admin’: No such file or directory
chmod: cannot access ‘/etc/sudoers.d/admin’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/logrotate/hestia’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/packages’: No such file or directory
sed: can’t read /usr/local/hestia/data/packages/.pkg: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/templates’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/templates/web/unassigned/index.html’: No such file or directory
cp: cannot stat '/usr/local/hestia/install/deb/templates/web/skel/document_errors/
’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/firewall’: No such file or directory
() Generating default self-signed SSL certificate…
hst-install-debian.sh: line 1110: /usr/local/hestia/bin/v-generate-ssl-cert: No such file or directory
(
) Adding SSL certificate to Hestia Control Panel…
sed: -e expression #1, char 3: unexpected ,' sed: -e expression #1, char 1: unknown command: ,’
cp: cannot stat ‘/usr/local/hestia/install/deb/ssl/dhparam.pem’: No such file or directory
(*) Configuring Apache Web Server…
cp: cannot stat ‘/usr/local/hestia/install/deb/apache2/apache2.conf’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/apache2/status.conf’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/logrotate/apache2’: No such file or directory
hst-install-debian.sh: line 1183: /etc/apache2/sites-available/default: No such file or directory
hst-install-debian.sh: line 1184: /etc/apache2/sites-available/default-ssl: No such file or directory
hst-install-debian.sh: line 1186: /etc/apache2/suexec/www-data: No such file or directory

Any clue?

Thanks.

Best regards

Please check the following

Run as root

apt-get update && apt-get dist-upgrade

Before executing the installer

@eris

Already tried… but errors keep showing up …

Here’s the content of setup log file:

Reading package lists…
Building dependency tree…
Reading state information…
Calculating upgrade…
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

and nothing else…

Regards

Currently there where a lot of persons with similar issues and there it solved the problems…

The issue is that It can’t load the packages for Hestia. You are sure using the the “release” install script?

wget https://raw.githubusercontent.com/hestiacp/hestiacp/release/install/hst-install.sh

I rebuilt the VPS and tried this time using the command “bash hst-install.sh” installing the whole package and it worked!!

So the problem is with the command line I was using to install it:

bash hst-install.sh --apache yes --nginx no --phpfpm no --multiphp no --vsftpd no --proftpd no --named no --mysql yes --postgresql no --exim no --dovecot no --clamav no --spamassassin no --iptables yes --fail2ban no --quota no --api no --force no --interactive yes --port 8083 --hostname server.domain.lan --email [email protected] --password passWD123 --lang en

Is anything wrong with it?

Regards

Hi again,

I was wrong with “bash hst-install.sh” command… it didn’t work at the end…

The following error showed up:

(*) Configuring Apache Web Server…
Job for apache2.service failed because the control process exited with error code.
See “systemctl status apache2.service” and “journalctl -xe” for details.
Error: apache2 start failed

Content of “journalctl -xe”:

May 21 23:48:02 server.monitor.lan systemd-tmpfiles[8673]: [/usr/lib/tmpfiles.d/fail2ban-tmpfiles.conf:1] Line referen
May 21 23:48:02 server.monitor.lan systemd-tmpfiles[8673]: [/usr/lib/tmpfiles.d/vsftpd.conf:1] Line references path be
May 21 23:48:02 server.monitor.lan systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
– Subject: Unit succeeded
– Defined-By: systemd
– Support: https://www.debian.org/support

– The unit systemd-tmpfiles-clean.service has successfully entered the ‘dead’ state.
May 21 23:48:02 server.monitor.lan systemd[1]: Started Cleanup of Temporary Directories.
– Subject: A start job for unit systemd-tmpfiles-clean.service has finished successfully
– Defined-By: systemd
– Support: https://www.debian.org/support

– A start job for unit systemd-tmpfiles-clean.service has finished successfully.

Regards

–force no causing the error should be placed on the and …

We are currently working on a replacement generator string

See https://github.com/hestiacp/hestiacp-generator

@eris

You mean “-force no” must be placed at the end of the command line?

Regards

It is -f or --force no… I case of no it can also been left out. Maybe easier… But replied just after your last post so I didn’t read that yet…

Just checked couldn’t find any reason why it should not work. Just send a message to the team maybe they have a better idea…

See https://github.com/hestiacp/hestiacp/issues/824#issuecomment-632500917

1 Like