Thanks a lot for your answers. I will analyze and do my tests. I'm using Bacula Community version 9.6.7 with PostgreSQL, and in the database I found a 'status' table with the following data: |jobstatus|jobstatuslong |severity| |---------|-------------------------------|--------| |C |Created, not yet running |15 | |R |Running |15 | |B |Blocked |15 | |T |Completed successfully |10 | |E |Terminated with errors |25 | |e |Non-fatal error |20 | |f |Fatal error |100 | |D |Verify found differences |15 | |A |Canceled by user |90 | |F |Waiting for Client |15 | |S |Waiting for Storage daemon |15 | |m |Waiting for new media | | |M |Waiting for media mount |15 | |s |Waiting for storage resource |15 | |j |Waiting for job resource |15 | |c |Waiting for client resource |15 | |d |Waiting on maximum jobs |15 | |t |Waiting on start time |15 | |p |Waiting on higher priority jobs|15 | |a |SD despooling attributes |15 | |i |Doing batch insert file records|15 | |I |Incomplete Job |25 |
As you can see it doesn't have the 'W' status that you use in the SQL query. Does this jobstatus exist in my bacula version or is this table incomplete? Marcelo
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
