Hi,
> * What led up to the situation? Upgrade from 5.2.6+dfsg-9.2
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
> * What was the outcome of this action?
> bacula=# SELECT DISTINCT j.JobId, j.Name AS JobName, j.Level,
> j.ClientId, j.StartTime, j.EndTime, j.VolSessionId, j.VolSessionTime,
> j.JobFiles, j.JobBytes, j.JobErrors, j.Reviewed, j.PoolId,
> j.FileSetId,
> j.PurgedFiles, j.JobStatus, j.(NOW() - StartTime) AS DurationTime,
> s.JobStatusLong, c.Name AS ClientName, p.Name AS PoolName FROM Job AS
> j
> LEFT JOIN Status AS s ON j.JobStatus = s.JobStatus LEFT JOIN Client AS
> c
> ON j.ClientId = c.ClientId LEFT JOIN Pool AS p ON j.PoolId = p.PoolId
> WHERE ((j.EndTime IS NULL) OR (j.JobStatus IN
> ('C
can you provide more information about the bug you reported?
What database backend are you using?
When exactly did the error occur - during the upgrade itself, afterwards
when using bacula, if during usage, what exactly did you do that lead up
to the error?
leo
