[Bug 1562450] [NEW] package memcached 1.4.25-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: package memcached 1.4.25-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1. After booting it crashes. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: memcached 1.4.25-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 AptOrdering: memcached: Install memcached: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Mar 26 22:58:37 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-03-12 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.7 SourcePackage: memcached Title: package memcached 1.4.25-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: memcached (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to memcached in Ubuntu. https://bugs.launchpad.net/bugs/1562450 Title: package memcached 1.4.25-2ubuntu1 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/memcached/+bug/1562450/+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 1540407] Comment bridged from LTC Bugzilla
--- Comment From thorsten.di...@de.ibm.com 2016-03-21 13:50 EDT--- Hi Ryan, hi Dimitri, Update from LP 1551952: > St?phane Graber (stgraber) wrote on 2016-03-18: #7 > > Unfortunate that this only gets in so late in the cycle, but I can certainly > see the benefit of updating this before we have to support it for 5 years. > > Testing seems reasonable. debdiff is unreviewable so we can only rely on the > testing... > > Assuming that you'll take care of any yet unknown regression from this, you > may go ahead and upload the merge. > Changed in multipath-tools (Ubuntu): > status: New ? Triaged ...let's roll. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1540407 Title: multipathd drops paths of a temporarily lost device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540407/+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 1540407] Re: multipathd drops paths of a temporarily lost device
This bug was fixed in the package multipath-tools - 0.5.0+git1.656f8865-5ubuntu1 --- multipath-tools (0.5.0+git1.656f8865-5ubuntu1) xenial; urgency=medium * Merge from Debian. (LP: #1551952) (LP: #1540407) Remaining changes: - debian/control: - Bump debhelper dependency to install udev rules to /lib/udev/rules.d - Bump udev dependencies as well - debian/control: - multipath-tools: add sg3-utils-dev Depends - multipath-udeb: add sg3-udeb Depends - debian/initramfs/hooks: use 95 not 60 for multipath rules priority - debian/rules: Move udev rules to priority 95, because rules that load modules should be >90. - debian/multipath-tools.preinst: modprobe dm-multipath. This will make sure that multipathd will be able to start. - debian/initramfs/local-top: wait for udev to settle before running 'multipath' in order to avoid race condition on device-mapper calls. - debian/initramfs/local-top: remove '--timeout 10' which causes my test system to not boot roughly 3 out of 4 times. - Split kpartx initramfs bits into kpartx-boot for dmraid (LP: #941874) - debian/initramfs/kpartx.hook - debian/kpartx-boot.postinst - debian/kpartx-boot.postrm - debian/kpartx.install - debian/control: Add kpartx-boot package for dmraid - debian/rules: Install kpartx initramfs hook - debian/patches/1000--set-umask-in-multipathd.patch: Set umask in multipathd. - debian/patches/handle_spaces_in_rev_attr.patch: support IBM IPR devices and others which may have only spaces for the rev attribute. - debian/patches/path_selector.patch: switch the default path selector back to round-robin while service-time isn't available to the installer multipath-modules. - debian/patches/0015-shared-lock-for-udev.patch: (LP: #1431650) - debian/initramfs/hooks: also copy wwids file on the installed system to ensure all paths come up on boot. (LP: #1479929) - Disable -fexceptions on multipath-udeb (LP: #1489379): the flag causes libchecktur.so to link with libgcc_s.so.1 (even with -static-libgcc), which is not available in the installer environment. - debian/patches/disable-fexceptions-udeb.patch: conditionally disable -fexceptions with CFLAGS_DISABLE_FEXCEPTIONS. - debian/rules: set CFLAGS_DISABLE_FEXCEPTIONS to build multipath-udeb. - debian/patches/handle_spaces_in_rev_attr.patch: update patch to apply the change to the right line (LP: #1492425) - debian/initramfs/local-premount: wait for udev to settle before the call to resolve_device() in local_mount_root(), so the by-uuid/ symlinks have a chance to be updated by the multipath udev rules (LP: #1503286). - debian/multipath-tools.postinst: handle upgrades from < 0.5.0 by migrating from the old device names with device numbers to using letters for devices. - debian/patches/mpath_name_migration.patch: ship a multipath_migrate binary to make translation from pre-0.5.0 device naming to the new scheme. - debian/initramfs/hooks: install multipathd and required directories. - debian/initramfs/local-premount: reload all maps to make sure they're indeed loaded and ready before we end premount. - debian/initramfs/local-top: run multipathd rather than a one-off call to multipath so that new paths can be correctly added as detected while we're still in the initramfs. - debian/initramfs/local-bottom: remember to stop multipathd. - debian/rules: install debian/initramfs/local-bottom - debian/patches/0053-readonly-bindings_multipathd_prod.patch: support -B to allow multipathd to handle cases where the bindings file is read-only. (LP: #1526984) - debian/patches/git-kpartx-support-spaces-in-dev-names-b407050a.patch: deal with spaces in device names in kpartx too (LP: #1432062) - debian/tests/kpartx-file-loopback: add an autopkgtest to catch future cases where uploads might break kpartx's loopback file handling. - debian/patches/kpartx_more_loopback_fixes.patch: fix loopback mounted files some more: since we stat() the loopback device node, we can't rely on S_ISREG() tests to handle this case, and should look at the device itself instead. (LP: #1543430) - Remove partition device nodes of individual paths (for LVM on multipath) (LP: #1540401) - debian/multipath-tools.dm-mpath-lvm.udev: udev rule for that. - debian/initramfs/hooks: copy the udev rule and partx to the initramfs. - debian/initramfs/init-top: load the dm-multipath module for 'multipath -c'. - debian/rules: install the udev rule (priority 56: after 55-scsi-sg3_id) - debian/rules: don't ship 95-multipath.rules udev rules anymore; they are not necessary with multipath-tools listening for udev events directly. * Drop changes: - debian/patches/series: Drop obsol
[Bug 1551952] Re: FFE: Please merge multipath-tools 0.5.0+git1.656f8865 from Debian unstable
This bug was fixed in the package multipath-tools - 0.5.0+git1.656f8865-5ubuntu1 --- multipath-tools (0.5.0+git1.656f8865-5ubuntu1) xenial; urgency=medium * Merge from Debian. (LP: #1551952) (LP: #1540407) Remaining changes: - debian/control: - Bump debhelper dependency to install udev rules to /lib/udev/rules.d - Bump udev dependencies as well - debian/control: - multipath-tools: add sg3-utils-dev Depends - multipath-udeb: add sg3-udeb Depends - debian/initramfs/hooks: use 95 not 60 for multipath rules priority - debian/rules: Move udev rules to priority 95, because rules that load modules should be >90. - debian/multipath-tools.preinst: modprobe dm-multipath. This will make sure that multipathd will be able to start. - debian/initramfs/local-top: wait for udev to settle before running 'multipath' in order to avoid race condition on device-mapper calls. - debian/initramfs/local-top: remove '--timeout 10' which causes my test system to not boot roughly 3 out of 4 times. - Split kpartx initramfs bits into kpartx-boot for dmraid (LP: #941874) - debian/initramfs/kpartx.hook - debian/kpartx-boot.postinst - debian/kpartx-boot.postrm - debian/kpartx.install - debian/control: Add kpartx-boot package for dmraid - debian/rules: Install kpartx initramfs hook - debian/patches/1000--set-umask-in-multipathd.patch: Set umask in multipathd. - debian/patches/handle_spaces_in_rev_attr.patch: support IBM IPR devices and others which may have only spaces for the rev attribute. - debian/patches/path_selector.patch: switch the default path selector back to round-robin while service-time isn't available to the installer multipath-modules. - debian/patches/0015-shared-lock-for-udev.patch: (LP: #1431650) - debian/initramfs/hooks: also copy wwids file on the installed system to ensure all paths come up on boot. (LP: #1479929) - Disable -fexceptions on multipath-udeb (LP: #1489379): the flag causes libchecktur.so to link with libgcc_s.so.1 (even with -static-libgcc), which is not available in the installer environment. - debian/patches/disable-fexceptions-udeb.patch: conditionally disable -fexceptions with CFLAGS_DISABLE_FEXCEPTIONS. - debian/rules: set CFLAGS_DISABLE_FEXCEPTIONS to build multipath-udeb. - debian/patches/handle_spaces_in_rev_attr.patch: update patch to apply the change to the right line (LP: #1492425) - debian/initramfs/local-premount: wait for udev to settle before the call to resolve_device() in local_mount_root(), so the by-uuid/ symlinks have a chance to be updated by the multipath udev rules (LP: #1503286). - debian/multipath-tools.postinst: handle upgrades from < 0.5.0 by migrating from the old device names with device numbers to using letters for devices. - debian/patches/mpath_name_migration.patch: ship a multipath_migrate binary to make translation from pre-0.5.0 device naming to the new scheme. - debian/initramfs/hooks: install multipathd and required directories. - debian/initramfs/local-premount: reload all maps to make sure they're indeed loaded and ready before we end premount. - debian/initramfs/local-top: run multipathd rather than a one-off call to multipath so that new paths can be correctly added as detected while we're still in the initramfs. - debian/initramfs/local-bottom: remember to stop multipathd. - debian/rules: install debian/initramfs/local-bottom - debian/patches/0053-readonly-bindings_multipathd_prod.patch: support -B to allow multipathd to handle cases where the bindings file is read-only. (LP: #1526984) - debian/patches/git-kpartx-support-spaces-in-dev-names-b407050a.patch: deal with spaces in device names in kpartx too (LP: #1432062) - debian/tests/kpartx-file-loopback: add an autopkgtest to catch future cases where uploads might break kpartx's loopback file handling. - debian/patches/kpartx_more_loopback_fixes.patch: fix loopback mounted files some more: since we stat() the loopback device node, we can't rely on S_ISREG() tests to handle this case, and should look at the device itself instead. (LP: #1543430) - Remove partition device nodes of individual paths (for LVM on multipath) (LP: #1540401) - debian/multipath-tools.dm-mpath-lvm.udev: udev rule for that. - debian/initramfs/hooks: copy the udev rule and partx to the initramfs. - debian/initramfs/init-top: load the dm-multipath module for 'multipath -c'. - debian/rules: install the udev rule (priority 56: after 55-scsi-sg3_id) - debian/rules: don't ship 95-multipath.rules udev rules anymore; they are not necessary with multipath-tools listening for udev events directly. * Drop changes: - debian/patches/series: Drop obsol
[Bug 1488050] Re: Unable to connect to Upstart
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: samba (Ubuntu) Status: New => Confirmed -- 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/1488050 Title: Unable to connect to Upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1488050/+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 1522422] Re: Update to php 7.0
I'm not able to help with this at the moment, but I sent an e-mail to the package maintainers letting them know. Hopefully they'll get in touch. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1522422 Title: Update to php 7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1522422/+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 823878] Re: "bind interfaces only" requires a manual change to /etc/init/smbd.conf
> - "IFACE=eth0": shouldn't "net-device-up" wait for all interfaces to have an ip address ? No. That's the 'static-network-up' event, mentioned above. 'net-device- up' is a per-device event. > - "started nmbd": I wonder whether that should not be put per default by the samba's installation script. What do you think ? No, that's definitely wrong and will cause 'service nmbd restart' to hang. And I don't know why this would be necessary on your system. Regardless, beyond 14.04 the system init is handled completely differently (via systemd instead of upstart) so this bug will no longer apply in 16.04 LTS. -- 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/823878 Title: "bind interfaces only" requires a manual change to /etc/init/smbd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/823878/+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 1562349] Re: I can't update my Ubuntu cause of: package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall
Thank you for reporting this bug and helping to improve Ubuntu. Unfortunately, the logs in question only show that your system is in an inconsistent state; they do not explain how the system got to be that way, so there is nothing the developers can do to debug this and prevent this from occurring in the future. To correct the problem on your system, you need to do as the error message indicates and reinstall the libgssapi-krb5-2 package. You should be able to achieve this by running the following command from a terminal: sudo apt-get install --reinstall libgssapi-krb5-2 ** Changed in: krb5 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1562349 Title: I can't update my Ubuntu cause of: package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1562349/+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 1552983] Re: Please merge logwatch 7.4.2-1 from Debian
This bug was fixed in the package logwatch - 7.4.2-1ubuntu1 --- logwatch (7.4.2-1ubuntu1) xenial; urgency=medium * Merge from Debian unstable (LP: #1552983). Remaining changes: - debian/control: depend on postfix rather than exim4. - debian/dist.conf/logfiles/maillog.conf: adjust for logrotation - Drop libsys-cpu-perl and libsys-meminfo-perl from Recommends to Suggests as they are in universe. -- Nishanth Aravamudan Fri, 04 Mar 2016 11:42:51 -0800 ** Changed in: logwatch (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1552983 Title: Please merge logwatch 7.4.2-1 from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1552983/+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 1464990] Re: Job for dnsmasq.service failed because the control process exited with error code
FWIW, I see the same error on 15.10. ** Changed in: dnsmasq (Ubuntu) Status: Invalid => Confirmed -- 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/1464990 Title: Job for dnsmasq.service failed because the control process exited with error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1464990/+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 1562349] Re: I can't update my Ubuntu cause of: package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1562349 Title: I can't update my Ubuntu cause of: package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1562349/+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 1562349] [NEW] I can't update my Ubuntu cause of: package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinsta
Public bug reported: I could not update my ubuntu 15.10 (amd64) from some weeks. I tried with sudo apt-get clean sudo apt-get update It seemed to work, the update process found a lot of updates to install, but when the moment for krb5 arrived, the process crashed again ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sat Mar 26 13:27:25 2016 DuplicateSignature: package:libgssapi-krb5-2:amd64:1.13.2+dfsg-2ubuntu0.1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2011-10-15 (1624 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: krb5 Title: package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: krb5 (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 krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1562349 Title: I can't update my Ubuntu cause of: package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1562349/+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 1406499] Re: AMD Kaveri support needs lm-sensors 3.3.5
None of the current LTS versions (Ubuntu 12.04 and 14.04) contain a version of lm-sensors that supports the AMD Kaveri processors. ** Changed in: lm-sensors (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1406499 Title: AMD Kaveri support needs lm-sensors 3.3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1406499/+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 1561975] Re: default configuration warnings - minor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: postfix (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1561975 Title: default configuration warnings - minor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1561975/+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 1562268] [NEW] Missing package: nova-objectstore_13.0.0~b3-0ubuntu1_all.deb
Public bug reported: As per the summary, build 13.0.0~b3-0ubuntu1 is missing the nova- objectstore package. ** Affects: nova (Ubuntu) Importance: Undecided Status: New -- 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/1562268 Title: Missing package: nova-objectstore_13.0.0~b3-0ubuntu1_all.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1562268/+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 1562265] Re: named crashed with SIGABRT in isc_assertion_failed()
*** This bug is a duplicate of bug 1552801 *** https://bugs.launchpad.net/bugs/1552801 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1552801, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1562265/+attachment/4612215/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1562265/+attachment/4612217/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1562265/+attachment/4612220/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1562265/+attachment/4612221/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1562265/+attachment/461/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1562265/+attachment/4612223/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1562265/+attachment/4612225/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1552801 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1562265 Title: named crashed with SIGABRT in isc_assertion_failed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1562265/+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 823878] Re: "bind interfaces only" requires a manual change to /etc/init/smbd.conf
With quite a delay :) (almost three years after), I had the same issue, on 14.04.3 LTS (GNU/Linux 3.19.0-33-generic x86_64). After reading this bug and https://bugs.launchpad.net/ubuntu/+source/samba/+bug/596064 As a workaround, I set "start on (local-filesystems and net-device-up IFACE=eth0 and started nmbd)" in /etc/init/smbd.conf. I have two remarks, regarding: - "IFACE=eth0": shouldn't "net-device-up" wait for all interfaces to have an ip address ? (for interfaces configured on DHCP among others) - "started nmbd": I wonder whether that should not be put per default by the samba's installation script. What do you think ? -- 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/823878 Title: "bind interfaces only" requires a manual change to /etc/init/smbd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/823878/+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 1553460] Re: named crashed with SIGABRT in isc_assertion_failed()
Still continue crashing (in a random way) ** Attachment added: "_usr_sbin_named.126.crash" https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1553460/+attachment/4612190/+files/_usr_sbin_named.126.crash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1553460 Title: named crashed with SIGABRT in isc_assertion_failed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1553460/+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
