Page 1 of 1

Ubuntu 18.04

Posted: Tue May 01, 2018 2:20 pm
by QuadMcFly
Any timeline on when support for 18.04 will be added? Looking to use Vesta on a new server setup, but it's not in the repository yet for 18.04.

Re: Ubuntu 18.04

Posted: Sat Jun 16, 2018 8:56 am
by sandy
its a few hours job if vesta team consider it

Re: Ubuntu 18.04

Posted: Wed Jul 18, 2018 5:12 pm
by Spheerys
I have to setup a new server and I want to use the last Ubuntu 18.04 LTS version on it.

So I'm also interested by the official VestaCP support for this (not so) new Ubuntu version !!!

Re: Ubuntu 18.04

Posted: Wed Jul 18, 2018 7:08 pm
by imperio
Try to install VestaCP on Ubuntu 18.04 and let me know about results

Re: Ubuntu 18.04

Posted: Wed Jul 18, 2018 7:41 pm
by Spheerys
Some errors are still there during installation :

Code: Select all

Installation will take about 15 minutes ...

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.
--2018-07-18 21:40:37--  http://nginx.org/keys/nginx_signing.key
Resolving nginx.org (nginx.org)... 2001:1af8:4060:a004:21::e3, 2606:7100:1:69::3f, 206.251.255.63, ...
Connecting to nginx.org (nginx.org)|2001:1af8:4060:a004:21::e3|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1561 (1.5K) [text/plain]
Saving to: '/tmp/nginx_signing.key'

/tmp/nginx_signing.key                 100%[============================================================================>]   1.52K  --.-KB/s    in 0s      

2018-07-18 21:40:37 (83.2 MB/s) - '/tmp/nginx_signing.key' saved [1561/1561]

E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation
--2018-07-18 21:40:37--  http://c.vestacp.com/deb_signing.key
Resolving c.vestacp.com (c.vestacp.com)... 104.236.66.100
Connecting to c.vestacp.com (c.vestacp.com)|104.236.66.100|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1719 (1.7K) [text/plain]
Saving to: 'deb_signing.key'

deb_signing.key                        100%[============================================================================>]   1.68K  --.-KB/s    in 0s      

2018-07-18 21:40:37 (32.3 MB/s) - 'deb_signing.key' saved [1719/1719]

E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation
Ign:1 https://mirrors.gandi.net/gandi/ubuntu bionic InRelease
Get:2 https://mirrors.gandi.net/ubuntu bionic-security InRelease [83.2 kB]
Get:3 https://mirrors.gandi.net/ubuntu bionic-updates InRelease [88.7 kB]
Hit:4 https://mirrors.gandi.net/ubuntu bionic InRelease
Hit:5 https://mirrors.gandi.net/gandi/ubuntu bionic Release                        
Get:6 http://nginx.org/packages/mainline/ubuntu bionic InRelease [2109 B]          
Get:7 https://mirrors.gandi.net/ubuntu bionic-security/main amd64 Packages [116 kB]
Get:8 http://apt.vestacp.com/bionic bionic InRelease [2187 B]                      
Get:9 https://mirrors.gandi.net/ubuntu bionic-security/main Translation-en [46.0 kB]
Get:10 https://mirrors.gandi.net/ubuntu bionic-security/multiverse amd64 Packages [1168 B] 
Get:11 https://mirrors.gandi.net/ubuntu bionic-security/universe amd64 Packages [37.1 kB]
Get:12 https://mirrors.gandi.net/ubuntu bionic-security/universe Translation-en [21.6 kB]   
Get:13 https://mirrors.gandi.net/ubuntu bionic-updates/main amd64 Packages [204 kB]
Get:14 https://mirrors.gandi.net/ubuntu bionic-updates/main Translation-en [81.3 kB]
Get:15 https://mirrors.gandi.net/ubuntu bionic-updates/multiverse amd64 Packages [3544 B]   
Get:16 https://mirrors.gandi.net/ubuntu bionic-updates/multiverse Translation-en [2060 B]
Get:17 https://mirrors.gandi.net/ubuntu bionic-updates/universe amd64 Packages [129 kB]
Get:18 https://mirrors.gandi.net/ubuntu bionic-updates/universe Translation-en [57.6 kB]
Err:6 http://nginx.org/packages/mainline/ubuntu bionic InRelease                                  
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ABF5BD827BD9BF62
Err:8 http://apt.vestacp.com/bionic bionic InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 42C5B2130A1F7714
Reading package lists... Done
W: GPG error: http://nginx.org/packages/mainline/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ABF5BD827BD9BF62
E: The repository 'http://nginx.org/packages/mainline/ubuntu bionic InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://apt.vestacp.com/bionic bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 42C5B2130A1F7714
E: The repository 'http://apt.vestacp.com/bionic bionic InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package vesta
E: Unable to locate package vesta-ioncube
E: Unable to locate package vesta-nginx
E: Unable to locate package vesta-php
Error: apt-get install failed
I could unlock the situation with :

Code: Select all

apt update && apt install gnupg

Code: Select all

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys ABF5BD827BD9BF62

Code: Select all

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 42C5B2130A1F7714
After that, I laucnhed again VestaCp installer and after a while I get this new error :

