On Sunday 24 December 2006 02:32, Brian Minard wrote:
> Hello,
>
> I keep running into a "Spool block too big" error. I am running
> FreeBSD 6.2-PRERELEASE #1: Sat Oct 28 16:07:28 EDT 2006 with the
> bacula port 1.38.11_3. I have run all 9 of the tape testing steps and
> the problem has never appeared when jobs are not run concurrently.
> Messages from the storage daemon are:
>
> 23-Dec 16:58 client1-sd: Committing spooled data to Volume
> "A0000007". Despooling 6,615,803,396 bytes ...
> 23-Dec 16:58 client1-sd: client2-backup.2006-12-23_15.24.47 Fatal
> error: spool.c:320 Spool block too big. Max 64512 bytes, got 569964745
> 23-Dec 16:58 client2-fd: client2-backup.2006-12-23_15.24.47 Fatal
> error: job.c:1617 Bad response to Append End command. Wanted 3000 OK
> end, got [truncated in the logs]
> 23-Dec 16:58 client1-dir: client2-backup.2006-12-23_15.24.47 Error:
> Bacula 1.38.11 (28Jun06): 23-Dec-2006 16:58:55
Have you modified the default network buffer size?
>
> bacula-dir.conf:
>
> Director {
> Name = client1-dir
> DIRport = 9101
> DIRAddress = 10.10.10.12
> QueryFile = "/usr/local/share/bacula/query.sql"
> WorkingDirectory = "/var/db/bacula"
> PidDirectory = "/var/run"
> Maximum Concurrent Jobs = 5
> Password = "password"
> Messages = Daemon
> }
>
> JobDefs {
> Name = "WeeklyCycle"
> Maximum Concurrent Jobs = 5
> Type = Backup
> Pool = Default
> Storage = Exabyte
> Messages = Standard
> Max Start Delay = 22h
> SpoolData = yes
> Schedule = "WeeklyCycle"
> FileSet = "Full Set"
> Priority = 1
> }
>
> Job {
> JobDefs = WeeklyCycle
> Name = "client2-backup"
> Client = client2-fd
> Write Bootstrap = "client2.bsr"
> }
>
> Client {
>
> Name = client2-fd
> Address = client2
> FDPort = 9102
> Catalog = Catalog
> Password = "password1"
> Maximum Concurrent Jobs = 5
> }
>
> There are 5 clients with basically the same definition. Random spool
> failures occur on one or two of them from time to time. Occurs during
> full backups.
>
> Checked out the suggestions on the mailing list (http://www.mail-
> archive.com/[email protected]/msg01015.html):
>
> 1/ only one storage daemon.
> 2/ lots of space on the disk. No chance that if filled when this
> problem occurred.
> 3/ no.
> 4/ don't think so.
> 5/ don't know, but unlikely.
> 6/ no complaints.
Unfortunately, these make no sense since you did not include the context (I
have no idea what 1/, 2/, ... are).
>
> TIA,
> Brian
>
>
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
