On lundi, 23 janvier 2017 11.08:45 h CET Carsten Pache wrote: > Good morning, > > my backup configuration is as follows: > - Full backup on fridays > - Incremental backups on mondays/tuesdays/wednesdays/thursdays > - Backup to tape (using spool directory) > > This worked (more or less) fine for years. Since three weeks, however, the > full backup always stops with errors like the following ones: > 21-Jan 05:01 dasi-dir JobId 1763: Warning: Error updating job record. Query > failed: INSERT INTO Log (JobId, Time, LogText) VALUES (1763,'2017-01-21 > 05:00:57','dasi-dir JobId 1763: Error: sql_update.c:189 sql_update.c:189 > update UPDATE Job SET JobStatus=''f'',Level=''F'',EndTime=''2017-01-21 > 05:00:06'',ClientId=8,JobBytes=0,ReadBytes=0,JobFiles=0,JobErrors=2,VolSess > ionId=0,VolSessionTime=0,PoolId=8,FileSetId=6,JobTDate=1484971206,RealEndTim > e=''2017-01-21 05:00:06'',PriorJobId=0,HasBase=0,PurgedFiles=0 WHERE > JobId=1763 failed: no connection to the server > '): ERR=no connection to the server > 21-Jan 05:03 dasi-dir JobId 1763: Fatal error: sql_get.c:305 sql_get.c:305 > query SELECT > VolSessionId,VolSessionTime,PoolId,StartTime,EndTime,JobFiles,JobBytes,JobT > Date,Job,JobStatus,Type,Level,ClientId,Name,PriorJobId,RealEndTime,JobId,Fil > eSetId,SchedTime,RealEndTime,ReadBytes,HasBase,PurgedFiles FROM Job WHERE > JobId=1763 failed: no connection to the server > 21-Jan 05:04 dasi-dir JobId 1763: Warning: Error getting Job record for Job > report: ERR=Query failed: INSERT INTO Log (JobId, Time, LogText) VALUES > (1763,'2017-01-21 05:03:27','dasi-dir JobId 1763: Fatal error: > sql_get.c:305 sql_get.c:305 query SELECT > VolSessionId,VolSessionTime,PoolId,StartTime,EndTime,JobFiles,JobBytes,JobT > Date,Job,JobStatus,Type,Level,ClientId,Name,PriorJobId,RealEndTime,JobId,Fil > eSetId,SchedTime,RealEndTime,ReadBytes,HasBase,PurgedFiles FROM Job WHERE > JobId=1763 failed: no connection to the server > '): ERR=no connection to the server > 21-Jan 05:05 dasi-dir JobId 1763: Fatal error: sql_get.c:797 sql_get.c:797 > query SELECT ClientId,Name,Uname,AutoPrune,FileRetention,JobRetention FROM > Client WHERE Client.Name='srv-act-fd' failed: no connection to the server > > When I run the full backup jobs manually, they are running without errors. > > How can I solve the problem? > > Regards > Carsten Pache > It look like something is restarting your sql server. New packaging, logrotate script or whatever
I would monitor the db server and bareos-dir during your normal timeframe full backup, and recheck any cron script at that time. The fact that if you run it manually it works certainly during another timeframe would tend to prove that something is preventing bareos-dir to use the sql server at that time. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot openSUSE Tumbleweed Linux 4.9.3-1-default x86_64 GNU/Linux, nvidia: 375.26 Qt: 5.7.1, KDE Frameworks: 5.29.0, Plasma: 5.8.5, kmail2 5.4.0 -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
