On 11/01/2013 01:01 PM, John Drescher wrote:
> On Fri, Nov 1, 2013 at 1:51 PM, Dimitri Maziuk wrote:
>>
>> After yum updating postgres:
>>
>> 01-Nov 10:04 rendena-sd JobId 568: Writing spooled data to Volume.
>> Despooling 49,807,364,626 bytes ...
>>
>> 01-Nov 10:07 rendena-dir JobId 568: Fatal er
On Fri, Nov 1, 2013 at 1:51 PM, Dimitri Maziuk wrote:
>
> After yum updating postgres:
>
> 01-Nov 10:04 rendena-sd JobId 568: Writing spooled data to Volume.
> Despooling 49,807,364,626 bytes ...
>
> 01-Nov 10:07 rendena-dir JobId 568: Fatal error: sql.c:354 sql.c:354
> query SELECT count(*) from
Fixed. Restarted bacula-sd on the director (after stopping
bacula-director). There was a traceback when doing this, but after
restarting bacula-sd and then bacula-director, this seems to have corrected
itself.
On Fri, Nov 1, 2013 at 11:51 AM, brconflict wrote:
> Hello,
>I'm coming back af
After yum updating postgres:
01-Nov 10:04 rendena-sd JobId 568: Writing spooled data to Volume.
Despooling 49,807,364,626 bytes ...
01-Nov 10:07 rendena-dir JobId 568: Fatal error: sql.c:354 sql.c:354
query SELECT count(*) from JobMedia WHERE JobId=568 failed:
no connection to the server
Perhap
Hello,
I'm coming back after hiatus, and I'm currently troubleshooting
something I've not found online or crossed before. I have a bacula backup
job that has worked for the last year or so, but after changing the
bacula-director.conf file to reduce the max volume size from 250G to 25G
(to back u