On Wednesday 11 April 2007 17:57:45 Michael Proto wrote:
Any more ideas on getting the -fd to actually spit-out debug information
is very welcome, and thanks again for all the help!
Are you running SELinux ? On recent RH platforms, you might want to
search /var/log/audit/audit.log and/or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Getting closer on this, but not quite there yet. More info below
Arno Lehmann wrote:
Hi,
On 4/9/2007 10:23 PM, Michael Proto wrote:
Sorry I'm so late in replying back to this thread, I've had a number of
long-running full backups running on my
Hi,
On 4/9/2007 10:23 PM, Michael Proto wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry I'm so late in replying back to this thread, I've had a number of
long-running full backups running on my Bacula 2.0.3 server that I
didn't want to touch until completed.
I know the
-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:
30-Mar
Looks like you are having a socket timeout error. Put in the Heartbeat
Interval on the director config so it will keep the channel open and
see if that helps.
Jason
Michael Proto wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
I'm seeing a strange problem with my
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
