Bacula-users

[Bacula-users] FW: Archive Devices not created - Problem solved

2011-05-16 02:39:37
Subject: [Bacula-users] FW: Archive Devices not created - Problem solved
From: "Robert Kromoser" <Robert.Kromoser AT kinamu DOT com>
To: <bacula-users AT lists.sourceforge DOT net>
Date: Mon, 16 May 2011 08:35:57 +0200
Hi everybody. 

Some talks with John Drescher solved this problem.
I had always looked on the main firewall but I forgot to have a look
at the local linux firewall iptables.
After stopping the local iptables using "service iptables stop"
the bacula services were able to connect to the storge daemon,
the archive devices are be created and bacula works as designed.

Thx John.


-----Original Message-----
From: Robert Kromoser 
Sent: Freitag, 13. Mai 2011 17:17
To: John Drescher
Subject: RE: [Bacula-users] Archive Devices not created

Hi John.

*status dir
CBCK0001-dir Version: 5.0.3 (04 August 2010) x86_64-unknown-linux-gnu
redhat Daemon started 13-May-11 18:10, 0 Jobs run since started.
 Heap: heap=266,240 smbytes=114,388 max_bytes=115,093 bufs=601
max_bufs=605

Scheduled Jobs:
Level          Type     Pri  Scheduled          Name
Volume
========================================================================
===========
Full           Backup    11  13-May-11 23:10    CBCK0001_Backup_Catalog
*unknown*
Incremental    Backup    10  14-May-11 01:05    CCRM0004_01_Backup_Full
Vol-CCRM0004-Full-0001
Incremental    Backup    10  14-May-11 01:05    CCRM0004_02_Backup_Diff
Vol-CCRM0004-Diff-0004
Incremental    Backup    10  14-May-11 01:05    CCRM0004_03_Backup_Incr
*unknown*
Incremental    Backup    10  14-May-11 01:05    CCRMTEST_01_Backup_Full
Vol-CCRMTEST-Full-0001
Incremental    Backup    10  14-May-11 01:05    CCRMTEST_02_Backup_Diff
*unknown*
Incremental    Backup    10  14-May-11 01:05    CCRMTEST_03_Backup_Incr
*unknown*
====

Running Jobs:
Console connected at 13-May-11 18:12
 JobId Level   Name                       Status
======================================================================
     8 Full    CCRMTEST_01_Backup_Full.2011-05-13_18.11.15_03 is waiting
for Client CCRMTEST-fd to connect to Storage SugarCRM_CCRMTEST_Full
====

Terminated Jobs:
 JobId  Level    Files      Bytes   Status   Finished        Name
====================================================================
     1  Full          0         0   Cancel   13-May-11 12:01
CCRM0004_01_Backup_Full
     2  Full          0         0   Cancel   13-May-11 12:01
CCRMTEST_01_Backup_Full
     5  Full          0         0   Error    13-May-11 12:22
CCRMTEST_01_Backup_Full
     1  Full          0         0   Error    13-May-11 13:09
CCRMTEST_01_Backup_Full
     2  Full          0         0   Cancel   13-May-11 15:25
CCRMTEST_01_Backup_Full
     4  Full          0         0   Error    13-May-11 16:07
CCRM0004_01_Backup_Full
     5  Full          0         0   Error    13-May-11 16:37
CCRM0004_02_Backup_Diff
     7  Full          0         0   Error    13-May-11 18:08
CCRMTEST_01_Backup_Full

====
*

*status st
The defined Storage resources are:
     1: File
     2: SugarCRM_CCRM0004_Full
     3: SugarCRM_CCRM0004_Diff
     4: SugarCRM_CCRM0004_Incr
     5: SugarCRM_CCRM0004_System
     6: SugarCRM_CCRMTEST_Full
     7: SugarCRM_CCRMTEST_Diff
     8: SugarCRM_CCRMTEST_Incr
     9: SugarCRM_CCRMTEST_System
Select Storage resource (1-9):

*status client=CCRM0004-fd
Connecting to Client CCRM0004-fd at 192.168.100.42:9102

CCRM0004-fd Version: 5.0.3 (04 August 2010)  x86_64-unknown-linux-gnu
redhat Daemon started 06-May-11 18:01. Jobs: run=13 running=0.
 Heap: heap=1,667,072 smbytes=93,792 max_bytes=841,017 bufs=94
max_bufs=220
 Sizeof: boffset_t=8 size_t=8 debug=0 trace=0

Running Jobs:
Director connected at: 13-May-11 17:11
No Jobs running.
====

Terminated Jobs:
 JobId  Level    Files      Bytes   Status   Finished        Name
======================================================================
    23  Full      8,126    1.212 G  Cancel   09-May-11 10:42
CCRM0004_09_Backup_System
    26  Full         80    112.2 K  Error    09-May-11 10:42
CCRM0004_01_Backup_Full
     1  Full     45,520    2.233 G  Error    09-May-11 11:03
CCRM0004_01_Backup_Full
     4  Full     45,527    2.235 G  Error    10-May-11 01:19
CCRM0004_01_Backup_Full
     5  Full     45,527    2.235 G  Error    10-May-11 01:33
CCRM0004_02_Backup_Diff
     6  Full     45,527    2.235 G  Error    10-May-11 01:47
