[Bacula-users] Fatal error: Cannot find previous jobids

I recently updated both the OS (Ubuntu 23.10 to 24.04), and switched from the community download of 13.0.4 to the Ubuntu 13.0.4 package that goes with 24.04 Backups of the Catalog and Full Client backups are working, but the incremental Client backups fail 05-Jun 23:05 orac-dir JobId 7830: C

[Bacula-users] Fatal error: sql_create.c:841

Hey guys, what's up? Could someone try to help me to identify why some of my jobs have this error below? This happen only sometimes. Fatal error: sql_create.c:841 Fill File table Query failed: INSERT INTO File (FileIndex, JobId, PathId, FilenameId, LStat, MD5, DeltaSeq) SELECT batch.FileIndex,

Re: [Bacula-users] Fatal error: MD5 digest not same FileIndex

Hello Elias, On 04.06.21 00:39, Elias Pereira wrote: Hello, I am having this error Fatalerror: MD5 digest not same FileIndexin a backup to aws S3. This backup is of files from a fileserver. Is there any way to disable this check or something like that? Your issue is not very precise, but I

[Bacula-users] Fatal error: MD5 digest not same FileIndex

Hello, I am having this error Fatal error: MD5 digest not same FileIndex in a backup to aws S3. This backup is of files from a fileserver. Is there any way to disable this check or something like that? -- Elias Pereira ___ Bacula-users mailing list Ba

Re: [Bacula-users] Fatal error: catreq.c:751 fread attr spool error. Wanted 1478509141 bytes, maximum permitted 10000000 bytes

Hi folks, Answering my own question. Installing bacula 9.2.2 solved this problem. Best regards, Peter On 2021-05-01 15:05, Peter Milesson wrote: Hi folks, When running monthly full backup on a Linux server, the following error occurred in the final steps of the backup process, when despool

[Bacula-users] Fatal error: catreq.c:751 fread attr spool error. Wanted 1478509141 bytes, maximum permitted 10000000 bytes

Hi folks, When running monthly full backup on a Linux server, the following error occurred in the final steps of the backup process, when despooling attributes. Previous log entry was: Sending spooled attrs to the Director. Despooling 180,651,607 bytes ... Fatal error: catreq.c:751 fread att

Re: [Bacula-users] Fatal error on catalogue backup

On Tuesday, 04 February 2020 17:58:26 SAST Martin Simmons wrote: > It looks like your Storage Daemon (TapeServer) is runnning an older Bacula > version than your Director (trooper-dir). Bacula expects the versions to be > the same. Thanks, all working fine after yum update. Cheers, Ian -- i..

Re: [Bacula-users] Fatal error on catalogue backup

On Tuesday, 04 February 2020 17:58:26 SAST Martin Simmons wrote: > It looks like your Storage Daemon (TapeServer) is runnning an older Bacula > version than your Director (trooper-dir). Bacula expects the versions to be > the same. Ah. I thought it was perhaps some piece of hardware like a cable

Re: [Bacula-users] Fatal error on catalogue backup

> On Sat, 01 Feb 2020 00:15:07 +0200, Ian Douglas said: > > hi all > > Can someone who knows please advise if this is an issue with my database, my > tape server, the tape machine, or the tape? > > The director machine (this machine) died (power failure) without being shut > down properly.

[Bacula-users] Fatal error on catalogue backup

hi all Can someone who knows please advise if this is an issue with my database, my tape server, the tape machine, or the tape? The director machine (this machine) died (power failure) without being shut down properly. Tape server is HP, as is tape drive. Tape was out of drive, and I shut down

Re: [Bacula-users] Fatal error on catalogue backup

On Saturday, 01 February 2020 00:15:07 SAST you wrote: > I've tried a few times, including restarting MariaDB and the tape machine. I mean Postgresql. Keep forgetting Bacula runs with Postgresql :-) Thanks, Ian -- i...@zti.co.za http://www.zti.co.za Zero 2 Infinity - The net.works Phone +27-21

Re: [Bacula-users] Fatal error: Version error for database "bacula". Wanted 16, got 15

Oops, my error.  I was looking at a file that was created with the Enterprise Source. The correct version for the current community version is actually 16 (not 1019, which is the BEE version). Anyway, I see that your problem is resolved. Best regards, Kern On 11/08/2017 03:44 PM, Kern Sib

Re: [Bacula-users] Fatal error: Version error for database "bacula". Wanted 16, got 15

Either it is a Bacula bug, or you are not using version 9.0.x On 11/08/2017 02:40 PM, bernhard.glomm wrote: UPDATE Version SET VersionId=1019; why is that so when bacula-director want version 16 instead of 15 as said in the logfile "Fatal error: Version error for database "bacula". Wanted 1

