Hello,
The upgrade scripts used to update from one Bacula DB schema to
the next are kept in /src/cats and have names that begin
with update_ There is one main script named update_bacula_tables
(build during the ./configure command from update_bacula_tables.in).
This script then calls the appropr
It appears that the upgrade process attempted to upgrade two versions of the
database at one time. Bacula only supports upgrading one version at a time,
so from database version 10, you must first apply the scripts that do the
upgrade to version 11, and then apply the upgrade scripts that upgra
On Wednesday 25 August 2010 10:01:27 Chuck Short wrote:
> I have submitted this bug upstream as:
>
> http://bugs.bacula.org/view.php?id=1629
>
> chuck
>
> ** Bug watch added: bugs.bacula.org/ #1629
>http://bugs.bacula.org/view.php?id=1629
>
> ** Changed in: bacula (Ubuntu)
>Status: Inco
> There is an attachment - see on the right side of the page "Bug
> attachments" -> "debug messages and running under gdb"
It is just as I suspected: Bacula has called gethostbyname, which then seg
faults when in the wins code. Unless Bacula is passing bad arguments to
gethostbyname, which is hi
On Monday 07 March 2011 16:12:51 Chuck Short wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please try to obtain a backtrace following the
> instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
> the backtrace (as an attachment) to
On Monday 07 March 2011 16:12:51 Chuck Short wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please try to obtain a backtrace following the
> instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
> the backtrace (as an attachment) to
The new version of Bacula (5.2.0) to be released in about a month has a number
of fixes, and will work perfectly with Qt 4.6.2 (Lucid) where I have done the
development work. There have been quite a number of enhancements and a lot
of stability improvements in bat 5.2.0.
As I previously report
On Saturday 02 April 2011 02:23:21 Clint Byrum wrote:
> Kern, does this mean that there is an explicit fix in the code of 5.2.0
> that will make this problem go away on Qt 4.6.2 ?
There have been a very large number of changes to bat from 5.0.x to 5.2.0,
including new features, bug fixes, and par
On Saturday 02 April 2011 16:40:13 Clint Byrum wrote:
> Excerpts from Kern Sibbald's message of Sat Apr 02 07:20:23 UTC 2011:
> > On Saturday 02 April 2011 02:23:21 Clint Byrum wrote:
> > > Kern, does this mean that there is an explicit fix in the code of 5.2.0
> > > that will make this problem go
It looks like the Bacula version has changed between LTS versions, and in the
change, the Bacula catalog
database changed format, so it has a new version number. Updating the Bacula
catalog is done automatically
in rpms, but probably not in .debs. You must apply an update script that you
can f
Hello,
Disclaimer: I don't have anything to do with LTS (other than I develop on a
Ubuntu system), so I cannot resolve the Ubuntu problem.
However, I suggest you download the source, either from the Ubuntu
source or from Source Forge and look in the updatedb directory. It has
all the scripts you
This ticket is a bit old. Could someone please try turning on fortify source
with a current 5.2.x version
and see if there is a problem. If there is I will fix it. That said, I still
recommend against using fortify
source, as I previously wrote, Bacula has all its own routines since 10 years
Someone must have fat fingered something because upstream we have never had the
semicolon misplaced
as in the above problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/830108
Titl
This looks like Bacula (bat) is blowing itself up with a segfault on purpose to
get a dump. This
usually happens after Bacula has detected an error in the bat.conf file. The
only way to know
exactly what is going on is to see what Bat has sent to stdout.
--
You received this bug notification
ted in the saga of the Bareos
fork, please see the new Bacula website (under development) at:
http://blog.bacula.org
Kern Sibbald
Bacula Project Manager
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.
Although it is true that the git repo has not been updated for some time,
there is a good reason, for more information, please see www.bacula.org
-> News.
There is indeed a fork of Bacula, but that fork has only *one* former Bacula
developer. Although, like other open source projects, developers c
** Changed in: bacula
Status: New => Invalid
--
variable expansion uses outdated data
https://bugs.launchpad.net/bugs/459573
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubun
The threaded stack trace doesn't make much sense to me because it shows
that bat is seg faulting in wait_data_intr() because the class pointer
is NULL.
Can you answer the following?
- What version of the compiler are you using?
- Have you or the packaging changed any of Bacula's default compile
Hello Reinhard,
On Monday 14 April 2008 19:47:25 meux wrote:
> Hi Kern,
>
> thanks for your answer. I am using the default package provided by
> Ubuntu Hoary. I haven't compiled it nor have ich changed any compile
> options.
OK.
>
> I think this error occurs, when i close bat via File->Quit bu
If Fortify source is turned of the problem *is* fixed and not simply
hidden.
The output indicates that that this crash is due to the fact that Bacula
was built with -DFORTIFY_SOURCE=2 (please check spelling). The glibc
code that implements this feature according to the authors of the code
may gen
I would recommend to the packagers to move up to Bacula version 2.4.2 as
quickly as possible. Versions 2.4.0 and 2.4.1 had a number of important
problems concerning mounting tape volumes particularly in manual mount
situations (non-autochanger). Version 2.4.2 is a "critical" bug fix to
versions 2
This problem *should* already be fixed in the trunk, though I have never
actually tried building and running it with fortify source.
We *strongly* recommend not to enable fortify source. Bacula is already
well protected and has its own buffer overrun detection that in general
detects most overrun
Thanks for upgrading to the 2.4.2 version, which is much more stable
than 2.4.0 and 2.4.1.
One additional consideration when producing Bacula packages. I
regularly release well tested patches to bugs to the bacula-bugs section
of the Source Forge release are. When you are building new packages,
I was not aware of this bug (sorry, I should look at them all), but I
think I can shed some light on it and even provide the "code" necessary
to fix it.
Basically the user is saying that each Bacula daemon generated needs a
shared secrete random password used for authentication, and these
password
On Wednesday 24 September 2008 11:07:52 Ante Karamatić wrote:
> It's worth mentioning that after the network is started, avahi (on
> default install) looks at DNS to see if '.local' domain is served by DNS
> server. If that's true, avahi doesn't start. If there is no DNS for
> '.local', avahi will
On Wednesday 24 September 2008 11:13:20 Ante Karamatić wrote:
> I'll mark this bug as 'medium' at the moment. But this should be
> resolved as soon as possible.
>
> Kern, of course, any code would be welcome. It's clear that we should
> generate password on postinstall of package, not during compil
On Wednesday 24 September 2008 19:32:44 Ante Karamatić wrote:
> On Wed, 24 Sep 2008 13:58:46 -
>
> Kern Sibbald <[EMAIL PROTECTED]> wrote:
> > I don't understand why you cannot start Bacula after the network is
> > up and running and DNS is serving names. That
On Wednesday 24 September 2008 20:04:18 Ante Karamatić wrote:
"The upstream bug has not been fixed in 2.2.8!!"
The bug *was* fixed in the 2.2.8 version with two patches. Did you apply
them?
If not an easy way to fix it is to take src/dird/backup.c from either the last
commit to Branch-2.2 or
On Saturday 27 September 2008 09:45:11 Ante Karamatić wrote:
> On Thu, 25 Sep 2008 20:36:41 -
>
> Kern Sibbald <[EMAIL PROTECTED]> wrote:
> > On Wednesday 24 September 2008 20:04:18 Ante Karamatić wrote:
> >
> > "The upstream bug has not been fixed in 2
On Saturday 27 September 2008 12:06:24 Ante Karamatić wrote:
> On Sat, 27 Sep 2008 09:25:55 -
>
> Kern Sibbald <[EMAIL PROTECTED]> wrote:
> > OK, no problem. I didn't take offense, hope you didn't, but just
> > wanted to clarify.
>
> Of course
On Tuesday 21 October 2008 20:20:04 Ante Karamatić wrote:
> I would just like to present my opinion on this one...
>
> This change was introduced in Debian as fix for Debian bug 367105:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367105
>
> Both configurations have valid use cases. I'm kin
rovide as much help as I can to
arrive at solutions for all problems, concerns or questions you may have
about Bacula.
Kern Sibbald
Bacula Project Manager
--
bacula client configuration is broken out of the box
https://bugs.launchpad.net/bugs/286643
You received this bug notification because you ar
On Wednesday 06 May 2009 20:35:58 Matthew Hooker wrote:
> Have tried to rebuild using instructions from here (as root)
>
> http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-
> lists-3/bacula-25/bacula-in-ubuntu-8-04-without-tls-91988/#283516
>
> (some commands below changed as
On Tuesday 16 June 2009 20:17:49 Brian Murray wrote:
> Thanks for taking the time to report this bug and including a patch.
> However, the .desktop file is generated when building the source package
> so your patch, while it fixes the resulting .desktop file, won't apply
> to the package. I'm not
On Tuesday 16 June 2009 21:46:08 Martin Kalén wrote:
> 2009/6/16 Kern Sibbald
>
> > 1. Your bug emails generated by your system apparently don't take into
> > account
> > that there may be more one place we get bug emails. I recommend that you
> > add
>
One of the reasons for using Bacula is so that you don't have to track what
Volumes it is using. It does all the work for you, and if you trust it, you
won't need particular Volume labels.
That said, If you really want to use Client based Volume labels, you can, but
to do so, the only reasonabl
> Fair enough, obviously I have misunderstood the use case for variable
> expansion. My apologies.
No need to appologize. Bacula is very complicated, and it is not always
obvious what features to use to do what you want (even for me sometimes).
Unfortunately, for lots of reasons variable expansi
37 matches
Mail list logo
