Jason Dixon wrote:
a Packet size too big error. The Director resides on a global zone in
Solaris x86. I've managed to capture a truss during one of the
failures:
http://mirrors.omniti.com/bacula/bacula.truss
Very strange. Everything seems to be going normally:
14106/1:
Hi, Jason,
Just found this on SunSolve:
Solution Type Sun Alert
Solution 201321 : Solaris 10 Systems With Certain Patches
Installed May Experience Data Integrity Issues
Over TCP Loopback
1. Impact
Solaris 10 systems installed without patch 127111-03 or later
On Tue, Jan 27, 2009 at 10:36:05AM +, Allan Black wrote:
Hi, Jason,
Just found this on SunSolve:
Solution Type Sun Alert
Solution 201321 : Solaris 10 Systems With Certain Patches
Installed May Experience Data Integrity Issues
Over TCP Loopback
I
On Tue, Jan 27, 2009 at 12:37:36PM -0500, Jason Dixon wrote:
On Tue, Jan 27, 2009 at 10:36:05AM +, Allan Black wrote:
Hi, Jason,
Just found this on SunSolve:
Solution Type Sun Alert
Solution 201321 : Solaris 10 Systems With Certain Patches
Installed May
On Tue, Jan 27, 2009 at 10:12:03AM +, Allan Black wrote:
Jason Dixon wrote:
a Packet size too big error. The Director resides on a global zone in
Solaris x86. I've managed to capture a truss during one of the
failures:
http://mirrors.omniti.com/bacula/bacula.truss
...
[This is
[ Creating a fresh thread... ]
We moved our Bacula Director off Linux to Solaris (not my choice)
recently. Since then, we've encountered frequent failures of the
catalog backup job which reads from the local FD. They always fail with
a Packet size too big error. The Director resides on a
On Tue, Dec 23, 2008 at 04:36:00PM -0800, Conor Edberg wrote:
I saw some mention of these past problems during my research, so I
attempted to rule out network issues. In my case, the FD, SD, and dir are
all on the same machine, so I assume the problem isn't switches or cabling.
The
On Dec 9, 2008, at 2:36 PM, Jason Dixon wrote:
On Tue, Dec 09, 2008 at 09:26:38PM +, Allan Black wrote:
Jason Dixon wrote:
Alas, I spoke too soon. The CatalogBackup job failed again last
night,
usual symptoms.
OK. need to find out what the FD is doing. I would recommend:
truss -o
On Dec 23, 2008, at 11:53 AM, Conor Edberg wrote:
On Dec 9, 2008, at 2:36 PM, Jason Dixon wrote:
On Tue, Dec 09, 2008 at 09:26:38PM +, Allan Black wrote:
Jason Dixon wrote:
Alas, I spoke too soon. The CatalogBackup job failed again last
night,
usual symptoms.
OK. need to find out
On Dec 23, 2008, at 3:38 PM, Dan Langille wrote:
On Dec 23, 2008, at 11:53 AM, Conor Edberg wrote:
On Dec 9, 2008, at 2:36 PM, Jason Dixon wrote:
On Tue, Dec 09, 2008 at 09:26:38PM +, Allan Black wrote:
Jason Dixon wrote:
Alas, I spoke too soon. The CatalogBackup job failed again
On Fri, Dec 05, 2008 at 10:26:46PM -0500, Jason Dixon wrote:
One final report. Everything has been working fine since switching the
local FD to use the physical address (bge0) rather than loopback.
Sounds like a bug. If anyone needs further details, please let me know.
Alas, I spoke too
Jason Dixon wrote:
Alas, I spoke too soon. The CatalogBackup job failed again last night,
usual symptoms.
OK. need to find out what the FD is doing. I would recommend:
truss -o filename -f -a -e -v all -w 2 -p FD pid
Is it possible to run the catalog backup during the day, by hand?
That way
On Tue, Dec 09, 2008 at 09:26:38PM +, Allan Black wrote:
Jason Dixon wrote:
Alas, I spoke too soon. The CatalogBackup job failed again last night,
usual symptoms.
OK. need to find out what the FD is doing. I would recommend:
truss -o filename -f -a -e -v all -w 2 -p FD pid
Is it
On Wed, Dec 03, 2008 at 02:06:31PM -0500, Jason Dixon wrote:
On Wed, Dec 03, 2008 at 07:02:16PM +, Allan Black wrote:
Jason Dixon wrote:
Wouldn't it fail consistently in that case? It hasn't failed the last
two nights.
Good :-) Has it started working since you changed from
Jason Dixon wrote:
On Thu, Nov 27, 2008 at 01:01:12AM +0100, Kjetil Torgrim Homme wrote:
Jason Dixon [EMAIL PROTECTED] writes:
On Wed, Nov 26, 2008 at 11:59:41AM +0100, Kshatriya wrote:
recently. Since then, we've encountered frequent failures of the
catalog backup job which reads from the
On Wed, Dec 03, 2008 at 06:35:51PM +, Allan Black wrote:
Jason Dixon wrote:
On Thu, Nov 27, 2008 at 01:01:12AM +0100, Kjetil Torgrim Homme wrote:
Jason Dixon [EMAIL PROTECTED] writes:
On Wed, Nov 26, 2008 at 11:59:41AM +0100, Kshatriya wrote:
recently. Since then, we've encountered
Jason Dixon wrote:
Wouldn't it fail consistently in that case? It hasn't failed the last
two nights.
Good :-) Has it started working since you changed from localhost to
real host name?
Was it not just the catalog backup which was failing in this way?
Anyway, if it starts happening again, it
On Wed, Dec 03, 2008 at 07:02:16PM +, Allan Black wrote:
Jason Dixon wrote:
Wouldn't it fail consistently in that case? It hasn't failed the last
two nights.
Good :-) Has it started working since you changed from localhost to
real host name?
It has stopped failing since that change.
On Thu, Nov 27, 2008 at 01:01:12AM +0100, Kjetil Torgrim Homme wrote:
Jason Dixon [EMAIL PROTECTED] writes:
On Wed, Nov 26, 2008 at 11:59:41AM +0100, Kshatriya wrote:
On Mon, 24 Nov 2008, Jason Dixon wrote:
We moved our Bacula Director off Linux to Solaris (not my choice)
recently.
On Wed, Nov 26, 2008 at 11:59:41AM +0100, Kshatriya wrote:
On Mon, 24 Nov 2008, Jason Dixon wrote:
We moved our Bacula Director off Linux to Solaris (not my choice)
recently. Since then, we've encountered frequent failures of the
catalog backup job which reads from the local FD. They
On Mon, 24 Nov 2008, Jason Dixon wrote:
We moved our Bacula Director off Linux to Solaris (not my choice)
recently. Since then, we've encountered frequent failures of the
catalog backup job which reads from the local FD. They always fail with
a Packet size too big error, which seems to be
Jason Dixon [EMAIL PROTECTED] writes:
On Wed, Nov 26, 2008 at 11:59:41AM +0100, Kshatriya wrote:
On Mon, 24 Nov 2008, Jason Dixon wrote:
We moved our Bacula Director off Linux to Solaris (not my choice)
recently. Since then, we've encountered frequent failures of the
catalog backup job
Just a quick bump. Perhaps I should open a bug report?
Thanks,
Jason
On Mon, Nov 24, 2008 at 11:59:36AM -0500, Jason Dixon wrote:
We moved our Bacula Director off Linux to Solaris (not my choice)
recently. Since then, we've encountered frequent failures of the
catalog backup job which reads
We moved our Bacula Director off Linux to Solaris (not my choice)
recently. Since then, we've encountered frequent failures of the
catalog backup job which reads from the local FD. They always fail with
a Packet size too big error, which seems to be more common with
Windows hosts. Has anyone
24 matches
Mail list logo