Re: [Bacula-users] Fatal error: Version error for database "bacula". Wanted 16, got 15

UPDATE Version SET VersionId=1019; why is that so when bacula-director want version 16 instead of 15 as said in the logfile "Fatal error: Version error for database "bacula". Wanted 16, got 15" On 2017-11-08 13:44, Kern Sibbald wrote: Hello, In source form the script may not be too useful

Re: [Bacula-users] Fatal error: Version error for database "bacula". Wanted 16, got 15

You could try: dpkg -S update_mysql_tables I think it should be here: /usr/share/bacula-director/update_mysql_tables __Martin > On Wed, 08 Nov 2017 11:58:14 +0100, bernhard glomm said: > > hi all > after a regular apt-get update && apt-get upgrade > on a "trusty" ubuntu system > the upgr

Re: [Bacula-users] Fatal error: Version error for database "bacula". Wanted 16, got 15

I use Git for compil from source. And to have a v9.x.x not in binary (?) ... i under CentOs 7.4 / Postgres Prod -> bacula v7.4.7 Test -> bacula v9.0.4 ( -> 9.0.5 at 20171102 ) Le 08/11/2017 à 13:23, bernhard.glomm a écrit : ?? you mean the script might be in the source packages but not in the

Re: [Bacula-users] Fatal error: Version error for database "bacula". Wanted 16, got 15

Hello, In source form the script may not be too useful because the paths are different for each packager.  I recommend that you look at your binary files as they should have included the script.  You can also do: find / -name "update_bacula_tables" if there are multiple copies, you will need

Re: [Bacula-users] Fatal error: Version error for database "bacula". Wanted 16, got 15

