Hi, On 4/3/2007 12:04 AM, Michael Proto wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello all, > > I'm seeing a strange problem with my bacula-fd clients after upgrading > all of my systems to v2.0.3 (client and server). Intermittently, when > performing a backup of some random client I'll see the following error > in the Director: ... snip detailed problem description, where I don't know what might be the *real* reason beyond the problem... > I built and packaged all the Bacula Linux clients myself (so they all > pull from the same set of config files for quick installation), and I > used the following compile-time flags when building them: > > - --with-openssl --enable-client-only --enable-static-fd --enable-smartalloc > > I'm using the static-bacula-fd binary (instead of the bacula-fd binary)
Have you checked that the binary is really completely static? Lat time I tried I could not create a static binary of the FD, the one I could come up with was created under a really old linux/gcc/glibc combination, and lacked ACL support. If your binary pulls in shared objects, version differences there might be related to the problem. Of course, trying the heartbeat interval setting will be the most useful first step. I'm can't prove that, but I have the impression that Bacula reacts more sensitive to network problems recently. Might be because it's more efficient, and so leaves the TCP connections idling longer, or something... > for maximum portability. They were built on a Debian Sarge host and then > packaged into appropriate distribution packages. > > On one of the often-affected hosts I now have the client started with > the following flags (out of /etc/inittab): > > /sbin/static-bacula-fd -fvc -d100 /etc/bacula/bacula-fd.conf >> /tmp/bacula-fd.out > > When the client fails, I see the modification timestamp update on the > resultant /tmp/bacula-fd.out file, but its currently empty. Do I need to > redirect stderr to this file instead of stdout? It wouldn't do any harm redirecting *both* :-) > Anyone have any ideas what might be causing these errors or how I can go > about debugging this unusual (and while not critical, still very > annoying) problem? Check your system logs... I found some cases where Baculas components were killed because the used more memory than was healthy... the DIR mainly, but I have seen cases where I suspect the SD... no details available, unfortunately. Arno > > > Thanks! > Michael Proto > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (FreeBSD) > > iD8DBQFGEX3TOLq/wl1XW74RAmOeAJ9U9+O6kNDDp3LBVGyBHvD7Lt+JvgCdFsrI > f8IzD/gUPS0/F4dGgeIZ7J4= > =NcOC > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
