Ubuntu installation failure about hestiacp

[ScIT-Raphael]

Hi @howarddavis
I'm happy that it works now, I've added already a second commit to do a better handling with the fpm conditions: be69edc

Also for the note you've sent me, I adjusted the value to 10 as requested by mariadb with the following commit: 7c5708a

Because all issues are fixed now, I will close this issue. Please feel free to reopen it or create a new one, if you find any additional issue or also if you've a feature request.

[ScIT-Raphael]

Hi, thanks for your answer. I just checked the installer and fixed a bug with the latest commit: 8ce248c

Would you like to check it again and let me know, if all works?

[howarddavis]

Bravo!

Only one warning in the output, but everything appeared to install properly. The control panel is up and running.

...
Upgrade System using apt-get...|
Install third party repository keys... 
Install HestiaCP and all required packages, the process will take around 10-15 minutes...-
2019-02-22 15:00:26 0 [Warning] option 'table_open_cache': unsigned value 4 adjusted to 10
Upgrade phpMyAdmin to v4.8.5...

Congratulations, you have just successfully installed Hestia Control Panel
...

[KamuiX]

Tried today to install hestiacp on Ubuntu 18.04 the above problem poped up again.

Updating currently installed packages, please wait...|
Now installing Hestia Control Panel and all required dependencies.
NOTE: This process may take 10 to 15 minutes to complete, please wait... /
() Configuring system settings...
() Configuring Hestia Control Panel...
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-ubuntu.sh: line 1069: /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 NGINX...
cp: cannot stat '/usr/local/hestia/install/deb/nginx/nginx.conf': No such file or directory
cp: cannot stat '/usr/local/hestia/install/deb/nginx/status.conf': No such file or directory
cp: cannot stat '/usr/local/hestia/install/deb/nginx/phpmyadmin.inc': No such file or directory
cp: cannot stat '/usr/local/hestia/install/deb/nginx/phppgadmin.inc': No such file or directory
cp: cannot stat '/usr/local/hestia/install/deb/logrotate/nginx': No such file or directory
sed: can't read /etc/nginx/nginx.conf: No such file or directory
sed: can't read /usr/local/hestia/nginx/conf/nginx.conf: No such file or directory
Failed to start nginx.service: Unit nginx.service not found.
Error: nginx start failed

rssh error also showed up in the beggining but I manually installed it before copy paste here.

[ScIT-Raphael]

please add a new issue and also inform about all steps you did.

[HueyGeek]

Hi !

I also got this error with Ubuntu 16.04.

The bug is because setpriv is declared as part of the packages to install (end of line #43), only that this command is not a package by itself, but is part of util-linux.

I corrected by changing the declaration to util-linux, instead of setpriv.

[ScIT-Raphael]

Please open a new issue and follow the issue template to provide all needed informations. Setpriv was set for 1.1.0 which is currently not released, probably you use the wrong installer.

[ScIT-Raphael]

And probaly its a good idea to switch to ubuntu 18.04 :)

[HueyGeek]

No, I really did it on purpose, to be able to enjoy the latest features, and for some reason, the VPS provider does not have ubuntu 18.04 available

Thanks for the suggestion.