Hi, but issue is solved, I think, putting all key=values required. I
mean, file is:
Job {
Name = "Patricio Desktop"
File Set = "Windows7-Usuarios"
Client = "patriciodesktop-fd"
}
but for Job resource require Messages, Name, Pool and Type directives.
Examples from bareos installation works because JobDefs already define
those values, and examples jobs use JobDefs previously defined. But
customizing while learning I got that error.
Is possible to validate them and throw an exception/error
message/log/etc... instead of a crash? Seems tutorial
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-890006.8
for add a new client doesn't reflect this.
El 19/05/17 a las 04:51, Stephan Duehr escribió:
On 05/18/2017 09:02 AM, Bruno Friedmann wrote:
On jeudi, 18 mai 2017 06.25:05 h CEST [email protected] wrote:
Hi all, I'm new to Bareos and want to start using it. Currently with a
"hello world" example I have a segmentation violation in Director.
i) My environment is:
Director, Storage and File daemons:
KVM guest opensuse Leap 42.2, using Leap 42.1 repo (bareos 16.2.4-12.1)
Host is a openSUSE Leap 42.2, own "command" laptop
Database is other computer with openSUSE Leap 42.2, using one instance of
MySQL, but for bareos I have a MySQL 5.6 in a fresh docker container using
https://hub.docker.com/_/mysql/ and executed with:
docker run --name mysql56 \
-e MYSQL_ROOT_PASSWORD=mysql \
-e MYSQL_ONETIME_PASSWORD=yes \
-v /media/Data/docker_mysql56/databases:/var/lib/mysql \
-v /media/Data/docker_mysql56/conf.d:/etc/mysql/conf.d \
-d \
-p 3307:3306 \
mysql:5.6
after configuring root, created a 'bareos@%' pass:'bareos' to
database:'bareos_test' access only
ii) Can't create db, already exists. I realize that creation scripts for
mysql only create database, so skiped this step. Run table creation scripts
and finish without errors. No scripts after this.
iii) As a single test, I followed tutorial from Bareos manual and works OK
for "own command" laptop recovery and restore example. Both are openSUSE.
iv) Tryed to use it with a Windows File daemon (Windows 7), and I did this
(connected to the Guest VM): a) configured Director as
bareostest:/etc/bareos/bareos-dir.d # cat catalog/MyCatalog.conf
Catalog {
Name = MyCatalog
# Uncomment the following lines if you want the dbi driver
# dbdriver = "dbi:postgresql"; dbaddress = 127.0.0.1; dbport =
#dbdriver = "postgresql"
dbdriver = "mysql"
dbaddress = "192.168.1.10"
dbport = "3307"
dbname = "bareos_test"
dbuser = "bareos"
dbpassword = "bareos"
}
b) created files
bareostest:/etc/bareos/bareos-dir.d # cat fileset/Windows7-Usuarios.conf
FileSet {
Name = "Windows7-Usuarios"
Enable VSS = yes
Include {
Options {
Signature = MD5
Drive Type = fixed
IgnoreCase = yes
WildFile = "[A-Z]:/pagefile.sys"
WildDir = "[A-Z]:/RECYCLER"
WildDir = "[A-Z]:/$RECYCLE.BIN"
WildDir = "[A-Z]:/System Volume Information"
Exclude = yes
}
File = "C:/"
}
}
bareostest:/etc/bareos/bareos-dir.d # cat client/patriciodesktop-fd.conf
Client {
Name = patriciodesktop-fd
Description = "Windows 7 Desktop Patricio"
Address = 192.168.1.21
Password = "bareospatricio" # password for FileDaemon
}
bareostest:/etc/bareos/bareos-dir.d/job # cat patriciodesktop-fd.conf
Job {
Name = "Patricio Desktop"
File Set = "Windows7-Usuarios"
Client = "patriciodesktop-fd"
}
c) bareostest:/etc/bareos/bareos-dir.d/job # bconsole
Connecting to Director localhost:9101
1000 OK: bareos-dir Version: 16.2.4 (01 July 2016)
Enter a period to cancel a command.
*reload
bareostest:/etc/bareos/bareos-dir.d/job #
suddenly crash, logs say:
may 18 00:35:46 bareostest bareos-dir[3646]: BAREOS interrupted by signal
11: Segmentation violation
Everything is repeatable, because I've retryed creating docker mysql
container again, VM Guest again, example from tutorial step by step, but
can't find the way to know what I missing, or if is a bug.
Hope you can help me. Thanks in advance.
Patricio Mercado G.
Known segfault for experimented users ;-)
You normally have a Description field or another one that is missing it's
ending quote.
You can try
/usr/sbin/bareos-dir -t -d 200 -u bareos -g bareos
to find the culprit.
Also please install the package bareos-director-debuginfo and gdb:
zypper install bareos-director-debuginfo gdb
so when the segmentation fault happens, it will create a traceback
file in /var/lib/bareos
Regards,
--
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].
For more options, visit https://groups.google.com/d/optout.
