View Issue Details

IDProjectCategoryView StatusLast Update
0001373bareos-core[All Projects] directorpublic2021-08-03 11:03
ReporterdikulikovAssigned To 
Status newResolutionopen 
PlatformLinuxOSDebianOS Version10
Product Version20.0.2 
Fixed in Version 
Summary0001373: Director randomply crash with "ABORTING due to ERROR#012lib/ Could not add thread to list."
The version of bareos packages is 20.0.1-3
The problem appears almost every week, but not at the same time, sometimes even several times a week. The director's process hangs, the port listens, but does not respond when trying to connect to the console. After that, after 3-7 hours, it crashes with the error "ABORTING due to ERROR # 012lib / 400 Could not add thread to list."
Steps To Reproduce1. Start director
2. Wait some day normal work
3. Director does not accept connections
4. Wait 3-7 hours
5. Proccess director crash
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




2021-07-23 08:42


bareos:director.26918.bactrace (31,196 bytes)
bareos.26918.traceback (453,206 bytes)


2021-07-23 08:46

reporter   ~0004190

Log messages
bareos:director ABORTING due to ERROR#012lib/ Could not add thread to list.
BAREOS aborting to obtain traceback.
BAREOS interrupted by signal 6: IOT trap


2021-08-03 11:03

reporter   ~0004197

I increased the Max Connections parameter to 100 for the director, but the crashes did not go away

Issue History

Date Modified Username Field Change
2021-07-23 08:42 dikulikov New Issue
2021-07-23 08:42 dikulikov File Added: bareos:director.26918.bactrace
2021-07-23 08:42 dikulikov File Added: bareos.26918.traceback
2021-07-23 08:46 dikulikov Note Added: 0004190
2021-08-03 11:03 dikulikov Note Added: 0004197