Any help on this?We are still stuck during restore: "Waiting for jobs to start"
In logs I can see below error: failed to connect to director localhost:9101 We have created a similar machine with same configuration. I have not enabled network. Please let us know if anyone has any clue. Thanks On Thursday, 28 July 2022 at 16:27:49 UTC+5:30 Parashar Pradhan wrote: > > Thanks Juergen, > > After configuring bconsole in client now I am able to create rescue image > using rear. > > However during restore I am stuck at below > "Waiting for jobs to start" > > In logs I can see below error: > > failed to connect to director localhost:9101 > > Any help on this please? > > Thanks > > On Friday, 22 July 2022 at 19:20:29 UTC+5:30 j.echter wrote: > >> Am Freitag, Juli 22, 2022 07:59 CEST, schrieb Parashar Pradhan < >> [email protected]>: >> >> > Hello Team, >> > >> > I am integrating bareos with relax and recovery >> > >> > Here is my rear configuration which I kept to minimum >> > >> > cat /etc/rear/local.conf >> > BACKUP=BAREOS >> > BAREOS_CLIENT=client7-fd >> > >> > Here is my client configuration >> > >> > # cat client7-fd.conf >> > Client { >> > Name = "client7-fd" >> > Address = "x.x.x.x" >> > Password = "secret" >> > } >> > >> > I checked on bconsole and it is connecting to the client >> > >> > Connecting to Client client7-fd at x.x.x.x:9102 >> > Handshake: Immediate TLS, Encryption: TLS_CHACHA20_POLY1305_SHA256 >> TLSv1.3 >> > >> > Daemon started 22-Jul-22 11:11. Jobs: run=0 running=0, bareos.org >> build >> > binary >> > Sizeof: boffset_t=8 size_t=8 debug=0 trace=0 bwlimit=0kB/s >> > >> > Running Jobs: >> > bareos-dir (director) connected at: 22-Jul-22 11:25 >> > No Jobs running. >> > >> > But while running mkrescue I am getting below error: >> > >> > # rear -v mkrescue >> > Relax-and-Recover 2.6 / 2020-06-17 >> > Running rear mkrescue (PID 3252) >> > Using log file: /var/log/rear/rear-xxx.log >> > Running workflow mkrescue on the normal/original system >> > Using autodetected kernel '/boot/vmlinuz-5.15.0-41-generic' as kernel >> in >> > the recovery system >> > ERROR: Bareos client status unknown on director. >> > Some latest log messages since the last called script >> > 500_check_BAREOS_bconsole_results.sh: >> > 2022-07-22 11:14:08.399529544 Including >> > prep/BAREOS/default/500_check_BAREOS_bconsole_results.sh >> > 2022-07-22 11:14:08.404756789 Skipping ping test >> > Aborting due to an error, check /var/log/rear/rear-xxxx.log for details >> > Exiting rear mkrescue (PID 3252) and its descendant processes ... >> > Running exit tasks >> > Terminated >> > >> > Any help on this is appreciated. >> > >> > Thanks >> > >> > -- >> >> >> Hi, >> >> i think you need to setup bconsole on the client too. >> >> Cheers >> >> Juergen >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/7321b085-f721-4da9-b201-30c97dcfd657n%40googlegroups.com.
