Bacula-users

Re: [Bacula-users] Fatal error: askdir.c:339 NULL Volume name. This shouldn't happen!!!

2012-07-15 11:01:52
Subject: Re: [Bacula-users] Fatal error: askdir.c:339 NULL Volume name. This shouldn't happen!!!
From: Stephen Thompson <stephen AT seismo.berkeley DOT edu>
To: bacula-users AT lists.sourceforge DOT net
Date: Sun, 15 Jul 2012 07:57:28 -0700

Update.  We are still seeing this in 5.2.10 as well.
It seems to happen more often towards the beginning of a series of jobs, 
when a tape is first chosen (i.e. not when a job is directly using a 
tape that's already been chosen and loaded into a drive by a previous job).

Stephen



On 7/5/12 7:44 AM, Stephen Thompson wrote:
>
>
> Update.  We have seen the problem 2-3 times this past month running
> 5.2.9 on Redhat 6.2, much less frequent than before but still there.
>
> Stephen
>
>
>
> On 6/20/12 7:40 AM, Stephen Thompson wrote:
>>
>>
>> Well, since we upgraded to 5.2.9 we have not seen the problem.
>> Also when running 5.2.6 we were seeing it 2-3 times a week, during which
>> we run hundreds of incrementals and several fulls per day.
>> The error happened both with fulls and incrementals (which we have in
>> two different LTO3 libraries).  There was nothing amiss with our catalog
>> or volumes, or at least nothing obvious.  The error occurred when
>> attempting to use different volumes (mostly previously used ones,
>> including recycled), but those same volume were successful for other
>> jobs that attempted to use them.  Lastly, it wasn't reproducible, like I
>> said it happened 2-3 time out of several hundred jobs, but it was
>> happening over the course of a month or two while we ran 5.2.6 on RedHat
>> 6.2.
>>
>> Here was our config for 5.2.6
>>
>>
>> PATH=/usr/lib64/qt4/bin:$PATH
>> BHOME=/home/bacula
>> EMAIL=bacula AT seismo.berkeley DOT edu
>>
>> env CFLAGS='-g -O2' \
>>        ./configure \
>>            --prefix=$BHOME \
>>            --sbindir=$BHOME/bin \
>>            --sysconfdir=$BHOME/conf \
>>            --with-working-dir=$BHOME/work \
>>            --with-bsrdir=$BHOME/log \
>>            --with-logdir=$BHOME/log \
>>            --with-pid-dir=/var/run \
>>            --with-subsys-dir=/var/run \
>>            --with-dump-email=$EMAIL \
>>            --with-job-email=$EMAIL \
>>            --with-mysql \
>>            --with-dir-user=bacula \
>>            --with-dir-group=bacula \
>>            --with-sd-user=bacula \
>>            --with-sd-group=bacula \
>>      --with-openssl \
>>      --with-tcp-wrappers \
>>            --enable-smartalloc \
>>            --with-readline=/usr/include/readline \
>>            --disable-conio \
>>            --enable-bat \
>>        | tee configure.out
>>
>>
>>
>>
>> On 6/20/12 7:23 AM, Igor Blazevic wrote:
>>> On 18.06.2012 16:26, Stephen Thompson wrote:
>>>>
>>>>>
>>>>> hello,
>>>
>>> Hello:)
>>>
>>>>>
>>>>> Anyone run into this error before?
>>>>>
>>>>> We hadn't until we upgraded our bacula server from Centos 5.8 to Redhat
>>>>> 6.2, after which we of course had to recompile bacula.  However, we used
>>>>> the same source, version, and options, the exception being that we added
>>>>> readline for improved bconsole functionality.
>>>
>>> Can you post your config options, please? I've compiled versions 5.0.3 and
>>> 5.2.6 on RHEL 6.2 with following options:
>>>
>>> CFLAGS="-g -Wall" ./configure \
>>>      --sysconfdir=/etc/bacula \
>>>      --with-dir-user=bacula \
>>>      --with-dir-group=bacula \
>>>      --with-sd-user=bacula \
>>>      --with-sd-group=bacula \
>>>      --with-fd-user=root \
>>>      --with-fd-group=root \
>>>      --with-dir-password="somepasswd" \
>>>      --with-fd-password="somepasswd" \
>>>      --with-sd-password="somepasswd" \
>>>      --with-mon-dir-password="somepasswd" \
>>>      --with-mon-fd-password="somepasswd" \
>>>      --with-mon-sd-password="somepasswd" \
>>>      --with-working-dir=/var/lib/bacula \
>>>      --with-scriptdir=/etc/bacula/scripts \
>>>      --with-smtp-host=localhost \
>>>      --with-subsys-dir=/var/lib/bacula/lock/subsys \
>>>      --with-pid-dir=/var/lib/bacula/run \
>>>      --enable-largefile \
>>>      --disable-tray-monitor \
>>>      --enable-build-dird  \
>>>      --enable-build-stored \
>>>      --with-openssl \
>>>      --with-tcp-wrappers \
>>>      --with-python \
>>>      --enable-smartalloc \
>>>      --with-x \
>>>      --enable-bat \
>>>      --disable-libtool \
>>>      --with-postgresql \
>>>      --with-readline=/usr/include/readline \
>>>      --disable-conio
>>>
>>> and can atest that everything works just fine although I only used NEW
>>> volumes with it. Maybe there is something amiss with your catalog or
>>> volume media?
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Igor Blažević
>>>
>>>
>>
>

-- 
Stephen Thompson               Berkeley Seismological Laboratory
stephen AT seismo.berkeley DOT edu    215 McCone Hall # 4760
404.538.7077 (phone)           University of California, Berkeley
510.643.5811 (fax)             Berkeley, CA 94720-4760



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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>