 |
I've not been able to reproduce this. Instead, it gives me the status of a storage (I've also tested it against 17.2.7): *status job= Connecting to Storage daemon File at ci-CentOS-7-64-aa38a569bc6ae306:9103 bareos-sd Version: 18.2.3 (01 Jun 2018) Linux-4.4.92-6.18-default redhat CentOS Linux release 7.5.1804 (Core) Daemon started 13-Jul-18 14:21. Jobs: run=9, running=0. Heap: heap=45,056 smbytes=52,061 max_bytes=63,107,514 bufs=120 max_bufs=175 Sizes: boffset_t=8 size_t=8 int32_t=4 int64_t=8 mode=0 bwlimit=0kB/s Running Jobs: No Jobs running. ==== Jobs waiting to reserve a drive: ==== Terminated Jobs: JobId Level Files Bytes Status Finished Name =================================================================== 1 Full 495 45.53 M OK 13-Jul-18 14:21 backup-bareos-fd 2 0 0 OK 13-Jul-18 14:21 RestoreFiles 3 Full 2 22.20 M OK 13-Jul-18 14:21 BackupData 4 0 0 OK 13-Jul-18 14:21 RestoreFiles 5 Full 84 162.8 K OK 13-Jul-18 14:21 BackupCatalog 6 Full 496 45.53 M OK 13-Jul-18 14:21 backup-s3-fd 7 0 0 OK 13-Jul-18 14:22 RestoreFiles 8 Full 496 45.53 M OK 13-Jul-18 14:24 backup-s3-fd 11 Full 496 45.53 M OK 13-Jul-18 14:36 backup-s3-fd ==== Device status: Device "FileStorage" (/var/lib/bareos/storage) is not open. == ==== Used Volume status: ==== ==== ---- When there is more than one storage, it picks one, in our case the second of three. You may test all your storage (from bconsole:.storages) with "status storage=..." Maybe it crashes on one of them. |
|
|
I'm closing this issue, as there has not been any new information for a long time and there is nothing we can do right now. If you can provide additional information concerning this issue, please feel free to reopen the bug. |
- Anonymous
