View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001278 | bareos-core | director | public | 2020-11-02 16:19 | 2023-08-22 15:26 |
Reporter | jm95 | Assigned To | bruno-at-bareos | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | unable to reproduce | ||
Platform | Linux | OS | Ubuntu | OS Version | 16.04 |
Product Version | 19.2.8 | ||||
Summary | 0001278: Running Job Stuck at "status client=" | ||||
Description | Some of our backups were stuck due to an unreachable NFS mount on the file daemeon machine. The NFS issue has been resolved and backup are running again. During debugging the director und storage daemon were restartetd. On 2 clients jobs are shown as running when they are not running. *status client=vm-XXX-fd Connecting to Client vm-XXX-fd at vm-XXX:9102 Handshake: Immediate TLS, Encryption: PSK-AES256-CBC-SHA vm-XXX-fd Version: 19.2.6 (11 February 2020) Linux-3.10.0-1062.9.1.el7.x86_64 redhat CentOS Linux release 7.7.1908 (Core) Daemon started 01-Apr-20 12:11. Jobs: run=179 running=1, bareos.org build binary Sizeof: boffset_t=8 size_t=8 debug=0 trace=0 bwlimit=0kB/s Running Jobs: JobId 151543 Job vm-XXX-ToDisk.2020-10-28_20.30.01_25 is running. Incremental Backup Job started: 28-Okt-20 21:17 Files=85 Bytes=2,791,166,095 Bytes/sec=6,747 Errors=0 Bwlimit=0 Files Examined=75,502 Processing file: /var/spool/anacron/cron.monthly SDReadSeqNo=5 fd=5 JobId 151626 Job vm-XXX-ToDisk.2020-10-29_20.30.00_24 is running. Incremental Backup Job started: 29-Okt-20 21:11 Files=599 Bytes=2,828,467,903 Bytes/sec=8,632 Errors=0 Bwlimit=0 Files Examined=75,495 Processing file: /opt/sonarqube-7.9.1/logs SDReadSeqNo=5 fd=8 bareos-dir (director) connected at: 02-Nov-20 16:12 "status dir" returns that no jobs are running. Running Jobs: Console connected at 02-Nov-20 16:10 No Jobs running. ==== | ||||
Additional Information | We are running Bareos 19.2.7 on Ubuntu 18.04. | ||||
Tags | No tags attached. | ||||
Forgot to add that we are unable to cancel the job. *cancel jobid=151543 JobId 151543 is not running. Use Job name to cancel inactive jobs. No Jobs running. *cancel job=vm-XXX-ToDisk.2020-10-28_20.30.01_25 No Jobs running. |
|
Is this still reproducible easily with recent version like 22.1.0? As you said "During debugging the director und storage daemon were restartetd." I would have also restarted the bareos-fd daemon. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2020-11-02 16:19 | jm95 | New Issue | |
2020-11-02 16:21 | jm95 | Note Added: 0004051 | |
2023-08-22 15:26 | bruno-at-bareos | Assigned To | => bruno-at-bareos |
2023-08-22 15:26 | bruno-at-bareos | Status | new => closed |
2023-08-22 15:26 | bruno-at-bareos | Resolution | open => unable to reproduce |
2023-08-22 15:26 | bruno-at-bareos | Note Added: 0005332 |