?? you mean the script might be in the source packages but not in the binary packages ?? bizarre but I will have a look On 2017-11-08 13:03, Olivier Delestre wrote: For me with bacula 7.4.7 /usr/local/src/bacula/bacula/src/cats/update_bacula_tables et grant_bacula_privileges ( with user postg

Re: [Bacula-users] Fatal error: Version error for database "bacula". Wanted 16, got 15

> hi all Hello, Bernhard, > after a regular apt-get update && apt-get upgrade > on a "trusty" ubuntu system > the upgrade of package bacula-director FAILED > with the following errors in bacula_daemon.log: > > 08-Nov 10:27 bacula-dir JobId 0: Fatal error: Version error for database > "bacula".

Re: [Bacula-users] Fatal error: Version error for database "bacula". Wanted 16, got 15

For me with bacula 7.4.7 /usr/local/src/bacula/bacula/src/cats/update_bacula_tables et grant_bacula_privileges ( with user postgres ) bacula=# select * from version; versionid --- 15 And 16 for version 9 (?) Le 08/11/2017 à 11:58, bernhard.glomm a écrit : hi all after a reg

[Bacula-users] Fatal error: Version error for database "bacula". Wanted 16, got 15

hi all after a regular apt-get update && apt-get upgrade on a "trusty" ubuntu system the upgrade of package bacula-director FAILED with the following errors in bacula_daemon.log: 08-Nov 10:27 bacula-dir JobId 0: Fatal error: Version error for database "bacula". Wanted 16, got 15 08-Nov 10:27 bac

Re: [Bacula-users] Fatal error: Pipe write error

> > Hello, I solved the problem. There was no restore path I had set up in the bpipe script. I use the webacula and in it I set up to replace the final path, but it did not work. -- Check out the vibrant tech community on

Re: [Bacula-users] Fatal error: Pipe write error

On 7/15/2017 7:51 AM, Elias Pereira wrote: hello kern, How can I test to see, for example, if the two ends are connected? Using the PID of the process that has the other end of the pipe open, use: ls -l /proc//fd You are likely seeing a permissions problem. Is the pipe writable by the user

Re: [Bacula-users] Fatal error: Pipe write error

hello kern, How can I test to see, for example, if the two ends are connected? On Thu, Jul 13, 2017 at 4:58 PM, Kern Sibbald wrote: > Hello, > > It appears to me that there is nothing on the other end of the pipe -- > i.e. the two ends are not connected. > > Best regards, > > Kern > > > > On 07

Re: [Bacula-users] Fatal error: Pipe write error

Hello, It appears to me that there is nothing on the other end of the pipe -- i.e. the two ends are not connected.  Best regards, Kern On 07/13/2017 09:49 PM, Elias Pereira wrote: hello, I'm t

[Bacula-users] Fatal error: Pipe write error

hello, I'm trying to perform a restore from a backup made through the bpipe plugin, but errors below always occur. 2017-07-13 16:33:49 vamp-dir JobId 2710: Start Restore Job RestoreFilesGenerico.2017-07-13_16.33.47_17 2017-07-13 16:33:49 vamp-dir JobId 2710: Using Device "freenasDev" to read.

Re: [Bacula-users] Fatal error while backup catreq.c:631

Title: Fatal error while backup catreq.c:631 Hello, There is some problem from your catalog.  What database catalog type are you using MySQL or Postgres?  It seems a bit unusual that it only prints "\". Do you have attribute spooling turned on?  If you do not, you

[Bacula-users] Fatal error while backup catreq.c:631

Hi all, recently I shifted my bacula director from a linux box to a qnap NAS. Everything went fine beside of the backup of 2 boxes. One is alinux box the other a qnap NAS. They're both trowing the same error catreq.c:631 Unfortunately I wasn't able to find anything about it via google. Hope

Re: [Bacula-users] Fatal error sql_create.c

Hello Ana, Thank you very much on detail description. I will set innodb_autoinc_lock_mode=2 and I will test this. I don’t use replication. Yes, I was build bacula with batch-insert. Batch insert works, I can see that when bacula send attributes and I show all process in mysql. Thank you very mu

Re: [Bacula-users] Fatal error sql_create.c

Hello Petar, I'm sorry I didn't give you details about the best value for ' innodb_autoinc_lock_mode' to use with bacula catalog. Having "innodb_autoinc_lock_mode=2" is the best option for performance of bulk INSERTs (you can see some INSERT...SELECT statements in the logs you sent here). I am

Re: [Bacula-users] Fatal error sql_create.c

Hello Petar, Please have a look here: http://bacula.10910.n7.nabble.com/innodb-autoinc-lock-mode-td82493.html Maybe the script for MySQL tunning can help with MariaDB too: https://github.com/major/MySQLTuner-perl Best regards, Ana On Thu, Apr 13, 2017 at 10:09 PM, Petar Kozić wrote: > I usin

Re: [Bacula-users] Fatal error sql_create.c

I using MariaDB 10.1. Which value of innodb_autoinc_lock_mode is best for Bacula, do you know ? *—* *Petar Kozić* System Administrator On April 13, 2017 at 10:04:23 PM, Ana Emília M. Arruda ( emiliaarr...@gmail.com) wrote: Hello Petar, Could you please let us know which Bacula/MySQL Databa

Re: [Bacula-users] Fatal error sql_create.c

Hello Petar, Could you please let us know which Bacula/MySQL Database version are you using? Maybe it would be a good idea to have a look at "innodb_autoinc_lock_mode " configuration.​ ​Best regards,

Re: [Bacula-users] Fatal error sql_create.c

Thank you on your answer. Yes I have about 80GB free in drive where is SD working directory. *—* *Petar Kozić* System Administrator On April 13, 2017 at 9:18:39 PM, Ana Emília M. Arruda ( emiliaarr...@gmail.com) wrote: Hi Petar, If you are using spool attributes, you need enough space in th

Re: [Bacula-users] Fatal error sql_create.c

Hi Petar, If you are using spool attributes, you need enough space in the SD working directory to store them before SD send attributes to Director. Could you please check if you have enough space in the SD working directory? Best regards, Ana On Wed, Apr 12, 2017 at 6:40 AM, Petar Kozić wrote:

Re: [Bacula-users] Fatal error sql_create.c

Yes, I have. I was upload on pasterbin: http://pastebin.ca/3794414 Log is contionous with same error. *—* *Petar Kozić* System Administrator On April 12, 2017 at 11:03:51 AM, Josip Deanovic (djosip+n...@linuxpages.net) wrote: On Wednesday 2017-04-12 01:07:41 Petar Kozić wrote: > @Josip Dean

Re: [Bacula-users] Fatal error sql_create.c

On Wednesday 2017-04-12 01:07:41 Petar Kozić wrote: > @Josip Deanovic > Are you using spooling? > If yes, is your spool directory on the same file system as your database > data? > > No, I don’t spooling Data, only Attributes > > My config: > Spool Data = no > Spool Attributes = yes > > > I was

Re: [Bacula-users] Fatal error sql_create.c

@Josip Deanovic Are you using spooling? If yes, is your spool directory on the same file system as your database data? No, I don’t spooling Data, only Attributes My config: Spool Data = no Spool Attributes = yes I was increase innodb_timewait_lockout = 150 but error appears again. Some ideas ?

Re: [Bacula-users] Fatal error sql_create.c

Thank you very much, I also think it is innodb_timeout is relevant for this problem, because I was get this error last week and when I increase timeout from 50 to 100 this problem was disappear. After few days I was restart mysql, but I still to add this statement in my.cnf and timeout was revert t

Re: [Bacula-users] Fatal error sql_create.c

> On Sunday 2017-04-09 02:49:41 Petar Kozić wrote: >> Hi, >> Can someone tell me why I get this error: >> >> Fatal error: sql_create.c:833 Fill File table Query failed: INSERT INTO >> File (FileIndex, JobId, PathId, FilenameId, LStat, MD5, DeltaSeq) SELECT >> batch.FileIndex, batch.JobId, Path.Pat

Re: [Bacula-users] Fatal error sql_create.c

Yes, I am using spooling, but I don't have define spooling directory. Director and mysql is on same server. Storage is on same but on different mount point LVM. On Apr 9, 2017 6:23 PM, "Josip Deanovic" wrote: On Sunday 2017-04-09 05:50:31 Petar Kozić wrote: > This happend only on Sunday when Bac

Re: [Bacula-users] Fatal error sql_create.c

On Sunday 2017-04-09 05:50:31 Petar Kozić wrote: > This happend only on Sunday when Bacula run scheduled full backup on > about 12 instances. Ofcorse, I have different run time in schedule, but > because some instances have lot data, in some time 2-3 instances works > in same time. > > I have over

Re: [Bacula-users] Fatal error sql_create.c

/tmp folder is on root where I have 70 GB free. On Apr 9, 2017 3:18 PM, "Gary R. Schmidt" wrote: > On 09/04/2017 22:50, Petar Kozić wrote: > > This happend only on Sunday when Bacula run scheduled full backup on > > about 12 instances. Ofcorse, I have different run time in schedule, but > > beca

Re: [Bacula-users] Fatal error sql_create.c

On 09/04/2017 22:50, Petar Kozić wrote: > This happend only on Sunday when Bacula run scheduled full backup on > about 12 instances. Ofcorse, I have different run time in schedule, but > because some instances have lot data, in some time 2-3 instances works > in same time. > > I have over 70GB

Re: [Bacula-users] Fatal error sql_create.c

This happend only on Sunday when Bacula run scheduled full backup on about 12 instances. Ofcorse, I have different run time in schedule, but because some instances have lot data, in some time 2-3 instances works in same time. I have over 70GB free space on mysql server and thats not problem. I’m a

Re: [Bacula-users] Fatal error sql_create.c

On Sunday 2017-04-09 02:49:41 Petar Kozić wrote: > Hi, > Can someone tell me why I get this error: > > Fatal error: sql_create.c:833 Fill File table Query failed: INSERT INTO > File (FileIndex, JobId, PathId, FilenameId, LStat, MD5, DeltaSeq) SELECT > batch.FileIndex, batch.JobId, Path.PathId, > F

[Bacula-users] Fatal error sql_create.c

Hi, Can someone tell me why I get this error: Fatal error: sql_create.c:833 Fill File table Query failed: INSERT INTO File (FileIndex, JobId, PathId, FilenameId, LStat, MD5, DeltaSeq) SELECT batch.FileIndex, batch.JobId, Path.PathId, Filename.FilenameId,batch.LStat, batch.MD5, batch.DeltaSeq FROM

Re: [Bacula-users] Fatal error when running script with arguments

On 21 November 2016 at 15:58, Gary R. Schmidt wrote: > On 22/11/2016 00:40, Kostis Fardelas wrote: >> 755 and extension is not needed. I have a lot of other scripts that do >> not have extensions, but none that calls a secondary script with >> arguments >> >> On 21 November 2016 at 15:06, Francisc

Re: [Bacula-users] Fatal error when running script with arguments

On 22/11/2016 00:40, Kostis Fardelas wrote: > 755 and extension is not needed. I have a lot of other scripts that do > not have extensions, but none that calls a secondary script with > arguments > > On 21 November 2016 at 15:06, Francisco Javier Funes Nieto > wrote: >> Permissions on the script f

Re: [Bacula-users] Fatal error when running script with arguments

On 11/21/2016 8:41 AM, Kostis Fardelas wrote: > $ICICMD has the full path. If I run the script from command line, the > script works. But if I let bacula run it, it throws a FATAL error. When the bacula-fd daemon launches your script, the script inherits its environment from the bacula-fd proces

Re: [Bacula-users] Fatal error when running script with arguments

what happens if you change your script to be ICICMD=$(/usr/bin/which ici) or even better run "which which" on the command line and change ICICMD to match the output. Misha On Mon, Nov 21, 2016 at 03:41:01PM +0200, Kostis Fardelas wrote: > $ICICMD has the full path. If I run the script from comm

Re: [Bacula-users] Fatal error when running script with arguments

$ICICMD has the full path. If I run the script from command line, the script works. But if I let bacula run it, it throws a FATAL error. On 21 November 2016 at 15:06, Bill Arlofski wrote: > On 11/21/2016 07:37 AM, Kostis Fardelas wrote: >> Hello community, >> I am trying to run a script as a Clie

Re: [Bacula-users] Fatal error when running script with arguments

755 and extension is not needed. I have a lot of other scripts that do not have extensions, but none that calls a secondary script with arguments On 21 November 2016 at 15:06, Francisco Javier Funes Nieto wrote: > Permissions on the script file? > The file finish with .sh extension? > > J. > > >

Re: [Bacula-users] Fatal error when running script with arguments

On 11/21/2016 07:37 AM, Kostis Fardelas wrote: > Hello community, > I am trying to run a script as a Client Run Before Job > > Client Run Before Job = "/etc/bacula/scripts/mysqlxtra_dt" > > The script: > #!/bin/sh > > ICICMD=$(which ici) > $ICICMD -dt 3600 -svc 'mysql-replication' > /dev/null >

Re: [Bacula-users] Fatal error when running script with arguments

Permissions on the script file? The file finish with .sh extension? J. 2016-11-21 13:37 GMT+01:00 Kostis Fardelas : > Hello community, > I am trying to run a script as a Client Run Before Job > > Client Run Before Job = "/etc/bacula/scripts/mysqlxtra_dt" > > The script: > #!/bin/sh > > ICICMD=$

[Bacula-users] Fatal error when running script with arguments

Hello community, I am trying to run a script as a Client Run Before Job Client Run Before Job = "/etc/bacula/scripts/mysqlxtra_dt" The script: #!/bin/sh ICICMD=$(which ici) $ICICMD -dt 3600 -svc 'mysql-replication' > /dev/null But the job keeps failing with: "ClientRunBeforeJob: /etc/bacula/scr

Re: [Bacula-users] Fatal error: askdir.c:373 NULL Volume name. This shouldn't

Hello Patti, Please see below ... On 05/06/2016 03:46 PM, Clark, Patti wrote: > No and no. I also don’t perform updates on my backup servers willy nilly. > > There are bugs in bacula regarding the "Null Volume name” error. I have > fewer contention issues with jobs requesting the same volume o

Re: [Bacula-users] Fatal error: askdir.c:373 NULL Volume name. This shouldn't

No and no. I also don’t perform updates on my backup servers willy nilly. There are bugs in bacula regarding the "Null Volume name” error. I have fewer contention issues with jobs requesting the same volume on different devices with some of the latest BEE versions. I expect that some of those

[Bacula-users] Fatal error: askdir.c:373 NULL Volume name. This shouldn't

If this ever happens to anyone else, see if either/both of these happened during one of the volume writes: 1. The disk which bacula uses for its logs became full 2. Someone did an apt-get update/dnf update or whatever during the backup. 1. Definitley just hit us so we had to start the whole job

Re: [Bacula-users] Fatal error: askdir.c:373 NULL Volume name. This shouldn't

> Thanks! > > device { >Maximum Changer Wait = 3d > } > > Hey that's interesting ... never heard of it before - do you think it will fix > my problem? I can set it to 30 days for this job Welcome back, Bill: there is not much research material about this askdir.c:373 error. It's clear

[Bacula-users] Fatal error: askdir.c:373 NULL Volume name. This shouldn't

Thanks! device { Maximum Changer Wait = 3d } Hey that's interesting ... never heard of it before - do you think it will fix my problem? I can set it to 30 days for this job +-- |This was sent by bill.dam...@yahoo.com vi

Re: [Bacula-users] Fatal error: askdir.c:373 NULL Volume name. This shouldn't

> Every time, it gets to about tape 10 or 11 in the set and the backup fails > with > this. Any clues what I can do to fix it please? > 13-Apr 02:41 tiger-sd JobId 6763: Fatal error: Too many tries: Wrong Volume > mounted on tape device "HP-ULTRIUM-LTO3-EXT2" (/dev/st1): Wanted > 001-014-58

[Bacula-users] Fatal error: askdir.c:373 NULL Volume name. This shouldn't

Fatal error: askdir.c:373 NULL Volume name. This shouldn't happen!!! Every time, it gets to about tape 10 or 11 in the set and the backup fails with this. Any clues what I can do to fix it please? 13-Apr 02:41 tiger-sd JobId 6763: Fatal error: Too many tries: Wrong Volume mounted on tape device

Re: [Bacula-users] Fatal Error on a job but I successfully set up 13 others...

omain > controller') ? > > Is the service actually running, or are you assuming so because it is set > to auto start? > It could fail to start for some reason. > > > -Original Message- > From: THEgame32 [mailto:bacula-fo...@backupcentral.com] > Sent: 02 J

Re: [Bacula-users] Fatal Error on a job but I successfully set up 13 others...

oller') ? Is the service actually running, or are you assuming so because it is set to auto start? It could fail to start for some reason. -Original Message- From: THEgame32 [mailto:bacula-fo...@backupcentral.com] Sent: 02 June 2015 22:22 To: bacula-users@lists.sourceforge.net Subject:

[Bacula-users] Fatal Error on a job but I successfully set up 13 others...

Let me prelude this by saying that I've been trying to fix this issue for a couple of weeks now. I will include the error then the files in this post... any suggestions will be appreciated... just can't figure it out since I have 13 other re-occurring jobs that worked just fine for me. Here is

Re: [Bacula-users] Fatal error: backup.c:975 Failed to initialize encryption context

--On Monday, January 26, 2015 01:46:07 PM -0600 ramesh penugonda wrote: > I am getting the encryption context error on a freebsd server when trying > to backup data encrypted. > > 1) when i run in daemon mode i get the encryption error > 26-Jan 19:33 bksrv1-dir JobId 123428: Start Backup Job

