Andrea Venturoli wrote:
> Frank Sweetser ha scritto:
> 
>> I would suggest starting it up manually in a terminal with debug output
>> enabled.  The -f option will keep it in the foreground, and -d100 will set 
>> the
>> debug level to 100 (a good start).  Using the script command will make it 
>> easy
>> to capture all of the output to a file as well.
>>
> 
> I've done this.
> Apart from the obvious fact that it is crashing, I cannot make too much 
> sense of this data.
> Here it is for anyone interested: http://netfence.it/bacula.log

It looks like it attempted a traceback, which would have the really useful
debugging information.  Did you by any chance get an email from Bacula which
contained the traceback?

-- 
Frank Sweetser fs at wpi.edu  |  For every problem, there is a solution that
WPI Senior Network Engineer   |  is simple, elegant, and wrong. - HL Mencken
    GPG fingerprint = 6174 1257 129E 0D21 D8D4  E8A3 8E39 29E3 E2E8 8CEC

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users