View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001003 | bareos-core | file daemon | public | 2018-08-31 20:39 | 2019-12-18 15:36 |
Reporter | Pedro | Assigned To | arogge | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | Linux | OS | Ubuntu | OS Version | 14.04 |
Product Version | 17.2.4 | ||||
Summary | 0001003: Fatal error: bpipe-fd: Error closing stream for pseudo file /home/backup.sql: 268435457 | ||||
Description | The fileset.conf has this configuration directive: Plugin = "bpipe:/home/backup.sql:mysqldump -u root -ppassword --databases MyDataBase:dd of=/home/restore.sql" After run a restore command, the bconsole shows the error messages: "... FD Errors: 1 FD termination status: Fatal Error SD termination status: OK Termination: *** Restore Error ***" But the restore was successful done. If the bareos-filedaemon is run with the "/usr/sbin/bareos-fd -d 100" command, no error message is displayed by bconsole: "... FD Errors: 0 FD termination status: OK SD termination status: OK Termination: Restore OK" | ||||
Additional Information | Server operating system: Ubuntu server 16.04.5 LTS. Client operating system: Ubuntu desktop 14.04.5 LTS. | ||||
Tags | No tags attached. | ||||
Try to wrap commands into shell scripts Plugin = "bpipe:/home/backup.sql:backup.sh backup:backup.sh restore" |
|
Now I can not backup or restore. "... Fatal error: bpipe-fd: Error closing stream for pseudo file /home/backup.sql: 268435664 ... Error: Bareos bareos-dir 17.2.4 (21Sep17): ... Non-fatal FD errors: 1 SD Errors: 0 FD termination status: Fatal Error SD termination status: Canceled Termination: *** Backup Error ***" |
|
Hope it helps Plugin = "bpipe:file=/home/backup.sql:reader=backup.sh backup:writer=backup.sh restore" |
|
Nothing solved again. "... Fatal error: bpipe-fd: Error closing stream for pseudo file /home/backup.sql: 268435664 ... Error: Bareos bareos-dir 17.2.4 (21Sep17): ... Non-fatal FD errors: 1 SD Errors: 0 FD termination status: Fatal Error SD termination status: Canceled Termination: *** Backup Error ***" |
|
was this ever resolved? We use: FileSet { Name = "mngdb1.hivecpq.com-mongo" Include { Options { signature = SHA1 compression = GZIP3 } # Backup mongodb Plugin = "bpipe:file=/_mongobackups_/restore.archive:reader=mongodump --host haset0/192.168.140.51,192.168.140.52,192.168.140.53 -u xxxx -p xxxx --readPreference primary --oplog --archive:writer=dd of=/home/mongo_restore.archive" } IgnoreFileSetChanges = yes } Backup seems to work, but whatever we tried, we can never restore :( 2019-06-20 17:11:49 xxxxx JobId 79267: Fatal error: bpipe-fd: Error closing stream for pseudo file /_mongobackups_/restore.archive: 268435457 2019-06-20 17:11:49 bareos-dir JobId 79267: Error: Bareos bareos-dir 18.2.6 (13Feb19): Build OS: Linux-4.4.92-6.18-default debian Debian GNU/Linux 9.7 (stretch) JobId: 79267 Job: RestoreFiles.2019-06-20_17.11.44_13 Restore Client: xxxx Start time: 20-Jun-2019 17:11:46 End time: 20-Jun-2019 17:11:49 Elapsed time: 3 secs Files Expected: 1 Files Restored: 1 Bytes Restored: 2,899 Rate: 1.0 KB/s FD Errors: 1 FD termination status: Fatal Error SD termination status: OK Bareos binary info: official Bareos subscription Termination: *** Restore Error *** |
|
Well for anyone looking for a solution; I used this writer and it works now: writer=dd of=/tmp/mongo_restore.archive bs=16M oflag=direct iflag=fullblock status=none Not sure if it's either of these: oflag=direct iflag=fullblock status=none But in any case 100% succesful now!! :) too bad it doesn't take the selected path in the restore GUI, it's now hardcoded to /tmp. |
|
Does this happen with different software or only with mongodb? Can you reproduce the issue with the latest nightly-build? Could you take the time to provide debug-traces from the filedaemon that did the failed restore? |
|
Hello arogge It was resolved with other dd settings, not sure if the bug is in Bareos. Although during all testing, it seemed very hard to find a workable solution :) It would be great if this plugin supported some more features out of the box like file path specification with a default writer or something which supports it. |
|
For the bug itself there is a workaround possible. If you have a feature request, please feel free to open a feature request describing what you expect. Thank you! |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2018-08-31 20:39 | Pedro | New Issue | |
2018-09-17 10:54 | Shodan | Note Added: 0003114 | |
2018-09-17 20:27 | Pedro | Note Added: 0003115 | |
2018-09-18 08:31 | Shodan | Note Added: 0003116 | |
2018-09-18 13:47 | Pedro | Note Added: 0003117 | |
2018-09-18 14:03 | Pedro | Note Edited: 0003115 | |
2018-09-18 14:04 | Pedro | Note Edited: 0003115 | |
2018-09-18 14:04 | Pedro | Note Edited: 0003115 | |
2019-06-20 17:18 | hostedpower | Note Added: 0003393 | |
2019-06-20 17:39 | hostedpower | Note Added: 0003394 | |
2019-07-08 12:08 | arogge | Status | new => feedback |
2019-07-08 12:08 | arogge | Note Added: 0003418 | |
2019-07-12 11:42 | hostedpower | Note Added: 0003453 | |
2019-12-18 15:36 | arogge | Assigned To | => arogge |
2019-12-18 15:36 | arogge | Status | feedback => resolved |
2019-12-18 15:36 | arogge | Resolution | open => no change required |
2019-12-18 15:36 | arogge | Note Added: 0003687 | |
2019-12-18 15:36 | arogge | Status | resolved => closed |