Re: [Bacula-users] Fatal error: backup.c:1019 Network send error to SD. ERR=Broken pipe

> First, thanks for everything. > I'm making a backup of a client hosted on a VPS. > When the task starts, it shows me this error: Fatal error: backup.c: 1019 > Network Error send to SD. ERR = Broken pipe > In another similar server, also in the same VPS I do not have the same > problem, > Rul

[Bacula-users] Fatal error: backup.c:1019 Network send error to SD. ERR=Broken pipe

First, thanks for everything. I'm making a backup of a client hosted on a VPS. When the task starts, it shows me this error: Fatal error: backup.c: 1019 Network Error send to SD. ERR = Broken pipe In another similar server, also in the same VPS I do not have the same problem, Rule out

[Bacula-users] Fatal error: backup.c:975 Failed to initialize encryption context

I am getting the encryption context error on a freebsd server when trying to backup data encrypted. 1) when i run in daemon mode i get the encryption error 26-Jan 19:33 bksrv1-dir JobId 123428: Start Backup JobId 123428, Job=bys01s1.2015-01-26_19.33.37_03 26-Jan 19:33 bksrv1-dir JobId 123428:

Re: [Bacula-users] Fatal error: label.c:464 Truncate error on device - ERR=No such file or directory

Hello all, I am using Bacula v5.2.6. My Storage Daemon runs on the same machine like the Director and writes to a NAS that is mounted via SSHFS. I had the some trouble with exactly this truncate error shown below. Writing to a volume on Directors HDD and truncating works, but not with the externa

