Re: [bareos-users] Segmentation fault (core dumped)
You may want to try bareos -t -d 200 #where 200 is the debug level; the higher the number the more output. Do not be confused by the segmentation fault, this is the current fatal-exit of the director. This can also happen on a misconfigured config or database connection. The debug messages should tell you more. Am 26.11.19 um 16:09 schrieb 'DUCARROZ Birgit' via bareos-users: P.S. I installed bareos now on 3 different servers (new installation). 3x the same error: # bareos-dir -t BAREOS interrupted by signal 11: Segmentation violation Segmentation fault (core dumped) Seems to be in relation with the DB, not with the files in bareos-dir.d Can someone reproduce this error? This is my installation: Ubuntu 16.04 LTS Linux diufnas26 4.4.0-169-generic #198-Ubuntu SMP Tue Nov 12 10:38:00 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # Install the DB: apt update && apt upgrade -y RELEASE=release/latest/ DIST=xUbuntu_$(lsb_release -sr) URL=http://download.bareos.org/bareos/$RELEASE/$DIST printf "deb $URL /\n" | sudo tee /etc/apt/sources.list.d/bareos.list wget -q $URL/Release.key -O- | sudo apt-key add - apt update apt install mariadb-server -y apt install mariadb-server bareos bareos-database-mysql /usr/lib/bareos/scripts/create_bareos_database /usr/lib/bareos/scripts/make_bareos_tables /usr/lib/bareos/scripts/grant_bareos_privileges systemctl start bareos-dir systemctl start bareos-sd systemctl start bareos-fd systemctl restart mysql Kind regards, Birgit On 26/11/19 12:52, 'DUCARROZ Birgit' via bareos-users wrote: Hello, Can someone help me with this please? root@diufnas26:/etc/bareos/bareos-dir.d/fileset# systemctl restart bareos-dir Job for bareos-director.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status bareos-director.service" and "journalctl -xe" for details. When I execute /usr/sbin/bareos-dir I get no error. bareos-dir -t BAREOS interrupted by signal 11: Segmentation violation Segmentation fault (core dumped) root@diufnas26:/etc/bareos/bareos-dir.d/fileset# journalctl -xe -- Subject: Unit apache2.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2.service has begun starting up. Nov 26 12:43:12 diufnas26 apache2[12710]: * Starting Apache httpd web server apache2 Nov 26 12:43:13 diufnas26 apache2[12710]: * Nov 26 12:43:13 diufnas26 systemd[1]: Started LSB: Apache2 web server. -- Subject: Unit apache2.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2.service has finished starting up. -- -- The start-up result is done. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: State 'stop-sigterm' timed out. Killing. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: Main process exited, code=killed, status=9/KILL Nov 26 12:43:28 diufnas26 systemd[1]: Stopped Bareos Storage Daemon service. -- Subject: Unit bareos-storage.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit bareos-storage.service has finished shutting down. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: Unit entered failed state. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: Failed with result 'signal'. Nov 26 12:43:28 diufnas26 systemd[1]: Starting Bareos Storage Daemon service... -- Subject: Unit bareos-storage.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit bareos-storage.service has begun starting up. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: PID file /var/lib/bareos/bareos-sd.9103.pid not readable (yet Nov 26 12:43:28 diufnas26 systemd[1]: Started Bareos Storage Daemon service. -- Subject: Unit bareos-storage.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit bareos-storage.service has finished starting up. -- -- The start-up result is done. Nov 26 12:43:57 diufnas26 bareos-dir[12756]: BAREOS interrupted by signal 11: Segmentation violation root@diufnas26:/etc/bareos/bareos-dir.d/fileset# /usr/sbin/bareos-dir -t -d 200 -u bareos -g bareos bareos-dir (10): dird/dird.cc:258-0 Debug level = 200 bareos-dir (100): lib/parse_conf.cc:191-0 config file = /etc/bareos/bareos-dir.d/*/*.conf bareos-dir (100): lib/lex.cc:335-0 glob /etc/bareos/bareos-dir.d/*/*.conf: 86 files bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/catalog/MyCatalog.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/bareos-fd.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/lx85.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/
Re: [bareos-users] Segmentation fault (core dumped)
P.S. I installed bareos now on 3 different servers (new installation). 3x the same error: # bareos-dir -t BAREOS interrupted by signal 11: Segmentation violation Segmentation fault (core dumped) Seems to be in relation with the DB, not with the files in bareos-dir.d Can someone reproduce this error? This is my installation: Ubuntu 16.04 LTS Linux diufnas26 4.4.0-169-generic #198-Ubuntu SMP Tue Nov 12 10:38:00 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # Install the DB: apt update && apt upgrade -y RELEASE=release/latest/ DIST=xUbuntu_$(lsb_release -sr) URL=http://download.bareos.org/bareos/$RELEASE/$DIST printf "deb $URL /\n" | sudo tee /etc/apt/sources.list.d/bareos.list wget -q $URL/Release.key -O- | sudo apt-key add - apt update apt install mariadb-server -y apt install mariadb-server bareos bareos-database-mysql /usr/lib/bareos/scripts/create_bareos_database /usr/lib/bareos/scripts/make_bareos_tables /usr/lib/bareos/scripts/grant_bareos_privileges systemctl start bareos-dir systemctl start bareos-sd systemctl start bareos-fd systemctl restart mysql Kind regards, Birgit On 26/11/19 12:52, 'DUCARROZ Birgit' via bareos-users wrote: Hello, Can someone help me with this please? root@diufnas26:/etc/bareos/bareos-dir.d/fileset# systemctl restart bareos-dir Job for bareos-director.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status bareos-director.service" and "journalctl -xe" for details. When I execute /usr/sbin/bareos-dir I get no error. bareos-dir -t BAREOS interrupted by signal 11: Segmentation violation Segmentation fault (core dumped) root@diufnas26:/etc/bareos/bareos-dir.d/fileset# journalctl -xe -- Subject: Unit apache2.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2.service has begun starting up. Nov 26 12:43:12 diufnas26 apache2[12710]: * Starting Apache httpd web server apache2 Nov 26 12:43:13 diufnas26 apache2[12710]: * Nov 26 12:43:13 diufnas26 systemd[1]: Started LSB: Apache2 web server. -- Subject: Unit apache2.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2.service has finished starting up. -- -- The start-up result is done. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: State 'stop-sigterm' timed out. Killing. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: Main process exited, code=killed, status=9/KILL Nov 26 12:43:28 diufnas26 systemd[1]: Stopped Bareos Storage Daemon service. -- Subject: Unit bareos-storage.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit bareos-storage.service has finished shutting down. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: Unit entered failed state. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: Failed with result 'signal'. Nov 26 12:43:28 diufnas26 systemd[1]: Starting Bareos Storage Daemon service... -- Subject: Unit bareos-storage.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit bareos-storage.service has begun starting up. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: PID file /var/lib/bareos/bareos-sd.9103.pid not readable (yet Nov 26 12:43:28 diufnas26 systemd[1]: Started Bareos Storage Daemon service. -- Subject: Unit bareos-storage.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit bareos-storage.service has finished starting up. -- -- The start-up result is done. Nov 26 12:43:57 diufnas26 bareos-dir[12756]: BAREOS interrupted by signal 11: Segmentation violation root@diufnas26:/etc/bareos/bareos-dir.d/fileset# /usr/sbin/bareos-dir -t -d 200 -u bareos -g bareos bareos-dir (10): dird/dird.cc:258-0 Debug level = 200 bareos-dir (100): lib/parse_conf.cc:191-0 config file = /etc/bareos/bareos-dir.d/*/*.conf bareos-dir (100): lib/lex.cc:335-0 glob /etc/bareos/bareos-dir.d/*/*.conf: 86 files bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/catalog/MyCatalog.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/bareos-fd.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/lx85.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/nas01.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/nas20.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/nas21.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/nas22.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /e
[bareos-users] 18.2.6 statistics collection
Hello,
I'm trying to enable the statistics collection on 18.2.6, FreeBSD - without
success.
in dir-Director {
Statistics Collect Interval = 60
Statistics Retention = 7776000
in dir-Storage {
Collect Statistics = yes
in sd-Storage {
Collect Device Statistics = yes
Collect Job Statistics = yes
Statistics Collect Interval = 60
When I run a job, the JobStats table is empty and stays empty and there's a
Device table but it's also empty, 0 rows, just like DeviceStats.
What do I miss?
Thank you in advance,
Felicián
--
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/2c873898-279d-4169-9315-b69bcccd0833%40googlegroups.com.
[bareos-users] Segmentation fault (core dumped)
Hello, Can someone help me with this please? root@diufnas26:/etc/bareos/bareos-dir.d/fileset# systemctl restart bareos-dir Job for bareos-director.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status bareos-director.service" and "journalctl -xe" for details. When I execute /usr/sbin/bareos-dir I get no error. bareos-dir -t BAREOS interrupted by signal 11: Segmentation violation Segmentation fault (core dumped) root@diufnas26:/etc/bareos/bareos-dir.d/fileset# journalctl -xe -- Subject: Unit apache2.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2.service has begun starting up. Nov 26 12:43:12 diufnas26 apache2[12710]: * Starting Apache httpd web server apache2 Nov 26 12:43:13 diufnas26 apache2[12710]: * Nov 26 12:43:13 diufnas26 systemd[1]: Started LSB: Apache2 web server. -- Subject: Unit apache2.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2.service has finished starting up. -- -- The start-up result is done. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: State 'stop-sigterm' timed out. Killing. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: Main process exited, code=killed, status=9/KILL Nov 26 12:43:28 diufnas26 systemd[1]: Stopped Bareos Storage Daemon service. -- Subject: Unit bareos-storage.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit bareos-storage.service has finished shutting down. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: Unit entered failed state. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: Failed with result 'signal'. Nov 26 12:43:28 diufnas26 systemd[1]: Starting Bareos Storage Daemon service... -- Subject: Unit bareos-storage.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit bareos-storage.service has begun starting up. Nov 26 12:43:28 diufnas26 systemd[1]: bareos-storage.service: PID file /var/lib/bareos/bareos-sd.9103.pid not readable (yet Nov 26 12:43:28 diufnas26 systemd[1]: Started Bareos Storage Daemon service. -- Subject: Unit bareos-storage.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit bareos-storage.service has finished starting up. -- -- The start-up result is done. Nov 26 12:43:57 diufnas26 bareos-dir[12756]: BAREOS interrupted by signal 11: Segmentation violation root@diufnas26:/etc/bareos/bareos-dir.d/fileset# /usr/sbin/bareos-dir -t -d 200 -u bareos -g bareos bareos-dir (10): dird/dird.cc:258-0 Debug level = 200 bareos-dir (100): lib/parse_conf.cc:191-0 config file = /etc/bareos/bareos-dir.d/*/*.conf bareos-dir (100): lib/lex.cc:335-0 glob /etc/bareos/bareos-dir.d/*/*.conf: 86 files bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/catalog/MyCatalog.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/bareos-fd.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/lx85.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/nas01.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/nas20.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/nas21.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/nas22.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/nas26.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/nas27.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/rd140.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/rd141.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/vm20.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/vm25.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/vm32.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/vm35.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/vm57.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/client/websrv.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/console/admin.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bareos/bareos-dir.d/console/bareos-mon.conf bareos-dir (100): lib/lex.cc:229-0 open config file: /etc/bar
