Hello,

16.07.2007 13:46,, Kern Sibbald wrote::
> On Monday 16 July 2007 13:17, Arno Lehmann wrote:
>> Hello,
...
>>> Yes, either a kernel problem or a hardware problem seem the most likely.  
> We 
>>> cannot exclude a Bacula bug, but the finger is pointing to the 
> CPU/hardware.
>> Well, this is problematic... Alfredo gave good reasons to assume that 
>> it's not purely hardware/OS related. Basically, the problem occurs 
>> when he runs certain jobs.
> 
> I didn't see that, but then I am no longer receive any email from the 
> bacula-users list.

Yes. I know, but it's hard moderating a discussion across two separate 
mailing list :-)

>> I guess that the interworking of DIR, SD, catalog database, and OS 
>> might trigger some sort of resource exhaustion, but debugging this is 
>> beyond my abilities :-)
> 
> Or as I mentioned, it could be that Bacula is self destructing ...
> 
>>> I recommend shutting down your machine, rebooting it, running memtest, and 
> if 
>>> all is OK, restarting Bacula and see what happens.
>> Fortunately, that's not my machine :-)
>>
>> Unfortunately, my backup server is dying, but I know and understand 
>> that problem :-(
> 
> If you and he *really* think it is a Bacula bug, I'd *strongly* recommend 
> that 
> he upgrade to the latest 2.1.26 beta version.

Ok... Alfredo, I suggest you try this. Upgrade and see what happens. 
If the problem occurs again after two weeks, use the (then-generated) 
trace file and strace output to file a bug report.

Also, I recommend to closely watch the mailing list for possible 
updates of the code... it would not be uncommon that some interesting 
bugs are found shortly after the final beta or the release version is 
published.

>  IMO (aside from the Win32 
> testing problem -- the old FD daemons do not need to be upgraded) it is ready 
> for production use, and I've knocked off 3 or 4 memory overrun problems -- 
> particularly one in PostgreSQL.  So before declaring it a bug, it is 
> important to reproduce it on 2.1.26 or later.

Good... I send this to the users list, too, so Alfredo can notice it :-)

Arno

PS: And in case the select() fails again like this, make sure you 
subscribe to the developers list, too - this bug might be one needing 
some communication between the developers and the one with the 
reproducible problem.


-- 
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to