Re: [Bacula-users] Fatal error: label.c:464 Truncate error on device - ERR=No such file or directory

Hello List. I followed the advice you gave and updated director and sd to the most current version to avoid this truncate error I reported before (see below). Too sad, we do have the same issue again. Do you have any more advice? Thank you! Stefan This is the current log: 29-Jul 23:30 backnix05

Re: [Bacula-users] Fatal error: askdir.c:355 NULL Volume name. This shouldn't happen!!!

On 07/22/2014 11:34 PM, Clark, Patricia A. wrote: > Sadly, this error is still present in v7.0.4. There is another error, too, > where there is no writeable media in the tape drive. > Fatal error: spool.c:263 Fatal append error on device "LTO5-2" > (/dev/tape-admin2): ERR=tape_dev.c:161 Unable t

[Bacula-users] Fatal error: askdir.c:355 NULL Volume name. This shouldn't happen!!!

Sadly, this error is still present in v7.0.4. There is another error, too, where there is no writeable media in the tape drive. Fatal error: spool.c:263 Fatal append error on device "LTO5-2" (/dev/tape-admin2): ERR=tape_dev.c:161 Unable to open device "LTO5-2" (/dev/tape-admin2): ERR=No medium

Re: [Bacula-users] Fatal error: label.c:464 Truncate error on device - ERR=No such file or directory

