|
Hello Jonathan,
The only hope you have to get these changes made is to either
submit a Feature Request in the bugs database for each one, or
submit a patch -- also to the bugs database.
With emails, these ideas disappear in about a half hour as our
inboxes fill rapidly.
Best regards,
Kern
On 10/02/2016 09:02 AM, Hankins, Jonathan wrote:
Kern,
If there's any work to improve the error from bconsole when
the max console connections are exceeded, it may be helpful to
add a debug msg on the director indicating this too...i think
was running under debug level 99999 and didn't see anything
indicating that condition.
For that matter, maybe the dir should refuse to
start and explain when things like max dir connections = 0 are
specified, since it is an invalid configuration (in spirit).
I think it'd also be useful if the daemons and
bconsole dumped their entire config tree in debug, so you
could see what final values are in effect, maybe noting which
ones are set per defaults. (Maybe they already do?)
-Jonathan Hankins
Hello,
When one uses the -Bsymbolic_functions link option, the
effect on
Bacula is that the default values will not in all cases
be set
correctly. The exact mechanism is a bit complicated but
I think it
applies mostly to the Director. The "workaround" for
this problem
(requiring no rebuilding) is to explicitly set the
needed default
values. In the case of bconsole, the Director's
"Maximum Console
Connections" is by fault set to 20, but with the silly
fiddling that the
linker does to the source code with that option on, it
sets it to zero,
and you see the results (the error message could
probably be improved).
So to make bconsole work in the Director's Director
resource set:
Maximum Console Connections = 20
or what ever value you want (I recommend at least 5 in
case you get
zombies).
Best regards,
Kern
On 10/02/2016 01:06 AM, Jan Martin wrote:
> Thanks to Kern, John, and Josh,
>
> It seems I am not crazy after all :). So the
current release version
> from Mint 18 seems to be compiled with a link
switch
> -Bsymbolic_functions, which makes it not work. The
version lines for my
> bacula-dir and bconsole:
>
> trinity% sudo /usr/sbin/bacula-dir -?
> Copyright (C) 2000-2014 Free Software Foundation
Europe e.V.
>
> Version: 7.0.5 (28 July 2014)
>
> trinity% bconsole -?
> Copyright (C) 2000-2014 Free Software Foundation
Europe e.V.
>
> Version: 7.0.5 (28 July 2014) x86_64-pc-linux-gnu
ubuntu 16.04
>
> suggest that they were compiled two years ago,
perhaps before Kern
> became involved in the process? It also suggests
that bconsole at
> least, was from the ubuntu distribution 16.04.
>
> I'm a little unclear about how software updates
flow between Debian,
> Ubuntu, and Mint - is there a way to get the Mint
18 packager to
> recompile the package, or does he/she need to just
get a later 16.04
> update which is correctly compiled? Is there
something I can do to help?
>
> Overall, thanks very much guys!
>
> -Jan
>
>
> On 10/01/2016 08:47 AM, Kern Sibbald wrote:
>> I cannot say for sure about Debian, but for
Ubuntu there are/were bug
>> reports open. All have been
>> resolved by the packagers with my input. What
happened with Ubuntu is
>> that they simply
>> packaged it and released it without testing
(surely due to lack of
>> time). This meant that Bacula
>> failed out of the box -- at least this is the
case for their latest
>> release. I must say that in
>> general Ubuntu keeps up pretty well with the
Bacula releases, and now
>> they know how to
>> run the Bacula regression tests, so it is
likely that future releases
>> will be better.
>>
>> Best regards,
>> Kern
>>
>> On 10/01/2016 04:51 PM, Hankins, Jonathan
wrote:
>>> It seems weird that the bacula package in
Debian and Ubuntu, et al, is
>>> broken and no one has noticed (checked
Debian bug database). I know
>>> Debian has been on 5.x in the stable
release for years (still is).
>>> It's possible that 7.0.5 got packaged for
their testing release and
>>> maybe Ubuntu xenial picked it up and thus
Mint 18. My guess is most
>>> folks using bacula on a Debian distro are
on Debian stable, and not
>>> Ubuntu or mint (workstation oriented
releases...if anything, may be
>>> using bacula-fd) and thus no one has
noticed. I'll do a little digging
>>> and talk to the person who packages bacula
for Debian and see if I
>>> figure it out.
>>>
>>> Thanks for the insight about the known
compiler issues!
>>>
>>> -Jonathan Hankins
>>>
>>>
>>> On Sat, Oct 1, 2016, 7:57 AM Kern Sibbald
<k...@sibbald.com
>>> <mailto:k...@sibbald.com>> wrote:
>>>
>>> Hello Josh,
>>>
>>> Yes, if you build either with -D
fortify-source=2 or link with
>>> -Bsymbolic-functions, Bacula will
fail. It is best
>>> to stick with the Bacula recommended
build options, which is what
>>> you are using.
>>>
>>> Also if you have a Bacula version less
that 7.4.3 and you build
>>> with GNU C++ 6.0 or greater,
>>> Bacula will not work. This problem is
fixed in 7.4.3 and greater,
>>> but the guys committing to
>>> C++ have lost all common sense of the
basic function of the C++
>>> compiler that is to correctly
>>> compile the source code written by the
author. On multiple
>>> occasions, they now simply elide (drop
>>> or delete) your source code.
Consequently, it is likely that with
>>> new C++ compiler we will
>>> run into additional problems, unless
we can find a C++ compiler
>>> that respects what the programmer
>>> writes. It is the user's
responsibility (or problem) if he/she
>>> adds options that the project
>>> does not use (and often warns
against), but when you have rogue
>>> C++ compiler writers, life
>>> gets much more complicated.
>>>
>>> Best regards,
>>> Kern
>>>
>>> On 10/01/2016 02:11 PM, Josh Fisher
wrote:
>>>> On 10/1/2016 2:44 AM, Hankins,
Jonathan wrote:
>>>>> So I've narrowed it down. If I
build from Debian's patched
>>>>> source, but run ./configure
myself, my flags in config.out look
>>>>> like:
>>>>>
>>>>> Compiler flags: -g
-O2 -Wall -fno-strict-aliasing
>>>>> -fno-exceptions -fno-rtti
>>>>> Linker flags:
>>>>>
>>>>> However, if I build using
debian's rules file, my flags in
>>>>> config.out look like:
>>>>>
>>>>> Compiler flags: -g
-O2 -fstack-protector-strong
>>>>> -Wformat
-Werror=format-security -fno-strict-aliasing
>>>>> -fno-exceptions -fno-rtti
-fno-strict-aliasing -fno-exceptions
>>>>> -fno-rtti
>>>>> Linker flags:
-Wl,-Bsymbolic-functions -Wl,-z,relro
>>>>>
>>>> Years ago I ran into a situation
with building Bacula RPMS when
>>>> RedHat started adding -D
fortify-source to CFLAGS by default.
>>>> This would cause 'buffer overflow
detected' errors even though
>>>> what Bacula was doing in the code
was perfectly safe. It just
>>>> didn't match what GCC's detection
code expected. The answer was
>>>> to override RedHat's RPM macro
additions with user-defined macros
>>>> and build using the CLFAGS that
Bacula's configure creates. I'm
>>>> not so familiar with Debian
packaging, but I'm sure there must be
>>>> a way to override the default
rules so that Bacula can be built
>>>> with a proper CFLAGS.
>>>>
>>>>
>>>>
>>>>
>>>>
------------------------------------------------------------------------------
>>>> Check out the vibrant tech
community on one of the world's most
>>>> engaging tech sites, SlashDot.org!
http://sdm.link/slashdot
>>>>
>>>>
>>>>
_______________________________________________
>>>> Bacula-users mailing list
>>>> Bacula-users@lists.sourceforge.net
>>>> <mailto:Bacula-users@lists.sourceforge.net>
>>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>>
>>>
------------------------------------------------------------------------------
>>> Check out the vibrant tech community
on one of the world's most
>>> engaging tech sites, SlashDot.org!
>>> http://sdm.link/slashdot_______________________________________________
>>> Bacula-users mailing list
>>> Bacula-users@lists.sourceforge.net
>>> <mailto:Bacula-users@lists.sourceforge.net>
>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>>
>>>
>>>
This e-mail is intended only for the recipient and may contain
>>>
confidential or proprietary information. If you are not the intended
>>>
recipient, the review, distribution, duplication or retention of this
>>>
message and its attachments is prohibited. Please notify the sender of
>>>
this error immediately by reply e-mail, and permanently delete this
>>>
message and its attachments in any form in which they may have been
>>> preserved.
>>
>>
>>
>>
------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of
the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>
>>
>>
>> _______________________________________________
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>
>
------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the
world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the
world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
This e-mail is intended only for the recipient and may contain confidential or proprietary information. If you are not the intended recipient, the review, distribution, duplication or retention of this message and its attachments is prohibited. Please notify the sender of this error immediately by reply e-mail, and permanently delete this message and its attachments in any form in which they may have been preserved.
|
