Could you try running the director in the foreground with 'bareos-dir -f
-d 1000' or 'bareos-dir -f -d 2000'.
.. frank
Am 27.05.19 um 14:43 schrieb bareos-user:
Hello.
I'm trying to test bareos-18.2.6 on ArchLinux.
And I have two questions:
1. When I try to run bareos-dir with the -d option (for example -d
2000), bareos-dir fails with the error:
----
[root@a10 ~]# systemctl status bareos-dir
* bareos-dir.service - Bareos Director Daemon service
Loaded: loaded (/etc/systemd/system/bareos-dir.service; enabled;
vendor preset: disabled)
Active: active (running) since Mon 2019-05-27 15:32:33 +05; 7s ago
Docs: man:bareos-dir(8)
Process: 933 ExecStartPre=/usr/bin/bareos-dir -t -f (code=exited,
status=0/SUCCESS)
Process: 934 ExecStart=/usr/bin/bareos-dir -d 2000 (code=exited,
status=0/SUCCESS)
Main PID: 935 (bareos-dir)
Tasks: 5 (limit: 2133)
Memory: 20.1M
CGroup: /system.slice/bareos-dir.service
|-935 /usr/bin/bareos-dir -d 2000
|-938 /bin/sh /usr/bin/btraceback /usr/bin/bareos-dir 935
/var/lib/bareos
`-952 /usr/bin/gdb -quiet -batch -x
/usr/lib/bareos/scripts/btraceback.gdb /usr/bin/bareos-dir
/var/lib/bareos/bareos-dir.core.935
May 27 15:32:33 a10.domain.tld bareos-dir[934]: BAREOS interrupted by
signal 11: Segmentation violation
May 27 15:32:33 a10.domain.tld bareos-dir[934]: bareos-dir,
a10-director got signal 11 - Segmentation violation. Attempting
traceback.
May 27 15:32:33 a10.domain.tld bareos-dir[934]: exepath=/usr/bin/
May 27 15:32:33 a10.domain.tld bareos-dir[934]: a10-director (300):
lib/signal.cc:207-0 Working=/var/lib/bareos
May 27 15:32:33 a10.domain.tld bareos-dir[934]: a10-director (300):
lib/signal.cc:208-0 btpath=/usr/bin/btraceback
May 27 15:32:33 a10.domain.tld bareos-dir[934]: a10-director (300):
lib/signal.cc:209-0 exepath=/usr/bin/bareos-dir
May 27 15:32:33 a10.domain.tld bareos-dir[934]: a10-director (500):
lib/signal.cc:240-0 Doing waitpid
May 27 15:32:33 a10.domain.tld bareos-dir[934]: a10-director (800):
lib/watchdog.cc:255-0 NicB-reworked watchdog thread entered
May 27 15:32:33 a10.domain.tld bareos-dir[935]: BAREOS interrupted by
signal 11: Segmentation violation
May 27 15:32:33 a10.domain.tld bareos-dir[934]: Calling:
/usr/bin/btraceback /usr/bin/bareos-dir 935 /var/lib/bareos
----
Has anyone tried running bareos-dir with the -d option and for it to
work?
2. In the event of an abnormal shutdown, the bareos-dir starts the
wrapper for the gdb debugger, and the file
/usr/lib/bareos/scripts/btraceback.gdb with the gdb commands is
included (ie: print my_name, print exename, ..). In my case, gdb
cannot execute a series of commands:
-----
[root@a10 ~]# cat /var/lib/bareos/bareos.935.traceback
Created /var/lib/bareos/bareos-dir.core.935 for doing postmortem
debugging
[New LWP 935]
[New LWP 936]
[New LWP 937]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/bareos-dir'.
#0 0xb6c5b32c in waitpid () from /usr/lib/libpthread.so.0
[Current thread is 1 (Thread 0xb6fafd40 (LWP 935))]
/usr/lib/bareos/scripts/btraceback.gdb:1: Error in sourced command file:
'my_name' has unknown type; cast it to its declared type
-----
and I would like to understand: is this my particular case like this
or is it all so?
Thank you.
--
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/11d90256-29a5-583b-bd50-d6b629665fbb%40bareos.com.
For more options, visit https://groups.google.com/d/optout.