> Kern Sibbald hat am 18. Juli 2014 um 10:37 geschrieben: > > On 07/17/2014 08:41 PM, Stefan Lamby wrote: > > > > Got the point. > > I'll think about buying 2 more SATA HDs using software raid to store > > the precious Volumes on those. > > > > > That should work well. > >

Re: [Bacula-users] Fatal error: label.c:464 Truncate error on device - ERR=No such file or directory

On 07/17/2014 08:41 PM, Stefan Lamby wrote: Got the point. I'll think about buying 2 more SATA HDs using software raid to store the precious Volumes on those. That should work well. Btw., using md, is there someth

[Bacula-users] Fatal error: bsock.c:134 Unable to connect to Storage daemon

11-Jul 10:35 debian-dir JobId 3300: Start Backup JobId 3300, Job=WEB-SVR.2014-07-11_10.06.12_07 11-Jul 10:35 debian-dir JobId 3300: Using Device "DDS-4" 11-Jul 10:42 WEB-SVR JobId 3300: Warning: bsock.c:128 Could not connect to Storage daemon on ESS-Backup-Svr:9103. ERR=Connection timed out Retry

Re: [Bacula-users] Fatal error: label.c:464 Truncate error on device - ERR=No such file or directory

Got the point. I'll think about buying 2 more SATA HDs using software raid to store the precious Volumes on those. Btw., using md, is there something wrong with using it in partnership with bacula? Cheers, Stefan > Kern Sibbald hat am 17. Juli 2014 um 19:38 geschrieben: > > On 07/17/2014 10:3

