Hello,
I have a Bareos 17.2.4 with postgreSQL
I am trying to do a restore via the WebUI.
But I only see directories if I select a client that runs linux.
If I try a Windows-Client - its loading and I see these lines in
/var/log/bareos/bareos-audit.log:
10-Jän 10:18 bareos-dir: Console
I can't writing in my Ultrim 960
"Bareos requires the nst devices so / dev / nst0 instead of / dev / st0. Shoe"
I tested all devices
"I'm not sure, if this solves the problem. You also get the btape test
program. Have you installed the bareos-storage-tape package?"
Of course
I testing
Am Mittwoch, 10. Januar 2018 10:41:38 UTC+1 schrieb Frank Bergkemper:
> Am 10.01.2018 um 10:25 schrieb Oliver Fink:
> > Hello,
> >
> > I have a Bareos 17.2.4 with postgreSQL
> >
> >
> > I am trying to do a restore via the WebUI.
> >
> > But I only see directories if I select a client that runs
I keep getting Segmentation Faults currently since I upgraded to version
17.2.4-9.1 on Debian Stretch.
Can anyone tell me what might be the problem?
Created /var/lib/bareos/bareos-dir.core.12956 for doing postmortem debugging
[New LWP 12956]
[New LWP 12957]
[New LWP 12960]
[New LWP 12961]
Try bareos-17.2.4 from download.bareos.org. There have been a bug with
block sizes in earlier versions (and "[6.252610] st 6:0:3:0: [st0]
Block limits 1 - 16777215 bytes." may points to that).
On 10.01.2018 at 11:14 wrote Maciej Piasecki:
> I can't writing in my Ultrim 960
>
> "Bareos
Hi Maciej,
have you tried /dev/tape/by-id/scsi...-nst ?
This is a a single drive, not a library, right? Is this the first time
you want to use it with Bareos?
Greetings from Berlin,
Kai
Am 10.01.2018 um 11:14 schrieb Maciej Piasecki:
I can't writing in my Ultrim 960
"Bareos requires the
Well, the segfault happens in Thread 5:
Thread 5 (Thread 0x7fab87fff700 (LWP 12962)):
#0 0x7fab9677db3a in __waitpid (pid=pid@entry=60063,
stat_loc=stat_loc@entry=0x7fab87ffd54c, options=options@entry=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
#1 0x7fab97f4dab4 in signal_handler
