Hello all, for the past few weeks I've had a Bacula deployment running with no issues. But for the past few days there has been a few issues thats has pretty much rendered my Bacula deployment completely useless.
One of the errors I've getting a lot is "waiting for a mount request" for the two largest jobs, even after restarting the SD and the Director and making sure the Storage is mounted, it happens.
Another one is that status director might show these large as running with no error messages whatsoever, but could spend up to 12 hours with nothing changing. As soon as you cancel and you get the stats for the job, the stats show 0 bytes copied.
Also been getting an error where Bacula will try to create a Volumen, notice that it already exists but then go into waiting mode saying it cannot find any appendable volumes
On Thu, Feb 09, 2017 at 09:57:54AM -0400, Alejandro M wrote:
> Hello all, for the past few weeks I've had a Bacula deployment running with
> no issues. But for the past few days there has been a few issues thats has
> pretty much rendered my Bacula deployment completely useless.
I'm wondering if you've hit your pool limitations after the "past few
weeks" and something is wrong with auto-recycling the used volumes?
Some more info on your setup (cfg files) would be helpful.
All the best, Uwe
Uwe Schürkamp | email: <[hidden email]>
Arvato Systems S4M GmbH | Sitz Köln | Amtsgericht Köln HRB 27038
Geschäftsführer: Ralf Schürmann | Dr. Manfred Heinen