John Lockard wrote:
> On Fri, May 15, 2009 at 04:28:23PM -0400, John Lockard wrote:
>> On Fri, May 15, 2009 at 01:30:57PM +0200, Bruno Friedmann wrote:
>>> John Lockard wrote:
Hi all,
Saw this last night. What would cause these Fatal errors?
Server: Linux 2.6.18 x86_64
>>>
On Fri, May 15, 2009 at 04:28:23PM -0400, John Lockard wrote:
> On Fri, May 15, 2009 at 01:30:57PM +0200, Bruno Friedmann wrote:
> > John Lockard wrote:
> > > Hi all,
> > >
> > > Saw this last night. What would cause these Fatal errors?
> > >
> > > Server: Linux 2.6.18 x86_64
> > > Bacula Versio
On Fri, May 15, 2009 at 01:30:57PM +0200, Bruno Friedmann wrote:
> John Lockard wrote:
> > Hi all,
> >
> > Saw this last night. What would cause these Fatal errors?
> >
> > Server: Linux 2.6.18 x86_64
> > Bacula Version:
> > Server: 3.0.0
> > Client: 2.4.4 (SPARC Solaris 8)
> > Filesystem:
John Lockard wrote:
> Hi all,
>
> Saw this last night. What would cause these Fatal errors?
>
> Server: Linux 2.6.18 x86_64
> Bacula Version:
> Server: 3.0.0
> Client: 2.4.4 (SPARC Solaris 8)
> Filesystem: just under 1TB
>
> Thanks for any help,
> John
>
> 13-May 22:25 tibor-sd JobId 383
On Thu, May 14, 2009 at 03:54:55PM -0400, John Drescher wrote:
> On Thu, May 14, 2009 at 2:26 PM, John Lockard wrote:
> > Hi all,
> >
> > Saw this last night. What would cause these Fatal errors?
> >
>
> Possible database corruption.
Other backups after this and concurrent ran fine. I am
consi
On Thu, May 14, 2009 at 2:26 PM, John Lockard wrote:
> Hi all,
>
> Saw this last night. What would cause these Fatal errors?
>
Possible database corruption.
John
--
The NEW KODAK i700 Series Scanners deliver under ANY
Hi all,
Saw this last night. What would cause these Fatal errors?
Server: Linux 2.6.18 x86_64
Bacula Version:
Server: 3.0.0
Client: 2.4.4 (SPARC Solaris 8)
Filesystem: just under 1TB
Thanks for any help,
John
13-May 22:25 tibor-sd JobId 3833: Labeled new Volume "Monthly-SIN-0363" on
dev
DAve wrote:
> Good morning. I have begun getting an error I cannot seem to track down.
> It seems that the job runs fine, the volumes fill, but when the job
> finishes Bacula is unable to write the completion because the job no
> longer exists. It looks to me like Bacula is purging the jobs too
Good morning. I have begun getting an error I cannot seem to track down.
It seems that the job runs fine, the volumes fill, but when the job
finishes Bacula is unable to write the completion because the job no
longer exists. It looks to me like Bacula is purging the jobs too soon.
The error I g
> On Fri, 8 Apr 2005 12:45:12 +0300, viktorija <[EMAIL PROTECTED]> said:
V> New FileSet looks like:
V> FileSet {
V> Name = "poh"
V> Include {
V> Options {
V> compression=GZIP
V> @exclude.list
V>
On Fri, 8 Apr 2005, viktorija wrote:
New FileSet looks like:
FileSet {
Name = "poh"
Include {
Options {
compression=GZIP
@exclude.list
exclude = yes
}
File = /etc
New FileSet looks like:
FileSet {
Name = "poh"
Include {
Options {
compression=GZIP
@exclude.list
exclude = yes
}
File = /etc
File = /opt
I have removed exclude set at all, and it doesn't help. I upgraded bacula on
client side to 1.36.2 and it doesn't help.
It seems problem somewhere in configuration. I don't know.
But what does it mean:
FD gave bad response to Include command: wanted 2000 OK include got: 2999
Invalid command ?
V
Another thing to try is to add a separate exclude block to the fileset.
/Jens
> So nobody knows what does it mean?
>
> 08-Apr 11:08 backup-dir: Start Backup JobId 341, Job=poh.2005-04-08_11.08.34
> 08-Apr 11:08 backup-dir: poh.2005-04-08_11.08.34 Fatal error: FD gave bad
> response to Include
What happens if you replace the "@" with a "<" ?
/Jens
> So nobody knows what does it mean?
>
> 08-Apr 11:08 backup-dir: Start Backup JobId 341, Job=poh.2005-04-08_11.08.34
> 08-Apr 11:08 backup-dir: poh.2005-04-08_11.08.34 Fatal error: FD gave bad
> response to Include command: wanted 2000 O
So nobody knows what does it mean?
08-Apr 11:08 backup-dir: Start Backup JobId 341, Job=poh.2005-04-08_11.08.34
08-Apr 11:08 backup-dir: poh.2005-04-08_11.08.34 Fatal error: FD gave bad
response to Include command: wanted 2000 OK include
got: 2999 Invalid command
Viktorija
On Fri, 8 Apr 2005 1
As i said before.
I got following error trying to make Full Backup from different servers with
versions 1.36.2 and 1.34.2. Bacula server is 1.36.2.
These errors started after i have changed my director configuration from old to
new syntax and added @exclude.list. With old configuration file all w
What's working and what's not? Can you see any pattern (backuplevel, OS etc) It
might be compatibility issues between 1.36.2 and 1.34.2.
/Jens
> On server side is 1.36.2
>
> On client side machines are Solaris, FreeBSD and Linux with following
> versions: 1.36.2 and 1.34.2
>
> Incremintal j
On server side is 1.36.2
On client side machines are Solaris, FreeBSD and Linux with following versions:
1.36.2 and 1.34.2
Incremintal jobs working fine, but Full jobs not :(
Viktorija
On Fri, 8 Apr 2005 08:54:41 +0200
Jens R. Victorin <[EMAIL PROTECTED]> wrote:
> What version/s are you usi
What version/s are you using (i.e dir,fd etc.)?
/Jens
> Hello,
>
> am trying to backup and am getting following errors:
>
> 07-Apr 23:39 backup-dir: No prior Full backup Job record found.
> 07-Apr 23:39 backup-dir: No prior or suitable Full backup found. Doing FULL
> backup.
> 07-Apr 23:39 bac
Hello,
am trying to backup and am getting following errors:
07-Apr 23:39 backup-dir: No prior Full backup Job record found.
07-Apr 23:39 backup-dir: No prior or suitable Full backup found. Doing FULL
backup.
07-Apr 23:39 backup-dir: Start Backup JobId 311, Job=dizzy.2005-04-07_22.05.19
07-Apr 23
Hello,
am trying to backup and am getting following errors:
07-Apr 23:39 backup-dir: No prior Full backup Job record found.
07-Apr 23:39 backup-dir: No prior or suitable Full backup found. Doing FULL
backup.
07-Apr 23:39 backup-dir: Start Backup JobId 311, Job=dizzy.2005-04-07_22.05.19
07-Apr 23
22 matches
Mail list logo
