Error during restore

17 views
Skip to first unread message

Łukasz Szczepanik

unread,
Jul 30, 2022, 4:44:02 AM7/30/22
to bareos-users
Hi,

For one of my directories ( /var ) on one of my host  I always get *** Restore Error *** status.

This strange behavior confuses me because according to the Bareos-fd logs all files have been restored without any issues. Debug mode shows me no errors during restoration just one line indicate some issue " End FD msg: 2800 End Job TermCode=69 ":

###############################################################
Jul 30 08:31:55 my-host-fd[2081653]:  my-host-fd(100): filed/restore.cc:552-0 === message_length=74 attrExlen=0 msg=23820 5 /var/
Jul 30 08:31:55  my-host-fd2081653]:  my-host-fd(10): filed/restore.cc:1054-0 End Do Restore. Files=3354 Bytes=3084036634
Jul 30 08:31:55  my-host-fd2081653]:  my-host-fd (100): filed/heartbeat.cc:153-0 Send kill to heartbeat id
Jul 30 08:31:55  my-host-fd2081653]:  my-host-fd100): lib/bsock.cc:136-0 Destruct BareosSocket
Jul 30 08:31:55  my-host-fd[2081653]: my-host-fd(100): filed/dir_cmd.cc:2328-0 filed>stored: read close session 85
Jul 30 08:31:55  my-host-fd2081653]:  my-host-fd (100): filed/dir_cmd.cc:2370-0 Done in job.c
Jul 30 08:31:55  my-host-fd[2081653]:  my-host-fd(100): filed/dir_cmd.cc:2373-0 2000 OK storage end
Jul 30 08:31:55  my-host-fd[2081653]:  my-host-fd (5): filed/dir_cmd.cc:2391-0 EndRestoreCmd
Jul 30 08:31:55  my-host-fd[2081653]:  my-host-fd (100): filed/dir_cmd.cc:452-0 Quit command loop. Canceled=1
Jul 30 08:31:55  my-host-fd[2081653]:  my-host-fd(110): filed/dir_cmd.cc:482-0 End FD msg: 2800 End Job TermCode=69 JobFiles=3354 ReadBytes=351341536 JobBytes=3084036634 Errors=1 VSS=0 Encrypt=1

###############################################################

Does anyone know how to debug such errors in other way. What else I can do to check where is the problem. Othere dirs on this machine restore without any issue.

Thanks

Philipp Storz

unread,
Aug 1, 2022, 12:49:41 PM8/1/22
to bareos...@googlegroups.com
Hello Łukasz,

at least one error is generated during the restore. You can check the system logs when this error
happens to see what might be the cause.
It might be the case that access rights, selinux/apparmor denies access to some files or directories.
Also, it might be problematic to restore /var while the system is running and /var is still in usage.

For debugging, you should set the debug level to e.g. 500 which will give you much more info and
probably the system call that gets the error result.

Also, it would help to have the full job log.

Best regards,

Philipp

Am 30.07.22 um 10:44 schrieb Łukasz Szczepanik:
> --
> You received this message because you are subscribed to the Google Groups "bareos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
> bareos-users...@googlegroups.com <mailto:bareos-users...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/bareos-users/223e357d-5722-42a1-b745-54a47872c28fn%40googlegroups.com
> <https://groups.google.com/d/msgid/bareos-users/223e357d-5722-42a1-b745-54a47872c28fn%40googlegroups.com?utm_medium=email&utm_source=footer>.


--
Mit freundlichen Grüßen

Philipp Storz philip...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221 63 06 93-92
http://www.bareos.com Fax: +49 221 63 06 93-10

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Geschäftsführer: Stephan Dühr, M. Außendorf,
J. Steffens, P. Storz

Łukasz Szczepanik

unread,
Aug 2, 2022, 9:58:17 AM8/2/22
to bareos-users
Hi Philipp,

Thanks for your feedback. I forgot to mention that the restore operation uses option 'where' which points to /tmp/bareos so this is not restoration on live /var file system.
Nevertheless I executed bareos-fd with debug 500 and  the output ( 3700 files + decryption and decompression ) is enormous :D  but I will try find something .
Do you know which specific keyword , rc codes I can search to find the answer ?

Thanks

Philipp Storz

unread,
Aug 2, 2022, 10:02:45 AM8/2/22
to bareos...@googlegroups.com
Hello Łukasz,

look for typical words that are logged when somethig goes wrong, like:
"failed, error, unable, cannot, warning" and so on.

Start your search from the bottom of the log file.

Am 02.08.22 um 15:58 schrieb Łukasz Szczepanik:
>
> Thanks for your feedback. I forgot to mention that the restore operation uses option 'where' which
> points to /tmp/bareos so this is not restoration on live /var file system.
> Nevertheless I executed bareos-fd with debug 500 and  the output ( 3700 files + decryption and
> decompression ) is enormous :D  but I will try find something .
> Do you know which specific keyword , rc codes I can search to find the answer ?
>


Reply all
Reply to author
Forward
0 new messages