Hi!

Managed to solve problem. Don't know what in KVM/qemu/libvirt installation was 
bothering this but uninstalling those fixed the problem. Maybe it was the virbr 
bridge messing with comms.

Thanks,
Juhani

From: Juhani Rautiainen
Sent: torstai 7. maaliskuuta 2019 11.38
To: [email protected]
Subject: BackupCatalog fails in new 18.2.5 installation

Hi!

I decided to try new 18.2.5 on new installation and I can install it fine from 
RPM (Centos7). I use postgres as database. Problem is that BackupCatalog job 
fails and I can't find any reason why.  I could make other backup jobs and they 
ran fine but this always fails. So after daily backup it's stuck and can't 
backup itself. I removed everything and reinstalled everything to fresh 
database and I still get the problem. I only changed the SD storage to 
/backup1-folder.

This is what I can see from the bconsole:

*run
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
A job name must be specified.
The defined Job resources are:
     1: RestoreFiles
     2: BackupCatalog
     3: backup-bareos-fd
Select Job resource (1-3): 2
Run Backup job
JobName:  BackupCatalog
Level:    Full
Client:   bareos-fd
Format:   Native
FileSet:  Catalog
Pool:     Full (From Job FullPool override)
Storage:  File (From Job resource)
When:     2019-03-07 11:29:11
Priority: 11
OK to run? (yes/mod/no): yes
Job queued. JobId=5
*messages
07-Mar 11:29 bareos-dir JobId 5: shell command: run BeforeJob 
"/usr/lib/bareos/scripts/make_catalog_backup.pl MyCatalog"
07-Mar 11:29 bareos-dir JobId 5: Start Backup JobId 5, 
Job=BackupCatalog.2019-03-07_11.29.12_04
07-Mar 11:29 bareos-dir JobId 5: Connected Storage daemon at BLHBC1:9103, 
encryption: PSK-AES256-CBC-SHA
07-Mar 11:29 bareos-dir JobId 5: Using Device "FileStorage" to write.
07-Mar 11:29 bareos-dir JobId 5: Probing client protocol... (result will be 
saved until config reload)
07-Mar 11:29 bareos-dir JobId 5: Connected Client: bareos-fd at localhost:9102, 
encryption: PSK-AES256-CBC-SHA
07-Mar 11:29 bareos-dir JobId 5:    Handshake: Immediate TLS
07-Mar 11:29 BLHBC1-fd JobId 5: Connected Storage daemon at BLHBC1:9103, 
encryption: PSK-AES256-CBC-SHA
07-Mar 11:29 BLHBC1-fd JobId 5: Extended attribute support is enabled
07-Mar 11:29 BLHBC1-fd JobId 5: ACL support is enabled
07-Mar 11:29 bareos-sd JobId 5: Volume "Full-0001" previously written, moving 
to end of data.
07-Mar 11:29 bareos-sd JobId 5: Ready to append to end of Volume "Full-0001" 
size=72428285
07-Mar 11:29 bareos-sd JobId 5: Releasing device "FileStorage" (/backup1).
07-Mar 11:29 bareos-sd JobId 5: Elapsed time=00:00:01, Transfer rate=198.4 K 
Bytes/second
07-Mar 11:29 bareos-dir JobId 5: Insert of attributes batch table with 69 
entries start
07-Mar 11:29 bareos-dir JobId 5: Insert of attributes batch table done

And that's it. After this job is running but terminated:

*status
Status available for:
     1: Director
     2: Storage
     3: Client
     4: Scheduler
     5: All
Select daemon type for status (1-5): 1
bareos-dir Version: 18.2.5 (30 January 2019) Linux-4.4.92-6.18-default redhat 
CentOS Linux release 7.6.1810 (Core)
Daemon started 07-Mar-19 11:29. Jobs: run=0, running=1 mode=0 db:postgresql, 
bareos.org build binary
Heap: heap=270,336 smbytes=123,670 max_bytes=123,670 bufs=445 max_bufs=450

Scheduled Jobs:
Level          Type     Pri  Scheduled          Name               Volume
===================================================================================
Incremental    Backup    10  07-Mar-19 21:00    backup-bareos-fd   *unknown*
Full           Backup    11  07-Mar-19 21:10    BackupCatalog      *unknown*
====

Running Jobs:
Console connected at 07-Mar-19 11:29
JobId Level   Name                       Status
======================================================================
     5 Full    BackupCatalog.2019-03-07_11.29.12_04 has terminated
====
No Terminated Jobs.

Client Initiated Connections (waiting for jobs):
Connect time        Protocol            Authenticated       Name
====================================================================================================
====
*cancel
Automatically selected Job: JobId=5 Job=BackupCatalog.2019-03-07_11.29.12_04
Confirm cancel (yes/no): yes
Handshake: Immediate TLS, Encryption: PSK-AES256-CBC-SHA
2901 Job BackupCatalog.2019-03-07_11.29.12_04 not found.
3904 Job BackupCatalog.2019-03-07_11.29.12_04 not found.
*status
Status available for:
     1: Director
     2: Storage
     3: Client
     4: Scheduler
     5: All
Select daemon type for status (1-5): 1
bareos-dir Version: 18.2.5 (30 January 2019) Linux-4.4.92-6.18-default redhat 
CentOS Linux release 7.6.1810 (Core)
Daemon started 07-Mar-19 11:29. Jobs: run=0, running=1 mode=0 db:postgresql, 
bareos.org build binary
Heap: heap=270,336 smbytes=127,957 max_bytes=129,016 bufs=446 max_bufs=457

Scheduled Jobs:
Level          Type     Pri  Scheduled          Name               Volume
===================================================================================
Incremental    Backup    10  07-Mar-19 21:00    backup-bareos-fd   *unknown*
Full           Backup    11  07-Mar-19 21:10    BackupCatalog      *unknown*
====

Running Jobs:
Console connected at 07-Mar-19 11:29
JobId Level   Name                       Status
======================================================================
     5 Full    BackupCatalog.2019-03-07_11.29.12_04 has been canceled
====
No Terminated Jobs.

I tried with debug but could not find any errors in the log. Any one any ideas 
what I should be looking for?

Thanks,
Juhani

-- 
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 [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to