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.
Error v-update-sys-queue disk after restore a backup
Error v-update-sys-queue disk after restore a backup
hi,
i install the last version of vestacp with nginx and php-fpm and there are some troubles.
I have different user with different subdomain and for a week, after a little trouble with nginx/fpm templates, all works ok.
[i'm using a debian 8 and no error during the install, only a little mistake on clamav conf due to a big change that mantainer do in the last version]
Today a webdev make a big error in one of is dev-space and i restored the backup of the day before.
No problem, vesta do that.
But around one hour ago i receive this mail
i check manually and the db exist but from vesta webgui if i go to database it count 3 db on top and count 1 on bottom
and if i try from shell
i restore two times the backup i remember. so it's look like don't rewrite the variable and add a new one db instead replace.
that user has just one dev space for wordpress. just one db. i'm sure about that.
i inspect something more, so i try to do a manual backup [if vesta search 3db i think it will do error during backup]
and so it was. i press Y to move on during the error.
the db are removed but not from inside the db.conf of $user
the same problem in backup.conf
and so on ...
it make an error when update the object value, if i don't mistake.
and i put here a snippet about main.sh
Thanks
i install the last version of vestacp with nginx and php-fpm and there are some troubles.
I have different user with different subdomain and for a week, after a little trouble with nginx/fpm templates, all works ok.
[i'm using a debian 8 and no error during the install, only a little mistake on clamav conf due to a big change that mantainer do in the last version]
Today a webdev make a big error in one of is dev-space and i restored the backup of the day before.
No problem, vesta do that.
But around one hour ago i receive this mail
Code: Select all
/usr/local/vesta/func/main.sh: line 291: 2:DB=alexio_wp1: command not found
/usr/local/vesta/func/main.sh: line 291: 2:DB=alexio_wp1: command not found
/usr/local/vesta/func/main.sh: line 291: 2:DB=alexio_wp1: command not found
and if i try from shell
Code: Select all
# v-list-databases alexio
DATABASE USER HOST TYPE DISK SPND DATE
-------- ---- ---- ---- ---- ---- ----
alexio_wp1 alexio_sql localhost mysql 5 no 2016-07-27
alexio_wp1 alexio_sql localhost mysql 5 no 2016-07-29
alexio_wp1 alexio_sql localhost mysql 4 no 2016-07-29
that user has just one dev space for wordpress. just one db. i'm sure about that.
i inspect something more, so i try to do a manual backup [if vesta search 3db i think it will do error during backup]
and so it was. i press Y to move on during the error.
Code: Select all
~ # v-backup-user alexio
-- SYSTEM --
2016-07-30 04:02:15 alexio.conf
2016-07-30 04:02:15 stats.log
2016-07-30 04:02:15 history.log
2016-07-30 04:02:15 pam
-- WEB --
2016-07-30 04:02:15 wp1.alexio.blablabla.tld
2016-07-30 04:02:48 *** 1 domain ***
-- DNS --
2016-07-30 04:02:48 *** 0 domains ***
-- MAIL --
2016-07-30 04:02:48 *** 0 domains ***
-- DB --
2016-07-30 04:02:48 alexio_wp1 (mysql)
2016-07-30 04:02:49 alexio_wp1 (mysql)
gzip: /backup/tmp.AubOpqpZSk/db/alexio_wp1/alexio_wp1.mysql.sql.gz already exists; do you wish to overwrite (y or n)? y
2016-07-30 04:03:06 alexio_wp1 (mysql)
gzip: /backup/tmp.AubOpqpZSk/db/alexio_wp1/alexio_wp1.mysql.sql.gz already exists; do you wish to overwrite (y or n)? y
2016-07-30 04:03:09 *** 3 databases ***
-- CRON --
2016-07-30 04:03:09 *** 0 jobs ***
-- User Dir --
2016-07-30 04:03:09 adding .bash_history
2016-07-30 04:03:09 adding .bash_logout
2016-07-30 04:03:09 adding .bashrc
2016-07-30 04:03:09 adding .profile
2016-07-30 04:03:09 adding tmp
2016-07-30 04:03:09 adding .wp-cli
2016-07-30 04:03:10 *** 6 directories ***
-- SUMMARY --
2016-07-30 04:03:10 Local: /backup/alexio.2016-07-30.tar
2016-07-30 04:03:10 Size: 90 Mb
2016-07-30 04:03:10 Runtime: 1 minute
-- SYSTEM --
2016-07-30 04:02:15 alexio.conf
2016-07-30 04:02:15 stats.log
2016-07-30 04:02:15 history.log
2016-07-30 04:02:15 pam
-- WEB --
2016-07-30 04:02:15 wp1.alexio.blablabla.tld
2016-07-30 04:02:48 *** 1 domain ***
-- DNS --
2016-07-30 04:02:48 *** 0 domains ***
-- MAIL --
2016-07-30 04:02:48 *** 0 domains ***
-- DB --
2016-07-30 04:02:48 alexio_wp1 (mysql)
2016-07-30 04:02:49 alexio_wp1 (mysql)
2016-07-30 04:03:06 alexio_wp1 (mysql)
2016-07-30 04:03:09 *** 3 databases ***
-- CRON --
2016-07-30 04:03:09 *** 0 jobs ***
-- User Dir --
2016-07-30 04:03:09 adding .bash_history
2016-07-30 04:03:09 adding .bash_logout
2016-07-30 04:03:09 adding .bashrc
2016-07-30 04:03:09 adding .profile
2016-07-30 04:03:09 adding tmp
2016-07-30 04:03:09 adding .wp-cli
2016-07-30 04:03:10 *** 6 directories ***
-- SUMMARY --
2016-07-30 04:03:10 Local: /backup/alexio.2016-07-30.tar
2016-07-30 04:03:10 Size: 90 Mb
2016-07-30 04:03:10 Runtime: 1 minute
Code: Select all
/usr/local/vesta/data/users/alexio # cat db.conf
DB='alexio_wp1' DBUSER='alexio_sql' MD5='*BLABLABLA' HOST='localhost' TYPE='mysql' CHARSET='UTF8' U_DISK='5' SUSPENDED='no' TIME='00:46:30' DATE='2016-07-27'
DB='alexio_wp1' DBUSER='alexio_sql' MD5='*BLABLABLA' HOST='localhost' TYPE='mysql' CHARSET='UTF8' U_DISK='5' SUSPENDED='no' TIME='11:33:06' DATE='2016-07-29'
DB='alexio_wp1' DBUSER='alexio_sql' MD5='*BLABLABLA' HOST='localhost' TYPE='mysql' CHARSET='UTF8' U_DISK='4' SUSPENDED='no' TIME='11:40:01' DATE='2016-07-29'
Code: Select all
/usr/local/vesta/data/users/alexio # cat backup.conf
BACKUP='alexio.2016-07-27.tar' TYPE='local' SIZE='72' WEB='wp1.alexio.blablabla.tld' DNS='' MAIL='' DB='alexio_wp1' CRON='' UDIR='.bash_history,.bash_logout,.bashrc,.profile,tmp,.wp-cli' RUNTIME='1' TIME='05:10:55' DATE='2016-07-27'
BACKUP='alexio.2016-07-28.tar' TYPE='local' SIZE='72' WEB='wp1.alexio.blablabla.tld' DNS='' MAIL='' DB='alexio_wp1' CRON='' UDIR='.bash_history,.bash_logout,.bashrc,.profile,tmp,.wp-cli' RUNTIME='1' TIME='05:11:16' DATE='2016-07-28'
BACKUP='alexio.2016-07-29.tar' TYPE='local' SIZE='90' WEB='wp1.alexio.blablabla.tld' DNS='' MAIL='' DB='alexio_wp1' CRON='' UDIR='.bash_history,.bash_logout,.bashrc,.profile,tmp,.wp-cli' RUNTIME='1' TIME='05:11:33' DATE='2016-07-29'
BACKUP='alexio.2016-07-30.tar' TYPE='local' SIZE='90' WEB='wp1.alexio.blablabla.tld' DNS='' MAIL='' DB='alexio_wp1,alexio_wp1,alexio_wp1' CRON='' UDIR='.bash_history,.bash_logout,.bashrc,.profile,tmp,.wp-cli' RUNTIME='1' TIME='04:03:10' DATE='2016-07-30'
it make an error when update the object value, if i don't mistake.
and i put here a snippet about main.sh
Code: Select all
/usr/local/vesta/func # nano +291 main.sh
# Update object value
update_object_value() {
row=$(grep -nF "$2='$3'" $USER_DATA/$1.conf)
lnr=$(echo $row | cut -f 1 -d ':')
object=$(echo $row | sed "s/^$lnr://")
eval "$object"
eval old="$4"
old=$(echo "$old" | sed -e 's/\\/\\\\/g' -e 's/&/\\&/g' -e 's/\//\\\//g')
new=$(echo "$5" | sed -e 's/\\/\\\\/g' -e 's/&/\\&/g' -e 's/\//\\\//g')
sed -i "$lnr s/${4//$/}='${old//\*/\\*}'/${4//$/}='${new//\*/\\*}'/g" \
$USER_DATA/$1.conf
}
Re: Error v-update-sys-queue disk after restore a backup
hi,
to solve this a removed manually the duplicated entry inside the conf file of vesta but i not have the time to fix vestacp.
i hope next week i will find some time to do that.
meanwhile....
from queue i removed the duplicated entry
same thing from users/$user/ backup.conf stats.conf and other duplicated entry [you can see what/where in the precedent post]
if next week a fix vesta i write here how
bye
to solve this a removed manually the duplicated entry inside the conf file of vesta but i not have the time to fix vestacp.
i hope next week i will find some time to do that.
meanwhile....
from queue i removed the duplicated entry
same thing from users/$user/ backup.conf stats.conf and other duplicated entry [you can see what/where in the precedent post]
if next week a fix vesta i write here how
bye
Re: Error v-update-sys-queue disk after restore a backup
Is this problem adressed by developers?
I am getting the following email, should i be worried?
I am getting the following email, should i be worried?
Code: Select all
Subject: Cron <admin@prom01> sudo /usr/local/vesta/bin/v-update-sys-queue disk
usr/local/vesta/func/main.sh: line 291: 6:DB=kanclers_oc: command not found
/usr/local/vesta/func/main.sh: line 291: 4:DB=kanclers_1564: command not found
/usr/local/vesta/func/main.sh: line 291: 5:DB=kanclers_new22: command not found
/usr/local/vesta/func/main.sh: line 291: 4:DB=kanclers_1564: command not found
/usr/local/vesta/func/main.sh: line 291: 5:DB=kanclers_new22: command not found
/usr/local/vesta/func/main.sh: line 291: 6:DB=kanclers_oc: command not found
/usr/local/vesta/func/main.sh: line 291: 3:DB=gaismaspasaule_oc00: command not found
/usr/local/vesta/func/main.sh: line 291: 4:DB=gaismaspasaule_oc01: command not found
/usr/local/vesta/func/main.sh: line 291: 3:DB=gaismaspasaule_oc00: command not found
/usr/local/vesta/func/main.sh: line 291: 4:DB=gaismaspasaule_oc01: command not found
/usr/local/vesta/func/main.sh: line 291: 3:DB=gaismaspasaule_oc00: command not found
/usr/local/vesta/func/main.sh: line 291: 4:DB=gaismaspasaule_oc01: command not found
Re: Error v-update-sys-queue disk after restore a backup
If some problem exist, please update to latest version 0.9.8.17