Re: [Bacula-users] Fatal error: label.c:464 Truncate error on device - ERR=No such file or directory

On 07/17/2014 10:38 AM, Stefan Lamby wrote: You wrote writing Volumes directly to a CIFS mount is not really a good idea for a number of reasons. What do you recommend as best practice instead? Write your Volumes to a natively

Re: [Bacula-users] Fatal error: label.c:464 Truncate error on device - ERR=No such file or directory

Got you, thanks. Best regards, Stefan > Josh Fisher hat am 17. Juli 2014 um 14:12 geschrieben: > > On 7/17/2014 4:38 AM, Stefan Lamby wrote: > > > > You wrote writing Volumes directly to a CIFS mount is not really > > > a good idea for a number of reasons. > > What do you

Re: [Bacula-users] Fatal error: label.c:464 Truncate error on device - ERR=No such file or directory

On 7/17/2014 4:38 AM, Stefan Lamby wrote: You wrote writing Volumes directly to a CIFS mount is not really a good idea for a number of reasons. What do you recommend as best practice instead? Bacula reads/writes blocks of data.

Re: [Bacula-users] Fatal error: label.c:464 Truncate error on device - ERR=No such file or directory

You wrote writing Volumes directly to a CIFS mount is not really a good idea for a number of reasons. What do you recommend as best practice instead? Best regards, Stefan > Kern Sibbald hat am 10. Juli 2014 um 17:36 geschrieben: > > Unfortunately, neither CIFS nor NFS include a truncate() fun

Re: [Bacula-users] Fatal error: label.c:464 Truncate error on device - ERR=No such file or directory

Version 5.0.3 is quite old. You must upgrade the Director and all the SDs at the same time to the same version, as well as any FD on either the Dir or SD machine.  Other FDs do not need to be updated. Best regards, Kern On 07/10/20

Re: [Bacula-users] Fatal error: label.c:464 Truncate error on device - ERR=No such file or directory

Thank you very much for pointing this out. My Version is 5.0.3 and it is running at an opensuse 11.4 version. Could it work if I just compile a new sd executable and put the new one with depending libraries to that machine? Or to be more spefic: will director 5.0.3 and the other (old) components w

Re: [Bacula-users] Fatal error: label.c:464 Truncate error on device - ERR=No such file or directory

Unfortunately, neither CIFS nor NFS include a truncate() function, and this problem was not noticed because not many people write Volumes directly to a CIFS/NFS mount.  Doing so is not really a good idea for a number of reasons reasons.  Any way, onc

[Bacula-users] Fatal error: label.c:464 Truncate error on device - ERR=No such file or directory

Hello List. Once a week I got this error, when performing a backup. 19 out of 20 backup jobs work well, one fails. The nas_01 device is a small 1 TB NAS, mounted via fstab: //192.168.1.9/Volume_1 /nas01_backupcifs soft,username=**,password=**,uid=107,gid=107 0 0 The /nas01_backup

Re: [Bacula-users] fatal error

I think your next step here would be to restore a catalog backup using bscan, bextract etc. http://www.bacula.org/5.0.x-manuals/en/utility/utility/index.html Jeff. On Jul 3, 2014, at 4:32 PM, Dietz Pröpper wrote: > Am Donnerstag, 3. Juli 2014, 16:58:22 schrieb antonio.mannatzu: >> - -bash-4

