[bareos-users] Re: BAREOS interrupted by signal 11: Segmentation violation
Is nobody able to help? Which program issued that failure "Segmentation violation"? Does it mean, that MariaDb is corrupted? Thanks for any advice! Helmut P. Am Samstag, 30. November 2019 12:07:06 UTC+1 schrieb Helmut Pable: > > Hi, > my bareos installation worked well during the last 12 months without any > change of config-files, operating on dedicated server under Ubuntu 16.04.5 > LTS. Bareos Version: 18.2.5 (30 January 2019), Ver 15.1 Distrib > 10.0.38-MariaDB, for debian-linux-gnu (i686). > > Yesterday afternoon filedaemon of all my local workstations showed all > jobs were finished successfully, the last one at 26-Nov-19 04:12. > > Then I wanted to look at the results of the last backups. > I opened web-UI and it showed "Error: Connection refused, director seems > to be down or blocking our request". > > On the backup-server I got: > root@n8800:~# systemctl status bareos-director.service > ? bareos-director.service - Bareos Director Daemon service >Loaded: loaded (/lib/systemd/system/bareos-director.service; enabled; > vendor preset: enabled) >Active: failed (Result: signal) since Fre 2019-11-29 17:16:11 CET; 1min > 31s ago > Docs: man:bareos-dir(8) > Process: 25662 ExecStartPre=/usr/sbin/bareos-dir -t -f (code=killed, > signal=SEGV) > > Nov 29 17:16:11 n8800 systemd[1]: Starting Bareos Director Daemon > service... > Nov 29 17:16:11 n8800 bareos-dir[25662]: BAREOS interrupted by signal 11: > Segmentation violation > Nov 29 17:16:11 n8800 bareos-dir[25662]: BAREOS interrupted by signal 11: > Segmentation violation > Nov 29 17:16:11 n8800 systemd[1]: bareos-director.service: Control process > exited, code=killed status=11 > Nov 29 17:16:11 n8800 systemd[1]: Failed to start Bareos Director Daemon > service. > Nov 29 17:16:11 n8800 systemd[1]: bareos-director.service: Unit entered > failed state. > Nov 29 17:16:11 n8800 systemd[1]: bareos-director.service: Failed with > result 'signal'. > > Searching this mailinglist I found > https://groups.google.com/forum/#!searchin/bareos-users/BAREOS$20interrupted$20by$20signal$2011$3A$20Segmentation$20violation%7Csort:date/bareos-users/2AjM9gG6WdI/xkqRlhiGAAAJ > > Bruno Friedmann: > You can try > > /usr/sbin/bareos-dir -t -d 200 -u bareos -g bareos > > to find the culprit. > > root@n8800:~# /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: > 87 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/filesvr02-dat-fd.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/client/filesvr02-fd.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/client/filesvr02-pab-fd.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/client/NB02-fd.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/client/P03-dat-fd.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/client/P03-fd.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/client/P04-dat-fd.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/client/P04-fd.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/client/Win81Pro-fd.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/bareos/bareos-dir.d/director/bareos-dir.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/fileset/backup-bareos.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/fileset/BackupCatalog.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/fileset/Catalog.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/fileset/filesvr02.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/fileset/filesvr02-dat.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/fileset/filesvr02-pab.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/fileset/LinuxAll.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /etc/bareos/bareos-dir.d/fileset/NB02.conf > bareos-dir (100): lib/lex.cc:229-0 open config file: > /
Re: [bareos-users] Howto get used tapes in bareos
Hi MK, Am 03.12.19 um 21:02 schrieb Spadajspadaj: > >> Any hints? AS this are like 300 tapes, and doing "add" in bconsole by >> hand will take to long. >> > Won't update slots (or update slots scan) help? tried this already with no success. Regards Adam -- Adam Podstawka -- 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/5af0ac3f-9991-5309-7557-3953b05bbf07%40dsmz.de.
Re: [bareos-users] Howto get used tapes in bareos
Hi Brock, thanks for this, i think we need to go this way Just wanted to mention that the tapes came from an old bareos instance and were labeled there. Had the hope to get them used without any extra work. Regards Adam Am 03.12.19 um 16:05 schrieb Brock Palen: > I would do the following (google for exact commands) > > BTW I would personally relabel them, but I use encryption managed by bareos > in the tape drive. Also I think bareos tape labels are different than other > software, so the label on the media cannot be reused, (I think) > > Shutdown the SD, to be safe eject any tapes you don’t want to be purged. > If your library understands mtx us it to get a list of slots. > > Make a script that itterates over every tape (if you have two drives split > into two lists to speed up) > > use mt to weof to each tape and just loop through them. > > > eg. (verify working from memory) > sg0 is the library > sg1 is the first drive (lsscsi -g) May want to use the /dev/nst* devices > instead. > > for x in $(cat /tmp/slots) > do > echo “Loading slot $x" > mtx -f /dev/sg0 load $x 0 > > # write end of file at start of tape taking out old data/label > mt -f /dev/sg1 rewind > mt -f /dev/sg1 weof > mt -f /dev/sg1 rewind > > echo “Ejecting drive 0 to slot $x > mtx -f /dev/sg0 unload 0 $x > done > > > Finally when all done in bareos > > update slots > label pool=Scratch barcodes encrypt yes > > > Verify all my syntax/do a test run with a single tape, it will be slow but > should work. > > > Brock Palen > 1 (989) 277-6075 > bro...@mlds-networks.com > www.mlds-networks.com > Websites, Linux, Hosting, Joomla, Consulting > > > >> On Dec 3, 2019, at 5:45 AM, Adam Podstawka wrote: >> >> Hi, >> >> i have a little problem, we build a new backup system and wanted to use >> our old tapes in it. But the tapes are all labeled already through the >> old system. >> An "label barcodes" doesn't add them to the pool, as they are already >> labeld. >> i can't get to work an "echo 'add pool=Scratch volumename=01L6' | >> bconsole", but i don't want to mount all tapes and delete the >> label/empty them to be able to use them in the new system. >> >> Any hints? AS this are like 300 tapes, and doing "add" in bconsole by >> hand will take to long. >> >> Thanks >> Adam >> >> -- >> Adam Podstawka >> >> -- >> 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/0025900e-29cd-a635-dc6b-fa0e83748941%40dsmz.de. -- Adam Podstawka -- 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/0b0b86cb-23f5-4d81-b617-40aa61a0735d%40dsmz.de.
