View Issue Details

IDProjectCategoryView StatusLast Update
0000788bareos-coredirectorpublic2023-03-27 11:09
ReporterPaoloM Assigned Tobruno-at-bareos  
Status closedResolutionunable to reproduce 
PlatformLinuxOSDebianOS Version8
Product Version16.2.4 
Summary0000788: Failed job remain in running on director
DescriptionIf a job is succesfull all is working fine, but if a job fails, for any reason, the job remain in "R" on the console, and on the director status, while on the storage and client status it is correctly shown with Error Status:

*list jobs:
44 | AI-BackupMail2-Virtualmail4 | ************-fd | 2017-02-23 10:59:35 | B | F | 0 | 0 | R

*st 1:
 44 Full AI-BackupMail2-Virtualmail4.2017-02-23_10.59.29_25 has a fatal error
*st 2:
44 Full 9,092 1.647 G Error 23-Feb-17 15:20 AI-BackupMail2-Virtualmail4
*st 3:
 44 Full 9,092 1.646 G Error 23-Feb-17 13:25 AI-BackupMail2-Virtualmail4

The bareos-dir service hangs on restart and the only way is to kill the process. Only at this point, I see the job in "f" Status from *list jobs command
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action




2023-03-23 16:17

developer   ~0004933

Can you reproduce this malfunction on current code (Bareos >21?)


2023-03-27 11:09

developer   ~0004956

contact dead

Issue History

Date Modified Username Field Change
2017-02-23 17:46 PaoloM New Issue
2023-03-23 16:17 bruno-at-bareos Assigned To => bruno-at-bareos
2023-03-23 16:17 bruno-at-bareos Status new => feedback
2023-03-23 16:17 bruno-at-bareos Note Added: 0004933
2023-03-27 11:09 bruno-at-bareos Status feedback => closed
2023-03-27 11:09 bruno-at-bareos Resolution open => unable to reproduce
2023-03-27 11:09 bruno-at-bareos Note Added: 0004956