Thanks Jörg,
that helps a lot.
Best,
Arjen.
On 12/06/2017 03:29 PM, Jörg Steffens wrote:
On 06.12.2017 at 14:42 wrote Arjen Van Drie:
Hi list,
using 16.2.4 on Centos 7 from Bareos repo.
I wanted to do a restore today. I scheduled an immediate restore in
bconsole. I typed "messages" but nothing showed up.
After investigation it turned out that a couple of jobs were
hangingstarting at date 2017-12-03.
That day I had some issues of Maximum Volumes in pools that were not big
enough. I increased it, restarted bareos. I manually created labels for
the jobs that were hanging and, based on previous experience, I
_assumed_ (yes yes, never assume) that the jobs were picked up. They
obviously were not.
I can live with that. Something I cannot live with is only knowing that
after 3 days. So my question: how can I monitor queued / hanging jobs? I
have been looking around in bconsole but can't seem to find a command
that will give me just that.
I could:
- list all clients
- get status for all clients
- parse that stuff
- write that to proper strings for our monitoring env
or does anyone have a betterand less time-consuming way?
In bconsole:
list jobs last
Gives you the last runtime of each job(name). You should get suspicions,
if a job is older than 24 hours.
To get a parseable output:
.api json
list jobs last
But best you use bareos.bsock.DirectorConsoleJson from the python
interface, see https://www.bareos.org/en/python-bareos.html
Another option is to use/extend the Nagios plugin for the Bareos
Director, implemented as python plugin, see
https://github.com/bareos/bareos-contrib/tree/master/dir-plugins/nagios_icinga
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
