[Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.0
Never mind my previous question #22. I just had to enable the use of bionic-proposal, then the procedures worked. However, they generated a number of worrisome error messages. In any case, I am now able to use apt on my system again. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1791542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.0
Could you give me a simple command with complete syntax to download the new nvidia-340 driver for 18.04? I tried the following: apt download nvidia-340/bionic-proposed E: Release 'bionic-proposed' for 'nvidia-340' was not found -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1791542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553563] Re: bconsole to Bacula Director fails with authorization problem message
Hello Nish, As long as you can reproduce the problem yourself, I see no problem with you (or anyone else) finding a fix and when the problem is fixed to release a new version. I am a bit uncertain what snap'ing bacula means, how to do it, or what the responsibilities are. I assume you mean take the responsibility for Ubuntu Bacula releases. Please clarify what you are suggesting, and I will give you a full response. If you want to do it in this bug report of offline, either are find with me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553563 Title: bconsole to Bacula Director fails with authorization problem message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1553563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553563] Re: bconsole to Bacula Director fails with authorization problem message
Yes Roberto, as the Bacula project manager, I find this Ubuntu "bug" quite frustrating. The problem is three fold: 1. Ubuntu builds Bacula with flags that are not recommended by the Bacula project. 2. Ubuntu (at least for Bacula) does not (or did not) test the packages that are build. 3. Once the LTS is made, Ubuntu, at least to me, seems *very* slow at fixing problems and releasing the fixes to the LTS. The Bacula project will, in the next few months, distribute its own binaries, which are tested prior to release. For those of you who decide to switch to using the project binaries, this kind of problem will then be resolved. The main issue in that case will be for the Bacula project to provide packages for new distro releases in a reasonable time. Maybe the solution is to go back to the good old days of building with static libraries -- i.e. to build binaries that are self contained and will thus run on virtually all versions of a give distro (or even multiple distros). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553563 Title: bconsole to Bacula Director fails with authorization problem message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1553563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589551] Re: upgrading from 14.04 to 16.04 or direct install of 16.04 fails
Hello, I have thought a lot about why *all* my upgrades from 14.04 to 16.04 have failed. This does not fit with my past experience with Ubuntu, and quite frankly, it is worrisome. However, one thing does come to mind: I run LVM on virtually all my computers, and this may be the common element where the upgrader fails. Have you sufficiently tested upgrading 14.04 LVM installations (particularly those done manually) to 16.04? Note, there is nothing unusual or strange about my LVM installations: /dev/mapper/ubuntu--vg-root on / type ext4 (rw,errors=remount-ro) /dev/mapper/vgdisk-tmp on /tmp type ext4 (rw) /dev/mapper/vgdisk-home on /home type ext4 (rw) [home] /dev/mapper/vgdisk-opt on /opt type ext4 (rw) /dev/mapper/vgdisk-var on /var type ext4 (rw) or on another machine /dev/mapper/main-root / ext4 rw,noatime,errors=remount-ro 0 0 /dev/mapper/main-tmp /tmp ext4 rw,noatime 0 0 /dev/mapper/main-boot /boot ext4 rw,noatime 0 0 /dev/mapper/main-home /home ext4 rw 0 0 /dev/mapper/main-usr /usr ext4 rw,noatime 0 0 /dev/mapper/main-var /var ext4 rw,noatime 0 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589551 Title: upgrading from 14.04 to 16.04 or direct install of 16.04 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1589551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589551] Re: upgrading from 14.04 to 16.04 or direct install of 16.04 fails
Last night my wife made the mistake of answering yes to the upgrade to 16.04 message that appeared on her 14.04 Gnome desktop. Like the other upgrades this one was a spectacular failure. The net result is a black screen of death. I haven't seen this kind of total failure since the early Windows days. This is really pitiful. Almost 3 months after I first reported this problem (and there are *many* other similar reports), and something like four or five months after the product release, it still has a 100% failure rate to install here (4 different machines). The worst part of it, is though I am a relatively experienced Linux developer and long time Ubuntu user, I have been unable to resurrect a single one of these broken machines, because they end up in such a messed up final state of missing, conflicting, or misconfigured packages. I have no choice but to follow advice that previously given only by Microsoft and re-install the system from scratch. Two of the updates involved long running machines, so they probably had some old packages, but they were all 100% patched to the latest 14.04. Two of the machines were very recent new installations of 14.04 (less than a month old). Sorry for some of the insulting/sarcastic language, but for a long time you had a great product, but for this release you have really screwed up -- probably because you have diversified into too many new "products" and not allocated appropriate resources to your base system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589551 Title: upgrading from 14.04 to 16.04 or direct install of 16.04 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1589551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592749] Re: MySQL 5.7 slow with Bacula 7.4
Nish, The slow speed of MySQL is definitely seen in MySQL 5.7 on Xenial (and perhaps other platforms that release MySQL 5.7). I can say for certain that it does not exist in Ubuntu 14.04 (I am not sure about the intermediate Ubuntu releases 14.10, 15.04, and 15.10). Both the linking problem (mysql_thread_safe() not found), and the slow speed were caused by libmysqlxx_r no longer being present. I will release Bacula 7.4.2 tomorrow, which will have the problem fixed within the Bacula source code (i.e. it will have the two patches that I have posted). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592749 Title: MySQL 5.7 slow with Bacula 7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1592749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592749] Re: MySQL 5.7 slow with Bacula 7.4
If I could, I would do what you suggest as it would, as you mentioned, simplify the code. The problem is then Bacula 7.4.x would no longer build and run on platforms such as RedHat 4.0, ... I believe the problem is now resolved in what will be released as 7.4.2, and it is backward compatible with all old MySQL versions. Thanks for sticking with this problem. If you had not been active at responding, I might have dropped it (given my pains after trying to uninstall MariaDB) and a lot of Bacula + MySQL users would have suffered for quite some time before the performance issue became evident. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592749 Title: MySQL 5.7 slow with Bacula 7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592749] Re: MySQL 5.7 slow with Bacula 7.4
Yes, your solution will work quite fine. However, it has the downside of only working with MySQL 5.7 and later, so it not appropriate for the project where people link against lots of older versions of MySQL. I think the original Ubuntu bug report (https://bugs.launchpad.net/bugs/1570923) on the linking problems with MySQL has a patch that uses my patch (and now hopefully my second patch). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592749 Title: MySQL 5.7 slow with Bacula 7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570923] Re: bacula-dir won't start with "undefined symbol: mysql_init"
Oops, sorry, I attached the patch twice :-( -- 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 won't start with "undefined symbol: mysql_init" To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/1570923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570923] Re: bacula-dir won't start with "undefined symbol: mysql_init"
Please note that the above fixes do make Bacula run, but as was discovered in bug #1592749, MySQL runs ~10 times slower than it should. I attach a patch here and in the other bug as well that fixes this problem. The patch is relative to released version 7.4.1, and may (I am not sure) apply correctly after your patch is applied -- in fact, it is a one line addition to my original patch (yours also I think). See bug #1592749 for more details on why this patch is also needed. ** Patch added: "Define that MySQL has the mysql_thread_safe() function." https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1570923/+attachment/4694833/+files/mysql_thread_safe.patch -- 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 won't start with "undefined symbol: mysql_init" To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/1570923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570923] Re: bacula-dir won't start with "undefined symbol: mysql_init"
** Patch added: "Fixes broken Bacula batch mode for MySQL 5.7 -- applies to Bacula version 7.4.1" https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1570923/+attachment/4694834/+files/mysql_thread_safe.patch -- 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 won't start with "undefined symbol: mysql_init" To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/1570923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592749] Re: MySQL 5.7 slow with Bacula 7.4
I attach a patch to Bacula 7.4.1 that corrects the slow MySQL by properly detecting that the MySQL 5.7 library is thread safe and hence Bacula batch mode can be enabled. Not this patch may also apply to your patched version of Bacula in bug #157092749. ** Patch added: "Fixes broken Bacula batch mode for MySQL 5.7 -- applies to Bacula version 7.4.1" https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592749/+attachment/4694835/+files/mysql_thread_safe.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592749 Title: MySQL 5.7 slow with Bacula 7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592749] Re: MySQL 5.7 slow with Bacula 7.4
OK, I have rebuilt my Ubuntu 16.04 test server from scratch with MySQL loaded and running. The bad news is that I can definitively say that Bacula with MySQL 5.7 runs something like 10 times slower than it did with the prior version of MySQL as well as ~10 times slower than Postgres. The good news is that I had some time while rebuilding the server, and I successfully figured out what the problem is. When Bacula is doing big inserts (we call it batch insert) at the end of the job, it batches the metadata all together in transactions of 25,000 insertions at a time for insertion into the catalog (DB), but this batching is only done if MySQL is multi-threaded, and the old code tests explicitly for libmysqlxxx_r prior to even trying mysql_thread_safe(). So on any current Bacula with MySQL 5.7 there is no batch insert and a huge performance hit. I have made a first quickie patch and it seems to be working (now MySQL is only ~20-50% slower than the out-the-box postgres, which is normal). I will get back to you with a correct patch either later today or tomorrow (once I commit it). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592749 Title: MySQL 5.7 slow with Bacula 7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592749] Re: MySQL 5.7 slow with Bacula 7.4
I tried the latest apparmor trick, but it fails. It still complains about mysql and does not seem able to fix the problem. In addition, it is also complaining about dovecot :-( Thanks to both you and Robie (off bug). I definitely want Bacula to run well with MySQL and will keep working on this, but this evening I will bring up a new disk because it will give me a clean system that I can count on. By the way, one of the main reasons for bringing up Ubuntu 16.04 on by "build" machine is for the lxc containers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592749 Title: MySQL 5.7 slow with Bacula 7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592749] Re: MySQL 5.7 slow with Bacula 7.4
No, there are no MySQL programs running, and the daemon is not running. I have tried to clear the errors the best I can and go back and reload everything, but I am completely stuck with trying to remove the mysql- server-5.7. The problem is (reproduced here manually): AppArmor parser error for /etc/apparmor.d/user.sbin.mysqld in /etc/aptarmor.d/usr.sbin.mysqld at line 9: Could not open "abstractions/mysql". I have tried everything to fixup apparmor with the exception of removing it, because it will remove 90% of the system. At this point I will probably have wipe the disk and reload from a USB stick. That will take several days (the disk holds about 1.5TB of data). I'll check if there is some way to reload the whole OS without erasing the disk, but I find that the installation process are not very clear on what the various options will really do to your partitions prior to letting it run. At this point the least frustrating and possibly the fastest is to bring up a new Ubuntu 16.04 installation on another disk (without MariaDB!) and copy the bulk of the 1.5TB of data files (mainly my VMs to build various OS versions of Bacula). I am rather embarrassed to be taking your time for something seemingly so elementary and simple. I would feel better to disappear for a week and come back when I have a running system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592749 Title: MySQL 5.7 slow with Bacula 7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592749] Re: MySQL 5.7 slow with Bacula 7.4
Thanks for your tip. It did get me past the problem with apt not wanting to downgrade from version 10 to 5.7. However, it created other problems. Unfortunately, I am unable to re-install MySQL even after removing all traces of MariaDB and MySQL. There are always errors. It is so bad that even: apt-get purge mysql-server mysql-client mysql-common fails. All attempts to install/remove/purge MySQL fail. Bottom line: if you install MariaDB, it renders your system in a state that you can no longer revert to MySQL. I suggest the MySQL purge and MySQL install packages need some testing under the condition that MariaDB is installed. In my case, I first installed MySQL server and client, then with no problems installed MariaDB (it supposedly removed MySQL, which was not really what I wanted, but it wasn't unreasonable). I have been using Ubuntu for a very long time now, and sometimes I break packages or they fail, and I have always been able to recover from package installation problems using some combination of purge, dpkg --configure -a and apt-get -f install. In this case, I seem to be blocked every way I turn. The latest of many is: apt-get purge mysql-server-5.7 dpkg: error processing package mysql-server-5.7 (--purge) package is a very bad inconsistent state; you should reinstall it before attempting a removal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592749 Title: MySQL 5.7 slow with Bacula 7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592749] Re: MySQL 5.7 slow with Bacula 7.4
Lars, I am sorry. First, I had installed MariaDB and so the failures were for MariaDB and not MySQL. MariaDB is more than 10 times slower than PostgreSQL, and it shows very clearly in iostat and perf top output. iostat shows much higher iowait numbers than PostgreSQL, it appears that most of the difference in performance is just MariaDB (and thus probably MySQL) sitting waiting for I/Os. Unfortunately after installing MariaDB, it is not possible to remove (purge) MariaDB and then re-install MySQL. The installation of the server always fails, and I get lots of problems such as Can't connect to local MySQL server through socket ... as well of errors saying that the unix_socket plugin is not installed. One of the things I could not do was to compare the default my.cnf files on 14.04 and 16.04 to see if anything that could change the "out-of-the-box" performance changed. At this point, I have to give up, because I have too many urgent projects pressing on my. I am convinced that there is a serious performance problem on both MySQL and MariaDB compared to PostgreSQL when working with Bacula and both being untuned. I also think there is a "bug" in apt-get purge of MariaDB server that leaves some traces of MariaDB lying around so that a subsequent install of MySQL fails -- that probably should be the subject of another bug report. I see there is lots of advice on the web for fixing this problem, but I keep running into problems such as no mysql_safe, ... It is so bad that even apt-get purge mysql-server fails in horrible ways. Running as root: == apt-get purge mysql-server mysql-client Reading package lists... Done Building dependency tree Reading state information... Done Package 'mysql-client' is not installed, so not removed Package 'mysql-server' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 43 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up mysql-server-5.7 (5.7.12-0ubuntu1.1) ... mysql_upgrade: Got error: 1524: Plugin 'unix_socket' is not loaded while connecting to the MySQL server Upgrade process encountered error and will not continue. mysql_upgrade failed with exit status 11 dpkg: error processing package mysql-server-5.7 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: mysql-server-5.7 E: Sub-process /usr/bin/dpkg returned an error code (1) = I would really like to find out what is hurting the performance, but it will have to wait to a later time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592749 Title: MySQL 5.7 slow with Bacula 7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592749] Re: MySQL 5.7 slow with Bacula 7.4
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 5.7 and Postgres 9.5. Even more concerning is that there seem to be a number of Bacula regression failures with MySQL 5.7. I am working on this and will get back to you with some more detailed information on MySQL 5.7 timing and test failures, both of which I want to examine in some detail before reporting back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592749 Title: MySQL 5.7 slow with Bacula 7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592749] Re: MySQL 5.7 slow with Bacula 7.4
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 MySQL without any upgrade. Note, since those tests, I have rebuilt the Ubuntu 16.04 machine with a new installation of Ubuntu with new slightly faster disks, but more importantly the system is booted on ZFS, while the previous 5.7 test were run on an ext4 system. I will re-run the tests with what I have but with more tests. This will take a day or two, since I am still restoring the user files ... I will be happy to run with REGRESS_DEBUG=1, but I am not sure it will help -- except more debug will be printed. What exactly are you looking for? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592749 Title: MySQL 5.7 slow with Bacula 7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1553563] Re: bconsole to Bacula Director fails with authorization problem message
Many thanks. I will look in detail at the links to the PIE links you
provided to see if anything jumps out at me.
One possible concern in your patch for make_mysql_tables.in:
If the line:
SET SESSION sql_mode = (SELECT REPLACE(@@sql_mode,'NO_ZERO_DATE', ''));
simply sets the NO_ZERO_DATE to NULL rather than 1, all is OK and you
can skip the rest of this paragraph. However, on the off chance that it
tells MySQL not to permit any zero value for a date, then Bacula will
fail. Bacula does not need the default value to be zero, but Bacula
does set a zero value (a valid Unix/Linux value) in a number of the
DATETIME fields. If MySQL either changes the value or fails the SQL
command, Bacula will fail.
In the community version 7.4.1, I edited the make_mysql_tables.in to
remove all the DATETIME default values of 0 which were the cause the
incompatibility. Consequently, if you include my new
make_mysql_tables.in you should not need for the above SET SESSION line.
I'll leave it to you to decide what to do, if anything.
Best regards,
Kern
On 06/24/2016 05:54 PM, Nish Aravamudan wrote:
> On 24.06.2016 [06:07:06 -], Kern Sibbald wrote:
>> 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
>> -Bsymbolic-functions from what Bacula expects. While setting the
>> default values of directives, Bacula compares addresses of function
>> pointers. If these function pointers are changed from what Bacula
>> expects, setting the default value fails. Bacula does not use position
>> independent executables (at least we do not set it in our LDFLAGS).
> Yep, and Ubuntu uses PIE by default in 16.10 (on some archs), but I'm
> not sure it's set in 16.04 based upon the buildlog at
> https://launchpadlibrarian.net/267315679/buildlog_ubuntu-xenial-amd64.bacula_7.4.1~dfsg-1.1~ppa7_BUILDING.txt.gz.
> More details on
> PIE in Ubuntu: https://wiki.ubuntu.com/Security/Features#pie.
>
>> In a future version (hopefully the next one), I will identify the
>> function pointers with a unique index for each function, then instead of
>> comparing function pointers, I will compare indexes. This will
>> definitively avoid the problem. Thanks for making the Ubuntu build work
>> again.
> Yep, that makes sense!
>
>> On a different issue:
>> If you would like, I will be happy to look at your patch for [Bug
>> 1570923] Re: bacula-dir won't start with "undefined symbol: mysql_init",
>> however, I don't know where to find it.
> So the PPA build has the following changes, with my commentary in []:
>
> bacula (7.4.1~dfsg-1.1~ppa7) xenial; urgency=medium
>
>* debian/patches/libmysqlclient_r.patch: Fix bug where MySQL 5.7 is
> improperly linked on Ubuntu 16.04. Closes LP: #1570923.
> [ backport of
> http://www.bacula.org/git/cgit.cgi/bacula/commit/?h=Branch-7.4=d3196af3e6c9f65b9f0790625a2e844dcb5fd190
> ]
>* debian/patches/mysql_install_update.patch: mysql database
> install/update scripts patch. Fixes bug #1901.
> [ backport of
> http://www.bacula.org/git/cgit.cgi/bacula/commit/?h=Branch-7.4=074419ac0c9dbbde2e4d2f5ccb6d4ca85c6ec8a9
> ]
>* debian/patches/disable_mysql_NO_ZERO_DATE.patch: Disable
> NO_ZERO_DATE mode for MySQL table creation.
> [ Without this, I get an error from MySQL 5.7 (strict mode) about
>the CleaningDate field having an invalid default.
> --- bacula-7.4.1~dfsg.orig/src/cats/make_mysql_tables.in
> +++ bacula-7.4.1~dfsg/src/cats/make_mysql_tables.in
> @@ -14,6 +14,8 @@ PATH="$bindir:$PATH"
> db_name=${db_name:-@db_name@}
>
> if mysql -D ${db_name} $* -f < +SET SESSION sql_mode = (SELECT REPLACE(@@sql_mode,'NO_ZERO_DATE', ''));
> +
> --
> -- Note, we use BLOB rather than TEXT because in MySQL,
> -- BLOBs are identical to TEXT except that BLOB is case
> ]
>* d/rules: do not use -Bsymoblic-functions when linking.
> [ The result from this bug and Hiroaki's analysis ]
>
> -- Nishanth Aravamudan <nish.aravamu...@canonical.com> Thu, 23 Jun
> 2016 12:35:56 -0700
>
> I'll clean-up the changelog to ensure the bugs get auto-tagged
> appropriately and submit it for SRU.
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553563
Title:
bconsole to Bacula Director fails with authorization problem message
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1553563/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1592749] Re: MySQL 5.7 slow with Bacula 7.4
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, and pass > it on upstream. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592749 Title: MySQL 5.7 slow with Bacula 7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1553563] Re: bconsole to Bacula Director fails with authorization problem message
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 -Bsymbolic-functions from what Bacula expects. While setting the default values of directives, Bacula compares addresses of function pointers. If these function pointers are changed from what Bacula expects, setting the default value fails. Bacula does not use position independent executables (at least we do not set it in our LDFLAGS). In a future version (hopefully the next one), I will identify the function pointers with a unique index for each function, then instead of comparing function pointers, I will compare indexes. This will definitively avoid the problem. Thanks for making the Ubuntu build work again. On a different issue: If you would like, I will be happy to look at your patch for [Bug 1570923] Re: bacula-dir won't start with "undefined symbol: mysql_init", however, I don't know where to find it. Best regards, Kern On 06/24/2016 03:50 AM, Nish Aravamudan wrote: > @Kern, > > To clarify, this change: > > export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions > >[-Bsymbolic is not passed to the build currently, so omitted in my > changes] > > has nothing to do with stripping of binaries. It 'strips' the requested > LDFLAGS out of the DEBUILD_LDFLAGS (aiui, not much documentation of it). > So it seems that the Bacula build can't handle this option to ld: > > -Bsymbolic-functions > When creating a shared library, bind references to global function > symbols to the definition within the shared library, if any. This > option can also be used with the --export-dynamic option, when > creating a position independent executable, to bind references to > global function symbols to the definition within the executable. > This option is only meaningful on ELF platforms which support > shared libraries and position independent executables. > > Given Hiroaki's excellent analysis here and in Bug 1570923, I think this > relates to the use of a same-named function in a library that is linked > to? Maybe if we also passed --export-dynamic, it would also work, I'm > not 100%. I'd like to understand the exact issue better before > suggesting we SRU that change. > > -Nish > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553563 Title: bconsole to Bacula Director fails with authorization problem message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1553563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570923] Re: bacula-dir won't start with "undefined symbol: mysql_init"
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 additional problem that you must explicitly create the user "bacula" within the database using psql. See the postgres documentation on "create user ...". Prior versions were simpler since users were automatically created by the Bacula grant_bacula_privileges script. I highly recommend using PostgreSQL with Bacula -- it is *much* (10X) faster than MySQL for certain operations. See my bug report on MySQL about MySQL and Bacula. -- 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 won't start with "undefined symbol: mysql_init" To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/1570923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592749] [NEW] MySQL 5.7 slow with Bacula 7.4
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 expected with Bacula. MySQL 5.7, however, is 10 times slower than PostgreSQL and *possibly* 100% slower than prior versions of MySQL. When MySQL is running, the disk is making a typical thrashing sound (i.e. lots of accesses). This is as if MySQL has by default fsync enabled after every database update. Below, I show the first two Bacula regression tests for MySQL then for PostgreSQL. The point here is that MySQL out of the box does not perform "well". Comparison between the two different versions run on different machines so may not be totally valid. On the other hand, a difference in speed of a factor of 10 between MySQL and Postgres is remarkable. Note only a part of the time is actually consumed by the database thus the real difference in the database speeds is larger. I suggest that we cannot expect most users to be able to tune MySQL and that the out of the box performance ideally would be somewhat equivalent to PostgreSQL. Ubuntu 16.04: For MySQL 5.7the tests take: 239 seconds and 822 seconds to run. For Postgres 9.5 the tests take: 23 seconds and 81 seconds to run Ubuntu 14.04 (a different machine from the above) For MySQL 5.5the tests take: 115 seconds and 393 seconds to run. For Postgres 9.3 the tests take: 23 seconds and 76 seconds to run MySQL 5.7 tests for Ubuntu 16.04: Start non-root disk tests === Starting acl-xattr-test at 09:52:46 === = acl-xattr-test OK 09:56:46 00:03:59 239s = === Starting action-on-purge-test at 09:57:23 === = action-on-purge-test OK 10:11:05 00:13:42 822s = PostgreSQL tests: Start non-root disk tests === Starting acl-xattr-test at 10:13:21 === = acl-xattr-test OK 10:13:45 00:00:23 23s = === Starting action-on-purge-test at 10:13:56 === = action-on-purge-test OK 10:15:18 00:01:21 81s = ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592749 Title: MySQL 5.7 slow with Bacula 7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570923] Re: bacula-dir won't start with "undefined symbol: mysql_init"
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 clearly trashing the disk and runs Bacula jobs 10-15 times slower than on previous MySQL versions. I suspect that someone has by default turned on a sync/flush after every MySQL update. Prior MySQL releases by Ubuntu were relatively efficient. Out of the box they were between 10-20% slower than a slightly tuned PostgreSQL. Now it is 10-15 times slower than an untuned PostgreSQL out of the box on the same computer. Please let me know if I should open a new ticket on this. -- 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 won't start with "undefined symbol: mysql_init" To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/1570923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570923] Re: bacula-dir won't start with "undefined symbol: mysql_init"
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 good for MySQL 5.7 on Ubuntu 16.04. Unfortunately the patch needed to get Bacula to link properly with MySQL 5.7 and much older MySQL's is considerable more complex with this latest change to how the MySQL client libraries are linked. I have pushed what I hope is a "generic" fix to Bacula 7.4 to the public git repository. It has commit SHA 50327c9d4. The equivalent "generic" fix for Bacula 7.0 has commit SHA d6de542 and is also in the Bacula public repo. I imagine you will want to stay with your patch, but my version is also now available. Feedback from anyone would be appreciated. -- 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 won't start with "undefined symbol: mysql_init" To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/1570923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570923] Re: bacula-dir won't start with "undefined symbol: mysql_init"
Linking of Bacula 7.4.x on Ubuntu 16.04 has the same problem described in this bug report. It seems to me that something is wrong with the Ubuntu 16.04 packaging of MySQL. Bacula needs libmysqlclient_r.so to work correctly, and that shared library is not installed on Ubuntu 16.04 (at least not on my system). Thus when linking the Bacula catalog library, the mysql_init symbol is not defined. The "fix" in #22 from Marcos may work, but then the client library will be linked directly into Bacula rather than using the system shared object. Perhaps the libmysqlclient_r.so has been replaced in Ubuntu 16.04 with libmysqlclient.so, but if this is the case, it is somehow confusing the Bacula MySQL build. Consequently, as far as I am concerned, either the Ubuntu 16.04 package for MySQL is broken or it is changed in a way that is no longer compatible with Bacula or Bacula is 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 won't start with "undefined symbol: mysql_init" To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/1570923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553563] Re: bconsole to Bacula Director fails with authorization problem message
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 binaries (i.e. a deb) please let me know and I will
look for the Bacula Systems scripts that do this.
Concerning the current problem: what seems clear to me is that the
packaging has added additional build flags that either were not in the
previous version 14.04 or what those flags do has changed (e.g. more
randomization). ASLR and PIC sound like things that could cause
problems. Bacula does not explicitly set either in our binary builds.
Note for packaging: it is better to install all of Bacula in /opt/bacula, which
I think is permitted by the LSB. This is because by having it all installed in
one directory, it is *far* easier for Bacula to properly back itself up. All
distributions that I have looked at spread Bacula components all over the
directory structure, which prevents Bacula from easily backing up itself when
doing a backup of the catalog. From prior experience with distro packagers,
who have rather strict rules to follow, I doubt I will get very far with this,
but I wanted you to know.
For example, here is the FileSet that I use for my catalog backup:
# Backup the copy of the catalog
FileSet {
Name = "CatalogFile"
Include {
Options {
signature=MD5
}
File = /opt/bacula/working/bacula.sql # get catalog
File = /opt/bacula# get Bacula + conf
}
Exclude {
File = /opt/bacula/working # ignore temp files
}
}
Notice how easy it is to backup all of Bacula. For a disaster recovery,
it is *really* nice to have everything all in one backup -- all the
Bacula conf files, scripts, binaries, and the catalog backup as well.
Not also, the .bsr file is emailed to me every night, so that makes it
trivial to find and restore Bacula as it was at any particular backup
point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553563
Title:
bconsole to Bacula Director fails with authorization problem message
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1553563/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553563] Re: bconsole to Bacula Director fails with authorization problem message
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 Bacula from directly testing the equality of external subroutine addresses (probably by adding some thunking or other indirect addressing). Conclusion: eliminate all the non-Bacula compile and/or link options. If you really want to use esoteric options, I recommend running the regression tests on the packaged binaries prior to releasing. Successfully running the regression tests virtually guarantee a good build/package. Second conclusion: in a future version of Bacula, I will eliminate all code that tests equality of subroutine addresses. 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/1553563 Title: bconsole to Bacula Director fails with authorization problem message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1553563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589551] [NEW] upgrading from 14.04 to 16.04 or direct install of 16.04 fails
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. 16.04 is a total disaster for me. - Starting from a 14.04 desktop system fully patched and doing a dist- upgrade fails leaving many uninstalled packages and package conflicts that I have not been able to fix manually (50-100 packages). I think I know all the tricks for installing almost anything, but no go here. - New Lenovo Yoga 900. Install 14.04 zero problems. Fully update it. dist-upgrade. Same results as above. Note the 14.04 had only Ubuntu packages and was only about a week old before the dist-upgrade. - Retry the dist-upgrade on the above. No go, same problem. - Do a new upgrade from a USB stick of 16.04 on the above system containing 14.04 partially upgraded to 16.04 but not working. It produced a working 16.04, but destroyed my Windows dual boot, and wiped out the Windows recovery partition. This is extremely annoying because I had not made recovery disks. Once I get new install media and re- install Windows 10 (beautiful with a nice touch screen even if it is Windows) I am thinking about sticking to Windows (after 16 years of using Linux on my laptops this is really bad). - Do a fresh install of 16.04 on a tower computer. All goes quite well. However after doing an apt-get upgrade to get fully patched, then part way through loading about 100 packages for a developer's setup, I double click on the Amazon icon, which comes up slowly then totally freezes the system. This is much like the black screen syndrome that Windows used to have -- requires a power off (hold the power button down 10 seconds)! - Reboot after power off in prior case, and things seem to work until I double click on the Amazon button and then close the window. The app crashes with a webapp-container problem. Conclusion: This is not the way to keep happy users. 16.04 is for me unusable. For the first time in a very long time, I am very disappointed. IMO, 16.04 should be considered unstable beta software. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.8 ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39 Uname: Linux 3.13.0-87-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Mon Jun 6 16:53:55 2016 InstallationDate: Installed on 2014-12-23 (531 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to trusty on 2016-05-16 (21 days ago) VarLogDistupgradeAptlog: Log time: 2016-05-16 09:48:08.557294 Log time: 2016-05-16 09:48:12.502444 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589551 Title: upgrading from 14.04 to 16.04 or direct install of 16.04 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1589551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553563] Re: bconsole to Bacula Director fails with authorization problem message
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 not used in upstream development. From the comments from Hiroaki Hashi, it would appear that they are related to stripping the binaries. I recommend trying building Bacula without stripping and without the changed DEB_LDFLAGS_MAINT_STRIP and see if it works. If it does work, then the problem is only happening during stripping, which means that either the stripping is broken, or Bacula code is not compatible with stripping. The default value of Maximum Connections is 20 and is maintained in the same table that contain the "handler" addresses you mention above. The comments above at: "Hiroaki Hashi (hashiz) wrote on 2016-05-11:" are very interesting because the configuration tables in the Director are all in /src/dir/dird_conf.c. The ones that seem not to work correctly for the default values are in tables that are defined as "static" while the default values that are in non-"static" (referenced in more than one source file) tables seem to work. Perhaps something that is happening during stripping either .text or .data that is breaking the code. Perhaps stripping does not by default permit addresses that are in the .data section. Question: If the problem is related to addresses in the .data section, will adding the "const" attribute to the table definitions force them to all be in the .text section? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553563 Title: bconsole to Bacula Director fails with authorization problem message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1553563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577858] Re: bacula mysql support requires server configuration changes
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 is to remove all the "DEFAULT 0" values from the creation of the MySQL tables which is done in the Bacula source file /src/cats/make_mysql_tables.in You can get a copy of the current Bacula release file (will be released tomorrow) from the public Bacula repository. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577858 Title: bacula mysql support requires server configuration changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1577858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1005594] Re: Ubuntu server unusable due to poor performance
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 regards, Kern On 04/01/2014 05:38 PM, Phillip Susi wrote: I am not able to reproduce this with 12.04.4, are you? Using a vm with a disk of exactly the same size, I get partitions starting at: 2048 999424 1499136 ** Changed in: partman-partitioning (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005594 Title: Ubuntu server unusable due to poor performance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-partitioning/+bug/1005594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280149] Re: Add Bacula fork Bareos to repository
Although it is true that the Bacula git repo has not been updated for some time, there is a good reason, for more information, please see: http://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 come and go, I have been contacted by a number of former and current Bacula developers and they all remain with Bacula. I would appreciate it if people who make incorrect statements such as Most of the devlopers [sic] switched to the Bareos would take the time to investigate or simply look at the Bacula website before making such comments. You should realize that the Bareos fork has some serious problems, including copyright violations and alleged theft of proprietary code, so though anyone is free to download and use the Bareos release, you you will be downloading code that may contain code that Bareos has no right to release. On the other hand, Bacula's copyright is held by the Free Software Foundation, Europe, and I can assure you that all code in Bacula is used by written permission. Bacula has been under development for 14 years now and will continue so in the future at a pace that is faster than any fork that is created by one person in secret over a 3 year period. There will be another release of Bacula in the March-April time frame, which will have a lot of new features, many planned well before the fork. If you are the interested 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.launchpad.net/bugs/1280149 Title: Add Bacula fork Bareos to repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1280149/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1280149] Bug 1280149] [NEW] Add Bacula fork Bareos to repository
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 come and go, I have been contacted by a number of former and current Bacula developers and they all remain with Bacula. I would appreciate it if people who make incorrect statements such as Most of the devlopers [sic] switched to the Bareos would take the time to investigate or simply look at the Bacula website before making such comments. You should realize that the Bareos fork has some serious problems, including copyright violations and alleged theft of proprietary code, so though anyone is free to download and use the Bareos release, you you will be downloading code that may contain code that Bareos has no right to release. On the other hand, Bacula's copyright is held by the Free Software Foundation, Europe, and I can assure you that all code in Bacula is used by written permission. Bacula has been under development for 14 years now and will continue so in the future at a pace that is faster than any fork that is created by one person in secret over a 3 year period. There will be another release of Bacula in the March-April time frame, which will have a lot of new features, many planned well before the fork. If you are the interested in the saga of the Bareos fork, please see the new Bacula website (under development) at: http://blog.bacula.org -- 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/1280149 Title: Add Bacula fork Bareos to repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1280149/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1280149] Bug 1280149] [NEW] Add Bacula fork Bareos to repository
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 come and go, I have been contacted by a number of former and current Bacula developers and they all remain with Bacula. I would appreciate it if people who make incorrect statements such as Most of the devlopers [sic] switched to the Bareos would take the time to investigate or simply look at the Bacula website before making such comments. You should realize that the Bareos fork has some serious problems, including copyright violations and alleged theft of proprietary code, so though anyone is free to download and use the Bareos release, you you will be downloading code that may contain code that Bareos has no right to release. On the other hand, Bacula's copyright is held by the Free Software Foundation, Europe, and I can assure you that all code in Bacula is used by written permission. Bacula has been under development for 14 years now and will continue so in the future at a pace that is faster than any fork that is created by one person in secret over a 3 year period. There will be another release of Bacula in the March-April time frame, which will have a lot of new features, many planned well before the fork. If you are the interested in the saga of the Bareos fork, please see the new Bacula website (under development) at: http://blog.bacula.org -- 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 Bacula fork Bareos to repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1280149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280149] Re: Add Bacula fork Bareos to repository
Although it is true that the Bacula git repo has not been updated for some time, there is a good reason, for more information, please see: http://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 come and go, I have been contacted by a number of former and current Bacula developers and they all remain with Bacula. I would appreciate it if people who make incorrect statements such as Most of the devlopers [sic] switched to the Bareos would take the time to investigate or simply look at the Bacula website before making such comments. You should realize that the Bareos fork has some serious problems, including copyright violations and alleged theft of proprietary code, so though anyone is free to download and use the Bareos release, you you will be downloading code that may contain code that Bareos has no right to release. On the other hand, Bacula's copyright is held by the Free Software Foundation, Europe, and I can assure you that all code in Bacula is used by written permission. Bacula has been under development for 14 years now and will continue so in the future at a pace that is faster than any fork that is created by one person in secret over a 3 year period. There will be another release of Bacula in the March-April time frame, which will have a lot of new features, many planned well before the fork. If you are the interested 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280149 Title: Add Bacula fork Bareos to repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1280149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 579924] Re: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10
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 appropriate SQL backend script (e.g. update_postgresql_tables to actually do the schema modifications. That script must be called when installing a new version of Bacula AND when the database changes (normally only during major version changes). The rpm .spec files distributed with the project automatically call the script when needed, but we do not have .deb scripts, so that must be done by each packager (e.g. Ubuntu). That part is fairly straight forward. However, if you are updating Bacula and going from say version 1.38 to version 5.2.x, you may have several DB updates to make. These must be done one at a time, which can be slightly painful to know exactly which scripts need to be called. So to make packagers jobs a bit easier we supply a directory bacula-src/updatedb that has all the scripts necessary to upgrade from one DB version to the next (it may not have the very latest upgrade which is in src/cats). If you look in that directory and read the README file, you should be able to figure out what needs to be done. Also looking at the comments at the top of the upgrade scripts you will probably see what Bacula versions correspond to what DB versions. In the error message included in your subject line, it looks like the prior version of Bacula was running version 10 of the database schema, and the new version of Bacula that was loaded wants DB version 12. This means that the upgrade script from 10_to_11 must be applied followed by the script from 11_to_12. I hope this explanation helps. Best regards, Kern On 08/30/2012 05:38 PM, James Page wrote: As this bug is still being updated with comments I'm assuming its still impacting people. I took a look at the bacula packages in Lucid - they should be using dbconfig-common to do DB upgrades during packaging upgrade and I can see the required update scripts at version 3.0.0 (version 11) and 5.0.0 (version 12). So I'm a little mystified as to why this is not happening automatically. I'll do some more investigation. -- 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/579924 Title: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10 To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/579924/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 579924] Re: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10
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 appropriate SQL backend script (e.g. update_postgresql_tables to actually do the schema modifications. That script must be called when installing a new version of Bacula AND when the database changes (normally only during major version changes). The rpm .spec files distributed with the project automatically call the script when needed, but we do not have .deb scripts, so that must be done by each packager (e.g. Ubuntu). That part is fairly straight forward. However, if you are updating Bacula and going from say version 1.38 to version 5.2.x, you may have several DB updates to make. These must be done one at a time, which can be slightly painful to know exactly which scripts need to be called. So to make packagers jobs a bit easier we supply a directory bacula-src/updatedb that has all the scripts necessary to upgrade from one DB version to the next (it may not have the very latest upgrade which is in src/cats). If you look in that directory and read the README file, you should be able to figure out what needs to be done. Also looking at the comments at the top of the upgrade scripts you will probably see what Bacula versions correspond to what DB versions. In the error message included in your subject line, it looks like the prior version of Bacula was running version 10 of the database schema, and the new version of Bacula that was loaded wants DB version 12. This means that the upgrade script from 10_to_11 must be applied followed by the script from 11_to_12. I hope this explanation helps. Best regards, Kern On 08/30/2012 05:38 PM, James Page wrote: As this bug is still being updated with comments I'm assuming its still impacting people. I took a look at the bacula packages in Lucid - they should be using dbconfig-common to do DB upgrades during packaging upgrade and I can see the required update scripts at version 3.0.0 (version 11) and 5.0.0 (version 12). So I'm a little mystified as to why this is not happening automatically. I'll do some more investigation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/579924 Title: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10 To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/579924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005594] [NEW] Ubuntu server unusable due to poor performance
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 unusable. After a bit of investigation the problem turned out to be the harddisk partition that your partition code did. It partitioned something like this: Disk /dev/sda: 2930277168s Sector size (logical/physical): 512B/512B Partition Table: gpt Number StartEnd Size File system Name Flags 1 34s 390659s 390626s fat32 boot 2 390660s 890660s 51s ext2 boot 3 890661s 2930277118s xs lvm lvm where I have left the size of partition 3 out (it is not important). It turns out that this partitioning is about as bad as one can do on these new disks that have blocks aligned on 8 sector boundaries. I repartitioned the harddisk to: Model: ATA WDC WD15EARS-00Z (scsi) Disk /dev/sda: 2930277168s Sector size (logical/physical): 512B/512B Partition Table: gpt Number StartEnd Size File system Name Flags 1 34s 390659s 390626s fat32 boot 2 390660s 890660s 51s ext2 boot 3 890880s 2930277118s 2929386239s lvm lvm so that the main disk partition (3) is properly aligned. I did not align the other partitions to save time (I just copied partition off to another disk, repartitioned it properly aligned then copied it back). The difference in the performance of the system was absolutely mind boggling (it felt like it was at least 100 times faster, and for many operations it probably was). For the command: dd oflag=sync bs=4096 if=/dev/zero of=test.xx count=3000 with the partitioning done by your installer I got: 12288000 bytes (12 MB) copied, 572.024 s, 21.5 kB/s with the aligned partitioning: 12288000 bytes (12 MB) copied, 156.738 s, 78.4 kB/s That is more than 3X the speed. If Ubuntu wants to play in the server market, please teach the programmers who write the install program to know how to properly align the large modern disk. Hopefully the desktop installer doesn't do the same thing ... There is no need to answer this as the problem is resolved for me, but possibly not for many of your other users. ** Affects: partman-partitioning (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005594 Title: Ubuntu server unusable due to poor performance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-partitioning/+bug/1005594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 579924] Re: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10
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 need to go from one version to the next. Note, there may be more than one script that needs to be applied depending on what Bacula versions involved. In your case, I imagine you must apply the 10_to_11 script, and then the 11_to_12 script, so that the database will be upgraded from version 10 to 11 then from 11 to 12. The text in the script tells you what Bacula versions the upgrade corresponds to. Best regards, Kern On 04/19/2012 10:21 PM, Martin wrote: I am a litte bit surprised: Bacula is NOT an universe package and a LTS to LTS upgrade is broken (8.04 to 10.04). But noone takes care of this issue - even after 2 years... And yes, I am affected by this problem: An upgrade from 8.04 to 10.04 does not work as expected. -- 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/579924 Title: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10 To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/579924/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 579924] Re: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10
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 need to go from one version to the next. Note, there may be more than one script that needs to be applied depending on what Bacula versions involved. In your case, I imagine you must apply the 10_to_11 script, and then the 11_to_12 script, so that the database will be upgraded from version 10 to 11 then from 11 to 12. The text in the script tells you what Bacula versions the upgrade corresponds to. Best regards, Kern On 04/19/2012 10:21 PM, Martin wrote: I am a litte bit surprised: Bacula is NOT an universe package and a LTS to LTS upgrade is broken (8.04 to 10.04). But noone takes care of this issue - even after 2 years... And yes, I am affected by this problem: An upgrade from 8.04 to 10.04 does not work as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/579924 Title: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10 To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/579924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579924] Re: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10
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 find in the bacula/src/cats directory or in the bacula/updatedb directory. Sometimes the updatedb is package separately. Actually, it looks like you need to apply two update scripts. One goes from 10 to 11 and the second from 11 to 12. Of course, that all depends on the Bacula version you are starting from and the one you are going to. Normally, if one upgrades each major bacula version (change in second digit of version), you will move only one database version at a time. You might ask packagers to include the update procedure automatically when installing new packages. It is a lot more user friendly. -- 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/579924 Title: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10 To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/579924/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 579924] Re: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10
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 find in the bacula/src/cats directory or in the bacula/updatedb directory. Sometimes the updatedb is package separately. Actually, it looks like you need to apply two update scripts. One goes from 10 to 11 and the second from 11 to 12. Of course, that all depends on the Bacula version you are starting from and the one you are going to. Normally, if one upgrades each major bacula version (change in second digit of version), you will move only one database version at a time. You might ask packagers to include the update procedure automatically when installing new packages. It is a lot more user friendly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/579924 Title: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10 To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/579924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 265102] Re: bacula not compiled with FORTIFY_SOURCE
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 so adding fortify source will only add unnecessary additional overhead. Just the same, I would like to see this ticket closed one way or another. -- 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/265102 Title: bacula not compiled with FORTIFY_SOURCE To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/265102/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 830108] Re: bacula director eror in initial conf file
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 Title: bacula director eror in initial conf file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/830108/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 645097] Re: bat crashed with SIGSEGV in e_msg()
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 because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/645097 Title: bat crashed with SIGSEGV in e_msg() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/645097/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 265102] Re: bacula not compiled with FORTIFY_SOURCE
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 so adding fortify source will only add unnecessary additional overhead. Just the same, I would like to see this ticket closed one way or another. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/265102 Title: bacula not compiled with FORTIFY_SOURCE To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/265102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 830108] Re: bacula director eror in initial conf file
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 director eror in initial conf file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/830108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645097] Re: bat crashed with SIGSEGV in e_msg()
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/645097 Title: bat crashed with SIGSEGV in e_msg() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/645097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 840299] [NEW] Your ch.archive.ubuntu.com is missing a lot of packages
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. Switching to using fr.archive.ubuntu.com has all the needed packages. You sure don't make figuring out how to submit a bug report simple -- sorry this is a download bug, but it wanted a package name. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: liblua50 5.0.3-4 ProcVersionSignature: Ubuntu 2.6.32-29.58-generic 2.6.32.28+drm33.13 Uname: Linux 2.6.32-29-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Sep 3 14:37:01 2011 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lua50 ** Affects: lua50 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- 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: https://bugs.launchpad.net/ubuntu/+source/lua50/+bug/840299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 840299] Re: Your ch.archive.ubuntu.com is missing a lot of packages
-- 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: https://bugs.launchpad.net/ubuntu/+source/lua50/+bug/840299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 735369] Re: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid
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 particularly seg fault fixes. I am sorry, I don't remember the specifics, and since I did not explicitly reproduce the reported bug, I am not sure there is an explicit fix, but I think so. While I do think we should put 5.2.0 in backports when it arrives, if the fix is simple it might be worth patching 5.0.1 so it works in lucid. There were a lot of changes, and I believe we have a significant number in the Director too, so any backporting might not be easy. You are free to try backporting but it is not something that I am personally going to do. This one is really hard to confirm as I don't have any files to restore in my test bacula. Is there a shorter test case? I don't know as I haven't explicitly reproduced the reported bug. I'm going to mark this as Incomplete, pending a shorter test case and/or answers from Kern. If its too hard to test, and/or too hard to fix in lucid, it might just have to be a Won't Fix. OK. I am not sure what your procedure is -- it might be good to note fixed in 5.2.x providing that is really the case. * Changed in: bacula (Ubuntu) Status: Incomplete = Confirmed -- 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/735369 Title: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 735369] Re: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid
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 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 particularly seg fault fixes. I am sorry, I don't remember the specifics, and since I did not explicitly reproduce the reported bug, I am not sure there is an explicit fix, but I think so. While I do think we should put 5.2.0 in backports when it arrives, if the fix is simple it might be worth patching 5.0.1 so it works in lucid. There were a lot of changes, and I believe we have a significant number in the Director too, so any backporting might not be easy. You are free to try backporting but it is not something that I am personally going to do. This one is really hard to confirm as I don't have any files to restore in my test bacula. Is there a shorter test case? I don't know as I haven't explicitly reproduced the reported bug. I'm going to mark this as Incomplete, pending a shorter test case and/or answers from Kern. If its too hard to test, and/or too hard to fix in lucid, it might just have to be a Won't Fix. OK. I am not sure what your procedure is -- it might be good to note fixed in 5.2.x providing that is really the case. Hm. Sounds like this one may not get backported. The procedure is to mark the main bug task Fix Released, but then track each release of the package before that individually. Won't Fix means the bug is in that version, but we're not going to fix it. OK, your procedures are different from ours, which is OK. We normally indicate to the user that it is fixed in a future version. That is all I was trying to say. No problem however you do it :-) * Changed in: bacula (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/735369 Title: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid Status in Bacula the Network Backup Solution: New Status in “bacula” package in Ubuntu: Confirmed Bug description: Binary package hint: bacula-console-qt On lucid, in the Version Browser of bat, it is impossible to check the latest version of a file. This is described in the following upstream bug report: http://bugs.bacula.org/view.php?id=1550 (login using anonymous/anonymous) For convenience, here is the verbatim of the bug description: -- I often restore a single file, so I use Version Browser. 1) I browse for the file and when clicking on it, I see many different versions of it. 2) When I try to mark the file (tick the checkbox), it cannot be done 3) When I try to mark the most recent version of the file in 'Versions of File', it cannot be done 4) When I try to mark any other version of the file, it works OK 5) When there's another version of the file available (after the next backup), the version which couldn't be marked, can now be marked and the most recent can not It seems to be so for every job and every file within a job. I turned on all the debugging options of Bat, but there's nothing said when marking (or trying to) files/versions. - Response from the lead developer of Bacula: -- 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/735369 Title: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 735369] Re: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid
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 particularly seg fault fixes. I am sorry, I don't remember the specifics, and since I did not explicitly reproduce the reported bug, I am not sure there is an explicit fix, but I think so. While I do think we should put 5.2.0 in backports when it arrives, if the fix is simple it might be worth patching 5.0.1 so it works in lucid. There were a lot of changes, and I believe we have a significant number in the Director too, so any backporting might not be easy. You are free to try backporting but it is not something that I am personally going to do. This one is really hard to confirm as I don't have any files to restore in my test bacula. Is there a shorter test case? I don't know as I haven't explicitly reproduced the reported bug. I'm going to mark this as Incomplete, pending a shorter test case and/or answers from Kern. If its too hard to test, and/or too hard to fix in lucid, it might just have to be a Won't Fix. OK. I am not sure what your procedure is -- it might be good to note fixed in 5.2.x providing that is really the case. * Changed in: bacula (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/735369 Title: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 735369] Re: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid
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 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 particularly seg fault fixes. I am sorry, I don't remember the specifics, and since I did not explicitly reproduce the reported bug, I am not sure there is an explicit fix, but I think so. While I do think we should put 5.2.0 in backports when it arrives, if the fix is simple it might be worth patching 5.0.1 so it works in lucid. There were a lot of changes, and I believe we have a significant number in the Director too, so any backporting might not be easy. You are free to try backporting but it is not something that I am personally going to do. This one is really hard to confirm as I don't have any files to restore in my test bacula. Is there a shorter test case? I don't know as I haven't explicitly reproduced the reported bug. I'm going to mark this as Incomplete, pending a shorter test case and/or answers from Kern. If its too hard to test, and/or too hard to fix in lucid, it might just have to be a Won't Fix. OK. I am not sure what your procedure is -- it might be good to note fixed in 5.2.x providing that is really the case. Hm. Sounds like this one may not get backported. The procedure is to mark the main bug task Fix Released, but then track each release of the package before that individually. Won't Fix means the bug is in that version, but we're not going to fix it. OK, your procedures are different from ours, which is OK. We normally indicate to the user that it is fixed in a future version. That is all I was trying to say. No problem however you do it :-) * Changed in: bacula (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/735369 Title: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid Status in Bacula the Network Backup Solution: New Status in “bacula” package in Ubuntu: Confirmed Bug description: Binary package hint: bacula-console-qt On lucid, in the Version Browser of bat, it is impossible to check the latest version of a file. This is described in the following upstream bug report: http://bugs.bacula.org/view.php?id=1550 (login using anonymous/anonymous) For convenience, here is the verbatim of the bug description: -- I often restore a single file, so I use Version Browser. 1) I browse for the file and when clicking on it, I see many different versions of it. 2) When I try to mark the file (tick the checkbox), it cannot be done 3) When I try to mark the most recent version of the file in 'Versions of File', it cannot be done 4) When I try to mark any other version of the file, it works OK 5) When there's another version of the file available (after the next backup), the version which couldn't be marked, can now be marked and the most recent can not It seems to be so for every job and every file within a job. I turned on all the debugging options of Bat, but there's nothing said when marking (or trying to) files/versions. - Response from the lead developer of Bacula: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/735369 Title: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 735369] [NEW] Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid
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 reported, bat uses Qt, which has some important compatiblity problems between versions. Hopefully the new 5.2.0 bat will also work on Maveric. If not, I will be releasing a depkgs-qt-4.6.2 that can be used to compile bat on any Ubuntu release. Regards, Kern -- 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/735369 Title: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 735369] [NEW] Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid
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 reported, bat uses Qt, which has some important compatiblity problems between versions. Hopefully the new 5.2.0 bat will also work on Maveric. If not, I will be releasing a depkgs-qt-4.6.2 that can be used to compile bat on any Ubuntu release. Regards, Kern -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/735369 Title: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 590887] Re: btraceback utility doesn't work
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 bug report. This will greatly help us in tracking down your problem. ** Changed in: bacula (Ubuntu) Status: New = Incomplete This kind of problem ptrace: Operation not permitted. is common when you run some of your daemons as non-root. The core dump is produced as root because Bacula is started as root, but as user bacula gdb won't work. One solution is for obtaining a traceback, run bacula as root. This is most appropriate for a one-shot reproducible case. Another solution might be to put the appropriate command (e.g. sudo) in the btraceback script so that the debugger is able to do its job. Regards, Kern -- 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/590887 Title: btraceback utility doesn't work -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 590887] Re: btraceback utility doesn't work
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 bug report. This will greatly help us in tracking down your problem. ** Changed in: bacula (Ubuntu) Status: New = Incomplete By the way, I just wanted to mention that these kinds of problems are very clearly explained in the Kaboom chapter of the manual. -- 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/590887 Title: btraceback utility doesn't work -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 590887] Re: btraceback utility doesn't work
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 bug report. This will greatly help us in tracking down your problem. ** Changed in: bacula (Ubuntu) Status: New = Incomplete This kind of problem ptrace: Operation not permitted. is common when you run some of your daemons as non-root. The core dump is produced as root because Bacula is started as root, but as user bacula gdb won't work. One solution is for obtaining a traceback, run bacula as root. This is most appropriate for a one-shot reproducible case. Another solution might be to put the appropriate command (e.g. sudo) in the btraceback script so that the debugger is able to do its job. Regards, Kern -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/590887 Title: btraceback utility doesn't work -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 590887] Re: btraceback utility doesn't work
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 bug report. This will greatly help us in tracking down your problem. ** Changed in: bacula (Ubuntu) Status: New = Incomplete By the way, I just wanted to mention that these kinds of problems are very clearly explained in the Kaboom chapter of the manual. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/590887 Title: btraceback utility doesn't work -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 521698] Re: Fan runs too fast on Dell Studio 1747 with i7 chip
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 was so serious that I gave up, unplugged the computer, and stored it in my basement. I bought an HP Pavillion dv8, which is a *much* better computer. It was cheaper, has more features, and has no fan problem with a current Lucid (haven't tried other versions). I'll never buy another Dell. Kern -- Fan runs too fast on Dell Studio 1747 with i7 chip https://bugs.launchpad.net/bugs/521698 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 590894] Re: bacula-director crashes when nsswitch uses wins for hosts
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 unlikely, it is not a Bacula bug. It seems to me that someone has reported this some time ago, so I suspect it may not be a Ubuntu version bug. Unless someone can show me that Bacula is doing something wrong, I'm assuming at this point that it as an upstream OS or library bug. Kern -- bacula-director crashes when nsswitch uses wins for hosts https://bugs.launchpad.net/bugs/590894 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 590894] Re: bacula-director crashes when nsswitch uses wins for hosts
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 = Confirmed Thanks -- I have responded to bug report. Bottom line: we need a stack trace to determine where the problem is occurring, or some step by step instructions on how to reproduce it (I don't use WINS or even know how to turn it on). Kern -- bacula-director crashes when nsswitch uses wins for hosts https://bugs.launchpad.net/bugs/590894 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 590894] Re: bacula-director crashes when nsswitch uses wins for hosts
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 unlikely, it is not a Bacula bug. It seems to me that someone has reported this some time ago, so I suspect it may not be a Ubuntu version bug. Unless someone can show me that Bacula is doing something wrong, I'm assuming at this point that it as an upstream OS or library bug. Kern -- bacula-director crashes when nsswitch uses wins for hosts https://bugs.launchpad.net/bugs/590894 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 521698] Re: Fan runs too fast on Dell Studio 1747 with i7 chip
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 regression testing and a disk server. That way it can make all the noise it wants. I suppose I should re-install Windows on it, that is probably the ultimate solution. What a waste of money -- oh well. -- Fan runs too fast on Dell Studio 1747 with i7 chip https://bugs.launchpad.net/bugs/521698 You received this bug notification because you are a direct subscriber of the bug. Status in Ubuntu: New Bug description: 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 quiet and increases and decreases in speed according to the CPU load as I would expect. Apparently there are no temperature sensors and fan control for this CPU. Help would be appreciated. To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+bug/521698/+subscribe -- Fan runs too fast on Dell Studio 1747 with i7 chip https://bugs.launchpad.net/bugs/521698 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 579924] [NEW] Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10
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 upgrade from version 11 to version 12. All the scripts for an upgrade from the prior version to the version of the current release are found in bacula/src/cats ... All scripts for making an upgrade from an old version to a newer version (e.g. 8 to 9 or 10 to 11) are kept in bacula/updatedb. These scripts may need some manual editing to get the install locations to match where your database is installed. Kern On Thursday 13 May 2010 13:59:48 Tomasz wrote: Public bug reported: Binary package hint: bacula After upgrading Ubuntu from 8.04 LTS to 10.04 LTS backup software Bacula stopped working, starting bacula-director MySQL version results in: bacula-dir JobId 0: Fatal error: Version error for database bacula. Wanted 12, got 10 During upgrade Bacula was upgraded from 2.2 series (db version 10) to 5.0 (db version 12), dpkg.log shows. 2010-05-12 21:16:32 upgrade bacula-director-mysql 2.2.8-5ubuntu7.2 5.0.1-1ubuntu1 and /usr/share/bacula-director/update_mysql_tables upgrades only from db version 11: This script will update a Bacula MySQL database from version 11 to 12 which is needed to convert from Bacula Enterprise 2.6 to 4.0 or Standard version 3.0 to 5.0 I expected to have the database upgraded from version 10 to 12 when upgrading Ubuntu LTS series. ** Affects: bacula Importance: Undecided Status: New ** Affects: bacula (Ubuntu) Importance: Undecided Status: New ** Also affects: bacula Importance: Undecided Status: New -- Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10 https://bugs.launchpad.net/bugs/579924 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 579924] [NEW] Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10
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 upgrade from version 11 to version 12. All the scripts for an upgrade from the prior version to the version of the current release are found in bacula/src/cats ... All scripts for making an upgrade from an old version to a newer version (e.g. 8 to 9 or 10 to 11) are kept in bacula/updatedb. These scripts may need some manual editing to get the install locations to match where your database is installed. Kern On Thursday 13 May 2010 13:59:48 Tomasz wrote: Public bug reported: Binary package hint: bacula After upgrading Ubuntu from 8.04 LTS to 10.04 LTS backup software Bacula stopped working, starting bacula-director MySQL version results in: bacula-dir JobId 0: Fatal error: Version error for database bacula. Wanted 12, got 10 During upgrade Bacula was upgraded from 2.2 series (db version 10) to 5.0 (db version 12), dpkg.log shows. 2010-05-12 21:16:32 upgrade bacula-director-mysql 2.2.8-5ubuntu7.2 5.0.1-1ubuntu1 and /usr/share/bacula-director/update_mysql_tables upgrades only from db version 11: This script will update a Bacula MySQL database from version 11 to 12 which is needed to convert from Bacula Enterprise 2.6 to 4.0 or Standard version 3.0 to 5.0 I expected to have the database upgraded from version 10 to 12 when upgrading Ubuntu LTS series. ** Affects: bacula Importance: Undecided Status: New ** Affects: bacula (Ubuntu) Importance: Undecided Status: New ** Also affects: bacula Importance: Undecided Status: New -- Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10 https://bugs.launchpad.net/bugs/579924 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 459573] Re: variable expansion uses outdated data
** 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 459573] Re: variable expansion uses outdated data
** 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521698] Re: Fan runs too fast on Dell Studio 1747 with i7 chip
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 in the second comment, you say that everything is OK on both Linux and Window. If everything is OK on Linux, then please send me a dump of the sensors showing that the chip temperatures are sensed and the fan speed is being adjusted on Linux, and I would like to know what configuration, drivers, and kernel level make it work so I can get it working here. On my machine, there are no fan drivers and no sensors, and I have tried all the common things that are described on the web particularly the Ubuntu wiki for getting temperature sensors working. In that sense, we are not yet talking about a design problem where the CPU runs too hot, but a problem where my fan runs at a very high speed all the time (unless of course, the fan is controlled automatically, but that would not explain why Linux and Win7 have very different behaviors). -- Fan runs too fast on Dell Studio 1747 with i7 chip https://bugs.launchpad.net/bugs/521698 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521698] [NEW] Fan runs too fast on Dell Studio 1747 with i7 chip
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 quiet and increases and decreases in speed according to the CPU load as I would expect. Apparently there are no temperature sensors and fan control for this CPU. Help would be appreciated. ** Affects: ubuntu Importance: Undecided Status: New -- Fan runs too fast on Dell Studio 1747 with i7 chip https://bugs.launchpad.net/bugs/521698 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521703] [NEW] Cannot report kubuntu bug
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 put One button for searching bugs on Kubuntu, and One button for submitting a bug. That would simplify the process. ** Affects: ubuntu Importance: Undecided Status: New -- Cannot report kubuntu bug https://bugs.launchpad.net/bugs/521703 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521705] [NEW] Please do not package KPackageKit with Lucid
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 Adept listing with the search filter was very good). It uses big icons and displays none of the important info about the package, and I cannot find any way to select a package to load nor to see what is going to be installed or uninstalled. If you must include it, at least add a help button with a manual to the program. In summary, please supply some other package Adept, Synaptic, ... as a default with a menu item for a package manager. I can always use apt- get, but most times seeing the filtered package names in a gui is useful. ** Affects: ubuntu Importance: Undecided Status: New -- Please do not package KPackageKit with Lucid https://bugs.launchpad.net/bugs/521705 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521703] Re: Cannot report kubuntu bug
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 it at least two times before submitting this bug. The page is way to complicated with no clear link to the bug reporting web site. I am used to submitting bugs and run my own project, but I find no simple way to report a Kubuntu bug. It seems to me that it should be obvious, but either it isn't or I am loosing it ... -- Cannot report kubuntu bug https://bugs.launchpad.net/bugs/521703 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 463940] Re: No fans, thermalzone on HP Envy 15 and HP DV6T Quad
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, no sensors were detected Booting with acpi_enforce_resources=lax does not help. Is this the right place to ask for a solution? If so, what information do you need? (dmesg output, ...). If not, I can open a new bug. -- No fans, thermalzone on HP Envy 15 and HP DV6T Quad https://bugs.launchpad.net/bugs/463940 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 459573] Re: variable expansion uses outdated data
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 expansion never really worked out in Bacula. Some day, it will be removed once I find something better (probably plugins). Kern -- variable expansion uses outdated data https://bugs.launchpad.net/bugs/459573 You received this bug notification because you are subscribed to Bacula. Status in Bacula the Network Backup Solution: New Status in âbaculaâ package in Ubuntu: Invalid Bug description: Binary package hint: bacula I use $Client-$Year-$Month-$Day as my LabelFormat. Recently I tried to backup a server called ralph (this was a scheduled job). The Volume was created with the correct name but the job failed as the FileDaemon was not running, as below: 24-Oct 08:17 floyd-dir JobId 65: Created new Volume ralph-fd-2009-10-24 in catalog. 24-Oct 08:17 floyd-dir JobId 65: Using Device FileStorage 24-Oct 08:17 floyd-dir JobId 65: Warning: bsock.c:123 Could not connect to Client: ralph-fd on 192.168.1.254:9102. ERR=Connection refused The job eventually terminated itself. Subsequently I tried to run a job manually to backup a different server (benson) and got the following output: 24-Oct 13:43 floyd-dir JobId 66: No prior Full backup Job record found. 24-Oct 13:43 floyd-dir JobId 66: No prior or suitable Full backup found in catalog. Doing FULL backup. 24-Oct 13:43 floyd-dir JobId 66: Start Backup JobId 66, Job=benson.2009-10-24_13.43.03 24-Oct 13:43 floyd-dir JobId 66: Using Device FileStorage 24-Oct 13:43 floyd-sd JobId 66: Labeled new Volume ralph-fd-2009-10-24 on device FileStorage (/bacula-volumes). 24-Oct 13:43 floyd-sd JobId 66: Wrote label to prelabeled Volume ralph-fd-2009-10-24 on device FileStorage (/bacula-volumes) 24-Oct 13:43 floyd-dir JobId 66: Volume used once. Marking Volume ralph-fd-2009-10-24 as Used. Note that the Volume name is again ralph-fd-2009-10-24. It should have been benson-fd-2009-10-24. It looks like the variable expansion has retained the client name ralph-fd from the failed job. Either that or bacula is not trying to create a new volume at all, but instead reusing the volume created previously but not labelled or written to. r...@floyd:~# lsb_release -rd Description: Ubuntu 8.04.3 LTS Release: 8.04 r...@floyd:~# apt-cache policy bacula bacula: Installed: (none) Candidate: 2.2.8-5ubuntu7.2 Version table: 2.2.8-5ubuntu7.2 0 500 http://mirror.internode.on.net hardy-updates/main Packages 2.2.8-5ubuntu7 0 500 http://mirror.internode.on.net hardy/main Packages Best regards, Kern -- 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 459573] Re: variable expansion uses outdated data
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 expansion never really worked out in Bacula. Some day, it will be removed once I find something better (probably plugins). Kern -- variable expansion uses outdated data https://bugs.launchpad.net/bugs/459573 You received this bug notification because you are subscribed to Bacula. Status in Bacula the Network Backup Solution: New Status in âbaculaâ package in Ubuntu: Invalid Bug description: Binary package hint: bacula I use $Client-$Year-$Month-$Day as my LabelFormat. Recently I tried to backup a server called ralph (this was a scheduled job). The Volume was created with the correct name but the job failed as the FileDaemon was not running, as below: 24-Oct 08:17 floyd-dir JobId 65: Created new Volume ralph-fd-2009-10-24 in catalog. 24-Oct 08:17 floyd-dir JobId 65: Using Device FileStorage 24-Oct 08:17 floyd-dir JobId 65: Warning: bsock.c:123 Could not connect to Client: ralph-fd on 192.168.1.254:9102. ERR=Connection refused The job eventually terminated itself. Subsequently I tried to run a job manually to backup a different server (benson) and got the following output: 24-Oct 13:43 floyd-dir JobId 66: No prior Full backup Job record found. 24-Oct 13:43 floyd-dir JobId 66: No prior or suitable Full backup found in catalog. Doing FULL backup. 24-Oct 13:43 floyd-dir JobId 66: Start Backup JobId 66, Job=benson.2009-10-24_13.43.03 24-Oct 13:43 floyd-dir JobId 66: Using Device FileStorage 24-Oct 13:43 floyd-sd JobId 66: Labeled new Volume ralph-fd-2009-10-24 on device FileStorage (/bacula-volumes). 24-Oct 13:43 floyd-sd JobId 66: Wrote label to prelabeled Volume ralph-fd-2009-10-24 on device FileStorage (/bacula-volumes) 24-Oct 13:43 floyd-dir JobId 66: Volume used once. Marking Volume ralph-fd-2009-10-24 as Used. Note that the Volume name is again ralph-fd-2009-10-24. It should have been benson-fd-2009-10-24. It looks like the variable expansion has retained the client name ralph-fd from the failed job. Either that or bacula is not trying to create a new volume at all, but instead reusing the volume created previously but not labelled or written to. r...@floyd:~# lsb_release -rd Description: Ubuntu 8.04.3 LTS Release: 8.04 r...@floyd:~# apt-cache policy bacula bacula: Installed: (none) Candidate: 2.2.8-5ubuntu7.2 Version table: 2.2.8-5ubuntu7.2 0 500 http://mirror.internode.on.net hardy-updates/main Packages 2.2.8-5ubuntu7 0 500 http://mirror.internode.on.net hardy/main Packages Best regards, Kern -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 459573] Re: variable expansion uses outdated data
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 reasonable way is to work with Pools and either prelabel your Volumes, or use some labeling scheme such as you did. If you do not use Pools, there is no way to absolutely guarantee that Bacula will write on a Volume you have just created. With Pools, at least you can guarantee that it will write on a Volume within a given Pool. There is a whole chapter in the manual describing this for Full, Differential, and Incremental backups, which can be easily extrapolated to Clients. So, in my opinion, it isn't so much a question of a feature being worse than useless, but rather learning which features will accomplish what you want. On Monday 02 November 2009 04:38:38 Aidan Furlan wrote: I would certainly consider this a bug. It makes variable expansion worse than useless because I can no longer trust it to label volumes with the correct client or date, so that all the volume names are potentially misleading. To avoid misleading data I have gone back to using LabelFormat=Vol. -- 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 459573] Re: variable expansion uses outdated data
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 reasonable way is to work with Pools and either prelabel your Volumes, or use some labeling scheme such as you did. If you do not use Pools, there is no way to absolutely guarantee that Bacula will write on a Volume you have just created. With Pools, at least you can guarantee that it will write on a Volume within a given Pool. There is a whole chapter in the manual describing this for Full, Differential, and Incremental backups, which can be easily extrapolated to Clients. So, in my opinion, it isn't so much a question of a feature being worse than useless, but rather learning which features will accomplish what you want. On Monday 02 November 2009 04:38:38 Aidan Furlan wrote: I would certainly consider this a bug. It makes variable expansion worse than useless because I can no longer trust it to label volumes with the correct client or date, so that all the volume names are potentially misleading. To avoid misleading data I have gone back to using LabelFormat=Vol. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 387778] Re: Incorrect application entry for bacula-console-qt
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 quite certain how to fix this myself, but I believe you can investigate the problem further by using 'apt-get source bacula' and then looking at 'scripts/bat.desktop.in' in the package. A few responses: First some gripes about this bug tracking system: 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 or something like that to the Subject line as all other bug systems do. 2. Bug reports should never be directly addressed to people receiving them in a copy form -- as is the case for me. It is very confusing. This emails was addressed to me as: From: Brian Murray br...@ubuntu.com To: k...@sibbald.com Date: Today 20:17:49 which is incorrect since the bug report is copied to me. 3. I would like to unsubscribe from this list, but it seems to be next to impossible. Would you please tell me how? Thanks. = Now to answer the bug report. 4. The problem appears to be that the packaging of Bacula was incorrectly done. Bacula should be configured and built prior to packaging, and the configuration *must* correspond to the exact same places the packager is going to install files. Otherwise you introduce packing bugs as you have here. More specifically. It appears that the packager configured and built Bacula to install in /usr/sbin/bat (or at least that is where Bat was set to be installed), and then during the installation of the Bacula package, bat (the executable) was put into /usr/bin/bat. Thus the desktop files are not in synchronization with where the binary was installed. Regards, Kern Upstream Bacula Project Manager -- Incorrect application entry for bacula-console-qt https://bugs.launchpad.net/bugs/387778 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 387778] Re: Incorrect application entry for bacula-console-qt
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 or something like that to the Subject line as all other bug systems do. Sorry for the noise, as a public Ubuntu bug reporter I was not aware that Launchpad would spam people upstream before someone at Ubuntu had triaged the bug. Sorry I should have been more specific. No need for you to be sorry as a reporter of a problem (at least that is what I imagine). It has something to do with the lauchpad system that I haven't yet figured out. 2. Bug reports should never be directly addressed to people receiving them in a copy form -- as is the case for me. It is very confusing. Indeed - I was just as confused when your Launchpad reply first appeared to be a private e-mail reply. 4. The problem appears to be that the packaging of Bacula was incorrectly done. Bacula should be configured and built prior to packaging, and the configuration *must* correspond to the exact same places the packager is going to install files. Otherwise you introduce packing bugs as you have here. Thanks for your clarification. Obviously the Ubuntu (or Debian) package maintainer needs to fix this. Yes, someone should figure out some way to test these things, but with GUIs it is not so easy :-( I hope you succeed in unsubscribing from the Launchpad notifications Thanks. and once again my apologies for generating noise. For the apologies, thanks, no harm done, but as I said, it is not your fault. Regards, Kern -- Incorrect application entry for bacula-console-qt https://bugs.launchpad.net/bugs/387778 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 387778] Re: Incorrect application entry for bacula-console-qt
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 quite certain how to fix this myself, but I believe you can investigate the problem further by using 'apt-get source bacula' and then looking at 'scripts/bat.desktop.in' in the package. A few responses: First some gripes about this bug tracking system: 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 or something like that to the Subject line as all other bug systems do. 2. Bug reports should never be directly addressed to people receiving them in a copy form -- as is the case for me. It is very confusing. This emails was addressed to me as: From: Brian Murray br...@ubuntu.com To: k...@sibbald.com Date: Today 20:17:49 which is incorrect since the bug report is copied to me. 3. I would like to unsubscribe from this list, but it seems to be next to impossible. Would you please tell me how? Thanks. = Now to answer the bug report. 4. The problem appears to be that the packaging of Bacula was incorrectly done. Bacula should be configured and built prior to packaging, and the configuration *must* correspond to the exact same places the packager is going to install files. Otherwise you introduce packing bugs as you have here. More specifically. It appears that the packager configured and built Bacula to install in /usr/sbin/bat (or at least that is where Bat was set to be installed), and then during the installation of the Bacula package, bat (the executable) was put into /usr/bin/bat. Thus the desktop files are not in synchronization with where the binary was installed. Regards, Kern Upstream Bacula Project Manager -- Incorrect application entry for bacula-console-qt https://bugs.launchpad.net/bugs/387778 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 387778] Re: Incorrect application entry for bacula-console-qt
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 or something like that to the Subject line as all other bug systems do. Sorry for the noise, as a public Ubuntu bug reporter I was not aware that Launchpad would spam people upstream before someone at Ubuntu had triaged the bug. Sorry I should have been more specific. No need for you to be sorry as a reporter of a problem (at least that is what I imagine). It has something to do with the lauchpad system that I haven't yet figured out. 2. Bug reports should never be directly addressed to people receiving them in a copy form -- as is the case for me. It is very confusing. Indeed - I was just as confused when your Launchpad reply first appeared to be a private e-mail reply. 4. The problem appears to be that the packaging of Bacula was incorrectly done. Bacula should be configured and built prior to packaging, and the configuration *must* correspond to the exact same places the packager is going to install files. Otherwise you introduce packing bugs as you have here. Thanks for your clarification. Obviously the Ubuntu (or Debian) package maintainer needs to fix this. Yes, someone should figure out some way to test these things, but with GUIs it is not so easy :-( I hope you succeed in unsubscribing from the Launchpad notifications Thanks. and once again my apologies for generating noise. For the apologies, thanks, no harm done, but as I said, it is not your fault. Regards, Kern -- Incorrect application entry for bacula-console-qt https://bugs.launchpad.net/bugs/387778 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 372328] Re: Bacula has no encryption support in bacula-sd-sqlite3
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 new version of aptitude does not have 'Super Cow Powers'!) apt-get build-dep bacula apt-get install libssl-dev openssl apt-get source bacula cd bacula-2 vim debian/rules # (change the options to enable ssl tls) debian/rules binary #it should now compile and pack all bacula packages However after doing this and installing appropriate .debs the daemons die with buffer overflows when started. I am assuming this due to newer compiler/libs being used - the original package in the Jaunty distro was compiled on 18th March. http://launchpadlibrarian.net/24056236/buildlog_ubuntu-jaunty- amd64.bacula_2.4.4-1ubuntu5_FULLYBUILT.txt.gz Anyone had any luck rebuilding using a current build environment? Possible solution: make sure you are not compiling with _FORTIFY_SOURCE set to a non-zero value or simply put #undef _FORTIFY_SOURCE somewhere near the top of the bacula-source/src/bacula.h file. Rebuild all files ... Kern -- Bacula has no encryption support in bacula-sd-sqlite3 https://bugs.launchpad.net/bugs/372328 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 290775] Re: The nvidia module does not load on kernel 2.6.24-21
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 obviously something going wrong with the installation of these drivers, but in my opinion you can close this until we get a better idea of what is going wrong. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 290775] [NEW] The nvidia module does not load on kernel 2.6.24-21
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 bpp 32 (==) NVIDIA(0): RGB weight 888 (==) NVIDIA(0): Default visual is TrueColor (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) (**) NVIDIA(0): Option NoLogo True (**) NVIDIA(0): Option AddARGBGLXVisuals True (**) NVIDIA(0): Enabling RENDER acceleration (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is (II) NVIDIA(0): enabled. (EE) NVIDIA(0): Failed to load the NVIDIA kernel module! (EE) NVIDIA(0): *** Aborting *** (II) UnloadModule: nvidia (II) UnloadModule: wfb (II) UnloadModule: fb (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found This driver worked fine under all previous kernels. I have also re-installed nvidia-glx-new nvidia-kernel-common and the -21 kernel -- no go. Full log attached ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 290775] Re: The nvidia module does not load on kernel 2.6.24-21
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 286643] Re: bacula client configuration is broken out of the box
On Tuesday 21 October 2008 18:36:11 Mathias Gug wrote: Hi Scott, Thanks for taking the time to get in touch with the Ubuntu Development team. We understand that bacula is planning to send a couple of developers to Fosscamp, and think that might be an appropriate forum to collaborate on a final solution. I'll attend Fooscamp and I'm ready to discuss this issue with them. Is is this an acceptable solution for you? I won't speak for Scott for the above question, but I will be attending FossCamp, and would be more than happy to provide 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 are a member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 286643] Re: bacula client configuration is broken out of the box
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 in favor of having bacula file daemon listening only on localhost, as it is now. Why? Here is why... Bacula will never work out of box, cause of lots of configuration options that should be changed after installation. Changing listening IP address is just a tip of an iceberg. The standard Bacula rpms do work out of the box, as does the SQLite make install. Since .debs are better (I am not at all being sarcastic here), why cannot they do the same thing, or at least attempt to approach it? On the other hand, people that don't have any clue about bacula, and are just testing the software, are in danger. I would advise not changing default at least until we solve bug #222558 - each bacula client and daemon have the same password. This is cause password is generated on compile time. IMHO, talking about this and working on this issue should be post-intrepid. A couple of points here: Following your logic on the localhost problem, we arrive at the following: If you want to make daemons secure and hobble them to localhost then please do it uniformly to DNS, Apache, SSH, and the other daemons that can be used internally without connection to the Internet, because I may not have a clue about how they work and just want to test them. (A bit simplistic, but you probably get the idea). Concerning the random password problem: The rpms created by Bacula have had random passwords installed for many years now. It is really quite easy to fix. I mentioned this problem in the .debs and the solution to the Debian maintainer quite a long time ago (probably years). I have also sent the .deb scripts that we (Bacula) use internally to the Ubuntu Bacula packaging crew. Our .deb packages when installed produce random passwords. I'll leave it to you if/when to change anything. Kern 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 to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 286643] Re: bacula client configuration is broken out of the box
On Tuesday 21 October 2008 18:36:11 Mathias Gug wrote: Hi Scott, Thanks for taking the time to get in touch with the Ubuntu Development team. We understand that bacula is planning to send a couple of developers to Fosscamp, and think that might be an appropriate forum to collaborate on a final solution. I'll attend Fooscamp and I'm ready to discuss this issue with them. Is is this an acceptable solution for you? I won't speak for Scott for the above question, but I will be attending FossCamp, and would be more than happy to provide 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 227613] Re: [SRU] SIGSEGV in bacula-fd
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 didn't take offense, hope you didn't, but just wanted to clarify. The bug *was* fixed in the 2.2.8 version with two patches. Did you apply them? We have 2.2.8 version in Ubuntu 8.04, and this bug is filed for 2.2.8. I think it was fixed later in bacula, not in 2.2.8... The bug in the main Bacula 2.2.8 Branch HEAD is fixed because the code is identical to the current 2.4.2 code. That is if 2.2.8 is fully and correctly patched with the released patches, it should have this bug and others fixed. It is possible that there were confusions with the patches in getting from the first 2.2.8 to the version that is in the SVN. In any case, what is clear to me is that we have no problems in the 2.4.x base with this bug and that the 2.4.0 was pulled from the last 2.2.8 and that no additional strippath changes were made in the 2.4.x versions. 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 from the current released code (Branch-2.4) rather than trying to apply the patches. I guess you are referring to src/filed/backup.c? If yes, that file is exactly the same in my PPA version and in 2.4.2. Yes, sorry. I should have said src/filed/backup.c src/dird/backup.c has more differences, but I don't think those are relevant for this bug. Yes, you are correct. We'll wait for Sergio to test my PPA version. OK, if you have a 2.2.8 src/filed/backup.c that is the same as on 2.4.2, then the bug *should* be fixed. If not, I will be worried ... By the way, what does PPA mean and where does one find those versions? Thanks ... -- [SRU] SIGSEGV in bacula-fd https://bugs.launchpad.net/bugs/227613 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 227613] Re: [SRU] SIGSEGV in bacula-fd
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 didn't take offense, hope you didn't, but just wanted to clarify. The bug *was* fixed in the 2.2.8 version with two patches. Did you apply them? We have 2.2.8 version in Ubuntu 8.04, and this bug is filed for 2.2.8. I think it was fixed later in bacula, not in 2.2.8... The bug in the main Bacula 2.2.8 Branch HEAD is fixed because the code is identical to the current 2.4.2 code. That is if 2.2.8 is fully and correctly patched with the released patches, it should have this bug and others fixed. It is possible that there were confusions with the patches in getting from the first 2.2.8 to the version that is in the SVN. In any case, what is clear to me is that we have no problems in the 2.4.x base with this bug and that the 2.4.0 was pulled from the last 2.2.8 and that no additional strippath changes were made in the 2.4.x versions. 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 from the current released code (Branch-2.4) rather than trying to apply the patches. I guess you are referring to src/filed/backup.c? If yes, that file is exactly the same in my PPA version and in 2.4.2. Yes, sorry. I should have said src/filed/backup.c src/dird/backup.c has more differences, but I don't think those are relevant for this bug. Yes, you are correct. We'll wait for Sergio to test my PPA version. OK, if you have a 2.2.8 src/filed/backup.c that is the same as on 2.4.2, then the bug *should* be fixed. If not, I will be worried ... By the way, what does PPA mean and where does one find those versions? Thanks ... -- [SRU] SIGSEGV in bacula-fd https://bugs.launchpad.net/bugs/227613 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 227613] Re: [SRU] SIGSEGV in bacula-fd
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 is fixed because the code is identical to the current 2.4.2 code. That is if 2.2.8 is fully and correctly patched with the released patches, it should have this bug and others fixed. It is possible that there were confusions with the patches in getting from the first 2.2.8 to the version that is in the SVN. Oh! Mea culpa... I didn't know 2.2.8 is still getting patches. I'm checking out source as I write this... OK. Just to be clear, you can get it from the branches Branch-2.2 svn checkout https://bacula.svn.sf.net/svnroot/bacula/branches/Branch-2.2 ... You might want to subscribe to the Source Forge Bacula bacula-patches notification. That way, you will see when I post any new patch. In general, once I post a patch, it means it has been reasonably well tested and usually verified by the bug submittor (or myself if I found the bug). Occassionally, and very unusual, as was the case in the original strippath bug report, I cannot reproduce the problem and the reporter does not respond to requests to confirm the patch, and the patch may not be totally correct, which is why we had at least two patches for that bug. In any case, if you get a bug report, it always best to check if any patches on it have been released ... OK, if you have a 2.2.8 src/filed/backup.c that is the same as on 2.4.2, then the bug *should* be fixed. If not, I will be worried ... I've seen your comments on bug in bacula buglist, but we really need Sergio to confirm this. Thank you for the info! Thanks for the description of PPA, pretty cool. -- [SRU] SIGSEGV in bacula-fd https://bugs.launchpad.net/bugs/227613 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 227613] Re: [SRU] SIGSEGV in bacula-fd
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 from the current released code (Branch-2.4) rather than trying to apply the patches. If you diff src/dird/backup.c from what you are currently shipping in 2.2.8 to the current 2.4 release and there are differences, it is pretty sure they are the fixes to the strippath problem as I don't remember making any other fix there. -- [SRU] SIGSEGV in bacula-fd https://bugs.launchpad.net/bugs/227613 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 241480] Re: bacula-fd does not start when installed via bacula-client
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 start. Since it takes some time to register an IP with a hostname, it is possible that bacula-fd is started before that registration happens. This results in unresolvable hostname and thuss failure to start. I suggest using 'localhost' if you desire to have '127.0.0.1'. If there is an non-local interface (eth0, eth1, wlan0, ...), d420.local will be a record for non-local IP. This bug is valid, but at the moment is unresolvable. Ubuntu has plans on replacing SysV init system with upstart, which could solve this issue. I'm closing this bug. If you feel that's wrong, please reopen it. ** Changed in: bacula (Ubuntu) Status: Triaged = Won't Fix 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. We have never run into this problem elsewhere, so I cannot understand why it is unresolvable. -- bacula-fd does not start when installed via bacula-client https://bugs.launchpad.net/bugs/241480 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 222558] Re: password in bacula-fd.conf is not auto-generated
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 compile-time. ** Changed in: bacula (Ubuntu) Importance: Undecided = Medium Status: New = Confirmed I am not (yet) a Debian packaging expert, so I asked the Bacula .deb guy (Eric), and this is his response. Sorry for emailer wrapping, but you can probably figure it out. On Wednesday 24 September 2008 16:18:58 you wrote: Hello Eric, Do you have some .deb magic I could send off to the Ubuntu Bacula maintainers so that they can generate random passwords when installing Bacula? I use the bacula-common configuration script (debian/bacula-common.config) to compute and store random password for all bacula packages. (my template file is ok too) if ! db_get bacula/director_passwd; then db_set bacula/director_passwd $(cat /dev/urandom | tr -dc _A-Z-a-z-0-9 | head -c33) db_set bacula/director_mpasswd $(cat /dev/urandom | tr -dc _A-Z-a-z-0-9 | head -c33) db_set bacula/fd_passwd $(cat /dev/urandom | tr -dc _A-Z-a-z-0-9 | head -c33) db_set bacula/fd_mpasswd $(cat /dev/urandom | tr -dc _A-Z-a-z-0-9 | head -c33) db_set bacula/sd_passwd $(cat /dev/urandom | tr -dc _A-Z-a-z-0-9 | head -c33) db_set bacula/sd_mpasswd $(cat /dev/urandom | tr -dc _A-Z-a-z-0-9 | head -c33) fi After that, i use special strings to replace password in configuration file (like for RPM) ./configure ... --with-dir-password=XXX_REPLACE_WITH_DIRECTOR_PASSWORD_XXX \ --with-fd-password=XXX_REPLACE_WITH_CLIENT_PASSWORD_XXX \ --with-sd-password=XXX_REPLACE_WITH_STORAGE_PASSWORD_XXX \ --with-mon-dir-password=XXX_REPLACE_WITH_DIRECTOR_MONITOR_PASSWORD_XXX \ --with-mon-fd-password=XXX_REPLACE_WITH_CLIENT_MONITOR_PASSWORD_XXX \ --with-mon-sd-password=XXX_REPLACE_WITH_STORAGE_MONITOR_PASSWORD_XXX \ At the end, i just have to replace XXX_...XXX strings by what we have computed in each package.postinst script. db_get bacula/director_mpasswd db_dir_mpass=$RET db_get bacula/fd_mpasswd db_fd_mpass=$RET db_get bacula/sd_mpasswd db_sd_mpass=$RET db_stop sed \ -e s%XXX_REPLACE_WITH_DIRECTOR_MONITOR_PASSWORD_XXX%$db_dir_mpass% \ -e s%XXX_REPLACE_WITH_STORAGE_MONITOR_PASSWORD_XXX%$db_sd_mpass% \ -e s%XXX_REPLACE_WITH_CLIENT_MONITOR_PASSWORD_XXX%$db_fd_mpass% \ $SRCDIR/$CONFIG $TARGET At the end, if you configure FD/SD/DIR/Console on the same box, all your passwords will be ok. They have also to remove the XXAddress = 127.0.0.1 from all configuration file. -- password in bacula-fd.conf is not auto-generated https://bugs.launchpad.net/bugs/222558 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 241480] Re: bacula-fd does not start when installed via bacula-client
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. We have never run into this problem elsewhere, so I cannot understand why it is unresolvable. Avahi is an implementation of the DNS Service Discovery and Multicast DNS specifications for Zeroconf Networking. It uses 'special' '.local' domain. Problem is that network is up, but the user is using 'hostname.local' FQDN. This FQDN isn't managed by DNS, so it isn't resolvable. This domain is managed by interaction between all computers, which over Zeroconf talk to each other and arrange their FQDN inside '.local' domain. This can take a minute or two. This is why Bacula is started before the FQDN is resolvable. We could resolve this problem if we would stall booting of all services untill avahi registers server, but this isn't a nice solution :/. Upstart enables state driven booting, so all services would boot up, except those that depend on avahi. Those will wait until upstart declares that mDNS is up. http://en.wikipedia.org/wiki/Zeroconf OK, thanks for the explanation. I was unaware of the Zeroconf problems, and agree that stalling all services at boot time is not a good solution. I am going to note this because I imagine it will come up in other distros ... -- bacula-fd does not start when installed via bacula-client https://bugs.launchpad.net/bugs/241480 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
