Re: [Bacula-users] bacula-dir crashing
Hello, On 10 September 2012 01:11, Tim Dunphy bluethu...@gmail.com wrote: I was able to get a more recent version of bacula on my centos 5.6 with advice from Simone on this list. For some reason thinks that I'm using postgres instead of mysql. I tried setting MyCatalog to use mysql instead in the bacula-dir.conf file however that still resulted in the message you see above from the logs I've installed bacula with yum using the following info: http://repos.fedorapeople.org/repos/slaanesh/bacula/README.txt So in short I just need to know how to tell the current version of bacula to use mysql instead of postgres. you posted the link to the readme file, but did you read it? Here are the last lines of it: To change to a different backend, issue the following command: # alternatives --config libbaccats.so There are 3 programs which provide 'libbaccats.so'. SelectionCommand --- 1 /usr/lib64/libbaccats-mysql.so 2 /usr/lib64/libbaccats-sqlite3.so *+ 3 /usr/lib64/libbaccats-postgresql.so Enter to keep the current selection[+], or type selection number: 1 Regards, --Simone -- You cannot discover new oceans unless you have the courage to lose sight of the shore (R. W. Emerson). -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula-dir crashing
Hello,
I was able to get a more recent version of bacula on my centos 5.6 with
advice from Simone on this list.
I'm now running bacula 5.2.10 Thanks!
However my current situation is that bacula-sd and bacula-fd both run fine
when bacula-dir crashes with the following message in the logs:
[root@cloud:/etc/bacula] #tail -f /var/log/bacula/bacula.log
09-Sep 18:47 bacula-dir JobId 0: Fatal error: Could not open Catalog
MyCatalog, database bacula.
09-Sep 18:47 bacula-dir JobId 0: Fatal error: postgresql.c:248 Unable to
connect to PostgreSQL server. Database=bacula User=bacula
Possible causes: SQL server not running; password incorrect;
max_connections exceeded.
09-Sep 18:47 bacula-dir ERROR TERMINATION
Please correct configuration file: /etc/bacula/bacula-dir.conf
For some reason thinks that I'm using postgres instead of mysql.
I tried setting MyCatalog to use mysql instead in the bacula-dir.conf file
however that still resulted in the message you see above from the logs
# Generic catalog service
Catalog {
Name = MyCatalog
# Uncomment the following line if you want the dbi driver
# dbdriver = dbi:postgresql; dbaddress = 127.0.0.1; dbport =
dbdriver = dbi:mysql; dbaddress = 127.0.0.1; dbport = 3306
dbname = bacula; dbuser = bacula; dbpassword = secretsauce
}
I've checked and I can log into the database using the login information I
supplied in the config and use the bacula database.
I've installed bacula with yum using the following info:
http://repos.fedorapeople.org/repos/slaanesh/bacula/README.txt
Here are the packages I have installed:
[root@cloud:~] #rpm -qa | grep bacula
bacula-client-5.2.10-6.el5
bacula-storage-5.2.10-6.el5
bacula-libs-5.2.10-6.el5
bacula-console-5.2.10-6.el5
bacula-common-5.2.10-6.el5
bacula-director-5.2.10-6.el5
bacula-docs-5.2.10-1.el5
bacula-libs-sql-5.2.10-6.el5
bacula-traymonitor-2.4.4-10.el5
http://repos.fedorapeople.org/repos/slaanesh/bacula/
I'm including my bacula-dir as an attachment just in case it might shed
some light on what needs to be corrected.
So in short I just need to know how to tell the current version of bacula
to use mysql instead of postgres.
Thank you
Tim
--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
#
# Default Bacula Director Configuration file
#
# The only thing that MUST be changed is to add one or more
# file or directory names in the Include directive of the
# FileSet resource.
#
# For Bacula release 5.2.10 (28 June 2012) -- redhat Enterprise release
#
# You might also want to change the default email address
# from root to your address. See the mail and operator
# directives in the Messages resource.
#
Director {# define myself
Name = bacula-dir
DIRport = 9101# where we listen for UA connections
QueryFile = /etc/bacula/query.sql
WorkingDirectory = /var/spool/bacula
PidDirectory = /var/run
Maximum Concurrent Jobs = 1
Password = secretsauce # Console password
Messages = Daemon
}
JobDefs {
Name = DefaultJob
Type = Backup
Level = Incremental
Client = bacula-fd
FileSet = Full Set
Schedule = WeeklyCycle
Storage = File
Messages = Standard
Pool = File
Priority = 10
Write Bootstrap = /var/spool/bacula/%c.bsr
}
#
# Define the main nightly save backup job
# By default, this job will back up to disk in /tmp
Job {
Name = BackupClient1
JobDefs = DefaultJob
}
#Job {
# Name = BackupClient2
# Client = bacula2-fd
# JobDefs = DefaultJob
#}
# Backup the catalog database (after the nightly save)
Job {
Name = BackupCatalog
JobDefs = DefaultJob
Level = Full
FileSet=Catalog
Schedule = WeeklyCycleAfterBackup
# This creates an ASCII copy of the catalog
# Arguments to make_catalog_backup.pl are:
# make_catalog_backup.pl catalog-name
RunBeforeJob = /usr/libexec/bacula/make_catalog_backup.pl MyCatalog
# This deletes the copy of the catalog
RunAfterJob = /usr/libexec/bacula/delete_catalog_backup
Write Bootstrap = /var/spool/bacula/%n.bsr
Priority = 11 # run after main backup
}
#
# Standard Restore template, to be changed by Console program
# Only one such job is needed for all Jobs/Clients/Storage ...
#
Job {
Name = RestoreFiles
Type = Restore
Client=bacula-fd
FileSet=Full Set
Storage = File
Pool = Default
Messages = Standard
Where = /tmp/bacula-restores
}
# List of files to be backed up
FileSet {
Name = Full Set
Include {
Options {
signature = MD5
}
#
# Put your list of files here, preceded by 'File =', one per line
#or include an external list with:
#
#File = file-name
#
# Note: / backs up everything on the root partition.
#if you have other partitions such as /usr or /home
#you will probably want to add them too.
#
# By default this is defined to point to the Bacula binary
#directory to give a reasonable FileSet to backup to
#disk storage
Re: [Bacula-users] Bacula dir crashing
On Wednesday 21 September 2005 12:08, Arunav Mandal wrote:
Hi,
You said to attach gdb to bacula-dir but there are 4 bacula-dir
running which one to attach to? In the documentation it says if I have
/lib/tls it may have some problems. I am running Centos 4.1. Anyway the DIR
server has has only one cpu but was running smp kernel now I switched to
normail kernel.
Uh, if there are 4 bacula-dir's running, then you must be running on a 2.4
kernel, and in that case using /lib/tls will create no end of problems with
Bacula mostly bizarre hangs (missed signals). Under a 2.6 kernel, Bacula
should appear as a single process.
In the case you are using a 2.4 kernel, you either need to move /lib/tls, or
disable it with the environment variable as documented in the manual. When
using the debugger on a 2.4 kernel, you always attach to the first PID, but
if you follow the instructions in the manual, you will run Bacula under the
debugger rather than attaching to it later.
In the case of a 2.6 kernel, if there are multiple instances of Bacula, you
are most likely using an option that shows all the threads -- as opposed to
running under a 2.6 kernel, they should all have the same PID, or you have
disabled /lib/tls. This /lib/tls workaround is not needed for 2.6 kernels.
Arunav.
Hello,
I suspect that you have now set the record for having the most problems
with
Bacula, if not, you are close. Unfortunately, that is a rather
unpleasant distinction :-(
If you are asking if your FileSet is correct, I don't see any major
problems.
However, now that you have moved the wildcards to the Exclude resource, I
personally would remove the Exclude = yes from the Options. It should
do
no harm, but it could make reading the FileSet confusing for someone who
doesn't know the history ...
There is one known mutex race condition in 1.36.x that could cause a
Director
hang, and perhaps you are more likely to see it than most users because
you
are running a *lot* of jobs every night, and if I am not mistaken, you
have a
real smp system, which tends to make race conditions even more evident.
Note, I forgot to mention last time I emailed that if either the SD *or*
the
DIR crashes during a backup, the number of files on your tape is likely
to
be
wrong (if the Director goes down the SD cannot update the catalog).
If this happens again, please attach to the Director with the debugger
using
something like:
gdb bacula-dir pid
where you replace pid with the PID of the Director, then produce a
traceback as described in the Kaboom chapter of the manual. At least I
can
verify if you are seeing a known problem. This race bug is fixed in
1.37, but it was such a substantial fix that there is no patch for 1.36.
On Friday 16 September 2005 10:50, Arunav Mandal wrote:
On Wednesday 14 September 2005 08:45, Arunav Mandal wrote:
Now I got another problem bacula dir crashed without any reason.
What
debug
level I should use to see what's going on?
You should have gotten a traceback by email. If not, you can produce
one
by
running the Director under the debugger as described in the kaboom
chapter
of
the manual.
Arunav.
It happened again yesterday night bacula dir didnt crash it seems but
when
I tried to log into it in morning via bconsole I can't and there were
no backup mails also.I changed nothing in the config file expect the
Fileset
given below. Fileset was correct isnt?
FileSet {
Name = linux-default
Ignore Fileset changes = yes
Include {
Options {
signature=SHA1
verify=pins1
onefs=no
sparse=no
Exclude = yes
}
File = /
}
Exclude {
File = /sys
File = /proc
File = /tmp
File = /.journal
File = /.fsck
File = /mnt
File = /dev
File = /var/chroot/hoary-ia32/home
File = /space
File = *.mp3
File = *.m4a
File = *.o
File = *.obj
File = *.vob
File = *.VOB
File = *.journal
File = *.fsck
}
}
Arunav.
--
Best regards,
Kern
(
/\
V_V
--
Best regards,
Kern
(
/\
V_V
---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42 plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula dir crashing
I am running on 2.6.9-11. All the PID's are different.
Arunav.
- Original Message -
From: Kern Sibbald [EMAIL PROTECTED]
To: Arunav Mandal [EMAIL PROTECTED]
Cc: bacula-users@lists.sourceforge.net
Sent: Friday, September 23, 2005 8:59 AM
Subject: Re: [Bacula-users] Bacula dir crashing
On Wednesday 21 September 2005 12:08, Arunav Mandal wrote:
Hi,
You said to attach gdb to bacula-dir but there are 4 bacula-dir
running which one to attach to? In the documentation it says if I have
/lib/tls it may have some problems. I am running Centos 4.1. Anyway the
DIR
server has has only one cpu but was running smp kernel now I switched to
normail kernel.
Uh, if there are 4 bacula-dir's running, then you must be running on a 2.4
kernel, and in that case using /lib/tls will create no end of problems
with
Bacula mostly bizarre hangs (missed signals). Under a 2.6 kernel, Bacula
should appear as a single process.
In the case you are using a 2.4 kernel, you either need to move /lib/tls,
or
disable it with the environment variable as documented in the manual.
When
using the debugger on a 2.4 kernel, you always attach to the first PID,
but
if you follow the instructions in the manual, you will run Bacula under
the
debugger rather than attaching to it later.
In the case of a 2.6 kernel, if there are multiple instances of Bacula,
you
are most likely using an option that shows all the threads -- as opposed
to
running under a 2.6 kernel, they should all have the same PID, or you have
disabled /lib/tls. This /lib/tls workaround is not needed for 2.6
kernels.
Arunav.
Hello,
I suspect that you have now set the record for having the most
problems
with
Bacula, if not, you are close. Unfortunately, that is a rather
unpleasant distinction :-(
If you are asking if your FileSet is correct, I don't see any major
problems.
However, now that you have moved the wildcards to the Exclude
resource, I
personally would remove the Exclude = yes from the Options. It
should
do
no harm, but it could make reading the FileSet confusing for someone
who
doesn't know the history ...
There is one known mutex race condition in 1.36.x that could cause a
Director
hang, and perhaps you are more likely to see it than most users
because
you
are running a *lot* of jobs every night, and if I am not mistaken, you
have a
real smp system, which tends to make race conditions even more
evident.
Note, I forgot to mention last time I emailed that if either the SD
*or*
the
DIR crashes during a backup, the number of files on your tape is
likely
to
be
wrong (if the Director goes down the SD cannot update the catalog).
If this happens again, please attach to the Director with the debugger
using
something like:
gdb bacula-dir pid
where you replace pid with the PID of the Director, then produce a
traceback as described in the Kaboom chapter of the manual. At least
I
can
verify if you are seeing a known problem. This race bug is fixed in
1.37, but it was such a substantial fix that there is no patch for
1.36.
On Friday 16 September 2005 10:50, Arunav Mandal wrote:
On Wednesday 14 September 2005 08:45, Arunav Mandal wrote:
Now I got another problem bacula dir crashed without any reason.
What
debug
level I should use to see what's going on?
You should have gotten a traceback by email. If not, you can
produce
one
by
running the Director under the debugger as described in the kaboom
chapter
of
the manual.
Arunav.
It happened again yesterday night bacula dir didnt crash it seems
but
when
I tried to log into it in morning via bconsole I can't and there
were
no backup mails also.I changed nothing in the config file expect the
Fileset
given below. Fileset was correct isnt?
FileSet {
Name = linux-default
Ignore Fileset changes = yes
Include {
Options {
signature=SHA1
verify=pins1
onefs=no
sparse=no
Exclude = yes
}
File = /
}
Exclude {
File = /sys
File = /proc
File = /tmp
File = /.journal
File = /.fsck
File = /mnt
File = /dev
File = /var/chroot/hoary-ia32/home
File = /space
File = *.mp3
File = *.m4a
File = *.o
File = *.obj
File = *.vob
File = *.VOB
File = *.journal
File = *.fsck
}
}
Arunav.
--
Best regards,
Kern
(
/\
V_V
--
Best regards,
Kern
(
/\
V_V
---
SF.Net email is sponsored by:
Tame your development challenges
Re: [Bacula-users] Bacula dir crashing
Not sure if my case is at all related but with bacula 1.37.38 I had intermittent crashes with the director when I launched the tray monitor. I have since upgraded to the latest cvs and I have yet to see the problem. John --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula dir crashing
Hi,
You said to attach gdb to bacula-dir but there are 4 bacula-dir
running which one to attach to? In the documentation it says if I have
/lib/tls it may have some problems. I am running Centos 4.1. Anyway the DIR
server has has only one cpu but was running smp kernel now I switched to
normail kernel.
Arunav.
Hello,
I suspect that you have now set the record for having the most problems
with
Bacula, if not, you are close. Unfortunately, that is a rather unpleasant
distinction :-(
If you are asking if your FileSet is correct, I don't see any major
problems.
However, now that you have moved the wildcards to the Exclude resource, I
personally would remove the Exclude = yes from the Options. It should
do
no harm, but it could make reading the FileSet confusing for someone who
doesn't know the history ...
There is one known mutex race condition in 1.36.x that could cause a
Director
hang, and perhaps you are more likely to see it than most users because
you
are running a *lot* of jobs every night, and if I am not mistaken, you
have a
real smp system, which tends to make race conditions even more evident.
Note, I forgot to mention last time I emailed that if either the SD *or*
the
DIR crashes during a backup, the number of files on your tape is likely to
be
wrong (if the Director goes down the SD cannot update the catalog).
If this happens again, please attach to the Director with the debugger
using
something like:
gdb bacula-dir pid
where you replace pid with the PID of the Director, then produce a
traceback as described in the Kaboom chapter of the manual. At least I
can
verify if you are seeing a known problem. This race bug is fixed in 1.37,
but it was such a substantial fix that there is no patch for 1.36.
On Friday 16 September 2005 10:50, Arunav Mandal wrote:
On Wednesday 14 September 2005 08:45, Arunav Mandal wrote:
Now I got another problem bacula dir crashed without any reason.
What
debug
level I should use to see what's going on?
You should have gotten a traceback by email. If not, you can produce
one
by
running the Director under the debugger as described in the kaboom
chapter
of
the manual.
Arunav.
It happened again yesterday night bacula dir didnt crash it seems but
when
I tried to log into it in morning via bconsole I can't and there were no
backup mails also.I changed nothing in the config file expect the
Fileset
given below. Fileset was correct isnt?
FileSet {
Name = linux-default
Ignore Fileset changes = yes
Include {
Options {
signature=SHA1
verify=pins1
onefs=no
sparse=no
Exclude = yes
}
File = /
}
Exclude {
File = /sys
File = /proc
File = /tmp
File = /.journal
File = /.fsck
File = /mnt
File = /dev
File = /var/chroot/hoary-ia32/home
File = /space
File = *.mp3
File = *.m4a
File = *.o
File = *.obj
File = *.vob
File = *.VOB
File = *.journal
File = *.fsck
}
}
Arunav.
--
Best regards,
Kern
(
/\
V_V
---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42 plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula dir crashing
Hello,
I suspect that you have now set the record for having the most problems with
Bacula, if not, you are close. Unfortunately, that is a rather unpleasant
distinction :-(
If you are asking if your FileSet is correct, I don't see any major problems.
However, now that you have moved the wildcards to the Exclude resource, I
personally would remove the Exclude = yes from the Options. It should do
no harm, but it could make reading the FileSet confusing for someone who
doesn't know the history ...
There is one known mutex race condition in 1.36.x that could cause a Director
hang, and perhaps you are more likely to see it than most users because you
are running a *lot* of jobs every night, and if I am not mistaken, you have a
real smp system, which tends to make race conditions even more evident.
Note, I forgot to mention last time I emailed that if either the SD *or* the
DIR crashes during a backup, the number of files on your tape is likely to be
wrong (if the Director goes down the SD cannot update the catalog).
If this happens again, please attach to the Director with the debugger using
something like:
gdb bacula-dir pid
where you replace pid with the PID of the Director, then produce a
traceback as described in the Kaboom chapter of the manual. At least I can
verify if you are seeing a known problem. This race bug is fixed in 1.37,
but it was such a substantial fix that there is no patch for 1.36.
On Friday 16 September 2005 10:50, Arunav Mandal wrote:
On Wednesday 14 September 2005 08:45, Arunav Mandal wrote:
Now I got another problem bacula dir crashed without any reason. What
debug
level I should use to see what's going on?
You should have gotten a traceback by email. If not, you can produce one
by
running the Director under the debugger as described in the kaboom
chapter
of
the manual.
Arunav.
It happened again yesterday night bacula dir didnt crash it seems but when
I tried to log into it in morning via bconsole I can't and there were no
backup mails also.I changed nothing in the config file expect the Fileset
given below. Fileset was correct isnt?
FileSet {
Name = linux-default
Ignore Fileset changes = yes
Include {
Options {
signature=SHA1
verify=pins1
onefs=no
sparse=no
Exclude = yes
}
File = /
}
Exclude {
File = /sys
File = /proc
File = /tmp
File = /.journal
File = /.fsck
File = /mnt
File = /dev
File = /var/chroot/hoary-ia32/home
File = /space
File = *.mp3
File = *.m4a
File = *.o
File = *.obj
File = *.vob
File = *.VOB
File = *.journal
File = *.fsck
}
}
Arunav.
--
Best regards,
Kern
(
/\
V_V
---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42 plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula dir crashing
Hi,
Unfortunately yes I got some problems recently but now I have
reduced the number of jobs to 10 and on 2 occassions when I did raise the
jobs to 20 Dir crashed or hanged at night don't know why. I do use SMP in
both DIR and SD. Since from today I implemented network bonding I am going
to increase the jobs to 40 let's see what happens tonight. Regarding FileSet
I guess having wildfile = *.mp3 or File = *.mp3 will do the same job. Maybe
I should upgrade both DIR and SD to 1.37 as using a CVS version on
production system won't be a good idea I guess.
Arunav.
Hello,
I suspect that you have now set the record for having the most problems
with
Bacula, if not, you are close. Unfortunately, that is a rather unpleasant
distinction :-(
If you are asking if your FileSet is correct, I don't see any major
problems.
However, now that you have moved the wildcards to the Exclude resource, I
personally would remove the Exclude = yes from the Options. It should
do
no harm, but it could make reading the FileSet confusing for someone who
doesn't know the history ...
There is one known mutex race condition in 1.36.x that could cause a
Director
hang, and perhaps you are more likely to see it than most users because
you
are running a *lot* of jobs every night, and if I am not mistaken, you
have a
real smp system, which tends to make race conditions even more evident.
Note, I forgot to mention last time I emailed that if either the SD *or*
the
DIR crashes during a backup, the number of files on your tape is likely to
be
wrong (if the Director goes down the SD cannot update the catalog).
If this happens again, please attach to the Director with the debugger
using
something like:
gdb bacula-dir pid
where you replace pid with the PID of the Director, then produce a
traceback as described in the Kaboom chapter of the manual. At least I
can
verify if you are seeing a known problem. This race bug is fixed in 1.37,
but it was such a substantial fix that there is no patch for 1.36.
On Friday 16 September 2005 10:50, Arunav Mandal wrote:
On Wednesday 14 September 2005 08:45, Arunav Mandal wrote:
Now I got another problem bacula dir crashed without any reason.
What
debug
level I should use to see what's going on?
You should have gotten a traceback by email. If not, you can produce
one
by
running the Director under the debugger as described in the kaboom
chapter
of
the manual.
Arunav.
It happened again yesterday night bacula dir didnt crash it seems but
when
I tried to log into it in morning via bconsole I can't and there were no
backup mails also.I changed nothing in the config file expect the
Fileset
given below. Fileset was correct isnt?
FileSet {
Name = linux-default
Ignore Fileset changes = yes
Include {
Options {
signature=SHA1
verify=pins1
onefs=no
sparse=no
Exclude = yes
}
File = /
}
Exclude {
File = /sys
File = /proc
File = /tmp
File = /.journal
File = /.fsck
File = /mnt
File = /dev
File = /var/chroot/hoary-ia32/home
File = /space
File = *.mp3
File = *.m4a
File = *.o
File = *.obj
File = *.vob
File = *.VOB
File = *.journal
File = *.fsck
}
}
Arunav.
--
Best regards,
Kern
(
/\
V_V
---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42 plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula dir crashing
On Friday 16 September 2005 14:35, Arunav Mandal wrote:
Hi,
Unfortunately yes I got some problems recently but now I have
reduced the number of jobs to 10 and on 2 occassions when I did raise the
jobs to 20 Dir crashed or hanged at night don't know why. I do use SMP in
both DIR and SD. Since from today I implemented network bonding I am going
to increase the jobs to 40 let's see what happens tonight. Regarding
FileSet I guess having wildfile = *.mp3 or File = *.mp3 will do the same
job. Maybe I should upgrade both DIR and SD to 1.37 as using a CVS version
on production system won't be a good idea I guess.
To upgrade, you need to modify all the daemons on all the machines at the same
time, and you need to upgrade your database. There are still a few remaining
problems that exist in version 1.37, that I am working on but cannot assure
fixing before the first week in October.
Given all the problems you are currently having, and that you are running in
production, I would probably recommend you remain on the current version a
bit longer unless you find the current setup unbearable.
By the way, the CVS is version 1.37, though I have made a few specific
releases to Source Forge the latest being 1.37.38. At the moment, the CVS is
in bug fix mode only (no development).
Arunav.
Hello,
I suspect that you have now set the record for having the most problems
with
Bacula, if not, you are close. Unfortunately, that is a rather
unpleasant distinction :-(
If you are asking if your FileSet is correct, I don't see any major
problems.
However, now that you have moved the wildcards to the Exclude resource, I
personally would remove the Exclude = yes from the Options. It should
do
no harm, but it could make reading the FileSet confusing for someone who
doesn't know the history ...
There is one known mutex race condition in 1.36.x that could cause a
Director
hang, and perhaps you are more likely to see it than most users because
you
are running a *lot* of jobs every night, and if I am not mistaken, you
have a
real smp system, which tends to make race conditions even more evident.
Note, I forgot to mention last time I emailed that if either the SD *or*
the
DIR crashes during a backup, the number of files on your tape is likely
to
be
wrong (if the Director goes down the SD cannot update the catalog).
If this happens again, please attach to the Director with the debugger
using
something like:
gdb bacula-dir pid
where you replace pid with the PID of the Director, then produce a
traceback as described in the Kaboom chapter of the manual. At least I
can
verify if you are seeing a known problem. This race bug is fixed in
1.37, but it was such a substantial fix that there is no patch for 1.36.
On Friday 16 September 2005 10:50, Arunav Mandal wrote:
On Wednesday 14 September 2005 08:45, Arunav Mandal wrote:
Now I got another problem bacula dir crashed without any reason.
What
debug
level I should use to see what's going on?
You should have gotten a traceback by email. If not, you can produce
one
by
running the Director under the debugger as described in the kaboom
chapter
of
the manual.
Arunav.
It happened again yesterday night bacula dir didnt crash it seems but
when
I tried to log into it in morning via bconsole I can't and there were
no backup mails also.I changed nothing in the config file expect the
Fileset
given below. Fileset was correct isnt?
FileSet {
Name = linux-default
Ignore Fileset changes = yes
Include {
Options {
signature=SHA1
verify=pins1
onefs=no
sparse=no
Exclude = yes
}
File = /
}
Exclude {
File = /sys
File = /proc
File = /tmp
File = /.journal
File = /.fsck
File = /mnt
File = /dev
File = /var/chroot/hoary-ia32/home
File = /space
File = *.mp3
File = *.m4a
File = *.o
File = *.obj
File = *.vob
File = *.VOB
File = *.journal
File = *.fsck
}
}
Arunav.
--
Best regards,
Kern
(
/\
V_V
--
Best regards,
Kern
(
/\
V_V
---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42 plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula dir crashing
Now I got another problem bacula dir crashed without any reason. What debug level I should use to see what's going on? Arunav. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula dir crashing
On Wednesday 14 September 2005 08:45, Arunav Mandal wrote: Now I got another problem bacula dir crashed without any reason. What debug level I should use to see what's going on? You should have gotten a traceback by email. If not, you can produce one by running the Director under the debugger as described in the kaboom chapter of the manual. Arunav. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- Best regards, Kern ( /\ V_V --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula dir crashing
- Original Message - From: Kern Sibbald [EMAIL PROTECTED] To: bacula-users@lists.sourceforge.net Cc: Arunav Mandal [EMAIL PROTECTED] Sent: Wednesday, September 14, 2005 10:24 AM Subject: Re: [Bacula-users] Bacula dir crashing On Wednesday 14 September 2005 08:45, Arunav Mandal wrote: Now I got another problem bacula dir crashed without any reason. What debug level I should use to see what's going on? You should have gotten a traceback by email. If not, you can produce one by running the Director under the debugger as described in the kaboom chapter of the manual. Arunav. But can't I set the setdebug from the bconsole? Arunav. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula dir crashing
Hello, On 14.09.2005 22:12, Arunav Mandal wrote: ... Now I got another problem bacula dir crashed without any reason. What debug level I should use to see what's going on? You should have gotten a traceback by email. If not, you can produce one by running the Director under the debugger as described in the kaboom chapter of the manual. Arunav. But can't I set the setdebug from the bconsole? Arunav. Debug output (with a level) is something different from the traceback Kern mentioned. Usually, he guesses right what sort of output he needs to track an error :-) For the automatic traceback generation, you need gdb installed on the director machine. Arno -- IT-Service Lehmann[EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
