[Bug 1559517] [NEW] MySQL Server 5.6 fails to install on Wily (configuration fails)
Public bug reported: I have Ubuntu 15.10 (wily) and am trying to update MySQL to the latest version. When I run aptitude safe-upgrade, it fails like so: Errors were encountered while processing: mysql-server-5.6 mysql-server E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: Setting up mysql-server-5.6 (5.6.28-0ubuntu0.15.10.1) ... * Stopping MySQL database server mysqld [ OK ] * Starting MySQL database server mysqld [ OK ] invoke-rc.d: initscript mysql, action "start" failed. dpkg: error processing package mysql-server-5.6 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of mysql-server: mysql-server depends on mysql-server-5.6; however: Package mysql-server-5.6 is not configured yet. dpkg: error processing package mysql-server (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: mysql-server-5.6 mysql-server == Similarly, installing manually fails: # apt-get install mysql-server-5.6 Reading package lists... Done Building dependency tree Reading state information... Done mysql-server-5.6 is already the newest version. mysql-server-5.6 set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y Setting up mysql-server-5.6 (5.6.28-0ubuntu0.15.10.1) ... * Stopping MySQL database server mysqld [ OK ] * Starting MySQL database server mysqld [ OK ] invoke-rc.d: initscript mysql, action "start" failed. dpkg: error processing package mysql-server-5.6 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of mysql-server: mysql-server depends on mysql-server-5.6; however: Package mysql-server-5.6 is not configured yet. dpkg: error processing package mysql-server (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: mysql-server-5.6 mysql-server == dpkg -l shows: rc mysql-server-5.55.5.46-0ubuntu0.14.04.2 amd64 MySQL database server binaries and system database setup iF mysql-server-5.65.6.28-0ubuntu0.15.10.1 amd64 MySQL database server binaries and system database setup == Here's the MySQL error log: 160318 00:22:20 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 2016-03-18 00:22:20 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2016-03-18 00:22:20 0 [Note] /usr/sbin/mysqld (mysqld 5.6.28-0ubuntu0.15.10.1) starting as process 4383 ... 2016-03-18 00:22:20 4383 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000) 2016-03-18 00:22:20 4383 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000) 2016-03-18 00:22:20 4383 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 2016-03-18 00:22:20 4383 [Note] Plugin 'FEDERATED' is disabled. 2016-03-18 00:22:20 4383 [ERROR] Function 'innodb' already exists 2016-03-18 00:22:20 4383 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'. 2016-03-18 00:22:20 4383 [ERROR] Function 'federated' already exists 2016-03-18 00:22:20 4383 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'. 2016-03-18 00:22:20 4383 [ERROR] Function 'blackhole' already exists 2016-03-18 00:22:20 4383 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'. 2016-03-18 00:22:20 4383 [ERROR] Function 'archive' already exists 2016-03-18 00:22:20 4383
[Bug 1553757] Re: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or directory
Hi Andres, On 10-03-16 16:57, Paul Gevers wrote: >> however, I wonder if dbconfig-common should do >> something to not to write a new config ? > > As dbconfig-common leaves this to ucf, I think than it should be done > there. Or do you have something else in mind? It seems that there IS a bug in ucf when the source file is not present. At least the patch in Debian bug 817982¹ suggests as much. Paul ¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817982 ** Bug watch added: Debian Bug tracker #817982 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817982 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1553757 Title: dbconfig-common: writing config to /etc/dbconfig-common/maas-region- controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region- controller.conf': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+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 1556462] [NEW] package samba 2:4.1.17+dfsg-4ubuntu3.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: Regular Software Updater update failed - I am re-installing the software to hopefully correct the problem. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: samba 2:4.1.17+dfsg-4ubuntu3.3 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Mon Mar 7 18:47:11 2016 DuplicateSignature: package:samba:2:4.1.17+dfsg-4ubuntu3.3:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2012-11-18 (1209 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) RelatedPackageVersions: nautilus 1:3.14.2-0ubuntu13 gvfs 1.24.2-0ubuntu4 SambaClientRegression: Yes SourcePackage: samba Title: package samba 2:4.1.17+dfsg-4ubuntu3.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1556462 Title: package samba 2:4.1.17+dfsg-4ubuntu3.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1556462/+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 1553757] Re: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or director
Hi Andres, On 10-03-16 02:47, Andres Rodriguez wrote: > So this confirms that because of the postrm bug, we would see the install > issues. Good that we nailed it down. > however, I wonder if dbconfig-common should do > something to not to write a new config ? As dbconfig-common leaves this to ucf, I think than it should be done there. Or do you have something else in mind? Paul -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1553757 Title: dbconfig-common: writing config to /etc/dbconfig-common/maas-region- controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region- controller.conf': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+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 1553757] Re: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or director
Hi Andres, On 08-03-16 04:41, Andres Rodriguez wrote: > Sorry for the delay and thanks for looking into it. Good catch on the > postrm. At least I know that's my fault. That being said, I wonder if > unregistering the file actually explains why it doesn't get re-created. Hmm, I was a bit to certain in my phrasing. I should have said: it COULD be caused by the admin and the way maas handles purging. By no means did I mean that it is certain here. > The > funny thing here is that this is the first time it actually does something > similar (not creating the file), and the packaging hasn;'t really change in > that area. Neither has dbconfig-common. > I'm gonna try to reproduce what you suggest with touching the file and see > whether things get resolved with the fix to postrm.. Good. By the way, I tried removing the configuration file while working with one of my example packages (included in the source of dbconfig-common) and the behavior of ucf is as expected. Unfortunately, on my Debian system I can't easily check installing maas with apt-get, as that is not available in Debian. Paul -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1553757 Title: dbconfig-common: writing config to /etc/dbconfig-common/maas-region- controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region- controller.conf': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+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 1553757] Re: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or director
Hi Andres, On 08-03-16 04:38, Andres Rodriguez wrote: > So the reason we did this is because we wanted MAAS to be installed and we > didn't want any question to be asked, so we decided to do the preseeding. I recommend that you try to use dbc_prio_high=medium instead of your current code. By default only questions with prio=high are asked, so I think that the default behavior will be that dbconfig-common is run as you desire, without removing the possibility by the admin to configure otherwise. Also the default "remote-host" is localhost. You would also need way less code to "work around" dbconfig-common "limitations". > The registration piece is something that I found in another package, but > allowed MAAS to register the preseed options, otherwise this would have > failed! My point is that is looks like you are registering the wrong question for your template, aren't you? Or am I mistaken here/ Paul -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1553757 Title: dbconfig-common: writing config to /etc/dbconfig-common/maas-region- controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region- controller.conf': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+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 1553757] Re: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or director
Andres, This (in maas-region-controller.postrm) prevents dbconfig-common from unregistring the file with ucf (so the fact that you see the ucf prompt after purging and installing is at least caused by maas itself): if [ -f /etc/dbconfig-common/maas.conf ]; then if [ -f /usr/share/dbconfig-common/dpkg/postrm ]; then . /usr/share/dbconfig-common/dpkg/postrm.pgsql dbc_go maas-region-controller $@ fi fi Paul -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1553757 Title: dbconfig-common: writing config to /etc/dbconfig-common/maas-region- controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region- controller.conf': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+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 1553757] Re: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or director
Hi Andres,
Maybe unrelated and I may not understand your intentions, but I see the
following in your maas-region-controller.config:
set_question() {
if ! db_fget "$1" seen; then
db_register dbconfig-common/dbconfig-install "$1"
db_subst "$1" ID "$1"
db_fget "$1" seen
fi
Which gets called by:
set_question maas-region-controller/dbconfig-install true
set_question maas-region-controller/pgsql/app-pass ""
set_question maas-region-controller/remote/host "localhost"
But isn't the question from the second set, the $1 in the first
function? So shouldn't that "db_register" line also register the other
questions and use the value provided as argument?
Paul
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/1553757
Title:
dbconfig-common: writing config to /etc/dbconfig-common/maas-region-
controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-
controller.conf': No such file or directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+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 1553757] Re: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or directory
Hi Andres, On 07-03-16 06:07, Andres Rodriguez wrote: > Sorry for not being clear enough. NP, as long as you follow up on questions that is ok. > The actual issue/concern I have is: > > stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No > such file or directory Ack. I have a belly feeling that this may be related to the implementation in ucf of Debian wish list bug 812321¹. Can you try once again after you "touch /etc/dbconfig-common/maas-region-controller.conf". > Now, the way I'm reproducing this issue right now is an install. I have > remove/purged all the packages, include dbconfig common packages and > made sure that /etc/dbconfig-common doesn't exist : This looks like dbconfig-common isn't cleaning up properly on purge and keeps the file registered with ucf. Weird, I'll try to investigate, but I do purging a lot with all kind of example packages in my test suite² and have never seen this before. > The installation resumes, and It asks me the question to: http://pastebin.ubuntu.com/15319155/ Right. As expected, these are questions from ucf. So it may be that the issue lies there. > Right after answering the questions (no matter if I say install the > package maintainer's version or keep the local version currently > installed) , it is always the same result: > > Setting up maas-region-controller (2.0.0~alpha1+bzr4736-0ubuntu1~xenial2) ... > dbconfig-common: writing config to > /etc/dbconfig-common/maas-region-controller.conf > stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such > file or directory That at least is a bug in ucf. When you answer to use the package maintainers version, it must create the file as requested. So I guess we could at least file an additional bug against ucf. But let's wait until we find out if there isn't just one issue here. > As you can see, the file doesn't get created. Now, what I'm really > wondering if is there is only an issue in systems where dbconfig-common > was first upgraded to the latest version (2.0.3), and not on a freshly > installed system where dbconfig-common is latest, as I've not been able > to reproduce this on a freshly installed system yet. As said, I suspect this may be because the file is still registered with ucf. During install (after purge or on a clean system) ucf should not need to ask the question. It only should do that when there once was already a file (either still is or ucf knows that the admin has deleted the file). > Now, to answer your last question, the question raised by UCF was never there > because we preseed the following: > > set_question maas-region-controller/dbconfig-install true Doesn't look related. But how ugly is this, anyways. This means that you are preventing an admin from defering the setup to later, e.g. because she doesn't have the admin rights on the database he wants to use. By the way, you do know that when an admin installs dbconfig-no-thanks, dbconfig-common will not run, irrespective of your preseeding. > Or maybe, the preseeding doesn't really matter and we just have never > gotten into a similar situation, hence it never really has been shown > before. As said, this may be related to an updated ucf. I'll try to reproduce. Paul ¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812321 ² https://ci.debian.net/packages/d/dbconfig-common/unstable/amd64/ (test log; test case install-examples) ** Bug watch added: Debian Bug tracker #812321 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812321 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1553757 Title: dbconfig-common: writing config to /etc/dbconfig-common/maas-region- controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region- controller.conf': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+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 1553757] [NEW] dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or direct
Hi Andres, On 06-03-16 17:42, Andres Rodriguez wrote: > In MAAS, we make use of dbconfig common. We have been using it exactly > the same way for awhile now and we have just starting seeing the > following on install or upgrade: > > dbconfig-common: writing config to > /etc/dbconfig-common/maas-region-controller.conf dbconfig-common has always done that. So nothing new. > stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or directory Any idea why this happens? What is special about your setup? How did you configure dbconfig-common? Is the /etc/dbconfig-common directory missing, or is the maas-region-controller.conf file missing? Is this on BOTH install and upgrade or only during install or only during upgrade? > Also, before this it always asks whether to use the local version of the > file or install a new one in case of an upgrade. I am not 100% sure if I understand what you mean. The behavior that you describe seems to be the question raised by ucf. Are you now saying that that is not happening anymore? That would indeed be a serious bug, but nothing on that front has changed. The only thing that I can think of on this front is that I removed the date of installation, such that ucf will not ask the question if the content of the file has not changed. Can you confirm that this is what you mean? Furthermore, there is important information missing: about which version of dbconfig-common are you talking? With which version did you experience the alleged change? Paul -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1553757 Title: dbconfig-common: writing config to /etc/dbconfig-common/maas-region- controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region- controller.conf': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+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 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
@yadi: link-local only was the proposal by @andreserl (not RFC1918, or its IPv6 equivalent, ULA), and that is completely doable. So is detection of an isolated, but not link-local-only network. It's simple - if there's no route in the local routing table to the destination, it should be excluded from attempts. This would work for both IPv4 and IPv6, regardless of the presence of NAT, because NAT still requires a route to the destination in order to function. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+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 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
@yadi Won't changing the limit from 10 to 25 just put off the problem until later? As I understand it, the main reason this issue caused problems is that squid attempts IPv6 connections from hosts without global IPv6 connectivity. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+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 1546376] [NEW] package sa-compile 3.4.1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 25
Public bug reported: Bluetooth does not work after several reinstallations of Ubuntu 15.10 due to a memory crash. Please e-mail me informations of how to set this if i need to do it manually. Message from the system: Connection to BlueZ failed Bluez daemon is not running, blueman-manager cannot continue. This probably means that there were no Bluetooth adapters detected or Bluetooth daemon was not started. Note: The bluetooth adapter works on Maze and windows 7. It was working before the crash. Thank you. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: sa-compile 3.4.1-1 ProcVersionSignature: Ubuntu 4.2.0-29.34-generic 4.2.8-ckt3 Uname: Linux 4.2.0-29-generic i686 NonfreeKernelModules: hid_generic pata_acpi usbhid hid nouveau mxm_wmi wmi video i2c_algo_bit ttm drm_kms_helper drm firewire_ohci firewire_core via_rhine 8139too mii crc_itu_t sata_via pata_via floppy ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 Date: Tue Feb 16 18:36:48 2016 DuplicateSignature: package:sa-compile:3.4.1-1:subprocess installed post-installation script returned error exit status 25 ErrorMessage: subprocess installed post-installation script returned error exit status 25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: spamassassin Title: package sa-compile 3.4.1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 25 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: spamassassin (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1546376 Title: package sa-compile 3.4.1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1546376/+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 1543185] [NEW] Malformed query causing timeouts due to ignored upstream queries
Public bug reported: In some situations dnsmasq makes malformed upstream queries resulting in servfail being returned after the 5s timeout built in to dnsmask. For example asking for foo with athing.bar.com and bar.com in the search path and two servers dns1.bar.com and dns1.bar.com results in System asks both dns1 and dns2 about: foo.athing.bar.com => immediate NXDomain from both; asks dns1 about: foo. => Servfail; asks both about: foo. with what tcpdump transcribes as '[b2&3=0x182] A? => no response from either [5 sec timeout]; retries: simple "A? foo." query to both, immediate Servfail from both The query giving the time out appear to be malformed and the upstream servers are completely ignoring it leading to the time out. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dnsmasq-base 2.68-1ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 8 15:38:26 2016 InstallationDate: Installed on 2014-05-07 (642 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1543185 Title: Malformed query causing timeouts due to ignored upstream queries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1543185/+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 1543185] Re: Malformed query causing timeouts due to ignored upstream queries
Actually sorry the PPA is a backport of dnsmasq 2.68 not just the above patch. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1543185 Title: Malformed query causing timeouts due to ignored upstream queries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1543185/+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 1543185] Re: Malformed query causing timeouts due to ignored upstream queries
This patch http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2015q2/009575.html appears to solve the problem, cjwatson built a test package in his ppa which I used to test this. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1543185 Title: Malformed query causing timeouts due to ignored upstream queries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1543185/+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 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup
I tested the new wily-proposed version (5.1.1-1ubuntu2.1 ) and it works great for me. Thank you ! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1503034 Title: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+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 1502539] Re: open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel module failed to build
Hi, folks - any updates on plans to deal with this long-standing issue? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1502539 Title: open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1502539/+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 1500581] Re: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’]
Hi, folks - any updates on plans to deal with this long-standing issue? (I'm using Ubuntu 15.10 in VMware Workstation on a Windows 7 host.) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1500581 Title: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’] To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1500581/+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 1349949] Re: Juju's mongodb does not need to log every command in syslog
This is still affecting us on 1.25.3. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+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 1502539] Re: open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel module failed to build
Hi - is anything going to be done about this issue which has been going on for two releases of the OS? We have VMware saying to use open-vm-tools, and we have open-vm-tools malfunctioning. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1502539 Title: open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1502539/+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 1510345] Re: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules
Regressed; reported at https://bugs.launchpad.net/ubuntu/+source/livecd- rootfs/+bug/1525015 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1510345 Title: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1510345/+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 1437005] Re: Default sshd_config file has bad path to sftp-server. Should be /usr/lib/openssh/sftp-server, not /usr/libexec/openssh/sftp-server
Yes, I'm certain that I hand-edited the file, feel free to close the bug. I _assumed_ that the example file would be correct for the installed package, silly me. Cheers, Paul On Thu, Dec 3, 2015 at 6:56 AM, Colin Watson <cjwat...@canonical.com> wrote: > This is peculiar, because I don't believe we've ever written it out with > the upstream libexec path. Yes, the examples file shows it as libexec, > but we've written out "Subsystem sftp /usr/lib/openssh/sftp-server" for > new installations since 2005. > > Is it possible that you had hand-edited your sshd_config at some point? > > ** Changed in: openssh (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1437005 > > Title: > Default sshd_config file has bad path to sftp-server. Should be > /usr/lib/openssh/sftp-server, not /usr/libexec/openssh/sftp-server > > Status in openssh package in Ubuntu: > Incomplete > > Bug description: > Silly error, can't believe it wasn't found or reported earlier. > > SFTP wasn't working, auth.log showed "cannot stat /usr/libexec/openssh > /sftp-server: No such file or directory" > > I checked /etc/ssh/sshd_config and /usr/share/doc/openssh- > server/examples/sshd_config, which is apparently the source file. Both > had the "libexec" path to the file. > > I ran "locate openssh/sftp-server" and got "/usr/lib/openssh/sftp- > server" > > Corrected the path in the config file & all was well. > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: openssh-server 1:6.6p1-2ubuntu2 > ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 > Uname: Linux 3.13.0-46-generic x86_64 > ApportVersion: 2.14.1-0ubuntu3.7 > Architecture: amd64 > CurrentDesktop: Unity > Date: Thu Mar 26 11:40:13 2015 > InstallationDate: Installed on 2014-07-24 (244 days ago) > InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 > (20140416.2) > SourcePackage: openssh > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1437005/+subscriptions > -- p...@mackinney.net -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1437005 Title: Default sshd_config file has bad path to sftp-server. Should be /usr/lib/openssh/sftp-server, not /usr/libexec/openssh/sftp-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1437005/+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 1065331] Re: variables defined in maintanier script overriden by global config
The fixable part of this bug was fixed in version 1.8.50 which is part of The Willy Werewolf. Closing this bug ** Changed in: dbconfig-common (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1065331 Title: variables defined in maintanier script overriden by global config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1065331/+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 1310340] Re: live migration fails when use long hostname of a nova compute target host
** Tags removed: live-migrate ** Tags added: live-migration -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1310340 Title: live migration fails when use long hostname of a nova compute target host To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1310340/+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 243852] Re: improve handling of the lack of a database
Error handling has been unified and improved in the package that is in The Willy Werewolf. Closing this bug. ** Changed in: dbconfig-common (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/243852 Title: improve handling of the lack of a database To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/243852/+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 789030] Re: drop database when requested by dpkg-reconfigure answer
This was fixed in version 1.8.50 which is part of The Willy Werewolf. Closing this bug ** Changed in: dbconfig-common (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/789030 Title: drop database when requested by dpkg-reconfigure answer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/789030/+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 1398999] Re: Block migrate with attached volumes copies volumes to themselves
** Tags removed: live-migrate ** Tags added: live-migration -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1398999 Title: Block migrate with attached volumes copies volumes to themselves To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1398999/+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 1459724] Re: live-migration causes lack of access to instance
** Tags removed: live-migrate ** Tags added: live-migration -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1459724 Title: live-migration causes lack of access to instance To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1459724/+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 807038] Re: dbconfig-common fails to preseed phpmyadmin on natty/lucid
This was fixed in version 1.8.48 which is part of The Willy Werewolf. Closing this bug. ** Changed in: dbconfig-common (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/807038 Title: dbconfig-common fails to preseed phpmyadmin on natty/lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/807038/+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 440430] Re: handle off-line database during upgrade more gracefully
This was fixed in 1.8.50 which is part of The Wily Werewolf. So closing this bug. ** Changed in: dbconfig-common (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/440430 Title: handle off-line database during upgrade more gracefully To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/440430/+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 1457312] Re: package dbconfig-common 1.8.47+nmu1 failed to install/upgrade: package dbconfig-common is not ready for configuration cannot configure (current status `half-installed')
Thanks for reporting this issue. However, there is not enough information to debug this issue. What happens if you run (please copy/paste all the output): apt-get install dbconfig-common ** Changed in: dbconfig-common (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1457312 Title: package dbconfig-common 1.8.47+nmu1 failed to install/upgrade: package dbconfig-common is not ready for configuration cannot configure (current status `half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1457312/+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 573847] Re: package phpmyadmin 4:3.3.2-1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
This was fixed in version 1.8.50 which is part of The Willy Werewolf. Closing this bug. ** Changed in: dbconfig-common (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/573847 Title: package phpmyadmin 4:3.3.2-1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/573847/+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 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting
The above report is against: lxc 1.0.7-0ubuntu0.7 amd64 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1504781 Title: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+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 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting
I got hit by the same issue, with the same unlucky kernel (installed from normal update channel): root@x230:~# uname -a Linux x230 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Will read suggestions above before going to back to classical VM... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1504781 Title: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+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 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting
Upgrading to 1.0.7-0ubuntu0.9 from updates fixed it. Sorry for the noise. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1504781 Title: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+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 1505813] [NEW] package python-networkx (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/doc/python-networkx/examples/basic/read_write.py », qui appartient auss
Public bug reported: There seem to be a conflict between the package python-networkx and python3-networkx ProblemType: Package DistroRelease: Ubuntu 15.04 Package: python-networkx (not installed) ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 AptOrdering: python-networkx: Install python-networkx: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Oct 13 19:04:49 2015 DuplicateSignature: package:python-networkx:(not installed):tentative de remplacement de « /usr/share/doc/python-networkx/examples/basic/read_write.py », qui appartient aussi au paquet python3-networkx 1.8.1-0ubuntu3 ErrorMessage: tentative de remplacement de « /usr/share/doc/python-networkx/examples/basic/read_write.py », qui appartient aussi au paquet python3-networkx 1.8.1-0ubuntu3 InstallationDate: Installed on 2014-09-08 (399 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: python-networkx Title: package python-networkx (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/doc/python-networkx/examples/basic/read_write.py », qui appartient aussi au paquet python3-networkx 1.8.1-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-networkx (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-networkx in Ubuntu. https://bugs.launchpad.net/bugs/1505813 Title: package python-networkx (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/doc/python- networkx/examples/basic/read_write.py », qui appartient aussi au paquet python3-networkx 1.8.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-networkx/+bug/1505813/+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 1505473] [NEW] pollen does not start on boot
Public bug reported: ubuntu@keeton:~$ lsb_release -rc Release:14.04 Codename: trusty ubuntu@keeton:~$ dpkg-query -W pollen pollen 4.11-0ubuntu1 ubuntu@keeton:~$ _ pollen does not start on boot, due to an error in the upstart config: ubuntu@keeton:~$ grep start /etc/init/pollen.conf start on start on runlevel [2345] stop on start on runlevel [!2345] # Ensure our device exists, and is a character device, before starting our server ubuntu@keeton:~$ _ Deleting the second "start on" in each line seems to fix this. ** Affects: pollen (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollen in Ubuntu. https://bugs.launchpad.net/bugs/1505473 Title: pollen does not start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/1505473/+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 1317705] Re: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs
@brian-murray, it appears this was not released into trusty-updates as mentioned above: root@myserver:~$ apt-cache policy python-txtftp python-txtftp: Installed: 0.1~bzr38-0ubuntu4~14.04.1 Candidate: 0.1~bzr38-0ubuntu4~14.04.1 Version table: *** 0.1~bzr38-0ubuntu4~14.04.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.1~bzr38-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages I've installed it from -proposed and confirmed that it fixes the oops on one system. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-tx-tftp in Ubuntu. https://bugs.launchpad.net/bugs/1317705 Title: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1317705/+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 1498371] Re: Sync dbconfig-common 1.8.53 (main) from Debian unstable (main)
Hi On 23-09-15 21:07, Graham Inggs wrote: > If the fix is known, upload it to Debian first. From there we can try > to sync again or upload a new Ubuntu version. I decided to not fix more than just this issue. In the mean time I even received a patch from Martin Pitt. Once the package is accepted and shows up, I guess I have to request another sync right? Paul -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1498371 Title: Sync dbconfig-common 1.8.53 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1498371/+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 1498371] Re: Sync dbconfig-common 1.8.53 (main) from Debian unstable (main)
On 25-09-15 12:26, Paul Gevers wrote: > Once the package is accepted and shows up, I guess I have to request > another sync right? It now did, but I can't get requestsync to work on my system right now (it used to work in the past). Graham, can you request the syn again? Paul -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1498371 Title: Sync dbconfig-common 1.8.53 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1498371/+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 1498371] Re: Sync dbconfig-common 1.8.53 (main) from Debian unstable (main)
Hi Graham and Robie On 22-09-15 12:15, Robie Basak wrote: > This bug was fixed in the package dbconfig-common - 1.8.53 > Sponsored for Graham Inggs (ginggs) > * Add extended regression tests to autopkgtest list It seems dbconfig-common is now hold back because of this new test failing. I just confirmed in a clean chroot that this is due to a missing dependency in the control file for that test on fakeroot. What is the smartest way forward? That I upload a new version to Debian that fixes that, or that we fix it for now in Ubuntu? Or are we too late anyways? I really think we should at least get the fix for Debian bug #793816 in Ubuntu, as that is a regression. Paul -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1498371 Title: Sync dbconfig-common 1.8.53 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1498371/+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 1498371] Re: Sync dbconfig-common 1.8.53 (main) from Debian unstable (main)
On 23-09-15 21:07, Graham Inggs wrote: > If the fix is known, upload it to Debian first. From there we can try > to sync again or upload a new Ubuntu version. I believe I know the fix. However, if I can do that for Debian I like to also get the second autopkgtest to run as intended (after the upload I found stashed changes that I thought I committed long time ago, now the first test just runs twice). I was wondering how much time is still left. One day, couple of days, two weeks? I am unsure for a package in main. Paul -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1498371 Title: Sync dbconfig-common 1.8.53 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1498371/+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 715141] Re: Default NTP servers do not have AAAA records
Also, ipv6.ntp.ubuntu.com is available if you prefer to force IPv6-only. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/715141 Title: Default NTP servers do not have records To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/715141/+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 715141] Re: Default NTP servers do not have AAAA records
One of our NTP servers has been IPv6 enabled today. The other will follow as time permits. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/715141 Title: Default NTP servers do not have records To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/715141/+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 1472318] [NEW] iscsitarget-dkms 1.4.20.3+svn499-1ubuntu1: iscsitarget kernel module failed to build Edit
Public bug reported: make KERNELRELEASE=3.16.0-42-generic -C /lib/modules/3.16.0-43generic (x86_64) bad exit status 2 Make Log File : - DKMS make.log for iscsitarget-1.4.20.3+svn499 for kernel 3.16.0-43-generic (x86_64) Tue Jul 7 16:36:45 BST 2015 make: Entering directory `/usr/src/linux-headers-3.16.0-43-generic' LD /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/built-in.o LD /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/built-in.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/tio.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/iscsi.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/nthread.o /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/nthread.c: In function ‘close_conn’: /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/nthread.c:669:32: warning: assignment from incompatible pointer type [enabled by default] conn-sock-sk-sk_data_ready = target-nthread_info.old_data_ready; ^ /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/nthread.c: In function ‘do_recv’: /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/nthread.c:147:1: warning: the frame size of 1096 bytes is larger than 1024 bytes [-Wframe-larger-than=] } ^ CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/wthread.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/config.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/digest.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/conn.o /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/conn.c: In function ‘iet_socket_bind’: /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/conn.c:137:38: warning: assignment from incompatible pointer type [enabled by default] target-nthread_info.old_data_ready = conn-sock-sk-sk_data_ready; ^ /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/conn.c:138:32: warning: assignment from incompatible pointer type [enabled by default] conn-sock-sk-sk_data_ready = iet_data_ready; ^ CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/session.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/target.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/volume.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/iotype.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/file-io.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/null-io.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/target_disk.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/event.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/param.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/block-io.o /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/block-io.c: In function ‘blockio_make_request’: /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/block-io.c:90:6: error: ‘struct bio’ has no member named ‘bi_sector’ bio-bi_sector = ppos 9; ^ make[2]: *** [/var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/block-io.o] Error 1 make[1]: *** [/var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel] Error 2 make: *** [_module_/var/lib/dkms/iscsitarget/1.4.20.3+svn499/build] Error 2 make: Leaving directory `/usr/src/linux-headers-3.16.0-43-generic' ** Affects: iscsitarget (Ubuntu) Importance: Undecided Status: New ** Description changed: make KERNELRELEASE=3.16.0-42-generic -C /lib/modules/3.16.0-43generic (x86_64) bad exit status 2 - Unable to load iscsi_trgt module + Make Log File : - + + DKMS make.log for iscsitarget-1.4.20.3+svn499 for kernel 3.16.0-43-generic (x86_64) + Tue Jul 7 16:36:45 BST 2015 + make: Entering directory `/usr/src/linux-headers-3.16.0-43-generic' + LD /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/built-in.o + LD /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/built-in.o + CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/tio.o + CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/iscsi.o + CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/nthread.o + /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/nthread.c: In function ‘close_conn’: + /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/nthread.c:669:32: warning: assignment from incompatible pointer type [enabled by default] + conn-sock-sk-sk_data_ready = target-nthread_info.old_data_ready; + ^ + /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/nthread.c: In function ‘do_recv’: + /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/nthread.c:147:1: warning: the frame size of 1096 bytes is larger than 1024 bytes [-Wframe-larger-than=] + } + ^ + CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/kernel/wthread.o
[Bug 1460389] Re: Version number mismatches: 2.0 beta but actually 1.8.6
After looking further, this likely came from experimental - it's since been pulled. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to groovy in Ubuntu. https://bugs.launchpad.net/bugs/1460389 Title: Version number mismatches: 2.0 beta but actually 1.8.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/groovy/+bug/1460389/+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 1460389] Re: Version number mismatches: 2.0 beta but actually 1.8.6
Groovy = 2.0 is packaged as src:groovy2 - this package will never be = 2.0. Looks like we need an epoch (perhaps even in Debian) to unbreak this. Triaging. ** Changed in: groovy (Ubuntu) Status: New = Triaged ** Changed in: groovy (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to groovy in Ubuntu. https://bugs.launchpad.net/bugs/1460389 Title: Version number mismatches: 2.0 beta but actually 1.8.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/groovy/+bug/1460389/+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 1387805] Re: docker.io containers cannot use local dnsmasq
127.0.0.1 inside the container isn't the same as 127.0.0.1 inside the container. I'm OK calling this a container misconfiguration. I've not tried, but try setting dnsmasq to bind to the docker0 interface (likely bind to 172.17.42.1) and hit that IP. Otherwise you're hitting 127.0.0.1 in the container, which isn't what you want (or where dnsmasq is bound) This is part of network namespacing. Closing the ticket, thanks! ** Changed in: docker.io (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1387805 Title: docker.io containers cannot use local dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1387805/+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 520872] Re: dbconfig-common: mysqldump must dump routines during upgrade, or risk data loss
Upload of 1.8.51 will happen in about two weeks time. That gives translators the time to update the templates. It will be synced automatically to Ubuntu after that. Paul On 20-05-15 10:07, Robie Basak wrote: dbconfig-common = 1.8.48 is still in experimental in Debian. I don't want to sync it to Ubuntu without knowing why this is the case. When Debian upload it to unstable, Ubuntu should autosync it soon after unless we're in freeze by then. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/520872 Title: dbconfig-common: mysqldump must dump routines during upgrade, or risk data loss To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/520872/+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 1449903] Re: package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1447294 *** https://bugs.launchpad.net/bugs/1447294 ** This bug has been marked a duplicate of bug 1447294 package nginx-full 1.6.2-5ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1449903 Title: package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1449903/+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 1455766] Re: package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug
*** This bug is a duplicate of bug 1447294 *** https://bugs.launchpad.net/bugs/1447294 ** This bug has been marked a duplicate of bug 1447294 package nginx-full 1.6.2-5ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1455766 Title: package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1455766/+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 445418] Re: package bacula-director-mysql (not installed) failed to install/upgrade: installed post-installation script alfolyamat 1 hibak?ddal kil?pett
*** This bug is a duplicate of bug 243852 *** https://bugs.launchpad.net/bugs/243852 ** This bug has been marked a duplicate of bug 440430 handle off-line database during upgrade more gracefully ** This bug is no longer a duplicate of bug 440430 handle off-line database during upgrade more gracefully ** This bug has been marked a duplicate of bug 243852 improve handling of the lack of a database -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/445418 Title: package bacula-director-mysql (not installed) failed to install/upgrade: installed post-installation script alfolyamat 1 hibak?ddal kil?pett To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/445418/+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 494783] Re: package bacula-director-mysql 2.4.4-1ubuntu9 failed to install/upgrade: le sous-processus script post-installation install? a retourn? une erreur de sortie d'?tat 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, this bug report doesn't actually contain a bug. The configuration asked the password of the administrator of the mysql server, and the operator failed to provide a valid password. (Mind you the template of dbconfig should (and in Debian is) improved to give more information. ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES). unable to connect to mysql server. error encountered creating user: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) dbconfig-common: bacula-director-mysql configure: trying again. dbconfig-common: writing config to /etc/dbconfig-common/bacula-director-mysql.conf ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES). unable to connect to mysql server. error encountered creating user: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) dbconfig-common: bacula-director-mysql configure: trying again. dbconfig-common: writing config to /etc/dbconfig-common/bacula-director-mysql.conf ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES). unable to connect to mysql server. error encountered creating user: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) ** Changed in: dbconfig-common (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/494783 Title: package bacula-director-mysql 2.4.4-1ubuntu9 failed to install/upgrade: le sous-processus script post-installation install? a retourn? une erreur de sortie d'?tat 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/494783/+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 569313] Re: package bacula-director upgrade failed because it couldn't connect to mysql-server
Can you please explain why this is considered a bug? If the database is corrupt (or at least, the operator configured the package to use a wrong database) isn't this expected behavior? Relevant part of the DpkgTerminalLog.gz: Creating config file /etc/dbconfig-common/bacula-director-mysql.conf with new version ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2). unable to connect to mysql server. error encountered creating user: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) dbconfig-common: bacula-director-mysql configure: aborted. ** Changed in: dbconfig-common (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/569313 Title: package bacula-director upgrade failed because it couldn't connect to mysql-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/569313/+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 819251] Re: package phpmyadmin 4:3.3.10-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10
As I mentioned in my previous comment, I tend to think this issue (which was never a dbconfig-common bug AFAICT) has been solved. It would help if anybody could tell me if they still experience this issue or if they don't. Marking this bug as incomplete until somebody responds. ** Changed in: dbconfig-common (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/819251 Title: package phpmyadmin 4:3.3.10-1 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/819251/+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 564561] Re: package phpmyadmin 4:3.3.1-1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
*** This bug is a duplicate of bug 563256 *** https://bugs.launchpad.net/bugs/563256 Hmm, more looks like phpmyadmin had invalid mysql code, which caused multiple trials of installation to fail. Replacing config file /etc/dbconfig-common/phpmyadmin.conf with new version granting access to database phpmyadmin for phpmyadmin@localhost: success. verifying access for phpmyadmin@localhost: success. creating database phpmyadmin: success. verifying database phpmyadmin exists: success. populating database via sql... error encountered populating database: mysql said: ERROR 1064 (42000) at line 177: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 9 dbconfig-common: phpmyadmin reconfigure: aborted. This is a duplicate of bug 563256 which has been long fixed. ** This bug has been marked a duplicate of bug 563256 package phpmyadmin 4:3.3.1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/564561 Title: package phpmyadmin 4:3.3.1-1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/564561/+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 573847] Re: package phpmyadmin 4:3.3.2-1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Error handling during removal strangely involved configuration. This issue has been fixed in dbconfig-common 1.8.50. ** Also affects: dbconfig-common (Debian) Importance: Undecided Status: New ** Changed in: dbconfig-common (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/573847 Title: package phpmyadmin 4:3.3.2-1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/573847/+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 1406700] Re: dbconfig-common should not fail if the root password is not asked (e.g. in noninteractive mode)
From the changelog in 1.8.50: * Make check for DEBIAN_FRONTEND case insensitive (LP: #1406700) ** Also affects: dbconfig-common (Debian) Importance: Undecided Status: New ** Changed in: dbconfig-common (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1406700 Title: dbconfig-common should not fail if the root password is not asked (e.g. in noninteractive mode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1406700/+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 252882] Re: crash on multiple db install with dbc_dbpass in config
Changelog from 1.8.48: * Fix multiple db support install. Thanks to Sylvain Garcia and Soren Hansen (LP: #252882) ** Changed in: dbconfig-common (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/252882 Title: crash on multiple db install with dbc_dbpass in config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/252882/+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 1437005] [NEW] Default sshd_config file has bad path to sftp-server. Should be /usr/lib/openssh/sftp-server, not /usr/libexec/openssh/sftp-server
Public bug reported: Silly error, can't believe it wasn't found or reported earlier. SFTP wasn't working, auth.log showed cannot stat /usr/libexec/openssh /sftp-server: No such file or directory I checked /etc/ssh/sshd_config and /usr/share/doc/openssh- server/examples/sshd_config, which is apparently the source file. Both had the libexec path to the file. I ran locate openssh/sftp-server and got /usr/lib/openssh/sftp- server Corrected the path in the config file all was well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-server 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 11:40:13 2015 InstallationDate: Installed on 2014-07-24 (244 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1437005 Title: Default sshd_config file has bad path to sftp-server. Should be /usr/lib/openssh/sftp-server, not /usr/libexec/openssh/sftp-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1437005/+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 374896] Re: Servers specified in ntp.conf are not carried into ntp.conf.dhcp
One workaround is to add a tab in front of your server/peer lines. This prevents the above-quoted regex from matching. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/374896 Title: Servers specified in ntp.conf are not carried into ntp.conf.dhcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/374896/+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 1426962] Re: Unable to WHOIS new TLDs
@dwjr87 - Marking as affecting me too but for what it's worth those domains are resolvable in Vivid which has whois version 5.2.4 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to whois in Ubuntu. https://bugs.launchpad.net/bugs/1426962 Title: Unable to WHOIS new TLDs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whois/+bug/1426962/+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 1422416] Re: apt-get install docker.io does not install required package lxc
Closing as invalid. This is not required on Debian nor Ubuntu, you likely are missing both of aufs and devicemapper, and falling back to the lxc backend. I don't even think that relation is a recommends. Thanks for the report, but unless this is present on Ubuntu or Debian, it's not getting patched up here, for an optional backend that's not default, or even secondary :) ** Changed in: docker.io (Ubuntu) Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1422416 Title: apt-get install docker.io does not install required package lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1422416/+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 1422406] Re: docker command gives wrong install help
Seems like another Mint bug. Closing. Likely a result of command-not-found checking the wrong suite. ** Changed in: docker.io (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1422406 Title: docker command gives wrong install help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1422406/+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 1332203] Re: autofs5-ldap regularly crashes after long periods of time
Just a note that Bug #1176020 is also describing a side effect of this same problem (same web server in question here). We are disabling our remote loghost and seeing if that theory holds. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/1332203 Title: autofs5-ldap regularly crashes after long periods of time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1332203/+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 1322682] Re: -D variables not honored
Landon's suggestion appears to be a fix for us too (thanks!). I did alter the source package so I don't have to remember that should the package have to be rebuilt one day. I set DEB_LDFLAGS_SET on the main call to debhelper. I've included a patch to be precise. That does not appear to be a good solution by Lintian's standards, so I will not mark this as a solution for this bug. This is just a quick fix for us. ** Patch added: patch implementing Landon's suggestion inside of debian/rules https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1322682/+attachment/4314389/+files/no-symbolic-functions.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1322682 Title: -D variables not honored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1322682/+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 288905] Re: /etc/init.d/ntp doesnt use ntpdate to ensure clocks are aligned before starting server.
The way I read man ntpd (on Debian wheezy), we could (should?) replace ntpdate by ntpd -q; and if we are going to run ntpd then ntpdate is unnecessary anyway. If we have (or are going to have) ntpd, then we should simply skip /etc/network/if-up.d/ntpdate; seeing how that depends on NTPSERVERS in /etc/ntp.conf or somesuch, I do not see that /etc/network/if-up.d/ntpdate is ever any use. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/288905 Title: /etc/init.d/ntp doesnt use ntpdate to ensure clocks are aligned before starting server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/288905/+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 1125726] Re: boot-time race between /etc/network/if-up.d/ntpdate and /etc/init.d/ntp start
See also https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/288905 where I said: The way I read man ntpd (on Debian wheezy), we could (should?) replace ntpdate by ntpd -q; and if we are going to run ntpd then ntpdate is unnecessary anyway. If we have (or are going to have) ntpd, then we should simply skip /etc/network/if-up.d/ntpdate; seeing how that depends on NTPSERVERS in /etc/ntp.conf or somesuch, I do not see that /etc/network/if-up.d/ntpdate is ever any use. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1125726 Title: boot-time race between /etc/network/if-up.d/ntpdate and /etc/init.d/ntp start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1125726/+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 1414678] [NEW] package mysql-server-5.5 5.5.41-0ubuntu0.14.04.1 [modified: usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade: subprocess installed post-installation script returned error
Public bug reported: Never have been able to install mysql. Changing mysql requires removing most of KDE due to dependancies. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: mysql-server-5.5 5.5.41-0ubuntu0.14.04.1 [modified: usr/share/mysql/errmsg-utf8.txt] ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Mon Jan 26 10:26:30 2015 DuplicateSignature: package:mysql-server-5.5:5.5.41-0ubuntu0.14.04.1 [modified: usr/share/mysql/errmsg-utf8.txt]:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-08-15 (164 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) Logs.var.log.daemon.log: Logs.var.log.mysql.error.log: MySQLConf.etc.mysql.conf.d..keepme: MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['mysql_upgrade_info', 'ib_logfile0', 'mysql-bin.08', 'QRCards', 'ibdata1', 'mysql-bin.04', 'error.log', 'slow.log', 'mysql-bin.06', 'mysql-bin.09', 'mysql-bin.10', 'mysql-bin.02', 'mysql-bin.05', 'paul-desktop.err', 'mysql-bin.11', 'mysql-bin.07', 'debian-5.5.flag', 'mysql-bin.12', 'mysql-bin.index', 'mysql', 'ib_logfile1', 'performance_schema', 'mysql-bin.03', 'mysql-bin.01'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=f8d89217-df1e-4938-afa6-26e494cf3344 ro quiet splash SourcePackage: mysql-5.5 Title: package mysql-server-5.5 5.5.41-0ubuntu0.14.04.1 [modified: usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1414678 Title: package mysql-server-5.5 5.5.41-0ubuntu0.14.04.1 [modified: usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1414678/+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 1372449] Re: .
** Changed in: apache2 (Ubuntu) Assignee: (unassigned) = Paul Mack (6-me) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1372449 Title: . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1372449/+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 1065331] Re: variables defined in maintanier script overriden by global config
Just a remark as the new maintainer of dbconfig-common in Debian. Unfortunately, the behavior that you want is the wrong solution to the problem, as it would blindly overrule system administrators decisions. Therefore this bug is in essence wontfix. However, what is a legitimate question is that maintainers should have a way to change priority of questions. This is requested in Debian bug 607171. No solution yet, but I will probably be working on it. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607171 ** Bug watch added: Debian Bug tracker #607171 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607171 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1065331 Title: variables defined in maintanier script overriden by global config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1065331/+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 1372449] Re: package apache2 2.4.7-1ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Description changed: - upgrading from 12.04 to 14.04 remotely, failed, prompted for bug, might - have mangled the process because I suck at w3m and nano. - - ProblemType: Package - DistroRelease: Ubuntu 14.04 - Package: apache2 2.4.7-1ubuntu4.1 - ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 - Uname: Linux 3.2.0-32-generic x86_64 - Apache2ConfdDirListing: ['zz010_psa_httpd.conf', 'php_cgi_wrapper.conf'] - Apache2Modules: - Error: command ['/usr/sbin/apachectl', '-D DUMP_MODULES'] failed with exit code 1: apache2: Syntax error on line 210 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/aclr.load: API module structure 'aclr_module' in file /usr/lib/apache2/modules/mod_aclr.so is garbled - expected signature 41503234 but saw 41503232 - perhaps this is not an Apache module DSO, or was compiled for a different Apache version? - Action '-D DUMP_MODULES' failed. - The Apache error log may have more information. - ApportVersion: 2.14.1-0ubuntu3.4 - Architecture: amd64 - Date: Mon Sep 22 08:49:13 2014 - DuplicateSignature: package:apache2:2.4.7-1ubuntu4.1:subprocess installed post-installation script returned error exit status 1 - ErrorMessage: subprocess installed post-installation script returned error exit status 1 - SourcePackage: apache2 - Title: package apache2 2.4.7-1ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - UpgradeStatus: Upgraded to trusty on 2014-09-22 (0 days ago) - modified.conffile..etc.apache2.apache2.conf: [modified] - modified.conffile..etc.apache2.ports.conf: [modified] - modified.conffile..etc.apache2.sites.available.000.default.conf: [modified] - modified.conffile..etc.apache2.sites.available.default.ssl.conf: [modified] - mtime.conffile..etc.apache2.apache2.conf: 2013-10-30T06:26:19 - mtime.conffile..etc.apache2.ports.conf: 2013-05-10T11:09:02 - mtime.conffile..etc.apache2.sites.available.000.default.conf: 2013-05-10T11:09:02 - mtime.conffile..etc.apache2.sites.available.default.ssl.conf: 2013-05-10T11:09:02 + . ** Attachment removed: Dependencies.txt https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1372449/+attachment/4211363/+files/Dependencies.txt ** Summary changed: - package apache2 2.4.7-1ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 + . -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1372449 Title: . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1372449/+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 1406700] Re: package cacti 0.8.8b+dfsg-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hi, You dpkgTerminalLog.txt file shows a lot of errors. One of them being that debconf questions could not be asked. This results in failure of dbconfig-common to ask you the root password to log into the mysql database. For you to work around this, is to fix the issue with debconf not being allowed to ask questions and reconfigure cacti: dpkg-reconfigure cacti. dbconfig-common should be improved to not FAIL in such cases, so reassigning there. ** Package changed: cacti (Ubuntu) = dbconfig-common (Ubuntu) ** Summary changed: - package cacti 0.8.8b+dfsg-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 + dbconfig-common should not fail if the root password is not asked (e.g. in noninteractive mode) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1406700 Title: dbconfig-common should not fail if the root password is not asked (e.g. in noninteractive mode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1406700/+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 1407841] Re: docker.io package fails install if docker group is pre-existing
I'm marking this as Opinion. Here's why: The local sysadmin may have created a Docker group, but *not* intended to give the rights to use Docker to those users. Remember, the Docker group is root equivelent. [tag@cassiel:~][⌚ 09:02 PM] ♥ docker run -it --rm -v /./:/mnt debian:unstable chroot /mnt # ls /home tag As such, on conflict, I'd prefer a failure to install. Marking Opinion. ** Changed in: docker.io (Ubuntu) Status: New = Opinion -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1407841 Title: docker.io package fails install if docker group is pre-existing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1407841/+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 252882] alternative solution for bug 252882: crash on multiple db install
Sorry that it took so long to follow up on this bug, but dbconfig-common has been rather unmaintained last couple of years. I am taking over the maintainership of dbconfig-common in Debian and will upload a new version to debian/experimental in the next couple of days/weeks. Although I think the solution by Soren is correct, I rather have a solution that still works when $dbc_authenticated_dbtypes is expended. I am thinking of the attached solution, but I would appreciate it when somebody could verify that it works for the multiple db path. Otherwise, giving me a use case example (does anybody know a package that uses this scenario?) would be extremely helpful. Paul ** Patch added: 0001-Fix-multiple-db-support-install.patch https://bugs.launchpad.net/bugs/252882/+attachment/428/+files/0001-Fix-multiple-db-support-install.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/252882 Title: crash on multiple db install with dbc_dbpass in config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/252882/+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 1386869] Re: -host in auto.master not mounting nfs exports
Is there a reason we can't just go get the patches that Ian Kent already provided for Fedora (see my link to the Red Hat bugzilla entry, which contains references to RPM versions that fix the problem) and apply them here and/or in Debian since the bug exists there as well? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1386869 Title: -host in auto.master not mounting nfs exports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1386869/+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 789030] Re: drop database when requested by dpkg-reconfigure answer
** Summary changed: - package cacti 0.8.7e-2ubuntu0.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 + drop database when requested by dpkg-reconfigure answer -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/789030 Title: drop database when requested by dpkg-reconfigure answer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/789030/+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 243852] Re: improve handling of the lack of a database
I'll try to see what better behavior is possible, but it may take a while. ** Summary changed: - package torrentflux 2.3-6 failed to install/upgrade: subprocess post-installation script returned error exit status 1 + improve handling of the lack of a database -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/243852 Title: improve handling of the lack of a database To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/243852/+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 440430] Re: handle off-line database during upgrade more gracefully
** Summary changed: - package request-tracker3.8 3.8.4-1 failed to install/upgrade: + handle off-line database during upgrade more gracefully -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/440430 Title: handle off-line database during upgrade more gracefully To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/440430/+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 440430] Re: handle off-line database during upgrade more gracefully
** Bug watch added: Debian Bug tracker #706512 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706512 ** Also affects: dbconfig-common (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706512 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/440430 Title: handle off-line database during upgrade more gracefully To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/440430/+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 819251] Re: package phpmyadmin 4:3.3.10-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10
Hmm, looking at the amount of duplicates and the fact that they all fall in the same time frame I wonder if instead this being a bug in dbconfig- common if this wasn't a bug in the software center which is long fixed. I recall that I once had an issue that questions were not appropriately asked in one package manager. It might be the case in all these bugs. I expect most people don't remember which package manager they were using at the time. However, I think I will consider this bug as being fixed and not really a bug in dbconfig-common. By the way, I believe (although not sure yet) that the lines above in message #3 are a red harring. I think dbconfig-common sometimes accepts debconf to error out and based on that takes actions. I think these lines are the result of such code. Also, I don't really think that all the duplicates are really all the same. However, they also lack the information to really debug the issue. I believe that most bugs that have a string like ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO). to be caused by the package manager not asking the question. Those bugs that have a YES there, are probably user errors (i.e. wrong password provided. And yes, I believe that dbconfig-common does not recover properly when that happens (i.e. it should warn the user are retry all actions, but it looks like it doesn't behave the same in the retry as it would in the first successful run. There are plenty of bugs describing that situation. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/819251 Title: package phpmyadmin 4:3.3.10-1 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/819251/+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 1390771] Re: vim-puppet syntax highlighting scripts are not effective
Ah, just missed that. Thanks for clearing that up. I've marked this report invalid. ** Changed in: puppet (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1390771 Title: vim-puppet syntax highlighting scripts are not effective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1390771/+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 1390771] [NEW] vim-puppet syntax highlighting scripts are not effective
Public bug reported:
The scripts from vim-puppet are installed to `/usr/share/vim/addons`
which doesn't appear to be used by the current vim distributed with
Ubuntu 14.04. The net effect is that installing the vim-puppet package
seems to do nothing when you edit Puppet scripts.
Here is an example site.pp file:
file { '/etc/motd':
contents = 'Hello, world!',
}
To reproduce:
1. Run vim site.pp
Expected behavior:
Syntax highlighting works. Running :set filetype? reveals that the
filetype is puppet.
Observed behavior:
Syntax highlighting does not work. Running :set filetype? shows there
is no filetype set. On some files, some other script detects the
filetype as conf.
If I run vim site.pp and then :scriptnames this is what I get:
1: /usr/share/vim/vimrc
2: /usr/share/vim/vim74/debian.vim
3: /usr/share/vim/vim74/syntax/syntax.vim
4: /usr/share/vim/vim74/syntax/synload.vim
5: /usr/share/vim/vim74/syntax/syncolor.vim
6: /usr/share/vim/vim74/filetype.vim
7: ~/.vimrc
8: /usr/share/vim/vim74/plugin/getscriptPlugin.vim
9: /usr/share/vim/vim74/plugin/gzip.vim
10: /usr/share/vim/vim74/plugin/matchparen.vim
11: /usr/share/vim/vim74/plugin/netrwPlugin.vim
12: /usr/share/vim/vim74/plugin/rrhelper.vim
13: /usr/share/vim/vim74/plugin/spellfile.vim
14: /usr/share/vim/vim74/plugin/tarPlugin.vim
15: /usr/share/vim/vim74/plugin/tohtml.vim
16: /usr/share/vim/vim74/plugin/vimballPlugin.vim
17: /usr/share/vim/vim74/plugin/zipPlugin.vim
18: /usr/share/vim/vim74/scripts.vim
Since most of these scripts are installed into /usr/share/vim/vim74 I
guessed the files are just in the wrong place. I linked each of the
installed puppet.vim files into their corresponding subdirectory in
`vim74/`. This gets the expected behavior for me.
This is what I get after running vim site.pp and then :scriptnames
after doing this.
1: /usr/share/vim/vimrc
2: /usr/share/vim/vim74/debian.vim
3: /usr/share/vim/vim74/syntax/syntax.vim
4: /usr/share/vim/vim74/syntax/synload.vim
5: /usr/share/vim/vim74/syntax/syncolor.vim
6: /usr/share/vim/vim74/filetype.vim
7: /usr/share/vim/vim74/ftdetect/puppet.vim
8: ~/.vimrc
9: /usr/share/vim/vim74/plugin/getscriptPlugin.vim
10: /usr/share/vim/vim74/plugin/gzip.vim
11: /usr/share/vim/vim74/plugin/matchparen.vim
12: /usr/share/vim/vim74/plugin/netrwPlugin.vim
13: /usr/share/vim/vim74/plugin/rrhelper.vim
14: /usr/share/vim/vim74/plugin/spellfile.vim
15: /usr/share/vim/vim74/plugin/tarPlugin.vim
16: /usr/share/vim/vim74/plugin/tohtml.vim
17: /usr/share/vim/vim74/plugin/vimballPlugin.vim
18: /usr/share/vim/vim74/plugin/zipPlugin.vim
19: /usr/share/vim/vim74/scripts.vim
20: /usr/share/vim/vim74/syntax/puppet.vim
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: vim-puppet 3.4.3-1
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Nov 8 12:28:14 2014
InstallationDate: Installed on 2014-04-29 (193 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: puppet
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: puppet (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1390771
Title:
vim-puppet syntax highlighting scripts are not effective
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1390771/+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 1321354] Re: open samba shares become unresponsive if unused for 15 minutes
Thanks yoyoma2 - the script you provided works a treat! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1321354 Title: open samba shares become unresponsive if unused for 15 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1321354/+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 1387459] Re: autofs stops working after upgrade to 14.10
I believe this is a duplicate of Bug #1386869 There's a workaround in the comments of that bug. HTH! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1387459 Title: autofs stops working after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1387459/+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 1386869] Re: -host in auto.master not mounting nfs exports
This appears to be a bug in the version of autofs that Ubuntu is shipping. See this report from ArchLinux: https://bugs.archlinux.org/task/38379 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1386869 Title: -host in auto.master not mounting nfs exports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1386869/+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 1386869] Re: -host in auto.master not mounting nfs exports
Also there's a problem reported in Fedora against 5.0.7, but apparently still present for 5.0.8: https://bugzilla.redhat.com/show_bug.cgi?id=1038356 ** Bug watch added: Red Hat Bugzilla #1038356 https://bugzilla.redhat.com/show_bug.cgi?id=1038356 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1386869 Title: -host in auto.master not mounting nfs exports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1386869/+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 1332203] Re: autofs5-ldap regularly crashes after long periods of time
This problem has continued over the past few months. We slogged through
the strace output a few times and just today found this:
[pid 935] sendto(11, 27Sep 22 13:06:30 automount[92..., 90, MSG_NOSIGNAL,
NULL, 0) = -1 ECONNREFUSED (Connection refused)
[pid 935] close(11) = 0
[pid 935] socket(PF_FILE, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4
[pid 935] connect(4, {sa_family=AF_FILE, path=/dev/log}, 110) = -1
ECONNREFUSED (Connection refused)
[pid 935] close(4)= 0
[pid 935] ioctl(3, 0xc0189379, 0x7f22fecabb20) = 0
[pid 935] ioctl(3, 0xc0189375, 0x7f22fecabb20) = 0
[pid 935] sched_yield() = 0
[pid 935] umount(/home, 0) = -1 EBUSY (Device or resource busy)
[pid 935] nanosleep({0, 2}, NULL) = 0
[pid 935] umount(/home, 0) = -1 EBUSY (Device or resource busy)
[pid 935] nanosleep({0, 2}, NULL) = 0
Our syslog sends some events to another loghost and the top call to
sendto(), which appears to fail, and automount tries to go down
gracefully. Checking the .crash file again, the backtrace is identical.
The backtrace does seem to support this story since there is a call to
vsyslog() inside of log_error().
So this bug may be filed under the wrong package, depending on whose
responsibility it is to handle this kind of error. Reading the man page
for vsyslog(), I don't see any way the caller can catch an error so this
could in fact be a problem with it.
We are using rsyslog 5.8.6-1ubuntu8.9 currently.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
https://bugs.launchpad.net/bugs/1332203
Title:
autofs5-ldap regularly crashes after long periods of time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1332203/+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 1246236] Re: pxe boot from maas fails due to time out
** Changed in: maas Status: Expired = New ** Changed in: maas (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1246236 Title: pxe boot from maas fails due to time out To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1246236/+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 1381258] [NEW] openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel module failed to build
Public bug reported: Reinstalling openvswitch--datapath-dkms after all OVS commands failed (e.g. ovs vs-ctl show) with message saying db.sock connection attempt failed (No such file or directory). I think a recent update/upgrade installed a newer kernel (3.2.0-70-generic) and then OVS commands failed. I uninstalled all the openvswitch-* pacakages and reinstalled and get a failure building the datapath-dkms package. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3 ProcVersionSignature: Ubuntu 3.2.0-70.105-generic 3.2.63 Uname: Linux 3.2.0-70-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.7 Architecture: amd64 DKMSKernelVersion: 3.2.0-70-generic Date: Tue Oct 14 18:40:15 2014 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all PackageVersion: 1.4.6-0ubuntu1.12.04.3 SourcePackage: openvswitch Title: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1381258 Title: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1381258/+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 1372449] Re: package apache2 2.4.7-1ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Is there any way to close this and dispose of the logs or at least make them private? Every time I change it to Private Security it reverts. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1372449 Title: package apache2 2.4.7-1ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1372449/+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 1376548] [NEW] service slapd stop fails
The failure to stop was consistent.
There was no logging, consistent with the successful exit code triggered
by --oknodo.
Experimentation showed that --exec was failing and it was because
/proc/$(pidof slapd)/exe could not be read (Permission denied to
root).
It has occurred to me belatedly that this is because I'm running slapd
inside a docker container (Docker version 1.2). I apologize for not
being alert enough to recognize this earlier.
The container is running with various capabilities (NET_ADMIN,
SYS_ADMIN, SYSLOG, DAC_OVERRIDE, NET_BIND_SERVICE, SETGID, SETUID). It
will not run in privileged mode -- due to (flaws in the profile for)
apparmor. So /proc is a protected area (read-only for example if not in
privileged mode but even more limited for security reasons).
While I now understand what is causing the problem, and can edit the
init.d script when building the docker image, I believe that the logic
in the stop_slapd function is flawed.
The slapd function is not stopping, due to a failure, but the stop
function is ending with exit code 0. The fundamental flaw may well be in
start-stop-daemon but this init script tests for the existence of
SLAPD_PIDFILE but assumes erroneously that --exec $SLAPD is
functional.
I admit I don't grasp why --oknodo is not recognizing a failure (which is
evident if this option is dropped) and interpreting the situation as nothing to
do.
I suggest that the environment I am running in will become increasingly more
common and plea for a fix to be made.
The scenario of concern driving the current script, i.e. an existing
pidfile but daemon has died, could be tested for. If not the case then
--pidfile alone should be sufficient. If the daemon has stopped then it
would be OK for the stop function to exit gracefully, possibly with a
warning about the pidfile. If there is no pidfile then I think the
script is already exiting. One could, if the pidfile didn't stop a
running daemon, attempt the --exec option. One can also try a brute
force stop without using either option if both fail.
Cheers
Paul Bickerstaff
DevOps, Portland Software Services
Mobile: +6421390266
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Ryan
Tandy
Sent: Friday, 3 October 2014 8:04 a.m.
To: paul.bickerst...@portland-software.com
Subject: Re: [Bug 1376548] [NEW] service slapd stop fails
Hi Paul,
Thanks for the report.
On Wed, Oct 1, 2014 at 8:03 PM, Paul Bickerstaff
paul.bickerst...@portland-software.com wrote:
In Ubuntu 14.04.1 LTS amd64 with slapd package version
2.4.31-1+nmu2ubuntu8, OpenLDAP server (slapd), executing the
following standard service command fails to have effect.
Is there any output from slapd in /var/log/syslog that might indicate
why it didn't stop? Is it still responding normally to connections after
that?
Is this happening consistently for you, or only intermittently? If the
latter, can you see any pattern in when it happens?
The problem is clouded by the --oknodo option in /etc/init.d/slapd.
This is responsible for the erroneous report.
JFTR: the intent of --oknodo is to provide idempotence, per the examples
in the start-stop-daemon(8) man page.
stop_slapd() {
reason=`start-stop-daemon --stop --quiet --oknodo --retry TERM/10 \
--pidfile $SLAPD_PIDFILE \
--exec $SLAPD 21`
}
Removing --oknodo demonstrates a failure with exit code 1. The role of
oknodo should be reconsidered here.
Further experimentation shows that the --exec option is not working.
That agrees with the return codes; 0 with --oknodo and 1 without it
means that start-stop-daemon(8) thinks no action needs to be taken.
However, your ps output above shows the command as /usr/sbin/slapd,
which (assuming you haven't modified the init script) is exactly what
--exec should be checking for. So I don't understand why this wouldn't
be working for you.
It definitely doesn't seem that slapd is failing to stop (which answers
some of my questions above); I'd expect s-s-d to return 2 in that case.
Can you verify that /proc/$(pidof slapd)/exe does point to
/usr/sbin/slapd?
Since the init script is checking for $SLAPD_PIDFILE and exiting if
empty, I suggest just dropping --exec $SLAPD from the init script.
It is superfluous and the service slapd stop command will work after
its removal.
As I understand it, the --exec test is there to protect against the case
where the daemon has already died but the pidfile is stil present (for
example, if it crashed), and some other unrelated process has already
taken over the PID. My larger concern is *why* --exec isn't working
properly on your system -- this could be a symptom of something more
subtle.
cheers,
Ryan
--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1376548
Title:
service slapd stop fails
Status in “openldap” package in Ubuntu:
New
Bug description:
In Ubuntu 14.04.1
[Bug 1376548] [NEW] service slapd stop fails
Public bug reported:
In Ubuntu 14.04.1 LTS amd64 with slapd package version
2.4.31-1+nmu2ubuntu8, OpenLDAP server (slapd), executing the
following standard service command fails to have effect.
# service slapd stop
* Stopping OpenLDAP slapd [ OK ]
# ps -ef | grep slapd | grep -v grep
openldap 196 1 0 02:00 ?00:00:00 /usr/sbin/slapd -h ldap:///
ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d
i.e. it reports all is OK but it failed to stop the running process
which continues with the same pid.
The problem is clouded by the --oknodo option in /etc/init.d/slapd. This
is responsible for the erroneous report.
stop_slapd() {
reason=`start-stop-daemon --stop --quiet --oknodo --retry TERM/10 \
--pidfile $SLAPD_PIDFILE \
--exec $SLAPD 21`
}
Removing --oknodo demonstrates a failure with exit code 1. The role of
oknodo should be reconsidered here.
Further experimentation shows that the --exec option is not working.
Since the init script is checking for $SLAPD_PIDFILE and exiting if
empty, I suggest just dropping --exec $SLAPD from the init script. It
is superfluous and the service slapd stop command will work after its
removal.
SLAPD_PIDFILE is correctly identified on my system.
Mine is a stock standard fresh slapd install.
** Affects: openldap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1376548
Title:
service slapd stop fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1376548/+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 1372449] [NEW] package apache2 2.4.7-1ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: upgrading from 12.04 to 14.04 remotely, failed, prompted for bug, might have mangled the process because I suck at w3m and nano. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: apache2 2.4.7-1ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 Apache2ConfdDirListing: ['zz010_psa_httpd.conf', 'php_cgi_wrapper.conf'] Apache2Modules: Error: command ['/usr/sbin/apachectl', '-D DUMP_MODULES'] failed with exit code 1: apache2: Syntax error on line 210 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/aclr.load: API module structure 'aclr_module' in file /usr/lib/apache2/modules/mod_aclr.so is garbled - expected signature 41503234 but saw 41503232 - perhaps this is not an Apache module DSO, or was compiled for a different Apache version? Action '-D DUMP_MODULES' failed. The Apache error log may have more information. ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Mon Sep 22 08:49:13 2014 DuplicateSignature: package:apache2:2.4.7-1ubuntu4.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 SourcePackage: apache2 Title: package apache2 2.4.7-1ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-09-22 (0 days ago) modified.conffile..etc.apache2.apache2.conf: [modified] modified.conffile..etc.apache2.ports.conf: [modified] modified.conffile..etc.apache2.sites.available.000.default.conf: [modified] modified.conffile..etc.apache2.sites.available.default.ssl.conf: [modified] mtime.conffile..etc.apache2.apache2.conf: 2013-10-30T06:26:19 mtime.conffile..etc.apache2.ports.conf: 2013-05-10T11:09:02 mtime.conffile..etc.apache2.sites.available.000.default.conf: 2013-05-10T11:09:02 mtime.conffile..etc.apache2.sites.available.default.ssl.conf: 2013-05-10T11:09:02 ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1372449 Title: package apache2 2.4.7-1ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1372449/+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 1367547] [NEW] qemu-img convert -O raw is broken in trusty
Public bug reported: qemu-img convert -O raw with yields a file of the correct length with no content, e.g.: $ qemu-img convert -O raw trusty-server-cloudimg-amd64-disk1.img trusty-server-cloudimg-amd64-disk1.raw $ ls -l trusty-* -rw-rw-r-- 1 paul paul 255590912 Sep 10 09:14 trusty-server-cloudimg-amd64-disk1.img -rw-r--r-- 1 paul paul 2361393152 Sep 10 15:13 trusty-server-cloudimg-amd64-disk1.raw $ du -sh trusty-* 244Mtrusty-server-cloudimg-amd64-disk1.img 0 trusty-server-cloudimg-amd64-disk1.raw $ dpkg-query -W qemu-utils qemu-utils 2.0.0+dfsg-2ubuntu1.3 $ lsb_release -c Codename: trusty $ _ qemu-img in precise and in utopic both seem to work correctly, e.g.: $ qemu-img convert -O raw trusty-server-cloudimg-amd64-disk1.img trusty-server-cloudimg-amd64-disk1.raw $ ls -l trusty-* -rw-r--r-- 1 paul paul 255590912 Sep 9 21:14 trusty-server-cloudimg-amd64-disk1.img -rw-r--r-- 1 paul paul 2361393152 Sep 10 03:16 trusty-server-cloudimg-amd64-disk1.raw $ du -sh trusty-* 244Mtrusty-server-cloudimg-amd64-disk1.img 801Mtrusty-server-cloudimg-amd64-disk1.raw $ dpkg-query -W qemu-utils qemu-utils 2.1+dfsg-4ubuntu1 $ lsb_release -c Codename: utopic $ _ ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Affects: qemu (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1367547 Title: qemu-img convert -O raw is broken in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1367547/+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 1367547] Re: qemu-img convert -O raw is broken in trusty
I can't reproduce this in a freshly created trusty VM, so this may be something strange with my machine. Marking Invalid for now. ** Changed in: qemu (Ubuntu) Status: New = Invalid ** Changed in: qemu (Ubuntu Trusty) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1367547 Title: qemu-img convert -O raw is broken in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1367547/+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 1353269] [NEW] celery worker crashes on startup when python-librabbitmq is used
Public bug reported: On a vanilla trusty install with rabbitmq-server and celeryd installed, celery worker crashes as follows: $ dpkg-query -W python-librabbitmq rabbitmq-server python-amqp librabbitmq1 celeryd celeryd 3.1.6-1ubuntu1 librabbitmq10.4.1-1 python-amqp 1.3.3-1ubuntu1 python-librabbitmq 1.0.3-0ubuntu1 rabbitmq-server 3.2.4-1 $ celery worker [2014-08-06 05:19:00,142: WARNING/MainProcess] /usr/lib/python2.7/dist-packages/celery/apps/worker.py:159: CDeprecationWarning: Starting from version 3.2 Celery will refuse to accept pickle by default. The pickle serializer is a security concern as it may give attackers the ability to execute any command. It's important to secure your broker from unauthorized access when using pickle, so we think that enabling pickle should require a deliberate action and not be the default choice. If you depend on pickle then you should set a setting to disable this warning and to be sure that everything will continue working when you upgrade to Celery 3.2:: CELERY_ACCEPT_CONTENT = ['pickle', 'json', 'msgpack', 'yaml'] You must only enable the serializers that you will actually use. warnings.warn(CDeprecationWarning(W_PICKLE_DEPRECATED)) -- celery@juju-pjdc-lcy02-machine-4 v3.1.6 (Cipater) - --- * *** * -- Linux-3.13.0-32-generic-x86_64-with-Ubuntu-14.04-trusty -- * - --- - ** -- [config] - ** -- . broker: amqp://guest@localhost:5672// - ** -- . app: default:0x7ff5367585d0 (.default.Loader) - ** -- . concurrency: 1 (prefork) - *** --- * --- . events: OFF (enable -E to monitor this worker) -- *** --- * - [queues] -- . celery exchange=celery(direct) key=celery Segmentation fault (core dumped) If I remove python-librabbitmq so that celery falls back to python-amqp, celery worker starts up and works correctly. I have also discovered that a python-rabbitmq built from version 1.5.2 sources with its embedded copy of rabbitmq-c 0.5.0 also works correctly. I have attached a backtrace but it is not too useful as python- librabbitmq does not appear to make debug symbols available, and it occupies the second and third frames in the stack when the crash happens. ** Affects: python-librabbitmq (Ubuntu) Importance: Undecided Status: New ** Attachment added: celery-vs-python-librabbitmq-backtrace.txt https://bugs.launchpad.net/bugs/1353269/+attachment/4170851/+files/celery-vs-python-librabbitmq-backtrace.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-librabbitmq in Ubuntu. https://bugs.launchpad.net/bugs/1353269 Title: celery worker crashes on startup when python-librabbitmq is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-librabbitmq/+bug/1353269/+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 1349863] [NEW] pwgen does not not honour -B when output is a terminal
Public bug reported: The pwgen man page states: -B, --ambiguous Don't use characters that could be confused by the user when printed, such as 'l' and '1', or '0' or 'O'. This reduces the number of possible passwords significantly, and as such reduces the quality of the passwords. It may be useful for users who have bad vision, but in general use of this option is not recommended. This behaviour is not honoured in all runs where output is a terminal. e.g.: $ pwgen -B 8 8 Oy7iezuy toh7nieT JoBei3Oh hi4zaX9a bi4iegaY egh7Aiji Eez9icei noh7Po4e $ pwgen -B 8 8|cat aihaejoo eebieshu aotaekub uniegahp uotheboh weighoon reunguda onaemeiw ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pwgen 2.06-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 30 00:11:44 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libc6 2.19-0ubuntu6 libgcc1 1:4.9-20140406-0ubuntu1 multiarch-support 2.19-0ubuntu6 SourcePackage: pwgen UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pwgen (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pwgen in Ubuntu. https://bugs.launchpad.net/bugs/1349863 Title: pwgen does not not honour -B when output is a terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pwgen/+bug/1349863/+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 1297218] Re: guest hangs after live migration due to tsc jump
** Also affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1297218/+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
