Hello,
The message printed does not go to the standard Bacula Messages{}
resource. Instead it is a sort of debug message that goes to STDOUT,
thus you will not find it in the job logs.
I am going to think about sending it to the job log though.
The debug message should not have triggered because the test that
produces the message is incorrect. Consequently, in your case, there is
absolutely nothing to worry about.
The incorrect test has been corrected in a later version (August 2015)
so that had you been running version 7.2 you would not see the debug
output. That said, the message was never intended to print negative
numbers (it is actually a large positive number), so I have just
corrected that as well, and the fix will be in the next version.
Bottom line: Thanks for reporting this. Don't worry about it, just
ignore those messages.
Best regards,
Kern
On 12/31/2015 03:19 AM, Joseph L. Casale wrote:
> Running 7.0.5 on centos 7 and I am starting to get errors in
> /var/log/messages with
> bacula-sd: bacula-sd: block.c:304-27298 Incorrect EndBlock/EndFile
> oldEndBlock=-1838 newEndBlock=62674 oldEndFile=7 newEndFile=8
> while the bacula-sd related lines in the job log don't show this.
>
> Why do the job logs omit this, and what exactly does it mean?
>
> Thanks,
> jlc
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bacula-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
