Hello ,

there was a typo in the setdebug command from the old thread, the right
one is:

setdebug client=centos-fd trace=1 level=200

with your client (trace=1 instead 'on').

Please make sure to use this version of the plugin (it has a little bit
more error-handling and debug output at the crucial point than previous
ones):

https://github.com/bareos/bareos-contrib/blob/master/fd-plugins/bareos_percona/BareosFdPercona.py

Maik


Am 31.01.2017 um 16:51 schrieb Daniel:
> xtrabackup version 2.4.5 based on MySQL server 5.7.13 Linux (x86_64) 
> (revision id: e41c0be)
> /etc/mysql/my.cnf should be correct.
>
> root@icinga:/var/lib/bareos# echo 'SHOW ENGINE INNODB STATUS' | mysql -r -p
> Enter password:
> Type    Name    Status
> InnoDB
> =====================================
> 2017-01-31 16:48:44 0x7f2a88537700 INNODB MONITOR OUTPUT
> =====================================
> Per second averages calculated from the last 47 seconds
> -----------------
> BACKGROUND THREAD
> -----------------
> srv_master_thread loops: 8 srv_active, 0 srv_shutdown, 1002372 srv_idle
> srv_master_thread log flush and writes: 1002297
> ----------
> SEMAPHORES
> ----------
> OS WAIT ARRAY INFO: reservation count 14
> OS WAIT ARRAY INFO: signal count 14
> RW-shared spins 0, rounds 4, OS waits 2
> RW-excl spins 0, rounds 0, OS waits 0
> RW-sx spins 0, rounds 0, OS waits 0
> Spin rounds per wait: 4.00 RW-shared, 0.00 RW-excl, 0.00 RW-sx
> ------------
> TRANSACTIONS
> ------------
> Trx id counter 14362882
> Purge done for trx's n:o < 0 undo n:o < 0 state: running but idle
> History list length 0
> LIST OF TRANSACTIONS FOR EACH SESSION:
> ---TRANSACTION 421296075085664, not started
> 0 lock struct(s), heap size 1136, 0 row lock(s)
> --------
> FILE I/O
> --------
> I/O thread 0 state: waiting for completed aio requests (insert buffer thread)
> I/O thread 1 state: waiting for completed aio requests (log thread)
> I/O thread 2 state: waiting for completed aio requests (read thread)
> I/O thread 3 state: waiting for completed aio requests (read thread)
> I/O thread 4 state: waiting for completed aio requests (read thread)
> I/O thread 5 state: waiting for completed aio requests (read thread)
> I/O thread 6 state: waiting for completed aio requests (write thread)
> I/O thread 7 state: waiting for completed aio requests (write thread)
> I/O thread 8 state: waiting for completed aio requests (write thread)
> I/O thread 9 state: waiting for completed aio requests (write thread)
> Pending normal aio reads: [0, 0, 0, 0] , aio writes: [0, 0, 0, 0] ,
>  ibuf aio reads:, log i/o's:, sync i/o's:
> Pending flushes (fsync) log: 0; buffer pool: 0
> 667 OS file reads, 75 OS file writes, 7 OS fsyncs
> 0.00 reads/s, 0 avg bytes/read, 0.00 writes/s, 0.00 fsyncs/s
> -------------------------------------
> INSERT BUFFER AND ADAPTIVE HASH INDEX
> -------------------------------------
> Ibuf: size 1, free list len 0, seg size 2, 0 merges
> merged operations:
>  insert 0, delete mark 0, delete 0
> discarded operations:
>  insert 0, delete mark 0, delete 0
> Hash table size 34673, node heap has 1 buffer(s)
> Hash table size 34673, node heap has 0 buffer(s)
> Hash table size 34673, node heap has 0 buffer(s)
> Hash table size 34673, node heap has 0 buffer(s)
> Hash table size 34673, node heap has 0 buffer(s)
> Hash table size 34673, node heap has 0 buffer(s)
> Hash table size 34673, node heap has 0 buffer(s)
> Hash table size 34673, node heap has 1 buffer(s)
> 0.00 hash searches/s, 0.00 non-hash searches/s
> ---
> LOG
> ---
> Log sequence number 32475677035
> Log flushed up to   32475677035
> Pages flushed up to 32475677035
> Last checkpoint at  32475677026
> 0 pending log flushes, 0 pending chkp writes
> 10 log i/o's done, 0.00 log i/o's/second
> ----------------------
> BUFFER POOL AND MEMORY
> ----------------------
> Total large memory allocated 137428992
> Dictionary memory allocated 267804
> Buffer pool size   8191
> Free buffers       7548
> Database pages     641
> Old database pages 256
> Modified db pages  0
> Pending reads      0
> Pending writes: LRU 0, flush list 0, single page 0
> Pages made young 0, not young 0
> 0.00 youngs/s, 0.00 non-youngs/s
> Pages read 606, created 35, written 58
> 0.00 reads/s, 0.00 creates/s, 0.00 writes/s
> No buffer pool page gets since the last printout
> Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 
> 0.00/s
> LRU len: 641, unzip_LRU len: 0
> I/O sum[0]:cur[0], unzip sum[0]:cur[0]
> --------------
> ROW OPERATIONS
> --------------
> 0 queries inside InnoDB, 0 queries in queue
> 0 read views open inside InnoDB
> Process ID=20711, Main thread ID=139820798281472, state: sleeping
> Number of rows inserted 308, updated 0, deleted 0, read 316
> 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s
> ----------------------------
> END OF INNODB MONITOR OUTPUT
>
>
> a tracefile is neither on the backupserver nor on the client...
>
>
> Am Dienstag, 31. Januar 2017 16:40:14 UTC+1 schrieb maik.aussendorf:
>> Hello,
>>
>> you've missed to check some parts of the thread:
>>
>> - what version of xtrabackup are you using?
>> - .my.cnf correct?
>> - output of 
>> echo 'SHOW ENGINE INNODB STATUS' | mysql -r -p
>> - The fd-tracefile is supposed to be on the client.
>> Without tracefile, help is difficult (sometimes impossible)
>>
>> Regards
>> Maik
>>
>> Am 31.01.2017 um 16:25 schrieb Daniel:
>>> Thanks Maik.
>>> I tried the steps described in that topic.
>>>
>>>> Please do the following:
>>>> - run the xtrabackup manually as above.
>>>> send the file xtrabackup_checkpoints from your temp-directory: 
>>>> /tmp/tmpYmkHJn
>>> my directory is /tmp/test and there is a xtrabackup_checkpoints with the 
>>> following content:
>>> backup_type = full-backuped
>>> from_lsn = 0
>>> to_lsn = 32475677026
>>> last_lsn = 32475677035
>>> compact = 0
>>> recover_binlog_info = 0
>>>
>>>
>>>> Run FD in Debug mode and send the output after running a backup and a 
>>>> restore job.
>>>> To activate debug on your client-fd, do something like
>>>> *setdebug client=centos-fd trace=on level=200
>>> I did and got the output:
>>> Connecting to Client Icinga-fd at icinga.sitepark.local:9102
>>> 2000 OK setdebug=200 trace=0 hangup=0 timestamp=0 
>>> tracefile=/var/lib/bareos/Webserver-Icinga-fd.trace
>>>
>>>> bconsolse tells you where to look for the tracefile=/...
>>>> Attach that tracefile (after having removed eventual sensible information).
>>> I would do that, but after one backup and one restore, there is no file 
>>> /var/lib/bareos/Webserver-Icinga-fd.trace
>> The fd-tracefile is supposed to be on the client.
>> Without tracefile, help is difficult (sometimes impossible).
>>
>>> in the log of the backup there stands:
>>> 31-Jan 16:15 Webserver-Icinga-fd JobId 1179: python-fd: Starting backup of 
>>> /_percona/xbstream.0000001179
>>> 31-Jan 16:15 Webserver-Icinga-fd JobId 1179: python-fd: Starting backup of 
>>> /_percona/xtrabackup_checkpoints
>>>
>>> and in the restore:
>>> 31-Jan 16:20 Webserver-Icinga-fd JobId 1180: Error: python-fd: No lsn 
>>> information found in restore object for file 
>>> /tmp/bareos-restores//_percona/xbstream.0000001179 from job 1179
>>> 31-Jan 16:20 bareos-sd JobId 1180: Forward spacing Volume 
>>> "Icinga.2017-01-31_16.15.03_37.Incremental" to file:block 0:233.
>>> 31-Jan 16:21 bareos-dir JobId 1180: Error: Bareos bareos-dir 16.2.4 
>>> (01Jul16):
>>>   Build OS:               x86_64-pc-linux-gnu ubuntu Ubuntu 16.04 LTS
>>>   JobId:                  1180
>>>   Job:                    RestoreFiles.2017-01-31_16.20.06_55
>>>   Restore Client:         Icinga-fd
>>>   Start time:             31-Jan-2017 16:20:08
>>>   End time:               31-Jan-2017 16:21:09
>>>   Elapsed time:           1 min 1 sec
>>>   Files Expected:         1
>>>   Files Restored:         1
>>>   Bytes Restored:         5,819,132
>>>   Rate:                   95.4 KB/s
>>>   FD Errors:              1
>>>   FD termination status:  Error
>>>   SD termination status:  OK
>>>   Termination:            *** Restore Error ***
>>>
>> -- 
>> With kind regards // Mit freundlichen Grüßen
>> --
>>  Maik Außendorf                             maik.aussend...@bareos.com
>>  Bareos GmbH & Co. KG                       Phone: +49221630693-93
>>  http://www.bareos.com                      Fax: +49221630693-10
>>
>>  Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
>>  Komplementär: Bareos Verwaltungs-GmbH
>>  Geschäftsführer: Stephan Dühr, M. Außendorf, 
>>  J. Steffens, P. Storz

-- 
With kind regards // Mit freundlichen Grüßen
--
 Maik Außendorf                             maik.aussend...@bareos.com
 Bareos GmbH & Co. KG                       Phone: +49221630693-93
 http://www.bareos.com                      Fax: +49221630693-10

 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
 Komplementär: Bareos Verwaltungs-GmbH
 Geschäftsführer: Stephan Dühr, M. Außendorf, 
 J. Steffens, P. Storz

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bareos-users+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to