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
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
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
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
Hello,
The upgrade scripts used to update from one Bacula DB schema to
the next are kept in bacula-src/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 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 but i am
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
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
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
passwords
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
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 is how it works on all
other systems
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.2.8!!
I haven't said that :)
OK, no problem. I
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 are a member of Ubuntu
Server Team, which
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.launchpad.net/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
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
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
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
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
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 away on
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 k...@sibbald.com
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
something like Launchpad.bacula
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 highly
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
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
** 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
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
Public bug reported:
After upgrading to the latest kernel 2.6.24-21-generic the nvidia driver does
not load. I have reinstalled linux-restricted-modules-generic, but no go. The
nvidia error log is not very helpful:
...
(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer
** Attachment added: Xorg log
http://launchpadlibrarian.net/19032744/Xorg.0.log.save
--
The nvidia module does not load on kernel 2.6.24-21
https://bugs.launchpad.net/bugs/290775
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
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 kind of
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 are a member of Ubuntu
Bugs, which is subscribed
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 but i am
I can confirm that this was a bug, but the version mentioned (1.36.3) is
*very* old and the bug has long since been fixed in later versions.
--
Bacula Seems to Hang After Rerunning Failed Job
https://bugs.launchpad.net/bugs/91053
You received this bug notification because you are a member of
This bug report should be closed as it is a user input error. On the
queries reported as not working, the user has entered a string in places
where the query expects integers (MediaId and JobId). The query command
is not designed to check input types, that is the user's responsibility,
so it is
I had forgotten that I submitted this bug report -- in between time, I
resolved it somehow (editing the conf file I think) and now we are on
kernel 2.6.24-22, which works fine. However, in upgrading to 2.6.24-22,
it somehow broke my 2.6.24-21 boot so that X will no longer start.
There is
This bug report seems to be the most similar to my problem.
Problem: With latest Karmic (KDE) installed, my fan runs very fast (annoyingly
loud).
Computer: Dell Studio 1747: Intel i7-720QM chip.
Both /proc/acpi/fan and /proc/acpi/thermal_zone are empty.
Running sensors_detect results in Sorry,
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
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
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.2.8!!
I haven't said that :)
OK, no problem. I
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 not.
The bug in the main Bacula 2.2.8 Branch HEAD
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
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 is how it works on all
other systems
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
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
passwords
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
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
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
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
Public bug reported:
I have just loaded Lucid on a new laptop and have subsequently started loading
the ppa kubuntu-desktop-kde, in doing so, I am missing a *lot* of packages such
as liblua50. This is because I am in Switzerland, and you
are using a broken download site ch.archive.ubuntu.com.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/840299
Title:
Your ch.archive.ubuntu.com is missing a lot of packages
To manage notifications about this bug go to:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/830108
Title:
bacula
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
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 the
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
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 away on
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
On Tuesday 08 June 2010 22:45:37 wojtekjs wrote:
What video card do you have? Itn't it ATI?
If so - try installing ATIs catalyst driver (provided by ubuntu team).
Thanks for the suggestion.
I have given up. I put the laptop in the basement and use it as a test
machine doing nightly
On Sunday 17 October 2010 16:51:52 Fabio Marconi wrote:
Hello
Is this problem present with the latest updated Karmic's, Lucid's or
Maverick's packages? Thanks in advance
Fabio
** Changed in: ubuntu
Status: New = Incomplete
I am not sure if the Dell problem is now fixed. The problem
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
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
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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 k...@sibbald.com
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
something like Launchpad.bacula
Public bug reported:
On my Dell Studio 1747 i7 CPU, the fan runs too fast, making the machine
unusable because of the noise. I have tried Kubuntu Hardy, Karmic, and
Lucid. All have the same problem. It appears that there is no fan
control, no sensors are found. Under Win 7 the fan runs very
Public bug reported:
The kubuntu bug reporting page has way too much information, but does
not give me a link to report a bug on a particular application. It
talks a lot about clicking on help and all that, but on Lucid, I want to
report a bug on KPackageKit, which does not have a help.
Please
Public bug reported:
I've installed and used Lucid, and finally, it is the first Kubuntu
since Hardy that has a usable GUI (for me) -- please keep it up.
However, the KPackageKit is the worst package manager that I have ever
seen. There is no help, it is impossible to easily find packages (the
It is OK if you closed the bug. I don't want to annoy you, but I think
you missed my point. The point, is that there is no easy way to report
a bug. The ubuntu-bug program will not accept a bug report for
KPackageKit, and the page you pointed me to is exactly what I am
complaining about. I read
I have read about the fan problem long before submitting this bug report
-- there are definitely problems, but I have no problems on Win 7.
Your two responses don't seem to be consistent. First you say that this
is a problem with the Dell computer, and that it is even worse under
windows, then
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: Incomplete =
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 highly
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
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280149
Title:
Add
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
Public bug reported:
Recently I the Ubuntu 12.04 server installed 12.04 on an HP Compaq Elite 8200
with a 1.5TB harddisk Model: ATA WDC WD15EARS-00Z. I partitioned the disk with
guided full disk LVM. After it was up and running the performance was
so terrible that the machine was essentially
Hello,
The upgrade scripts used to update from one Bacula DB schema to
the next are kept in bacula-src/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
Thanks for trying it. I reported this so long ago, that I had even
forgotten about it. Since I'll be moving up to 14.04 in another month or
two, version 12.04 is less critical. I suggest that with numbers like
you show below the problem seems to be resolved, so please close the ticket.
Best
I am happy to pipe in as I would like to see Bacula working reliably
everywhere. The regression testing is documented in the Developer's
manual if I am not mistaken and is not hard to setup. The tests want to
build from source, link, install then run the tests so if you want to
run from pre-built
I have installed a 16.04 system and built Bacula using the project
compile and link options. Everything works perfectly both with and
without binary stripping. I conclude from this that the Ubuntu
packaging is using different options on the compiles and/or links and/or
stripping which prohibit
Public bug reported:
This is probably the same as many of the other bug reports already
reported on updating from 14.04 or directly installing 16.04, so after
reading this bug report, feel free to close it.
I have been using Ubuntu LTS for about 10 years now and never had any
serious problems.
Robie,
Thank you for your quick response. It makes sense that the default MySQL
is thread-safe and there is no _r variant. Your patch looks fine, but
please be aware that I suspect that it may link Bacula with the static
version of MySQL rather than the shared object (.so), and your patch is
The good news is that I have now build and tested Bacula version 7.4.1
with the patch for getting Bacula to properly link with MySQL 5.7 on
Ubuntu 16.04, and it does work.
The bad news is that the "out of the box" MySQL performs very badly to
the point of being unusable with Bacula -- it is
Public bug reported:
This is not really a bug report, rather it is a performance concern.
I am running a standard Ubuntu 16.04 64 bit desktop installation. On
this system, I have built a Bacula 7.4 and I have installed PostgreSQL
and MySQL both are "out of the box".
PostgreSQL performs as
no longer compatible with your
released MySQL. Can someone clarify this point for me?
Kern Sibbald
Bacula Project Manager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570923
Title:
bacula-dir w
I am not yet running Xenial because every machine I tried to update from
14.04 to 16.04 ended up being non-bootable, and on machine, I loaded
16.04 and it destroyed all my Windows partitions :-(
However, the problems you are experiencing seem to be related to some
new linking parameters that are
I consider this a MySQL bug, because they have apparently made the value
0 illegal as a default for a DATETIME value which is nothing other than
a standard Unix time variable. That said, they are not likely to agree
this is a bug and even if they do it will take a long time to fix.
The solution
This is getting a bit off the subject of this bug report, but ...
The only thing difficult about PostgreSQL with Bacula is getting the
authentication to work, and there is a chapter in the Bacula main manual
on PostgreSQL that tells how to get Bacula working with it. That said,
there is one
OK, thanks. Since you have an Oracle email address, you might be
particularly nterested to know that I tested the MariaDB on Ubuntu 16.04
in place of MySQL, and it was even slower :-)
On 06/24/2016 01:08 PM, Lars Tangvald wrote:
> I'll use your tests to try to make a simple test case for this,
Hello Nish,
Thanks for taking the time to send me a personal note. After more
research, I agree 100% with you that it is not related to stripping the
binaries. I deduce from Hiroaki's analysis that the problem is that the
addresses in the shared object that are exported are modified with the
Yes, on 5.7 the mysqlclient_r was replaced with mysqlclient, which
caused some linking problems until I corrected the configure.in script.
No, I do not have anything else installed that uses MySQL, but I can run
more of the regression tests. All the tests on 5.7 were run on a new
installation of
The good news is that I still have the disk with the Ubuntu 16.04
install where I did my original testing, so I plugged it in and booted
it. I am now running tests with exactly the same environment I
previously used.
The bad news is that I still see substantial timing differences between
MySQL
1 - 100 of 119 matches
Mail list logo