Re: [Bacula-users] fatal error

Am Donnerstag, 3. Juli 2014, 16:58:22 schrieb antonio.mannatzu: > - -bash-4.1$ psql bacula > psql: FATAL: database "bacula" does not exist > DETAIL: The database subdirectory "base/16386" is missing. This looks like your database went corrupt. Not directly a bacula problem. regards Diet

[Bacula-users] fatal error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - -bash-4.1$ psql bacula psql: FATAL: database "bacula" does not exist DETAIL: The database subdirectory "base/16386" is missing. bash-4.1$ psql -l List of databases Name| Owner | Encoding | Collatio

Re: [Bacula-users] Fatal error: Authorization key rejected by Storage daemon

On 06/12/2014 05:38 PM, Thomas Lohman wrote: > I've seen this error before on and off on one particular client. > Nothing changes with regard to the configuration and yet the error will > crop up. Usually a combination of the following "fixes" it - > cancel/restart the job, restart the Bacula c

Re: [Bacula-users] Fatal error: Authorization key rejected by Storage daemon

I've seen this error before on and off on one particular client. Nothing changes with regard to the configuration and yet the error will crop up. Usually a combination of the following "fixes" it - cancel/restart the job, restart the Bacula client, or restart the Bacula storage daemon. Since

Re: [Bacula-users] Fatal error: Authorization key rejected by Storage daemon

Hi Benjamin, Do you have localhost in any of your bacula conf files? Regards, Ana On Tue, Jun 3, 2014 at 11:48 AM, benji49320 wrote: > Hi, > > I've problem with my Bacula server and my FD on my client-test server > (centos6-fd). When I try to run a job with BAT I've the following error : > >

[Bacula-users] Fatal error: Authorization key rejected by Storage daemon

Hi, I've problem with my Bacula server and my FD on my client-test server (centos6-fd). When I try to run a job with BAT I've the following error : centos6-fd Fatal error: Authorization key rejected by Storage daemon. Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.htm

Re: [Bacula-users] Fatal error: askdir.c:340 NULL Volume name. This shouldn't happen!!!

Hello, I believe this bug is present in version 7.0.3. I just had it happen last night, much like I saw about 2 years ago. I run 100s of incrementals each night across 2 LTO tap drives, running with a concurrency limit, so that jobs start whenever others are finished (i.e. I cannot stagger

Re: [Bacula-users] Fatal error: askdir.c:340 NULL Volume name. This shouldn't happen!!!

Hello Wolfgang, The drive is allocated first. Your analysis is correct, but obviously something is wrong. I don't think this is happening any more with the Enterprise version, so it will very likely be fixed in the next release as we will backport (or flowback) some rather massive changes we hav

Re: [Bacula-users] Fatal error: askdir.c:340 NULL Volume name. This shouldn't happen!!!

Dear Kern Sibbald, In message <5301db23.6010...@sibbald.com> you wrote: > > Were you careful to change the actual volume retention period in > the catalog entry for the volume? That requires a manual step after > changing the conf file. You can check two ways: Yes, I was. "list volumes" shows

Re: [Bacula-users] Fatal error: askdir.c:340 NULL Volume name. This shouldn't happen!!!

Hello Wolfgang, Were you careful to change the actual volume retention period in the catalog entry for the volume? That requires a manual step after changing the conf file. You can check two ways: 1. Look at the full output from all the jobs and see if any volumes were recycled while the batch

Re: [Bacula-users] Fatal error: askdir.c:340 NULL Volume name. This shouldn't happen!!!

Dear Kern, In message <20140216153143.2d773380...@gemini.denx.de> I wrote: > > > I did find and fix was related to a user setting an expiration time of > > exactly 1 > > or n days, which means at some point when he started a whole batch of > > new backup jobs, a volume that was being used was re

Re: [Bacula-users] Fatal error: askdir.c:340 NULL Volume name. This shouldn't happen!!!

Dear Kern, In message <52fe44c5.8080...@sibbald.com> you wrote: > > If you were not aware, one developer left Bacula. He had previously > be the most active on bugs and responsible for putting patches into > the community version. As you probably also heard as a result of his > departure, I fro

Re: [Bacula-users] Fatal error: askdir.c:340 NULL Volume name. This shouldn't happen!!!

In message <2014021328.76b4f380...@gemini.denx.de> I wrote: > > > ... Signing up to make a bug > > report is also broken and has been mentioned on this list. No message is > > sent that allows for verification and setting up an account. > > Confirmed

  1   2   3   4   >