On Wed, 5 Dec 2007, Martin Simmons wrote:
If that is OK, then I suggest running the SD with debug level 200,
which
might give us a clue where the error occurs.
So far I have been unable to get it to fail using -d200, while it does
fail if I don't specify a debug level. Maybe there is a
On Wed, 5 Dec 2007, Martin Simmons wrote:
If that is OK, then I suggest running the SD with debug level 200, which
might give us a clue where the error occurs.
So far I have been unable to get it to fail using -d200, while it does
fail if I don't specify a debug level. Maybe there is a
On Wed, 5 Dec 2007, Martin Simmons wrote:
If that is OK, then I suggest running the SD with debug level 200, which
might give us a clue where the error occurs.
So far I have been unable to get it to fail using -d200, while it does
fail if I don't specify a debug level. Maybe there is a
On Wed, 5 Dec 2007 11:36:33 -0500 (EST), Steve Thompson said:
On Wed, 5 Dec 2007, [EMAIL PROTECTED] wrote:
I am still experiencing this problem on a regular basis; not every job
does this, but it seems a good 40% do each night.
[...]
05-Dec 03:33 escabot-fd JobId 8219: Fatal error:
On Wed, 5 Dec 2007 13:46:26 -0500 (EST), Steve Thompson said:
On Wed, 5 Dec 2007, Dan Langille wrote:
My first idea: different versions of SD and FD, with one trying to use a
command the other does not recognize.
What version is each of: bacula-dir, bacula-fd, bacula-sd
They are
On Wed, 5 Dec 2007, Steve Thompson wrote:
On Wed, 5 Dec 2007, Martin Simmons wrote:
On Wed, 5 Dec 2007 11:36:33 -0500 (EST), Steve Thompson said:
I see this very often as well, and I am using disk exclusively. It also
happens about 40% of the time, and has done since I started with
bacula at
On Wed, 5 Dec 2007, Steve Thompson wrote:
On Wed, 5 Dec 2007, Martin Simmons wrote:
On Wed, 5 Dec 2007 11:36:33 -0500 (EST), Steve Thompson said:
I see this very often as well, and I am using disk exclusively. It also
happens about 40% of the time, and has done since I started with bacula at
On Wed, 5 Dec 2007, Martin Simmons wrote:
On Wed, 5 Dec 2007 13:46:26 -0500 (EST), Steve Thompson said:
They are all the same at 2.2.4. It happens even in the case where
bacula-dir, bacula-fd and bacula-sd are running on the same machine.
Everything was rebuilt from source by myself, and
On Wed, 5 Dec 2007, Dan Langille wrote:
My first idea: different versions of SD and FD, with one trying to use a
command the other does not recognize.
What version is each of: bacula-dir, bacula-fd, bacula-sd
They are all the same at 2.2.4. It happens even in the case where
bacula-dir,
On Wed, 5 Dec 2007, [EMAIL PROTECTED] wrote:
I am still experiencing this problem on a regular basis; not every job
does this, but it seems a good 40% do each night.
[...]
05-Dec 03:33 escabot-fd JobId 8219: Fatal error: job.c:1811 Bad response
to Append Data command. Wanted 3000 OK data
I
On Wed, 5 Dec 2007, [EMAIL PROTECTED] wrote:
I am still experiencing this problem on a regular basis; not every job
does this, but it seems a good 40% do each night.
[...]
05-Dec 03:33 escabot-fd JobId 8219: Fatal error: job.c:1811 Bad response
to Append Data command. Wanted 3000 OK data
I am still experiencing this problem on a regular basis; not every job
does this, but it seems a good 40% do each night. I cleaned both of my
tape drives last night, but I still get the fatal errors. Here is another
example:
05-Dec 03:32 escabot-dir JobId 8219: BeforeJob: run command
Hi,
I am using Bacula 2.2.6 with a Spectra Logic T50 tape library (with 2 LTO3
drives). I have about 20 jobs that are run nightly, allowing Bacula to run
multiple jobs at once (one on each drive).
Here are my configuration files log:
http://esweb.mcc.edu/~marc.smith/bacula/
This seems to
Hello,
Note for Arno: 1.39.26+ does a better job of helping one diagnose these
problems by printing the full output from mtx when a failure occurs.
On Friday 10 November 2006 00:46, Arno Lehmann wrote:
Hi,
On 11/9/2006 7:25 AM, Ryan Novosielski wrote:
I've gotten this one... I'd love to
Hi,
On 11/9/2006 7:25 AM, Ryan Novosielski wrote:
I've gotten this one... I'd love to know what it is too. :)
Dat's an error
;-)
Jake Goerzen wrote:
What does it mean when this happens? and is there a way to fix it?
07-Nov 08:40 adam-dir: Start Backup JobId 369,
What does it mean when this happens?
07-Nov 08:40 adam-dir: Start Backup JobId 369,
Job=BackupACSRV.2006-11-07_08.40.54
07-Nov 08:40 adam-sd: 3301 Issuing autochanger loaded drive 0 command.
07-Nov 08:41 adam-sd: 3991 Bad autochanger loaded drive 0 command: ERR=Child
exited with code 1.
07-Nov
What does it mean when this happens? and is there a way to fix it?
07-Nov 08:40 adam-dir: Start Backup JobId 369,
Job=BackupACSRV.2006-11-07_08.40.54
07-Nov 08:40 adam-sd: 3301 Issuing autochanger loaded drive 0 command.
07-Nov 08:41 adam-sd: 3991 Bad autochanger loaded drive 0 command:
I've gotten this one... I'd love to know what it is too. :)
Jake Goerzen wrote:
What does it mean when this happens? and is there a way to fix it?
07-Nov 08:40 adam-dir: Start Backup JobId 369,
Job=BackupACSRV.2006-11-07_08.40.54
07-Nov 08:40 adam-sd: 3301 Issuing autochanger loaded
Hello,
I try to get bacula running on a Centos 4 running. I have VXA2
autochanger. I went through the manuals, and everything seems to work
fine. I started backup job and it looked very good. After the test run,
I changed my bacula-dir.conf to add another client and change what has
to be
Hello,
I try to get bacula running on a Centos 4 running. I have VXA2
autochanger. I went through the manuals, and everything seems to work
fine. I started backup job and it looked very good. After the test
run, I changed my bacula-dir.conf to add another client and change
what has to be backed
On Monday 09 October 2006 13:53, Robert Keidel wrote:
I try to get bacula running on a Centos 4 running. I have VXA2
autochanger. I went through the manuals, and everything seems to work
fine. I started backup job and it looked very good. After the test
run, I changed my bacula-dir.conf to
On Monday 09 October 2006 20:53, Robert Keidel wrote:
Hello,
I try to get bacula running on a Centos 4 running. I have VXA2
autochanger. I went through the manuals, and everything seems to work
fine. I started backup job and it looked very good. After the test
run, I changed my
I seem to be past the Appendable media issue I've been having - now
I'm getting something totally different when I try and run this
backup:
You have messages.
*
*
*
*messages
02-Oct 13:59 bacula-atl2-sd: 3302 Autochanger loaded drive 0, result
is Slot 8.
02-Oct 13:59 bacula-atl2-sd:
On Tue, 5 Sep 2006, Arno Lehmann wrote:
I get several messages like these on dmesg:
(scsi2:A:15:0): data overrun detected in Data-in phase. Tag == 0x3.
(scsi2:A:15:0): Have seen Data Phase. Length = 50. NumSGs = 1.
sg[0] - Addr 0x11c3b8000 : Length 50
These are SCSI errors and it's
Thank you Alan and Arno, for your help.
Although I made a kernel update, i checked the the data cable. Is was
slightly disconnected. Probably that was the problem.
Now those dmesg messages are gone.
Now I have a tape with volStatus =Error.
What now? What you recommend? delete the jobs associated
On Wed, 6 Sep 2006, Jaime Ventura wrote:
Although I made a kernel update, i checked the the data cable. Is was
slightly disconnected. Probably that was the problem.
very likely.
Now I have a tape with volStatus =Error.
What now? What you recommend? delete the jobs associated with that tape
Hello,
Im backing up data to tape using a tapeloader, and im experiencing
the following problem:
05-Sep 09:38 isep-dir: Start Backup JobId 498,
Job=jtgv-gsi.2006-09-05_09.38.17
05-Sep 09:38 localhost-sd: 3301 Issuing autochanger loaded drive 0
command.
05-Sep 09:38 localhost-sd: 3302
Hello,
On 9/5/2006 10:44 AM, Jaime Ventura wrote:
Hello,
Im backing up data to tape using a tapeloader, and im experiencing
the following problem:
05-Sep 09:38 isep-dir: Start Backup JobId 498,
Job=jtgv-gsi.2006-09-05_09.38.17
05-Sep 09:38 localhost-sd: 3301 Issuing autochanger
Arno Lehmann,
Thanks for you reply.
Im using RHEL 4 x86_64 with a dell powervault 124T.
Im using bacula for some time backing up to disk.
Now i bought a a dell powervault 124T so i can make backups to tape.
So, im newbe to tape issues.
Im on a test environment... making
: [Bacula-users] Bad response to Append Data command
Arno Lehmann,
Thanks for you reply.
Im using RHEL 4 x86_64 with a dell powervault 124T.
Im using bacula for some time backing up to disk.
Now i bought a a dell powervault 124T so i can make backups to tape.
So, im newbe to tape
] Bad response to Append Data command
Thanks for your reply.
I've already installer and heavily tested the tapeloader with bacula.
I've done lots of backups to tape. All worked ok.
Then I went on vacation, and when I came I was getting this error.
I cant figure out what happened
, 05 Sep 2006 12:59:57 +0100
Subject: Re: [Bacula-users] Bad response to Append Data command
Thanks for your reply.
I've already installer and heavily tested the tapeloader with bacula.
I've done lots of backups to tape. All worked ok.
Then I went on vacation, and when I came I
:
From: Jaime Ventura [EMAIL PROTECTED]
To: Uwe Schuerkamp [EMAIL PROTECTED]
Cc: Arno Lehmann [EMAIL PROTECTED],
Bacula Users bacula-users@lists.sourceforge.net
Date: Tue, 05 Sep 2006 12:59:57 +0100
Subject: Re: [Bacula-users] Bad response to Append Data command
Thanks for your reply.
I've
Kern,
thanks for your quick reply.
On Thursday 03 November 2005 19:33, Kern Sibbald wrote:
It looks like you stumbled into a change they made in the 2.6 kernel,
which will undoubtely cause a lot of people a *lot* of pain. The change
prohibits a program from opening a drive in read/write mode
On Friday 04 November 2005 09:15, Christoph Haas wrote:
Kern,
thanks for your quick reply.
On Thursday 03 November 2005 19:33, Kern Sibbald wrote:
It looks like you stumbled into a change they made in the 2.6 kernel,
which will undoubtely cause a lot of people a *lot* of pain. The change
Hello,
It looks like you stumbled into a change they made in the 2.6 kernel, which
will undoubtely cause a lot of people a *lot* of pain. The change prohibits
a program from opening a drive in read/write mode if there is no volume in
the drive.
If this is what is causing your problem, you
This error is appearing more and more. Sometimes the backups run,
sometimes I get the following error: We are obviously writing data to
a file, other backups are running on the machine. I am perplexed
since sometimes it works, other times it fails.
23-Aug 20:36 vortech-dir: Start Backup JobId
37 matches
Mail list logo