CCRM0004_03_Backup_Incr
    11  Full     45,538    2.237 G  Error    11-May-11 01:18
CCRM0004_01_Backup_Full
    12  Full     45,538    2.237 G  Error    11-May-11 01:32
CCRM0004_02_Backup_Diff
    13  Full     45,538    2.237 G  Error    11-May-11 01:47
CCRM0004_03_Backup_Incr
    18  Full      8,498    20.51 M  Cancel   12-May-11 08:27
CCRM0004_01_Backup_Full
====
*


And here the log with the error message:
========================================

13-May 15:37 CBCK0001-dir JobId 4: Start Backup JobId 4,
Job=CCRM0004_01_Backup_Full.2011-05-13_15.37.39_03
13-May 15:37 CBCK0001-dir JobId 4: Using Device "SugarCRM_CCRM0004_Full"
13-May 14:31 CCRM0004-fd JobId 4: Warning: bsock.c:128 Could not connect
to Storage daemon on CBCK0001:9103. ERR=No route to host Retrying ...
13-May 14:37 CCRM0004-fd JobId 4: Warning: bsock.c:128 Could not connect
to Storage daemon on CBCK0001:9103. ERR=No route to host Retrying ...
13-May 14:42 CCRM0004-fd JobId 4: Warning: bsock.c:128 Could not connect
to Storage daemon on CBCK0001:9103. ERR=No route to host Retrying ...
13-May 14:47 CCRM0004-fd JobId 4: Warning: bsock.c:128 Could not connect
to Storage daemon on CBCK0001:9103. ERR=No route to host Retrying ...
13-May 14:52 CCRM0004-fd JobId 4: Warning: bsock.c:128 Could not connect
to Storage daemon on CBCK0001:9103. ERR=No route to host Retrying ...
13-May 14:57 CCRM0004-fd JobId 4: Warning: bsock.c:128 Could not connect
to Storage daemon on CBCK0001:9103. ERR=No route to host Retrying ...
13-May 15:01 CCRM0004-fd JobId 4: Fatal error: bsock.c:134 Unable to
connect to Storage daemon on CBCK0001:9103. ERR=No route to host 13-May
15:01 CCRM0004-fd JobId 4: Fatal error: Failed to connect to Storage
daemon: CBCK0001:9103 13-May 16:07 CBCK0001-dir JobId 4: Fatal error:
Bad response to Storage command: wanted 2000 OK storage , got 2902 Bad
storage

13-May 16:07 CBCK0001-dir JobId 4: Error: Bacula CBCK0001-dir 5.0.3
(04Aug10): 13-May-2011 16:07:41
  Build OS:               x86_64-unknown-linux-gnu redhat
  JobId:                  4
  Job:                    CCRM0004_01_Backup_Full.2011-05-13_15.37.39_03
  Backup Level:           Full
  Client:                 "CCRM0004-fd" 5.0.3 (04Aug10)
x86_64-unknown-linux-gnu,redhat,
  FileSet:                "CCRM0004_Fileset_SugarCRM" 2011-05-13
15:37:39
  Pool:                   "SugarCRM_CCRM0004_Full" (From Job resource)
  Catalog:                "MyCatalog" (From Client resource)
  Storage:                "SugarCRM_CCRM0004_Full" (From Job resource)
  Scheduled time:         13-May-2011 15:37:00
  Start time:             13-May-2011 15:37:41
  End time:               13-May-2011 16:07:41
  Elapsed time:           30 mins
  Priority:               10
  FD Files Written:       0
  SD Files Written:       0
  FD Bytes Written:       0 (0 B)
  SD Bytes Written:       0 (0 B)
  Rate:                   0.0 KB/s
  Software Compression:   None
  VSS:                    no
  Encryption:             no
  Accurate:               no
  Volume name(s):
  Volume Session Id:      1
  Volume Session Time:    1305293804
  Last Volume Bytes:      257 (257 B)
  Non-fatal FD errors:    0
  SD Errors:              0
  FD termination status:  Error
  SD termination status:  Waiting on FD
  Termination:            *** Backup Error ***

In the attachment you can see my configuration:
The main configuration is already placed in bacula-<service>.conf.
The client configuration is placed in ccrm0004-<service>.conf.

All 3 Daemons are installed on the same machine named CBCK0001
192.168.100.93.

Regards Robert




-----Original Message-----
From: John Drescher [mailto:drescherjm AT gmail DOT com]
Sent: Freitag, 13. Mai 2011 17:00
To: Robert Kromoser
Cc: bacula-users AT lists.sourceforge DOT net
Subject: Re: [Bacula-users] Archive Devices not created

> Does the bacula user have write access to your storage location on 
> your filesystem? That is assuming bacula-sd is running as user bacula 
> like it does on many linux operating systems.
>

Also what do the messages say in the bacula console?

The output of

status dir

status st

and status client


would be helpful

John

Attachment: bacula-sd.conf
Description: bacula-sd.conf

Attachment: bacula-dir.conf
Description: bacula-dir.conf

Attachment: bacula-fd.conf
Description: bacula-fd.conf

Attachment: ccrm0004-sd.conf
Description: ccrm0004-sd.conf

Attachment: ccrm0004-dir.conf
Description: ccrm0004-dir.conf

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Bacula-users] FW: Archive Devices not created - Problem solved, Robert Kromoser <=