View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001291bareos-coredirectorpublic2020-12-17 09:342023-07-31 15:43
Reporterhostedpower Assigned Tobruno-at-bareos  
PriorityhighSeveritymajorReproducibilityrandom
Status closedResolutionfixed 
PlatformLinuxOSDebianOS Version10
Product Version19.2.9 
Summary0001291: Since upgrade a lot of jobs start hanging
DescriptionHi,

Since recently we see a lot of jobs which seem to start, but they never really start. They hang somewhere in the beginning of the backup job. We suspect it started when we upgraded to latest version.


Steps To ReproduceA sample:

2020-12-17 08:07:34 pim1.hostsample.com JobId 100580: Extended attribute support is enabled <------------- hangs forever here
2020-12-17 08:07:34 pim1.hostsample.com JobId 100580: ACL support is enabled
2020-12-17 08:07:23 mydir-dir JobId 100580: Start Backup JobId 100580, Job=backup-pim1.hostsample.com.2020-12-17_00.15.01_05
2020-12-17 08:07:23 mydir-dir JobId 100580: Connected Storage daemon at backup08.xxxxxx:9103, encryption: TLS_CHACHA20_POLY1305_SHA256
2020-12-17 08:07:23 mydir-dir JobId 100580: Using Device "hostsamplepim1-incr" to write.
2020-12-17 08:07:23 mydir-dir JobId 100580: Connected Client: pim1.hostsample.com at xxx.xxx.xxx.xxx:9102, encryption: TLS_CHACHA20_POLY1305_SHA256
2020-12-17 08:07:23 mydir-dir JobId 100580: Handshake: Immediate TLS
2020-12-17 08:07:23 mydir-dir JobId 100580: Encryption: TLS_CHACHA20_POLY1305_SHA256
2020-12-17 08:07:23 mydir-dir JobId 100580: Sending Accurate information.
2020-12-17 08:07:23 pim1.hostsample.com JobId 100580: Connected Storage daemon at backup08.xxxxxx:9103, encryption: TLS_CHACHA20_POLY1305_SHA256

Additional InformationWe tried waiting, but they just sit there hours and hours :(
TagsNo tags attached.

Activities

hostedpower

hostedpower

2020-12-17 09:44

reporter   ~0004071

We checked further, a high percentage of the jobs has these problems at this moment, it's quite severe :(
hostedpower

hostedpower

2020-12-18 11:31

reporter   ~0004073

We went back to bareos 19.2.8 on the director node, but we had the feeling the jobs still got stuck. Afterwards we also downgraded all storage daemons to 19.2.8 and rebooted all backup servers.

Since we did these steps, all seems back to normal.

Any idea something changed in the storage daemon which can cause this behavior?
bruno-at-bareos

bruno-at-bareos

2023-07-31 15:13

manager   ~0005286

Is this still accurate? What are the behavior with recent bareos 22 code?
Maybe this was a forgotten issue?
hostedpower

hostedpower

2023-07-31 15:41

reporter   ~0005287

We no longer have these issues, we're on 22 in the meanwhile, issue can be closed. I think it was still with MySQL (We're on PostgreSQL now)
bruno-at-bareos

bruno-at-bareos

2023-07-31 15:43

manager   ~0005288

Thanks for confirmation that everything work with recent 22 version.

Issue History

Date Modified Username Field Change
2020-12-17 09:34 hostedpower New Issue
2020-12-17 09:44 hostedpower Note Added: 0004071
2020-12-18 11:31 hostedpower Note Added: 0004073
2023-07-31 15:13 bruno-at-bareos Assigned To => bruno-at-bareos
2023-07-31 15:13 bruno-at-bareos Status new => feedback
2023-07-31 15:13 bruno-at-bareos Note Added: 0005286
2023-07-31 15:41 hostedpower Note Added: 0005287
2023-07-31 15:41 hostedpower Status feedback => assigned
2023-07-31 15:43 bruno-at-bareos Status assigned => closed
2023-07-31 15:43 bruno-at-bareos Resolution open => fixed
2023-07-31 15:43 bruno-at-bareos Note Added: 0005288