Well, I decided to see directly
in the Catalog :
mysql> select JobId,
JobStatus, PoolId, Level from Job where JobId=27110;
+-------+-----------+--------+-------+
| JobId | JobStatus | PoolId |
Level |
+-------+-----------+--------+-------+
| 27110 | R | 34
| F |
+-------+-----------+--------+-------+
1 row in set (0.00 sec)
mysql> select JobId,
JobStatus, PoolId, Level from Job where JobId=27265;
+-------+-----------+--------+-------+
| JobId | JobStatus | PoolId |
Level |
+-------+-----------+--------+-------+
| 27265 | R | 84
| I |
+-------+-----------+--------+-------+
1 row in set (0.00 sec)
As you can see, this two job
have JobStatus = R (for running), and it’s wrong. I think I could do that :
update Job set JobStatus = 'T'
where JobId = 27110;
update Job set JobStatus = 'T'
where JobId = 27265;
but I don’t know if it’s
really a good idea, someone can say me if I am wrong or not ?
and I read also about dbchek, I
don’t know if this tool can help me to solve my problem…
Regards,
François
De : François Mehault
[mailto:Francois.Mehault AT netplus DOT fr]
Envoyé : jeudi 28 mai 2009 11:27
À : bacula-users AT lists.sourceforge DOT net
Objet : [Bacula-users] running jobs in DB Catalog
Hi All
I have two jobs which are running in my DB Catalog for one
client, and no jub running in my bacula-dir for this client, I would like to
correct information in my Catalog. As I have this problem, my client
can’t be saved. And I don’t succeed to cancel the jobs with the
cancel command in bconsole as there is no running job for the director. Help will
be really appreciated.
Regards,
François
