DAve wrote:
> Martin Simmons wrote:
>>> On Mon, 16 Nov 2009 09:29:07 -0500, DAve said:
>>> 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.00.02 Warning: Error
>>> updating job record. sql_update.c:194 Update problem: affected_rows=0
>>> 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.
Martin Simmons wrote:
>> On Mon, 16 Nov 2009 09:29:07 -0500, DAve said:
>> 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.00.02 Warning: Error
>> updating job record. sql_update.c:194 Update problem: affected_rows=0
>> 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.00.02 Warning: Err
> On Mon, 16 Nov 2009 09:29:07 -0500, DAve said:
>
> 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.00.02 Warning: Error
> updating job record. sql_update.c:194 Update problem: affected_rows=0
> 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.00.02 Warning: Error
> getting job record
I have tried several things now to correct this error without success.
- Checked and repaired MySQL db with MySQL tools (mysqlcheck).
- Cleaned MySQL db with bacula tools (dbcheck).
- The offending pool has been removed and a new pool created and volumes
added. The backup ran without error over
DAve wrote:
> DAve wrote:
>> Cedric Tefft wrote:
>>> DAve wrote:
No change, same error.
30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error
updating job record. sql_update.c:194 Update problem: affected_rows=0
30-Oct 07:09 director-dir: Allied-ex3.2009
DAve wrote:
> Cedric Tefft wrote:
>> DAve wrote:
>>> No change, same error.
>>>
>>> 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error
>>> updating job record. sql_update.c:194 Update problem: affected_rows=0
>>> 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warni
Cedric Tefft wrote:
> DAve wrote:
>> No change, same error.
>>
>> 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error
>> updating job record. sql_update.c:194 Update problem: affected_rows=0
>> 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error
>> gettin
DAve wrote:
> No change, same error.
>
> 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error
> updating job record. sql_update.c:194 Update problem: affected_rows=0
> 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error
> getting job record for stats: sql_
DAve wrote:
>
> Ran dbcheck, found several paths to correct and also orphaned files.
> dbcheck results, second run, everything looks good.
>
> Select function number: 16
> Checking for Filenames with a trailing slash
> Found 0 bad Filename records.
> Checking for Paths without a trailing slash
>
DAve wrote:
> Ryan Novosielski wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> DAve wrote:
>>> DAve wrote:
Ryan Novosielski wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> DAve wrote:
>> DAve wrote:
>>> DAve wrote:
DAve wrote:
Ryan Novosielski wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> DAve wrote:
>> DAve wrote:
>>> Ryan Novosielski wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
DAve wrote:
> DAve wrote:
>> DAve wrote:
>>> DAve wrote:
Good afternoon.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
DAve wrote:
> DAve wrote:
>> Ryan Novosielski wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> DAve wrote:
DAve wrote:
> DAve wrote:
>> DAve wrote:
>>> Good afternoon.
>>>
>>> I am having a recurring issue w
DAve wrote:
> Ryan Novosielski wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> DAve wrote:
>>> DAve wrote:
DAve wrote:
> DAve wrote:
>> Good afternoon.
>>
>> I am having a recurring issue with a backup that is configured for DR
>> purposes. The client purc
Ryan Novosielski wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> DAve wrote:
>> DAve wrote:
>>> DAve wrote:
DAve wrote:
> Good afternoon.
>
> I am having a recurring issue with a backup that is configured for DR
> purposes. The client purchased a fixed amount of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
DAve wrote:
> DAve wrote:
>> DAve wrote:
>>> DAve wrote:
Good afternoon.
I am having a recurring issue with a backup that is configured for DR
purposes. The client purchased a fixed amount of space and wants to
overwrite the
DAve wrote:
> DAve wrote:
>> DAve wrote:
>>> Good afternoon.
>>>
>>> I am having a recurring issue with a backup that is configured for DR
>>> purposes. The client purchased a fixed amount of space and wants to
>>> overwrite the volumes each night. They have a local backup system in
>>> place an
DAve wrote:
> DAve wrote:
>> Good afternoon.
>>
>> I am having a recurring issue with a backup that is configured for DR
>> purposes. The client purchased a fixed amount of space and wants to
>> overwrite the volumes each night. They have a local backup system in
>> place and we are using Bacula
DAve wrote:
> Good afternoon.
>
> I am having a recurring issue with a backup that is configured for DR
> purposes. The client purchased a fixed amount of space and wants to
> overwrite the volumes each night. They have a local backup system in
> place and we are using Bacula to get those backu
Good afternoon.
I am having a recurring issue with a backup that is configured for DR
purposes. The client purchased a fixed amount of space and wants to
overwrite the volumes each night. They have a local backup system in
place and we are using Bacula to get those backups offsite for the
even
19 matches
Mail list logo