.. if the message-resource contains:
catalog = all
like this one i'm using:
> Messages {
> Name = VerifyJobs
> mailcommand = "/sbin/bsmtp -h localhost -f \"\(Bacula\) %r\" -s \"%t %e of
> %c %l\" %r"
> mail = [EMAIL PROTECTED] = all
> catalog = all
> }
what i have done:
after an InitCatalog I have touched a file /etc/einetestdatei.
the next verify-job reports an error "New file ..."
so i did the InitCatalog again.
after that i have removed the new file and started a verify-job.
the normal CatalogVerify-Jobs take about 2 minutes, so i have cancled this job
after 6 minutes.
then i got the email about the job:
>
> 16-Okt 14:47 backup-dir JobId 2332: Verifying against JobId=2331
> Job=client.ic3s.de.2007-10-16_14.45.12
> 16-Okt 14:47 backup-dir JobId 2332: Start Verify JobId=2332 Level=Catalog
> Job=client.ic3s.de.2007-10-16_14.46.03
> 16-Okt 14:48 backup-dir JobId 2332:
> The following files are in the Catalog but not on disk:
> 16-Okt 14:48 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:48 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:48 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:48 backup-dir JobId 2332: /etc/einetestdatei
> .......
> 16-Okt 14:49 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:49 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:49 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:49 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:49 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:49 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:49 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:49 backup-dir JobId 2332: /etc/einetestdatei
> ...
> 16-Okt 14:51 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:51 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:51 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:51 backup-dir JobId 2332: /etc/einetestdatei
> 16-Okt 14:51 backup-dir JobId 2332: Bacula backup-dir 2.2.5 (09Oct07):
> 16-Okt-2007 14:51:08
> Build: x86_64-unknown-linux-gnu debian 4.0
> JobId: 2332
> Job: client.ic3s.de.2007-10-16_14.46.03
> FileSet: IX-Server-Verify
> Verify Level: Catalog
> Client: client.ic3s.de
> Verify JobId: 2331
> Verify Job:
> Start time: 16-Okt-2007 14:47:01
> End time: 16-Okt-2007 14:51:08
> Files Examined: 13,008
> Non-fatal FD errors: 0
> FD termination status: OK
> Termination: Verify Canceled
>
> 16-Okt 14:51 backup-dir JobId 2332: Begin pruning Jobs.
> 16-Okt 14:51 backup-dir JobId 2332: No Jobs found to prune.
> 16-Okt 14:51 backup-dir JobId 2332: Begin pruning Files.
> 16-Okt 14:51 backup-dir JobId 2332: No Files found to prune.
> 16-Okt 14:51 backup-dir JobId 2332: End auto prune.
>
this mail contains 19873 lines with " backup-dir JobId 2332:
/etc/einetestdatei"
also the log-table in the catalog-database contains this number of rows about
that file.
the fd debug output shows no problems, the job finished successful,
the director debug output shows :
.......
> backup-dir: getmsg.c:110-0 bget_dirmsg -1: backup-dir: postgresql.c:314-0
> db_sql_query started
> backup-dir: postgresql.c:474-0 my_postgresql_query started
> backup-dir: postgresql.c:485-0 my_postgresql_query starts with 'SELECT
> Path.Path,Filename.Name FROM File,Path,Filename WHERE File.JobId=2331 AND
> File.MarkId!=2332 AND File.PathId=Path.PathId AND
> File.FilenameId=Filename.FilenameId'
> backup-dir: postgresql.c:501-0 we have a result
> backup-dir: postgresql.c:505-0 we have 2 fields
> backup-dir: postgresql.c:508-0 we have 1 rows
> backup-dir: postgresql.c:516-0 my_postgresql_query finishing
> backup-dir: postgresql.c:323-0 db_sql_query succeeded. checking handler
> backup-dir: postgresql.c:326-0 db_sql_query invoking handler
> backup-dir: postgresql.c:330-0 db_sql_query sql_store_result suceeded
> backup-dir: postgresql.c:355-0 my_postgresql_fetch_row start
> backup-dir: postgresql.c:359-0 we have need space of 16 bytes
> backup-dir: postgresql.c:375-0 my_postgresql_fetch_row row number '0' is
> acceptable (0..1)
> backup-dir: postgresql.c:379-0 my_postgresql_fetch_row field '0' has value
> '/etc/'
> backup-dir: postgresql.c:379-0 my_postgresql_fetch_row field '1' has value
> 'einetestdatei'
> backup-dir: postgresql.c:389-0 my_postgresql_fetch_row finishes returning
> 6cdfe8
> backup-dir: postgresql.c:333-0 db_sql_query sql_fetch_row worked
> backup-dir: message.c:1082-0 Enter Jmsg type=6
> backup-dir: message.c:608-0 Enter dispatch_msg type=6 msg=backup-dir JobId
> 2332:
> The following files are in the Catalog but not on disk:
> backup-dir: message.c:733-0 MAIL for following msg: backup-dir JobId 2332:
> The following files are in the Catalog but not on disk:
> backup-dir: postgresql.c:314-0 db_sql_query started
> backup-dir: postgresql.c:474-0 my_postgresql_query started
> backup-dir: postgresql.c:485-0 my_postgresql_query starts with 'INSERT INTO
> Log (JobId, Time, LogText) VALUES (2332,'2007-10-16 14:48:39','backup-dir
> JobId 2332:
> The following files are in the Catalog but not on disk:
> ')'
> backup-dir: postgresql.c:501-0 we have a result
> backup-dir: postgresql.c:505-0 we have 0 fields
> backup-dir: postgresql.c:508-0 we have 0 rows
> backup-dir: postgresql.c:516-0 my_postgresql_query finishing
> backup-dir: postgresql.c:323-0 db_sql_query succeeded. checking handler
> backup-dir: postgresql.c:343-0 db_sql_query finished
> backup-dir: message.c:1082-0 Enter Jmsg type=6
> backup-dir: message.c:608-0 Enter dispatch_msg type=6 msg=backup-dir JobId
> 2332: /etc/einetestdatei
> backup-dir: message.c:733-0 MAIL for following msg: backup-dir JobId 2332:
> /etc/einetestdatei
> backup-dir: postgresql.c:314-0 db_sql_query started
> backup-dir: postgresql.c:474-0 my_postgresql_query started
> backup-dir: postgresql.c:485-0 my_postgresql_query starts with 'INSERT INTO
> Log (JobId, Time, LogText) VALUES (2332,'2007-10-16 14:48:39','backup-dir
> JobId 2332: /etc/einetestdatei
> ')'
> backup-dir: postgresql.c:501-0 we have a result
> backup-dir: postgresql.c:505-0 we have 0 fields
> backup-dir: postgresql.c:508-0 we have 0 rows
> backup-dir: postgresql.c:516-0 my_postgresql_query finishing
> backup-dir: postgresql.c:323-0 db_sql_query succeeded. checking handler
> backup-dir: postgresql.c:343-0 db_sql_query finished
> backup-dir: postgresql.c:355-0 my_postgresql_fetch_row start
> backup-dir: postgresql.c:375-0 my_postgresql_fetch_row row number '-1' is
> acceptable (0..0)
> backup-dir: postgresql.c:389-0 my_postgresql_fetch_row finishes returning
> 6cdfe8
> backup-dir: postgresql.c:333-0 db_sql_query sql_fetch_row worked
> backup-dir: message.c:1082-0 Enter Jmsg type=6
> backup-dir: message.c:608-0 Enter dispatch_msg type=6 msg=backup-dir JobId
> 2332: /etc/einetestdatei
> backup-dir: message.c:733-0 MAIL for following msg: backup-dir JobId 2332:
> /etc/einetestdatei
> backup-dir: postgresql.c:314-0 db_sql_query started
> backup-dir: postgresql.c:474-0 my_postgresql_query started
> backup-dir: postgresql.c:485-0 my_postgresql_query starts with 'INSERT INTO
> Log (JobId, Time, LogText) VALUES (2332,'2007-10-16 14:48:39','backup-dir
> JobId 2332: /etc/einetestdatei
> ')'
> backup-dir: postgresql.c:501-0 we have a result
> backup-dir: postgresql.c:505-0 we have 0 fields
> backup-dir: postgresql.c:508-0 we have 0 rows
> backup-dir: postgresql.c:516-0 my_postgresql_query finishing
> backup-dir: postgresql.c:323-0 db_sql_query succeeded. checking handler
> backup-dir: postgresql.c:343-0 db_sql_query finished
> backup-dir: postgresql.c:355-0 my_postgresql_fetch_row start
> backup-dir: postgresql.c:375-0 my_postgresql_fetch_row row number '-1' is
> acceptable (0..0)
> backup-dir: postgresql.c:389-0 my_postgresql_fetch_row finishes returning
> 6cdfe8
> backup-dir: postgresql.c:333-0 db_sql_query sql_fetch_row worked
> backup-dir: message.c:1082-0 Enter Jmsg type=6
> backup-dir: message.c:608-0 Enter dispatch_msg type=6 msg=backup-dir JobId
> 2332: /etc/einetestdatei
> backup-dir: message.c:733-0 MAIL for following msg: backup-dir JobId 2332:
> /etc/einetestdatei
> backup-dir: postgresql.c:314-0 db_sql_query started
> backup-dir: postgresql.c:474-0 my_postgresql_query started
> backup-dir: postgresql.c:485-0 my_postgresql_query starts with 'INSERT INTO
> Log (JobId, Time, LogText) VALUES (2332,'2007-10-16 14:48:39','backup-dir
> JobId 2332: /etc/einetestdatei
> ')'
.....
and again and again and again..... ~19873 times till i have cancled the job
looks like the only limit is the diskspace on my database partition
after removing the "catalog = all" from my message-resource, i get the normal
email with:
The following files are in the Catalog but not on disk:
16-Okt 14:53 backup-dir JobId 2333: /etc/einetestdatei
16-Okt 14:53 backup-dir JobId 2333: Bacula backup-dir 2.2.5 (09Oct07):
16-Okt-2007 14:53:52
Build: x86_64-unknown-linux-gnu debian 4.0
Verify Level: Catalog
FD termination status: OK
Termination: Verify Differences
this happens with 2.2.5 debian 4.0 director and postgres 8.1.9-0etch1
can another postgres-user verify this?
Best Regards
Thomas
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
