Contenu | Rechercher | Menus

Annonce

Ubuntu-fr.org recrute toujours de nouveaux modérateurs, avec de l'expérience.

Ubuntu 16.04 LTS
Commandez vos DVD et clés USB Ubuntu-fr !

Si vous avez des soucis pour rester connecté, déconnectez vous et reconnectez vous depuis ce lien en cochant le case
Me connecter automatiquement lors de mes prochaines visites.

#1 Le 10/10/2013, à 09:50

tutoux

automysqlbackup: failed

automysqlbackup

Bonjour,

avec ubuntu12.10-64bits_3.5.0-41-generic
asus-UL30A_4GBram

j'essaye automysqlbackup_3.0, en mode simulation (dry running), pour sauvegarder sur un ssd externe chiffré avec truecrypt.

~$ sudo automysqlbackup /etc/automysqlbackup/myserver.conf 
Parsed config file "/etc/automysqlbackup/automysqlbackup.conf" 

NOTE: We are dry-running. That means, that the script just shows you what it would do, if it were operating normally. 
THE PRINTED COMMANDS CAN'T BE COPIED AND EXECUTED IF THERE ARE SPECIAL CHARACTERS, SPACES, ETC. IN THERE THAT WOULD NEED TO BE PROPERLY QUOTED IN ORDER TO WORK. THESE WERE CORRECTLY QUOTED FOR THE OUTPUT COMMAND, BUT CAN'T BE SEEN NOW. 

que signifie ce paragraphe en capitales ?
qu'est-ce que les PRINTED COMMANDS ?

# Checking for permissions to write to folders: 
base folder /media ... exists ... ok. 
backup folder /media/truecrypt1 ... exists ... writable?
 dry-running. Skipping. Logging to /tmp 

le "?" de "writable?" indique-t-il un pb ?

checking directory "/media/truecrypt1/daily" ... creating ... dry-running. Skipping. 
checking directory "/media/truecrypt1/weekly" ... creating ... dry-running. Skipping. 
checking directory "/media/truecrypt1/monthly" ... creating ... dry-running. Skipping. 
checking directory "/media/truecrypt1/latest" ... creating ... dry-running. Skipping. 
checking directory "/media/truecrypt1/tmp" ... creating ... dry-running. Skipping. 
checking directory "/media/truecrypt1/fullschema" ... creating ... dry-running. Skipping. 
checking directory "/media/truecrypt1/status" ... creating ... dry-running. Skipping. 

# Testing for installed programs 
WARNING: Turning off multicore support, since pigz isn't there. 
mysql ... found. 
mysqldump ... found. 

# Parsing databases ... done. 
Dump full schema. 

dry-running: mysqldump --user=root --password=XXXXXXXX --host=localhost --all-databases --routines --no-data --ssl --port=3306 | gzip_compression > /media/truecrypt1/fullschema/fullschema_daily_2013-10-09_23h25m_Wednesday.sql.gz 
Rotating 4 month backups for 

====================================================================== 

====================================================================== 
Dump status. 
 
dry-running: mysqlshow --user=root --password=XXXXX --host=localhost --status --ssl --port=3306 | gzip_compression > /media/truecrypt1/status/status_daily_2013-10-09_23h25m_Wednesday.txt.gz 
Rotating 4 month backups for 

====================================================================== 

Backup Start Time Wed Oct  9 23:25:09 CEST 2013 
====================================================================== 
Daily Backup ... 

Daily Backup of Database ( BaseGetTest ) 
dry-running: mkdir -p /media/truecrypt1/${subfolder}/BaseGetTest 
## Reading in Manifest file 

Number of manifest entries: 0 

ensuite, idem pour toutes les bases.

Backup End Time Wed Oct  9 23:25:10 CEST 2013 
====================================================================== 
Total disk space used for backup storage... 
Size - Location 
20K /media/truecrypt1 

====================================================================== 

