-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem on CentOS 6.6 / Maria 10.0.16 #33
Comments
Have a look at the logs files of the tool, especially the |
Hi, thanks for the reply! I had posted in my query, the content of the Tim Tim Chipman ------ Original Message ------
|
Hey Tim, I just found out that you're using the bash scripts, which are deprecated ! Is this really necessary? I recommend you to use the Python version ! |
Hi, No, not at all necessary. Rather, it was the only version I knew I believe the page was, (maybe it is easily possible to put a 'warn' message at top of that Sigh! My mistake. So - I will get the Python version, repeat my tests and let you know how Thanks for your help with this! Tim Tim Chipman ------ Original Message ------
|
Yeaye I'll update my post ! |
Hi Anthony, I wanted to briefly followup. (I can do this via git hub if you prefer I've had backups / running for a while now - and thought it would be a So: I was testing the restore-from-incrementals today. and I appear to hit a Context:
---paste--- [root@gpli-vsd2 bin]# cd /nfs-mount/backuppc/ (note other intermentals are in the other directories, as per their date [root@gpli-vsd2 INC]# pwd [root@gpli-vsd2 INC]# ls -la ---endpaste--- So, then I try to kick off a restore .. -- have a clean /var/lib/mysql directory pyxtrabackup-restore --incremental-archive=/nfs-mount/backuppc/20160129/INC/inc_19_backup_20160129_0303.tar.gz and for reference, here is how I generated the (a) full backup once per (A) FULL once per month (B) Incremental all nights per month (slightly later start time than the And. When I ran the pyxtrabackup-restore ... It gave me output thus: (after a [root@gpli-vsd2 ~]# pyxtrabackup-restore
INFO:xtrabackup.restoration_tools:Base backup restoration time: and we have output dumped to disk, not a trivial amount, but not the [root@gpli-vsd2 FAILED_restore-test]# ls -la The date-stamps on some of the files, seems to be giving me a hint - Anyhow. If you see anything here that immediately says, oh gosh, that is not correct - do this, not that! or other thoughts - any comments are certainly appreciated. (For example? I'm not 100% clear that the incremental restore script .. Many thanks for your assistance with this, Tim Chipman Tim Chipman ------ Original Message ------
|
Hey @mrtdc, I'm not really available right now, I'll try to have a look at this issue next week ! |
Hi, no worries! Thanks for the reply. I really appreciate it. Any Tim Tim Chipman ------ Original Message ------
|
Hi, I wanted to ask if this is known issue, or if there is a way to get more verbose error messages to give me a hint on what is the issue.
I am able to run innobackupex and successfully generate a backup via command line, approx thus:
innobackupex --user=root --password=SecretPassGoesHere /nfs-mount/dump-path/
however when I use xtrabackup script it throws an error, thus:
./xb-backup-incremental.sh -r /nfs-mount/dump-path/-u root -p SecretPassGoesHere
Command: mkdir -pv /nfs-mount/backuppc...20151206_1450 [ OK ]
Starting base backup. [ INFO ]
An exception occured while trying to use innobackupex.
and similarly when I look in the logfile,
[root@gpli-vsu2 xb-backup]# cd /var/log/mysql
[root@gpli-vsu2 mysql]# ls -la
total 12
drwxr-xr-x 2 root root 4096 Nov 25 14:08 .
drwxr-xr-x. 7 root root 4096 Dec 6 03:40 ..
-rw-r--r-- 1 root root 1328 Dec 6 14:50 xb-backup-incremental.log
[root@gpli-vsu2 mysql]# more xb-backup-incremental.log
...
2015-12-06T18:50:17+0000 - Executing: mkdir -pv /nfs-mount/backuppc/20151206_1450
2015-12-06T18:50:17+0000 - Command: mkdir -pv /nfs-mount/backuppc... - Status: OK
2015-12-06T18:50:17+0000 - Starting base backup. - Status: INFO
2015-12-06T18:50:17+0000 - An exception occured while trying to use innobackupex. - Status: FAILED
[root@gpli-vsu2 mysql]#
For ref:
host:
[root@srv mysql]# cat /etc/redhat-release
CentOS release 6.6 (Final)
MariaDB Version:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 45064
Server version: 10.0.16-MariaDB-log MariaDB Server
Just curious what might be the next step to debug this.
Thanks!
Tim
The text was updated successfully, but these errors were encountered: