Update. We are still seeing this in 5.2.10 as well.
It seems to happen more often towards the beginning of a series of jobs,
when a tape is first chosen (i.e. not when a job is directly using a
tape that's already been chosen and loaded into a drive by a previous job).
Stephen
On 7/5/12
Update. We have seen the problem 2-3 times this past month running
5.2.9 on Redhat 6.2, much less frequent than before but still there.
Stephen
On 6/20/12 7:40 AM, Stephen Thompson wrote:
Well, since we upgraded to 5.2.9 we have not seen the problem.
Also when running 5.2.6 we were
Well, since we upgraded to 5.2.9 we have not seen the problem.
Also when running 5.2.6 we were seeing it 2-3 times a week, during which
we run hundreds of incrementals and several fulls per day.
The error happened both with fulls and incrementals (which we have in
two different LTO3
This good to know. I have postgresql under my catalog and I've been
seeing this behavior intermittently under 5.2.6. I'm waiting for some
shake out of 5.2.9 before upgrading.
Patti Clark
Information International Associates, Inc.
Linux Administrator and subcontractor to:
Research and
On 20.06.2012 16:40, Stephen Thompson wrote:
Well, since we upgraded to 5.2.9 we have not seen the problem.
Also when running 5.2.6 we were seeing it 2-3 times a week, during
which we run hundreds of incrementals and several fulls per day.
Well, we did far less incrementals per day and full
This (fingers crossed) may have been fixed with 5.2.9 which we upgraded
to last week. It hasn't quite been long enough for me to be convinced
the problem won't return, but I'm hopeful.
Stephen
On 5/24/12 7:08 AM, Stephen Thompson wrote:
hello,
Anyone run into this error before?
We
hello,
Anyone run into this error before?
We hadn't until we upgraded our bacula server from Centos 5.8 to Redhat
6.2, after which we of course had to recompile bacula. However, we used
the same source, version, and options, the exception being that we added
readline for improved bconsole