###### WARNING ###### 
Errors reported during AutoMySQLBackup execution.. Backup failed 
Error log below.. 
find: `/media/truecrypt1/fullschema': No such file or directory 
find: `/media/truecrypt1/status': No such file or directory 
mktemp: failed to create file via template `/media/truecrypt1/daily/BaseGetTest/daily_BaseGetTest_2013-10-09_23h25m_Wednesday_XXXXXXXX.sql.gz': No such file or directory 
/usr/local/bin/automysqlbackup: line 713: : No such file or directory 
mysqldump: Got errno 32 on write

idem pour toutes les bases

find: `/media/truecrypt1/fullschema': No such file or directory 

laisserait à penser que le "fullshema" n'a pas été créé. or le volume truecrypt1 est, sauf erreur, writable car j'ai pu y copier, via sudo, un fichier.
et automysqlbackup est également lancé via sudo.

une (ou plusieurs) idée ?

merci d'avance.
Cordialement.
tutoux

Hors ligne

#2 Le 11/10/2013, à 10:27

tutoux

Re : automysqlbackup: failed

Bonjour,
nouvelle tentative en changeant de répertoire de sauvegarde, qui, sauf erreur, a les permissions requises :

drwx------  2 mlbg mlbg     32768 oct.  11 09:39 autobackup
mlbg@mlbg-UL30A:~$ sudo automysqlbackup /etc/automysqlbackup/myserver.conf
Parsed config file "/etc/automysqlbackup/automysqlbackup.conf"

NOTE: We are dry-running. That means, that the script just shows you what it would do, if it were operating normally.
THE PRINTED COMMANDS CAN'T BE COPIED AND EXECUTED IF THERE ARE SPECIAL CHARACTERS, SPACES, ETC. IN THERE THAT WOULD NEED TO BE PROPERLY QUOTED IN ORDER TO WORK. THESE WERE CORRECTLY QUOTED FOR THE OUTPUT COMMAND, BUT CAN'T BE SEEN NOW.

# Checking for permissions to write to folders:
base folder /media/mlbg/9016-4EF81 ... exists ... ok.
backup folder /media/mlbg/9016-4EF81/autobackup ... exists ... writable? dry-running. Skipping. Logging to /tmp
checking directory "/media/mlbg/9016-4EF81/autobackup/daily" ... creating ... dry-running. Skipping.
checking directory "/media/mlbg/9016-4EF81/autobackup/weekly" ... creating ... dry-running. Skipping.
checking directory "/media/mlbg/9016-4EF81/autobackup/monthly" ... creating ... dry-running. Skipping.
checking directory "/media/mlbg/9016-4EF81/autobackup/latest" ... creating ... dry-running. Skipping.
checking directory "/media/mlbg/9016-4EF81/autobackup/tmp" ... creating ... dry-running. Skipping.
checking directory "/media/mlbg/9016-4EF81/autobackup/fullschema" ... creating ... dry-running. Skipping.
checking directory "/media/mlbg/9016-4EF81/autobackup/status" ... creating ... dry-running. Skipping.

...

###### WARNING ######
Errors reported during AutoMySQLBackup execution.. Backup failed
Error log below..
find: `/media/mlbg/9016-4EF81/autobackup/fullschema': No such file or directory
find: `/media/mlbg/9016-4EF81/autobackup/fullschema': No such file or directory
find: `/media/mlbg/9016-4EF81/autobackup/status': No such file or directory
find: `/media/mlbg/9016-4EF81/autobackup/status': No such file or directory
mktemp: failed to create file via template `/media/mlbg/9016-4EF81/autobackup/daily/BaseGetTest/daily_BaseGetTest_2013-10-11_09h45m_Friday_XXXXXXXX.sql.gz': No such file or directory
/usr/local/bin/automysqlbackup: line 713: : No such file or directory
mysqldump: Got errno 32 on write

idem pour toutes les bases :-(

cela pourrait-il être lié au "dry-running" ?

Hors ligne