Hi,

I can reproducible crash bacula-dir when starting a backup on a client with
Accurate backups enabled.

The dir is running debian lenny + bacula 3.0.2 from backports (did also try
self compiled 3.0.3), psql 8.4.

The client is running Red Hat Enterprise Linux 4.8, with bacula-fd build from
bacula-3.0.3-1.src.rpm. I also tried a rpm package from 

ftp://ftp.pbone.net/mirror/ftp.pramberger.at/systems/linux/contrib/rhel4/i386

What me makes wonder first, I see 3 bacula-fd processes on the client:

-bacula-fd(8128)---bacula-fd(8129)---bacula-fd(8130)

Without "Accurate = yes" the backup runs fine. Accurate backup was enabled
weeks ago a couple of backup were running fine with this option enabled.
So I don't know what has changed since last week.

Here's the level 150 dir debug output.

VUMEM004-dir: fd_cmds.c:322-19628 >filed: VUMEM004-dir: getmsg.c:138-19628 
bget_dirmsg 14: 2000 OK level
VUMEM004-dir: getmsg.c:138-19628 bget_dirmsg 47: 3010 Job 
VU0EM003.2010-02-17_00.06.00_03 start
VUMEM004-dir: getmsg.c:138-19628 bget_dirmsg 56: Status 
Job=VU0EM003.2010-02-17_00.06.00_03 JobStatus=82
VUMEM004-dir: getmsg.c:138-19628 bget_dirmsg 16: 2000 OK storage
VUMEM004-dir: fd_cmds.c:581-19628 bdird: sending runscripts to fd
VUMEM004-dir: util.c:723-19628 edit_job_codes: %c
VUMEM004-dir: fd_cmds.c:586-19628 bdird: runscript %c -> VU0EM003
VUMEM004-dir: fd_cmds.c:592-19628 bdird: sending runscripts to fd 
'/opt/scripts/bacula/find.sh server'
VUMEM004-dir: fd_cmds.c:555-19628 bdird: sending old runcommand to fd 
'/opt/scripts/bacula/find.sh^Aserver'
VUMEM004-dir: getmsg.c:138-19628 bget_dirmsg 162: Jmsg 
Job=VU0EM003.2010-02-17_00.06.00_03 type=6 level=1266361563 VU0EM003 JobId 
19628: shell command: run ClientRunBeforeJob "/opt/scripts/bacula/find.sh 
server"
VUMEM004-dir: getmsg.c:138-19628 bget_dirmsg 137: Jmsg 
Job=VU0EM003.2010-02-17_00.06.00_03 type=6 level=1266361563 VU0EM003 JobId 
19628: ClientRunBeforeJob: Fuehre Skript fuer server aus
VUMEM004-dir: getmsg.c:138-19617 bget_dirmsg -1: 
VUMEM004-dir: getmsg.c:138-19617 bget_dirmsg -1: 
VUMEM004-dir: getmsg.c:138-19627 bget_dirmsg 129: Jmsg 
Job=SMTCZB0003.2010-02-17_00.05.00_02 type=6 level=1266361622 SMTCZB0003-fd 
JobId 19627: ClientRunBeforeJob: Starte MKS... 
VUMEM004-dir: getmsg.c:138-19627 bget_dirmsg 18: 2000 OK RunBefore
VUMEM004-dir: util.c:723-19627 edit_job_codes: %c
VUMEM004-dir: fd_cmds.c:586-19627 bdird: runscript %c -> SMTCZB0003
VUMEM004-dir: fd_cmds.c:592-19627 bdird: sending runscripts to fd 
'/home/mksadmin/backup/script/db2_backup_offline_post.sh'
VUMEM004-dir: fd_cmds.c:555-19627 bdird: sending old runcommand to fd 
'/home/mksadmin/backup/script/db2_backup_offline_post.sh'
VUMEM004-dir: getmsg.c:138-19627 bget_dirmsg 17: 2000 OK RunAfter
/usr/sbin/bacula-dir: symbol lookup error: /usr/sbin/bacula-dir: undefined 
symbol: _Z22db_accurate_get_jobidsP3JCRP4B_DBP7JOB_DBRPc


I've set the debug level on the client to 200, the debug log file is created 
but empty.

I read Kaboom chapter in the manual but I can't get it to work on the dir.
Before I put more time in this problem, is there anything obvious in the dir
debug output (well, it's not that much...)? 


Ralf

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to