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

[Marco v. W. <mv...@pl...>]

Jean-François Leroux <leroux.jeanfrancois <at> gmail.com> writes:

> 
> 
> Sorry, forgot the title in my former message. Here it goes again.Hi
list,Here's my setup : DIR, SD and FD are on different 
> virtual machines. They are debian squeeze vservers (all of them). Until 
> recently, we were running 2.4.4.1 (lenny) and everything was fine. I had
>  to update some servers in squeeze, so I also created new virtual 
> machines and configured them with bacula (DIR/SD), version 5.0.2-2.2+b1 
> and configured my clients with the corresponding FD.Now the problem :When
executing a backup for big servers (100 Gb +), I get this error :Fatal error:
sql_create.c:800 sql_create.c:800 insert -- followed by the mysql query.Then
:Fatal error: catreq.c:497 attribute create error. sql_find.c:376 Request for
Volume item 1 greater than max 0 or less than 1
> 
> 13-Jun 18:01 unisson.private.tice.ac-orlea JobId 170: Fatal error: 
> Network error with FD during Backup: ERR=Interrupted system call13-Jun 18:01
unisson.private.tice.ac-orlea JobId 170: Fatal error: No Job status returned
from FD.
> 13-Jun 18:01 unisson.private.tice.ac-orlea JobId 170: Fatal error: 
> sql_get.c:373 sql_get.c:373 query SELECT VolumeName,MAX(VolIndex) FROM 
> JobMedia,Media WHERE JobMedia.JobId=170 AND 
> JobMedia.MediaId=Media.MediaId GROUP BY VolumeName ORDER BY 2 ASC 
> failed:
> Got error 28 from storage engine

Try a google search for "error 28 mysql" and you will find out its
a known mysql error for telling you run out of space. So I would
search in the mysql space first something is filling probably some
temp space.

Marco