We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Problem with update
Problem with update
Hi,
I have installed vestacp on ubuntu 16.
Fail to update with cron.
When trying to update from ssh I get it.
Can somebody help me. Thank you.
I have installed vestacp on ubuntu 16.
Fail to update with cron.
When trying to update from ssh I get it.
Code: Select all
root@server:~# sudo /usr/local/vesta/bin/v-update-sys-vesta-all
/usr/local/vesta/bin/v-update-sys-vesta: line 38: yum: command not found
Error: vesta update failed
/usr/local/vesta/bin/v-update-sys-vesta: line 38: yum: command not found
Error: vesta-nginx update failed
/usr/local/vesta/bin/v-update-sys-vesta: line 38: yum: command not found
Error: vesta-php update failed
/usr/local/vesta/bin/v-update-sys-vesta: line 38: yum: command not found
Error: vesta-ioncube update failed
/usr/local/vesta/bin/v-update-sys-vesta: line 38: yum: command not found
Error: vesta-softaculous update failed
Code: Select all
root@server:~# v-list-sys-vesta-updates
/usr/local/vesta/bin/v-list-sys-vesta-updates: line 72: rpm: command not found
date: invalid date '@'
date: invalid date '@'
/usr/local/vesta/bin/v-list-sys-vesta-updates: line 93: rpm: command not found
date: invalid date '@'
date: invalid date '@'
/usr/local/vesta/bin/v-list-sys-vesta-updates: line 111: rpm: command not found
date: invalid date '@'
date: invalid date '@'
PKG VER REL ARCH UPDT DATE
--- --- --- ---- ---- ----
vesta 0.9.8 no
vesta-php 0.9.8 no
vesta-nginx 0.9.8 no
Re: Problem with update
Hello,
I have exactly the same issue. The fact is, by habits I ran apt-get upgrade once. Since I have an issue with the update of php7 :
So I'm pretty sure that's the issue which break the autoupdate of vestacp. So I have several questions :
- What is the best practice when running vesta cp, running update with /usr/local/vesta/bin/v-update-sys-vesta-all or can we use apt-get ?
- Does vestacp modify config files from packages (like apache php mysql etc) and we should always let vestacp deal with update ?
- How can I solve my issue ? As I don't want to override the configuration of php in case it's actually vestacp which deal with it.
It would have be nice to have caution about that somewhere.
Thanks
I have exactly the same issue. The fact is, by habits I ran apt-get upgrade once. Since I have an issue with the update of php7 :
Code: Select all
dpkg: error processing package php-cli (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
php7.0-cli
libapache2-mod-php7.0
libapache2-mod-php
php7.0-fpm
php7.0-cgi
php7.0
php
php-cgi
php-cli
E: Sub-process /usr/bin/dpkg returned an error code (1)
- What is the best practice when running vesta cp, running update with /usr/local/vesta/bin/v-update-sys-vesta-all or can we use apt-get ?
- Does vestacp modify config files from packages (like apache php mysql etc) and we should always let vestacp deal with update ?
- How can I solve my issue ? As I don't want to override the configuration of php in case it's actually vestacp which deal with it.
It would have be nice to have caution about that somewhere.
Thanks
Re: Problem with update
run
apt-get update && apt-get upgrade -y
apt-get update && apt-get upgrade -y
Re: Problem with update
Hi,
Thans for your answer. So it did install new updates (shame I didn't think about updating repos).
But I'm still getting the same error :
But then I can try to fix this issue from apt-get side ? It won't impact vestacp config ? Like what if I reconfigure the packages ?
Thans for your answer. So it did install new updates (shame I didn't think about updating repos).
But I'm still getting the same error :
Code: Select all
Errors were encountered while processing:
php7.0-cli
php7.0-fpm
php7.0-cgi
libapache2-mod-php7.0
php7.0
libapache2-mod-php
php
php-cgi
php-cli
E: Sub-process /usr/bin/dpkg returned an error code (1)