Code: Select all

...
update-alternatives: using /usr/bin/display-im6.q16 to provide /usr/bin/display (display) in auto mode
update-alternatives: using /usr/bin/display-im6.q16 to provide /usr/bin/display-im6 (display-im6) in auto mode
update-alternatives: using /usr/bin/montage-im6.q16 to provide /usr/bin/montage (montage) in auto mode
update-alternatives: using /usr/bin/montage-im6.q16 to provide /usr/bin/montage-im6 (montage-im6) in auto mode
update-alternatives: using /usr/bin/mogrify-im6.q16 to provide /usr/bin/mogrify (mogrify) in auto mode
update-alternatives: using /usr/bin/mogrify-im6.q16 to provide /usr/bin/mogrify-im6 (mogrify-im6) in auto mode
Setting up libpangocairo-1.0-0:amd64 (1.40.14-1) ...
Setting up librrd8:amd64 (1.7.0-1build1) ...
Setting up imagemagick (8:6.9.7.4+dfsg-16ubuntu6.3) ...
Setting up rrdtool (1.7.0-1build1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for dovecot-core (1:2.2.33.2-1ubuntu4.1) ...
invoke-rc.d: policy-rc.d denied execution of restart.
Errors were encountered while processing:
 vsftpd
E: Sub-process /usr/bin/dpkg returned an error code (1)
Error: apt-get install failed

Re: Ubuntu 18.04

Posted: Wed Jul 18, 2018 7:56 pm
by imperio
On our test servers this problem is not reproducible. Can you provide clean server without Vesta installation. We will check this.

Re: Ubuntu 18.04

Posted: Wed Jul 18, 2018 8:09 pm
by Spheerys
Can you give me your ssh key by private message and I will return you the ssh access of a fresh new test server ?

Re: Ubuntu 18.04

Posted: Thu Jul 19, 2018 6:12 am
by alexcy
I also didn't have these problems when installing Ubuntu 18.04. The issues I face are:

dbconfig-common: writing config to /etc/dbconfig-common/roundcube.conf
Creating config file /etc/dbconfig-common/roundcube.conf with new version
Creating config file /etc/roundcube/debian-db.php with new version
checking privileges on database roundcube for roundcube@localhost: user creation needed.
granting access to database roundcube for roundcube@localhost: failed.
error encountered creating user:
mysql said: ERROR 1044 (42000) at line 1: Access denied for user 'debian-sys-maint'@'localhost' to database 'roundcube'
dbconfig-common: roundcube configure: noninteractive fail.
dbconfig-common: roundcube configure: ignoring errors from here forwards


Creating config file /etc/phpmyadmin/config-db.php with new version
checking privileges on database phpmyadmin for phpmyadmin@localhost: user creation needed.
granting access to database phpmyadmin for phpmyadmin@localhost: failed.
error encountered creating user:
mysql said: ERROR 1044 (42000) at line 1: Access denied for user 'debian-sys-maint'@'localhost' to database 'phpmyadmin'
dbconfig-common: phpmyadmin configure: noninteractive fail.
dbconfig-common: phpmyadmin configure: ignoring errors from here forwards



Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for dovecot-core (1:2.2.33.2-1ubuntu4.1) ...
Installing MariaDB/MySQL system tables in '/var/lib/mysql' ...
Installation of system tables failed! Examine the logs in
/var/lib/mysql for more information.
The problem could be conflicting information in an external
my.cnf files. You can ignore these by doing:
shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf
You can also try to start the mysqld daemon with:
shell> /usr/sbin/mysqld --skip-grant-tables --general-log &
and use the command line tool /usr/bin/mysql
to connect to the mysql database and look at the grant tables:
shell> /usr/bin/mysql -u root mysql
mysql> show tables;
Try 'mysqld --help' if you have problems with paths. Using
--general-log gives you a log in /var/lib/mysql that may be helpful.


2018-06-29 1:11:21 0 [Note] mysqld (mysqld 10.3.7-MariaDB-1:10.3.7+maria~bionic) starting as process 31393 ...
Setting /usr/sbin/named to complain mode.
Adding user Debian-exim to group mail
Adding user dovecot to group mail
Job for dovecot.socket failed.
See "systemctl status dovecot.socket" and "journalctl -xe" for details.
Adding user clamav to group mail
Adding user clamav to group Debian-exim
Synchronizing state of spamassassin.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable spamassassin
mv: cannot move '/usr/local/vesta/data/ips/' to a subdirectory of itself, '/usr/local/vesta/data/ips/37.187.73.103'
sed: can't read /usr/local/vesta/data/users/*/dns/*.conf: No such file or directory
sed: -e expression #1, char 0: no previous regular expression
sed: -e expression #1, char 0: no previous regular expression


exim: failed to find uid for user name "Debian-exim"


Job for vesta.service failed because the control process exited with error code. failed!
[....] Restarting vesta (via systemctl): vesta.serviceJob for vesta.service failed becaus$
Jun 29 01:06:35 domain.tld vesta[2661]: /etc/init.d/vesta: 31: .: Can't open /etc/profile.d/vesta.sh


Job for dovecot.socket failed.
See "systemctl status dovecot.socket" and "journalctl -xe" for details.