Hi Philipp and Bruno, Thank you for your answers and sorry for the late reply. Bareos sends me all the mails, but no mail with .bsr messages. And yes, I backup my bsr files on a third share, I always did. For me the problem is solved although I do not know why I get no email with the bsr information.
BTW, since I use bareos (version 18) : It works perfectly :-) Best regards, Birgit Bruno Friedmann schrieb am Dienstag, 20. Juni 2023 um 17:51:43 UTC+2: > Mainly if you have a working message resource configuration, then you can > almost copy and paste it to the Write Bootstrap line. > The syntax you had use let think to Bareos to write a file, and no more > running a shell command. > > The other way is to store the bsr somewhere else (like other job bsr for > example) you know you will be able to grab in case of disaster recovery. > > On Tuesday, June 20, 2023 at 12:34:09 PM UTC+2 Philipp Storz wrote: > >> Am 20.06.23 um 12:09 schrieb 'Birgit Ducarroz' via bareos-users: >> > Hi Philipp, >> > >> > Thank you for your response. I changed the bsmtp call into >> > Write Bootstrap = "/usr/bin/bsmtp -h localhost -f \"\(Bareos\) \" -s >> \"Bootstrap for Job %j\" root" >> > But then I get the following error: >> > Error: Could not open WriteBootstrap file: >> > /usr/bin/bsmtp -h root@localhost -f: ERR=Permission denied >> > >> > However, the file bareos.sql has been written into the directory. >> According to >> > https://bugs.bareos.org/view.php?id=587 >> > list jobs shows me a T and successfull terminated. >> > >> > Enter a period (.) to cancel a command. >> > *list joblog >> > Automatically selected Catalog: MyCatalog >> > Using Catalog "MyCatalog" >> > You have messages. >> > *list jobs >> > >> +-------+------------------+-----------+---------------------+----------+------+-------+----------+------------+-----------+ >> >> >> > | jobid | name | client | starttime | duration >> | type | level | jobfiles | >> > jobbytes | jobstatus | >> > >> +-------+------------------+-----------+---------------------+----------+------+-------+----------+------------+-----------+ >> >> >> > | 1 | BackupCatalog | bareos-fd | 2023-06-20 11:01:37 | 00:00:01 >> | B | F | 3,275 | >> > 24,520,303 | T | >> > >> +-------+------------------+-----------+---------------------+----------+------+-------+----------+------------+------- >> >> >> > >> > If I comment out Write Bootstrap = "/usr/bin/bsmtp -h localhost -f >> \"\(Bareos\) \" -s \"Bootstrap >> > for Job %j\" root" >> > No errors anymore, but I think it is not the aim to ignore the return >> value ... >> > >> > I'm a bit confused about the permission denied error, since the job >> returns a success and the file >> > has been written. Any ideas? >> The bootstrap file should be sent via email, not the sql dump (which is >> much too large probably). >> >> What you can try is to find a working bsmtp call on your machine by >> echoing some text into bsmtp to >> check what the error might be, like >> >> echo "hello" | /usr/bin/bsmtp -h localhost ... >> >> >> > >> > Philipp Storz schrieb am Montag, 19. Juni 2023 um 12:36:13 UTC+2: >> > >> > Hello Birgit, >> > >> > this error is caused by the changes introduced with PR 1296: >> > https://github.com/bareos/bareos/pull/1296 < >> https://github.com/bareos/bareos/pull/1296> >> > >> > The old behaviour was to ignore the return value of the program that >> the bootstrap was sent to, now >> > bareos checks for the return value. >> > >> > So to solve your problem you need to make sure that the bsmtp call is >> successful. >> > >> > Probably you can see the problem if you execute the command show >> manually. >> > >> > Best regards, >> > >> > Philipp >> > >> > >> > Am 19.06.23 um 12:21 schrieb 'DUCARROZ Birgit' via bareos-users: >> > > Hi, >> > > >> > > Please can someone help me with this error? >> > > I installed a brand new bareos 22 >> > > Build OS: Ubuntu 22.04.1 LTS >> > > >> > > In the webGUI the job is marked ass success - green >> > > >> > > It happens with the Catalog Backup. The bareos-fd backup shows no >> errors >> > > >> > > bareos-dir JobId 2: Error: Error running program when updating >> bootstrap file: >> > |/usr/bin/bsmtp -h >> > > localhost -f "(Bareos) " -s "Bootstrap for Job >> BackupCatalog.2023-06-19_12.02.07_09" root: >> > ERR=Child >> > > exited with code 1 >> > > >> > > Thank you a lot! >> > > Regards, >> > > Birgit >> > > >> > >> > -- >> > Mit freundlichen Grüßen >> > >> > Philipp Storz philip...@bareos.com >> > Bareos GmbH & Co. KG Phone: +49 221 63 06 93-92 <+49%20221%2063069392> >> <tel:+49%20221%2063069392> >> > http://www.bareos.com <http://www.bareos.com> Fax: +49 221 63 06 93-10 >> <+49%20221%2063069310> <tel:+49%20221%2063069310> >> > >> > Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 >> > Geschäftsführer: Stephan Dühr, J. Steffens, P. Storz >> > >> > -- >> > 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/1ad86ead-ab1c-4e27-a4ff-44c4a41d8d1bn%40googlegroups.com >> >> < >> https://groups.google.com/d/msgid/bareos-users/1ad86ead-ab1c-4e27-a4ff-44c4a41d8d1bn%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 <+49%20221%2063069392> >> http://www.bareos.com Fax: +49 221 63 06 93-10 <+49%20221%2063069310> >> >> Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 >> Geschäftsführer: Stephan Dühr, J. Steffens, P. Storz >> >> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/e1fcec60-017c-4d55-ba92-0aa9a18355ffn%40googlegroups.com.
