[Bug 1878417] Re: Floppy causes processes to hang when trying to access an empty drive
we're testing blacklisting the floppy module as a workaround, per https://tickets.puppetlabs.com/browse/FACT-1922 ([FACT-1922] Log file being spammed with the error: floppy: error -5 while read ing block 0 - Puppet Tickets) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878417 Title: Floppy causes processes to hang when trying to access an empty drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1878417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888009] Re: smartmontools.service: start operation timed out. Terminating.
thank you for the clarification and the suggestion. i was confused by the timeout occurring after the message "Monitoring 38 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices" as that seemed to indicate a successful startup. it appears to have been just the number of devices, not an issue with any particular one. raising the timeout gave `smartd` time to start properly. thanks again, this report can be closed as not-a-bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888009 Title: smartmontools.service: start operation timed out. Terminating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1888009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888009] [NEW] smartmontools.service: start operation timed out. Terminating.
Public bug reported: the smartmontools.service is seen by systemd as timing out and is terminated. `systemctl status smartmontools.service` reports: ● smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon Loaded: loaded (/lib/systemd/system/smartmontools.service; enabled; vendor preset: enabled) Active: failed (Result: timeout) since Fri 2020-07-17 17:32:59 UTC; 29min ago Docs: man:smartd(8) man:smartd.conf(5) Process: 57674 ExecStart=/usr/sbin/smartd -n $smartd_opts (code=killed, signal=TERM) Main PID: 57674 (code=killed, signal=TERM) Status: "Checking 38 devices ..." Jul 17 17:31:38 ia804105.us.archive.org smartd[57674]: Device: /dev/sdal [SAT], opened Jul 17 17:31:38 ia804105.us.archive.org smartd[57674]: Device: /dev/sdal [SAT], WDC WD4005FZBX-00K5WB0, S/N:VBG7B3WR, WWN:5-000cca-095c3585c, FW:01.01A01, 4.00 TB Jul 17 17:31:38 ia804105.us.archive.org smartd[57674]: Device: /dev/sdal [SAT], not found in smartd database. Jul 17 17:31:38 ia804105.us.archive.org smartd[57674]: Device: /dev/sdal [SAT], enabled SMART Attribute Autosave. Jul 17 17:31:38 ia804105.us.archive.org smartd[57674]: Device: /dev/sdal [SAT], enabled SMART Automatic Offline Testing. Jul 17 17:31:38 ia804105.us.archive.org smartd[57674]: Device: /dev/sdal [SAT], is SMART capable. Adding to "monitor" list. Jul 17 17:31:38 ia804105.us.archive.org smartd[57674]: Monitoring 38 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices Jul 17 17:32:59 ia804105.us.archive.org systemd[1]: smartmontools.service: start operation timed out. Terminating. Jul 17 17:32:59 ia804105.us.archive.org systemd[1]: smartmontools.service: Failed with result 'timeout'. Jul 17 17:32:59 ia804105.us.archive.org systemd[1]: Failed to start Self Monitoring and Reporting Technology (SMART) Daemon. per the suggestion from the mailing list thread at https://sourceforge.net/p/smartmontools/mailman/message/33725719/ and the referenced upstream service file at https://www.smartmontools.org/export/4048/trunk/smartmontools/smartd.service.in i used an override file to switch to Type=simple (the default afaict) and that allows the service to start. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: smartmontools 7.1-1build1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jul 17 11:50:19 2020 ProcEnviron: SHELL=/bin/zsh LANG=en_US.UTF-8 TERM=rxvt-unicode-256color XDG_RUNTIME_DIR= PATH=(custom, user) SourcePackage: smartmontools UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.smartd.conf: DEVICESCAN \ -d sat -d removable -H -l error -l selftest -f -t \ -n standby -a -o on -S on \ -s (O/../.././(00|06|12|18)|S/../.././06|L/../../2/06) mtime.conffile..etc.default.smartmontools: 2020-07-17T10:29:30.610929 mtime.conffile..etc.smartd.conf: 2020-07-17T10:29:29.786929 ** Affects: smartmontools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Patch added: "smartmontools_service.patch" https://bugs.launchpad.net/bugs/1888009/+attachment/5393625/+files/smartmontools_service.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888009 Title: smartmontools.service: start operation timed out. Terminating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1888009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633098] Re: override of APT_LISTCHANGES_FRONTEND can/should be removed
** Changed in: unattended-upgrades (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633098 Title: override of APT_LISTCHANGES_FRONTEND can/should be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1633098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786910] Re: Latest patch breaks command line 'restart all'
did some quick testing (also on a single host) and the "Invalid action" error is not appearing with the 1:5.16-2ubuntu0.2 version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786910 Title: Latest patch breaks command line 'restart all' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monit/+bug/1786910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633098] Re: override of APT_LISTCHANGES_FRONTEND can/should be removed
the linked comment seems to describe a different circumstance than the comments in setup_apt_listchanges (which does not mention the pager frontend). debian bug 579733 is also focused on mail behavior rather than pager. that said, i can confirm that u-u does NOT hang with the above patch applied and "frontend = pager" in /etc/apt/listchanges.conf. the apt- listchanges output ends up in /var/log/unattended-upgrades/unattended- upgrades-dpkg.log. when "confirm=1" is set in listchanges.conf then u-u does stop and wait for confirmation. however, in my testing this happens if either the mail or pager frontend is chosen and even when the patch is reverted (so afaict the code in question was not meant to address this condition). if the (self-inflicted) conflict between requiring confirmation on upgrade while using unattended-upgrades is the concern, then it would seem that overriding the confirmation would be more appropriate than changing the frontend. thanks! please let me know if additional information is required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633098 Title: override of APT_LISTCHANGES_FRONTEND can/should be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1633098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691899] Re: regression: the 4.8 hwe kernel does not create the /sys/block/*/device/enclosure_device:* symlinks
** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691899 Title: regression: the 4.8 hwe kernel does not create the /sys/block/*/device/enclosure_device:* symlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691899] Re: regression: the 4.8 hwe kernel does not create the /sys/block/*/device/enclosure_device:* symlinks
hi - any update on including this fix in the next release of the 4.8 series? thanks in advance... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691899 Title: regression: the 4.8 hwe kernel does not create the /sys/block/*/device/enclosure_device:* symlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1691899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691899] Re: regression: the 4.8 hwe kernel does not create the /sys/block/*/device/enclosure_device:* symlinks
it looks like linux-image-4.8.0-52 has already been released. do you think this fix might make it into the -53 version? thanks again... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691899 Title: regression: the 4.8 hwe kernel does not create the /sys/block/*/device/enclosure_device:* symlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1691899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691899] Re: regression: the 4.8 hwe kernel does not create the /sys/block/*/device/enclosure_device:* symlinks
yep, looks good. thank you for the quick turnaround! % uname -a Linux ia805401.us.archive.org 4.8.0-52-generic #55~lp1691899 SMP Fri May 19 18:09:12 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux % ls -l /sys/block/*/device/enclosure* lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdaa/device/enclosure_device:013 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/013/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdab/device/enclosure_device:015 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/015/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdac/device/enclosure_device:016 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/016/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdad/device/enclosure_device:017 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/017/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdaf/device/enclosure_device:019 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/019/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdag/device/enclosure_device:020 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/020/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdah/device/enclosure_device:021 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/021/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdai/device/enclosure_device:022 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/022/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdaj/device/enclosure_device:023 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/023/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdc/device/enclosure_device:000 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/000/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdd/device/enclosure_device:001 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/001/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sde/device/enclosure_device:002 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/002/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdf/device/enclosure_device:003 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/003/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdg/device/enclosure_device:004 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/004/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdh/device/enclosure_device:005 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/005/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdi/device/enclosure_device:006 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/006/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdj/device/enclosure_device:007 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/007/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdk/device/enclosure_device:008 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/008/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdl/device/enclosure_device:010 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/010/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdm/device/enclosure_device:011 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/011/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdn/device/enclosure_device:000 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/000/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdo/device/enclosure_device:001 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/001/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdp/device/enclosure_device:002 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/002/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdq/device/enclosure_device:003 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/003/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdr/device/enclosure_device:004 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/004/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sds/device/enclosure_device:005 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/005/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdt/device/enclosure_device:006 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/006/ lrwxrwxrwx 1 root root 0 May 19 12:01 /sys/block/sdu/device/
[Bug 1691899] Re: regression: the 4.8 hwe kernel does not create the /sys/block/*/device/enclosure_device:* symlinks
details can be found at: * https://bugzilla.redhat.com/show_bug.cgi?id=1394089 * https://bugzilla.redhat.com/show_bug.cgi?id=1427815 ** Bug watch added: Red Hat Bugzilla #1394089 https://bugzilla.redhat.com/show_bug.cgi?id=1394089 ** Bug watch added: Red Hat Bugzilla #1427815 https://bugzilla.redhat.com/show_bug.cgi?id=1427815 ** Patch added: "commit 9373eba6cfae48911b977d14323032cd5d161aae upstream." https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1691899/+attachment/4879377/+files/4.9-109-130-scsi-ses-Fix-SAS-device-detection-in-enclosure.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691899 Title: regression: the 4.8 hwe kernel does not create the /sys/block/*/device/enclosure_device:* symlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1691899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691899] [NEW] regression: the 4.8 hwe kernel does not create the /sys/block/*/device/enclosure_device:* symlinks
Public bug reported: the 4.8 kernel does not create symlinks/sys/block/*/device/enclosure_device:*. this appears to have been resolved in 4.9+ what you expected to happen: with the ga 4.4 and hwe-edge 4.10 kernels the symlinks are created % ls -l /sys/block/*/device/enclosure* lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdaa/device/enclosure_device:013 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/013/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdab/device/enclosure_device:015 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/015/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdac/device/enclosure_device:016 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/016/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdad/device/enclosure_device:017 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/017/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdaf/device/enclosure_device:019 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/019/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdag/device/enclosure_device:020 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/020/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdah/device/enclosure_device:021 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/021/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdai/device/enclosure_device:022 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/022/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdaj/device/enclosure_device:023 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/023/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdc/device/enclosure_device:000 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/000/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdd/device/enclosure_device:001 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/001/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sde/device/enclosure_device:002 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/002/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdf/device/enclosure_device:003 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/003/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdg/device/enclosure_device:004 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/004/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdh/device/enclosure_device:005 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/005/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdi/device/enclosure_device:006 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/006/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdj/device/enclosure_device:007 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/007/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdk/device/enclosure_device:008 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/008/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdl/device/enclosure_device:010 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/010/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdm/device/enclosure_device:011 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/011/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdn/device/enclosure_device:000 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/000/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdo/device/enclosure_device:001 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/001/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdp/device/enclosure_device:002 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/002/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdq/device/enclosure_device:003 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/003/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdr/device/enclosure_device:004 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/004/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sds/device/enclosure_device:005 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/005/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdt/device/enclosure_device:006 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/006/ lrwxrwxrwx
[Bug 1633098] [NEW] override of APT_LISTCHANGES_FRONTEND can/should be removed
Public bug reported: unattended-upgrades overrides the setting of APT_LISTCHANGES_FRONTEND. per the comments, this was done at a time when apt-listchanges would "always send a mail if there is a mail address set in the config regardless of the frontend used." this is no longer the case and this (now unnecessary) local override of APT_LISTCHANGES_FRONTEND can cause confusion when apt-listchanges appears to ignore its configured settings. What I expected to happen: i expected apt-listchanges to conform to its configuration. setting the "none" frontend in /etc/apt/listchanges.conf should ensure it "Does nothing" as per the manpage. What happened instead: unattended-upgrades does not respect the frontend setting, essentially now replicating the bad behavior this snippet was originally meant to workaround (i.e., mail is currently sent when email_address is set but frontend=none). with the attached patch the frontend specified in listchanges.conf is no longer unnecessarily overridden. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 13 07:07:44 2016 JournalErrors: -- Logs begin at Tue 2016-10-11 08:02:03 PDT, end at Thu 2016-10-13 07:06:49 PDT. -- Oct 11 08:13:30 hostname systemd-tmpfiles[10524]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Oct 12 08:13:50 hostname systemd-tmpfiles[25099]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Patch added: "remove the APT_LISTCHANGES_FRONTEND override" https://bugs.launchpad.net/bugs/1633098/+attachment/4760432/+files/unattended-upgrade_APT_LISTCHANGES_FRONTEND.patch ** Description changed: unattended-upgrades overrides the setting of APT_LISTCHANGES_FRONTEND. per the comments, this was done at a time when apt-listchanges would "always send a mail if there is a mail address set in the config regardless of the frontend used." this is no longer the case and this (now unnecessary) local override of APT_LISTCHANGES_FRONTEND can cause confusion when apt-listchanges appears to ignore its configured settings. What I expected to happen: i expected apt-listchanges to conform to its configuration. setting the "none" frontend in /etc/apt/listchanges.conf should ensure it "Does nothing" as per the manpage. What happened instead: unattended-upgrades does not respect the frontend setting, essentially now replicating the bad behavior this snippet was originally meant to - workaround. with the attached patch the frontend specified in + workaround (i.e., mail is currently sent when email_address is set but + frontend=none). with the attached patch the frontend specified in listchanges.conf is no longer unnecessarily overridden. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 13 07:07:44 2016 JournalErrors: - -- Logs begin at Tue 2016-10-11 08:02:03 PDT, end at Thu 2016-10-13 07:06:49 PDT. -- - Oct 11 08:13:30 hostname systemd-tmpfiles[10524]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. - Oct 12 08:13:50 hostname systemd-tmpfiles[25099]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. + -- Logs begin at Tue 2016-10-11 08:02:03 PDT, end at Thu 2016-10-13 07:06:49 PDT. -- + Oct 11 08:13:30 hostname systemd-tmpfiles[10524]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. + Oct 12 08:13:50 hostname systemd-tmpfiles[25099]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. PackageArchitecture: all ProcEnviron: - TERM=rxvt-unicode-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/zsh + TERM=rxvt-unicode-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/zsh SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633098 Title: override of APT_LISTCHANGES_FRONTEND can/should be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bu
[Bug 837385] Re: hostname from dhcp STILL not set, despite multiple ubuntu fixes and bug reports
it appears that this is resolved in xenial/16.04. booting with both an empty /etc/hostname and no /etc/hostname result in the system picking up its dhcp-assigned hostname. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/837385 Title: hostname from dhcp STILL not set, despite multiple ubuntu fixes and bug reports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/837385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598326] additional debug info
my initial problem was that i'd not been including the 'language-pack-en' but it still doesn't seem to be working as expected. attempting to noninteractively reconfigure locales *un*sets locales/locales_to_be_generated (full output in noninteractive-dpkg-reconfigure+debug.log): ~# debconf-show locales * locales/locales_to_be_generated: en_US.UTF-8 UTF-8 * locales/default_environment_locale: en_US.UTF-8 ~# egrep -v ^\# /etc/locale.gen [intentionally blank lines] ~# cat /etc/default/locale # File generated by update-locale ~# DEBIAN_FRONTEND=noninteractive /usr/sbin/dpkg-reconfigure locales Generating locales (this might take a while)... en_AG.UTF-8... done en_AU.UTF-8... done en_BW.UTF-8... done en_CA.UTF-8... done en_DK.UTF-8... done en_GB.UTF-8... done en_HK.UTF-8... done en_IE.UTF-8... done en_IN.UTF-8... done en_NG.UTF-8... done en_NZ.UTF-8... done en_PH.UTF-8... done en_SG.UTF-8... done en_US.UTF-8... done en_ZA.UTF-8... done en_ZM.UTF-8... done en_ZW.UTF-8... done Generation complete. ~# debconf-show locales * locales/locales_to_be_generated: * locales/default_environment_locale: en_US.UTF-8 ~# egrep -v ^\# /etc/locale.gen ~# cat /etc/default/locale # File generated by update-locale LANG=en_US.UTF-8 notably, when `/usr/sbin/dpkg-reconfigure locales` is run *interactively* in place of the noninteractive call, "en_US.UTF-8 UTF-8" is *not* preselected; selecting it and completing the reconfigure results in what i would expect (full output in interactive-dpkg-reconfigure+debug.log): ~# debconf-show locales * locales/locales_to_be_generated: en_US.UTF-8 UTF-8 * locales/default_environment_locale: en_US.UTF-8 ~# egrep -v ^\# /etc/locale.gen ~# cat /etc/default/locale # File generated by update-locale ~# /usr/sbin/dpkg-reconfigure locales Generating locales (this might take a while)... en_AG.UTF-8... done en_AU.UTF-8... done en_BW.UTF-8... done en_CA.UTF-8... done en_DK.UTF-8... done en_GB.UTF-8... done en_HK.UTF-8... done en_IE.UTF-8... done en_IN.UTF-8... done en_NG.UTF-8... done en_NZ.UTF-8... done en_PH.UTF-8... done en_SG.UTF-8... done en_US.UTF-8... done en_ZA.UTF-8... done en_ZM.UTF-8... done en_ZW.UTF-8... done Generation complete. ~# debconf-show locales * locales/default_environment_locale: en_US.UTF-8 * locales/locales_to_be_generated: en_US.UTF-8 UTF-8 ~# egrep -v ^\# /etc/locale.gen en_US.UTF-8 UTF-8 ~# cat /etc/default/locale # File generated by update-locale LANG=en_US.UTF-8 it's unclear to me why the run of `/var/lib/dpkg/info/locales.config reconfigure 2.23-0ubuntu3` behaves as it does, but something appears awry. after finding /etc/locale.gen empty, the locales.config script (via GEN_LOCALES and SELECTED_LOCALES variables) appears to *un*set locales/locales_to_be_generated. similarly, it seems that the script tries to substitute the DEFAULT_LOCALES that it finds (from on-disk files) into locales/default_environment_locale (cf. the debconf error above) without regard to its existing value. tia! andy -- andrew bezella Internet Archive ** Attachment added: "interactive-dpkg-reconfigure+debug.log" https://bugs.launchpad.net/bugs/1598326/+attachment/4698959/+files/interactive-dpkg-reconfigure+debug.log ** Attachment added: "noninteractive-dpkg-reconfigure+debug.log" https://bugs.launchpad.net/bugs/1598326/+attachment/4698960/+files/noninteractive-dpkg-reconfigure+debug.log ** Changed in: glibc (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598326 Title: preseeded value of "locales/locales_to_be_generated" lost on `locales.postinst configure` action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1598326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598326] Re: preseeded value of "locales/locales_to_be_generated" lost on `locales.postinst configure` action
i am back to believing this is a bug, as others have found the same problem, cf. https://lists.uni-koeln.de/pipermail/linux- fai/2016-July/011398.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598326 Title: preseeded value of "locales/locales_to_be_generated" lost on `locales.postinst configure` action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1598326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598326] Re: preseeded value of "locales/locales_to_be_generated" lost on `locales.postinst configure` action
others have found the same problem, cf. https://lists.uni- koeln.de/pipermail/linux-fai/2016-July/011398.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598326 Title: preseeded value of "locales/locales_to_be_generated" lost on `locales.postinst configure` action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1598326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598326] Re: preseeded value of "locales/locales_to_be_generated" lost on `locales.postinst configure` action
i'm much less clear on this now than i was yesterday. continuing to investigate. ** Changed in: glibc (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/glibc/+question/295923 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598326 Title: preseeded value of "locales/locales_to_be_generated" lost on `locales.postinst configure` action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1598326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598326] [NEW] preseeded value of "locales/locales_to_be_generated" lost on `locales.postinst configure` action
Public bug reported:
in attempting to track down why locales are unset, i noticed this issue
(perhaps related to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=684134). running
`/var/lib/dpkg/info/locales.postinst configure` appears to unset the
seeded value of locales/locales_to_be_generated, but only if that value
was set via noninteractive means.
to reproduce (1):
# debconf-set-selections /tmp/locales.debconf (2)
# debconf-show locales
* locales/default_environment_locale: en_US.UTF-8
* locales/locales_to_be_generated: en_US.UTF-8 UTF-8
# /var/lib/dpkg/info/locales.postinst configure
Generating locales (this might take a while)...
Generation complete.
# debconf-show locales
* locales/locales_to_be_generated:
* locales/default_environment_locale: en_US.UTF-8
# cat /etc/default/locale
# File generated by update-locale
# grep -v ^\# /etc/locale.gen
[empty and locale errs continue]
on the other hand, setting the same value via an interactive `dpkg-reconfigure
locales` works:
# debconf-show locales
* locales/default_environment_locale: en_US.UTF-8
* locales/locales_to_be_generated: en_US.UTF-8 UTF-8
# dpkg-reconfigure locales (nb. en_US.UTF-8 UTF-8 is NOT pre-selected, but once
manually selected and dpkg-reconfigure has finished the locales errors are gone)
Generating locales (this might take a while)...
en_US.UTF-8... done
Generation complete.
# grep -v ^\# /etc/locale.gen
en_US.UTF-8 UTF-8
# cat /etc/default/locale
# File generated by update-locale
LANG=en_US.UTF-8
when i watch the postinst script it can be seen in an unsuccessful run that
`db_get locales/locales_to_be_generated` (line 19) gives an empty RET value:
+ db_get locales/locales_to_be_generated
+ _db_cmd GET locales/locales_to_be_generated
+ _db_internal_IFS=
+ IFS=
+ printf %s\n GET locales/locales_to_be_generated
+ IFS=
+ IFS=
read -r _db_internal_line
+ RET=
+ return 0
+ SELECTED_LOCALES=
+ echo
+ sed -e s/, /\n/g
+ SELECTED_LOCALES=
the immediately prior `db_get locales/default_environment_locale` (line
18) gives RET=en_US.UTF-8 as expected.
when locales/locales_to_be_generated has been set interactively,
RET=en_US.UTF-8 UTF-8, also as expected.
setting the value via ansible's debconf module also results in failure.
than you for your time and effort in supporting ubuntu.
andy
1) as the locales are not configured at this point, most debconf commands
result in an additional error of:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
i have left these out of this description but included them in the full
output attachment
2) see attached, generated via `debconf-get-selections` on another host
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: locales 2.23-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sat Jul 2 00:08:05 2016
PackageArchitecture: all
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: glibc
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
** Attachment added: "locales.debconf"
https://bugs.launchpad.net/bugs/1598326/+attachment/4693895/+files/locales.debconf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598326
Title:
preseeded value of "locales/locales_to_be_generated" lost on
`locales.postinst configure` action
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1598326/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598326] Re: preseeded value of "locales/locales_to_be_generated" lost on `locales.postinst configure` action
full output ** Attachment added: "includes perl errors re: locale unset" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1598326/+attachment/4693898/+files/full.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598326 Title: preseeded value of "locales/locales_to_be_generated" lost on `locales.postinst configure` action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1598326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514485] Re: [SRU] cloud-init should use "nofail" instead of "bootwait"
apologies for commenting on a resolved bug, but adding another FTR comment: it is my understanding that, contrary to statements above, the upstart-specific "nobootwait" is/was not equivalent to the util-linux defined "nofail." see e.g., https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/610869 for some differences in behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1514485 Title: [SRU] cloud-init should use "nofail" instead of "bootwait" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1514485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1021506] Re: dirinstall on 12.04 appears to require `fai-divert -a /sbin/initctl`
updated patch for fai 5.0.3 ** Patch added: "add /sbin/initctl to the list of automatic diversions in updatebase." https://bugs.launchpad.net/ubuntu/+source/fai/+bug/1021506/+attachment/4629809/+files/fai-divert_initctl.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021506 Title: dirinstall on 12.04 appears to require `fai-divert -a /sbin/initctl` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fai/+bug/1021506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1100336] Re: make-fai-nfsroot installs debian/squeeze by default
i attempted to make xenial my nfsroot w/fai 5.0.3. i was unsuccessful due to the dracut requirement. as suggested by a launchpad bug, i found the package(s) that depended on initramfs-tools and rebuilt to depend on linux-initramfs-tool instead (which dracut Provides). but once that was done it turned out that (iirc) ubuntu's initramfs management didn't actually work w/dracut in place. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1100336 Title: make-fai-nfsroot installs debian/squeeze by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fai/+bug/1100336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1040254] Re: disk device-paths using e.g., /dev/disk/by-id not supported (contrary to manpage)
this patch appears to have been accepted upstream, cf. https://github.com/faiproject/fai/pull/22 ** Changed in: fai (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1040254 Title: disk device-paths using e.g., /dev/disk/by-id not supported (contrary to manpage) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fai/+bug/1040254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450667] Re: timezone not cleared despite "env_keep -= TZ" in /etc/sudoers
** Description changed:
the sanity check of the TZ env variable implemented in
1.8.9p5-1ubuntu1.1 to address CVE-2014-9680 apparently has the side
effect of carrying forward the TZ variable despite explicit removal in
/etc/sudoers. 1.8.9p5-1ubuntu1 does not exhibit this behavior.
% fgrep env_ /etc/sudoers
Defaults env_reset
Defaults env_keep+="JAVA_HOME"
Defaults env_keep+="SSH_AUTH_SOCK"
Defaults env_keep-="TZ"
with 1.8.9p5-1ubuntu1:
% sudo sudo -V
Sudo version 1.8.9p5
Configure options: --prefix=/usr -v --with-all-insults --with-pam --with-fqdn
--with-logging=syslog --with-logfac=authpriv --with-env-editor
--with-editor=/usr/bin/editor --with-timeout=15 --with-password-timeout=0
--with-passprompt=[sudo] password for %p: --without-lecture --with-tty-tickets
--disable-root-mailer --enable-admin-flag --with-sendmail=/usr/sbin/sendmail
--with-timedir=/var/lib/sudo --mandir=/usr/share/man --libexecdir=/usr/lib/sudo
--with-sssd --with-sssd-lib=/usr/lib/x86_64-linux-gnu --with-selinux
Sudoers policy plugin version 1.8.9p5
Sudoers file grammar version 43
Sudoers path: /etc/sudoers
Authentication methods: 'pam'
Syslog facility if syslog is being used for logging: authpriv
Syslog priority to use when user authenticates successfully: notice
Syslog priority to use when user authenticates unsuccessfully: alert
Send mail if the user is not in sudoers
Lecture user the first time they run sudo
Require users to authenticate by default
Root may run sudo
Always set $HOME to the target user's home directory
Allow some information gathering to give useful error messages
Require fully-qualified hostnames in the sudoers file
Visudo will honor the EDITOR environment variable
Set the LOGNAME and USER environment variables
Length at which to wrap log file lines (0 for no wrap): 80
Authentication timestamp timeout: 60.0 minutes
Password prompt timeout: 0.0 minutes
Number of tries to enter a password: 3
Umask to use or 0777 to use user's: 022
Path to mail program: /usr/sbin/sendmail
Flags for mail program: -t
Address to send mail to: root
Subject line for mail messages: *** SECURITY information for %h ***
Incorrect password message: Sorry, try again.
Path to authentication timestamp dir: /var/lib/sudo
- Default password prompt: [sudo] password for %p:
+ Default password prompt: [sudo] password for %p:
Default user to run commands as: root
Path to the editor for use by visudo: /usr/bin/editor
When to require a password for 'list' pseudocommand: any
When to require a password for 'verify' pseudocommand: all
File descriptors >= 3 will be closed before executing a command
Reset the environment to a default set of variables
Environment variables to check for sanity:
- TERM
- LINGUAS
- LC_*
- LANGUAGE
- LANG
- COLORTERM
+ TERM
+ LINGUAS
+ LC_*
+ LANGUAGE
+ LANG
+ COLORTERM
Environment variables to remove:
- RUBYOPT
- RUBYLIB
- PYTHONUSERBASE
- PYTHONINSPECT
- PYTHONPATH
- PYTHONHOME
- TMPPREFIX
- ZDOTDIR
- READNULLCMD
- NULLCMD
- FPATH
- PERL5DB
- PERL5OPT
- PERL5LIB
- PERLLIB
- PERLIO_DEBUG
- JAVA_TOOL_OPTIONS
- SHELLOPTS
- GLOBIGNORE
- PS4
- BASH_ENV
- ENV
- TERMCAP
- TERMPATH
- TERMINFO_DIRS
- TERMINFO
- _RLD*
- LD_*
- PATH_LOCALE
- NLSPATH
- HOSTALIASES
- RES_OPTIONS
- LOCALDOMAIN
- CDPATH
- IFS
+ RUBYOPT
+ RUBYLIB
+ PYTHONUSERBASE
+ PYTHONINSPECT
+ PYTHONPATH
+ PYTHONHOME
+ TMPPREFIX
+ ZDOTDIR
+ READNULLCMD
+ NULLCMD
+ FPATH
+ PERL5DB
+ PERL5OPT
+ PERL5LIB
+ PERLLIB
+ PERLIO_DEBUG
+ JAVA_TOOL_OPTIONS
+ SHELLOPTS
+ GLOBIGNORE
+ PS4
+ BASH_ENV
+ ENV
+ TERMCAP
+ TERMPATH
+ TERMINFO_DIRS
+ TERMINFO
+ _RLD*
+ LD_*
+ PATH_LOCALE
+ NLSPATH
+ HOSTALIASES
+ RES_OPTIONS
+ LOCALDOMAIN
+ CDPATH
+ IFS
Environment variables to preserve:
- SSH_AUTH_SOCK
- JAVA_HOME
- XAUTHORIZATION
- XAUTHORITY
- PS2
- PS1
- PATH
- LS_COLORS
- KRB5CCNAME
- HOSTNAME
- HOME
- DISPLAY
- COLORS
+ SSH_AUTH_SOCK
+ JAVA_HOME
+ XAUTHORIZATION
+ XAUTHORITY
+ PS2
+ PS1
+ PATH
+ LS_COLORS
+ KRB5CCNAME
+ HOSTNAME
+ HOME
+ DISPLAY
+ COLORS
Locale to use while parsing sudoers: C
Directory in which to store input/output logs: /var/log/sudo-io
File in which to store the input/output log: %{seq}
Add an entry to the utmp/utmpx file when allocating a pty
PAM service name to use
PAM service name to use for login shells
Create a new PAM session for the command to run in
Maximum I/O log sequence number: 0
Local IP address and netmask pairs:
- 207.241.227.232/255.255.248.0
- fe80::225:90ff:fee4:aef0/:::::
- fe80::225:90ff:fee4:aef0/:::
[Bug 1450667] [NEW] timezone not cleared despite "env_keep -= TZ" in /etc/sudoers
Public bug reported:
the sanity check of the TZ env variable implemented in
1.8.9p5-1ubuntu1.1 to address CVE-2014-9680 apparently has the side
effect of carrying forward the TZ variable despite explicit removal in
/etc/sudoers. 1.8.9p5-1ubuntu1 does not exhibit this behavior.
% fgrep env_ /etc/sudoers
Defaults env_reset
Defaults env_keep+="JAVA_HOME"
Defaults env_keep+="SSH_AUTH_SOCK"
Defaults env_keep-="TZ"
with 1.8.9p5-1ubuntu1:
% sudo sudo -V
Sudo version 1.8.9p5
Configure options: --prefix=/usr -v --with-all-insults --with-pam --with-fqdn
--with-logging=syslog --with-logfac=authpriv --with-env-editor
--with-editor=/usr/bin/editor --with-timeout=15 --with-password-timeout=0
--with-passprompt=[sudo] password for %p: --without-lecture --with-tty-tickets
--disable-root-mailer --enable-admin-flag --with-sendmail=/usr/sbin/sendmail
--with-timedir=/var/lib/sudo --mandir=/usr/share/man --libexecdir=/usr/lib/sudo
--with-sssd --with-sssd-lib=/usr/lib/x86_64-linux-gnu --with-selinux
Sudoers policy plugin version 1.8.9p5
Sudoers file grammar version 43
Sudoers path: /etc/sudoers
Authentication methods: 'pam'
Syslog facility if syslog is being used for logging: authpriv
Syslog priority to use when user authenticates successfully: notice
Syslog priority to use when user authenticates unsuccessfully: alert
Send mail if the user is not in sudoers
Lecture user the first time they run sudo
Require users to authenticate by default
Root may run sudo
Always set $HOME to the target user's home directory
Allow some information gathering to give useful error messages
Require fully-qualified hostnames in the sudoers file
Visudo will honor the EDITOR environment variable
Set the LOGNAME and USER environment variables
Length at which to wrap log file lines (0 for no wrap): 80
Authentication timestamp timeout: 60.0 minutes
Password prompt timeout: 0.0 minutes
Number of tries to enter a password: 3
Umask to use or 0777 to use user's: 022
Path to mail program: /usr/sbin/sendmail
Flags for mail program: -t
Address to send mail to: root
Subject line for mail messages: *** SECURITY information for %h ***
Incorrect password message: Sorry, try again.
Path to authentication timestamp dir: /var/lib/sudo
Default password prompt: [sudo] password for %p:
Default user to run commands as: root
Path to the editor for use by visudo: /usr/bin/editor
When to require a password for 'list' pseudocommand: any
When to require a password for 'verify' pseudocommand: all
File descriptors >= 3 will be closed before executing a command
Reset the environment to a default set of variables
Environment variables to check for sanity:
TERM
LINGUAS
LC_*
LANGUAGE
LANG
COLORTERM
Environment variables to remove:
RUBYOPT
RUBYLIB
PYTHONUSERBASE
PYTHONINSPECT
PYTHONPATH
PYTHONHOME
TMPPREFIX
ZDOTDIR
READNULLCMD
NULLCMD
FPATH
PERL5DB
PERL5OPT
PERL5LIB
PERLLIB
PERLIO_DEBUG
JAVA_TOOL_OPTIONS
SHELLOPTS
GLOBIGNORE
PS4
BASH_ENV
ENV
TERMCAP
TERMPATH
TERMINFO_DIRS
TERMINFO
_RLD*
LD_*
PATH_LOCALE
NLSPATH
HOSTALIASES
RES_OPTIONS
LOCALDOMAIN
CDPATH
IFS
Environment variables to preserve:
SSH_AUTH_SOCK
JAVA_HOME
XAUTHORIZATION
XAUTHORITY
PS2
PS1
PATH
LS_COLORS
KRB5CCNAME
HOSTNAME
HOME
DISPLAY
COLORS
Locale to use while parsing sudoers: C
Directory in which to store input/output logs: /var/log/sudo-io
File in which to store the input/output log: %{seq}
Add an entry to the utmp/utmpx file when allocating a pty
PAM service name to use
PAM service name to use for login shells
Create a new PAM session for the command to run in
Maximum I/O log sequence number: 0
Local IP address and netmask pairs:
207.241.227.232/255.255.248.0
fe80::225:90ff:fee4:aef0/:::::
fe80::225:90ff:fee4:aef0/:::::
Sudoers I/O plugin version 1.8.9p5
% sudo env | g TZ
[no output]
with sudo 1.8.9p5-1ubuntu1.1:
% sudo sudo -V
Sudo version 1.8.9p5
Configure options: --prefix=/usr -v --with-all-insults --with-pam --with-fqdn
--with-logging=syslog --with-logfac=authpriv --with-env-editor
--with-editor=/usr/bin/editor --with-timeout=15 --with-password-timeout=0
--with-passprompt=[sudo] password for %p: --without-lecture --with-tty-tickets
--disable-root-mailer --enable-admin-flag --with-sendmail=/usr/sbin/sendmail
--with-timedir=/var/lib/sudo --mandir=/usr/share/man --libexecdir=/usr/lib/sudo
--with-sssd --with-sssd-lib=/usr/lib/x86_64-linux-gnu --with-selinux
Sudoers policy plugin version 1.8.9p5
Sudoers file grammar version 43
Sudoers path: /etc/sudoers
Authentication methods: 'pam'
Syslog facility if syslog is bein
[Bug 1358226] Re: kernel and lockd xprt_adjust_timeout rq_timeout
doesn't appear to have made it into 3.19-rc3 but beyond that i don't have any information other than what is in http://www.spinics.net/lists /linux-nfs/msg48569.html (patch appears to be from and signed off by the NFS client maintainer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358226 Title: kernel and lockd xprt_adjust_timeout rq_timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358226] Re: kernel and lockd xprt_adjust_timeout rq_timeout
still no errors seen. i believe this patch addresses the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358226 Title: kernel and lockd xprt_adjust_timeout rq_timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358226] Re: kernel and lockd xprt_adjust_timeout rq_timeout
to apply to the 3.13 trusty kernel source i had to make a trivial edit to the patch (result attached). the power user/developer whose workflow typically triggers these messages has been using it and i have not yet seen the errors recur. ** Patch added: "initialising-nlmsvc_timeout.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358226/+attachment/4292577/+files/initialising-nlmsvc_timeout.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358226 Title: kernel and lockd xprt_adjust_timeout rq_timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1334858] Re: histreduceblanks can corrupt history
fwiw zsh 5.0.5-4ubuntu1~ubuntu14.04.1 from backports does not have this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1334858 Title: histreduceblanks can corrupt history To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1334858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383921] Re: kipmi0 process hangs with ipmitool
@arges - fyi the 20 nodes running 3.16.0-031600-generic #201408031935 have not encountered this problem in the ~2 weeks since install & reboot. @matt-jarvis - thx for the verification, i was out-of-office most of this week. i just took the 20 nodes that had been running 3.13.0-38.65-generic #lp1383921 and upgraded them to the -proposed kernel 3.13.0-41-generic #70-Ubuntu i will report back if they encounter ipmi issues but tend to concur that this is resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383921 Title: kipmi0 process hangs with ipmitool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358226] Re: kernel and lockd xprt_adjust_timeout rq_timeout
http://www.spinics.net/lists/linux-nfs/index.html#47942 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358226 Title: kernel and lockd xprt_adjust_timeout rq_timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358226] Re: kernel and lockd xprt_adjust_timeout rq_timeout
verified that messages persist w/3.18.0-031800rc6-generic #201411231935 and sent email to linux-...@vger.kernel.org ** Tags added: kernel-bug-reported-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358226 Title: kernel and lockd xprt_adjust_timeout rq_timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383921] Re: kipmi0 process hangs with ipmitool
@chris - i have 10 nodes that i just installed w/3.16.0-031600-generic #201408031935 i will increase that number tomorrow and update thisbug report if i see ipmi hangs on these hosts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383921 Title: kipmi0 process hangs with ipmitool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358226] Re: kernel and lockd xprt_adjust_timeout rq_timeout
@Joseph - rebooted into 3.18.0-031800rc5-generic #201411162035 and the msgs are still being logged: [ 231.437941] xprt_adjust_timeout: rq_timeout = 0! [ 231.437945] lockd: server nfs-home not responding, still trying [ 231.441744] lockd: server nfs-home OK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358226 Title: kernel and lockd xprt_adjust_timeout rq_timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383921] Re: kipmi0 process hangs with ipmitool
Matt - i am using the following (takes advantage of the ipmi_si module's hot
add and remove):
KIPMI_INST="0" # the web suggests this should increment but i've always seen 0
IPMI_PARAMS="$(cat /proc/ipmi/"${KIPMI_INST}"/params)"
sudo sh -c "echo "remove,${IPMI_PARAMS}" >
/sys/module/ipmi_si/parameters/hotmod"
sleep 5
sudo sh -c "echo "add,${IPMI_PARAMS}" > /sys/module/ipmi_si/parameters/hotmod"
takes a while (30min+) but that sounds better than "many many hours"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383921
Title:
kipmi0 process hangs with ipmitool
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383921/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383921] Re: kipmi0 process hangs with ipmitool
agreed. thank you for providing the test kernel! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383921 Title: kipmi0 process hangs with ipmitool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383921] Re: kipmi0 process hangs with ipmitool
the reboot was delayed but 7 of the 8 remaining hosts are now running the 3.13.0-38.65-generic #lp1383921 kernel. i have not yet seen a recurrence of the ipmi hang on any hosts running this version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383921 Title: kipmi0 process hangs with ipmitool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358226] Re: kernel and lockd xprt_adjust_timeout rq_timeout
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358226 Title: kernel and lockd xprt_adjust_timeout rq_timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358226] Re: kernel and lockd xprt_adjust_timeout rq_timeout
hello - per the above comments, i installed the 3.18.0-031800rc1-generic mainline kernel on the Ubuntu 14.04.1 LTS vm that we have been seeing log these errors. the error persists: Oct 29 22:30:37 vm1 kernel: [ 214.434104] xprt_adjust_timeout: rq_timeout = 0! Oct 29 22:30:37 vm1 kernel: [ 214.434110] lockd: server nfs-home not responding, still trying Oct 29 22:30:37 vm1 kernel: [ 214.728194] lockd: server nfs-home OK i tried to install the 3.18-rc2-utopic version but the result was unable to boot properly. it looks like the kernel modules were gzip'ed and trusty wasn't expecting this(?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358226 Title: kernel and lockd xprt_adjust_timeout rq_timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383921] Re: kipmi0 process hangs with ipmitool
the hot-add/hot-remove workaround was performed on a mishmash of hosts where this has crept up. the majority were precise hosts w/a 3.5.0 hwe kernel. one was trusty w/3.13.0-37-generic and the remainder are running locally built kernels from linux-source 3.13.0-35.62 w/the patch from lp#1368991 applied (these are the hosts i have to wait for reboot). thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383921 Title: kipmi0 process hangs with ipmitool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot
`mountall --verbose` log w/ip addr in fstab ** Attachment added: "mountall.log.ipaddr" https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242077/+files/mountall.log.ipaddr -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384502 Title: fstab entry for nfs /home fails to mount on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot
i also attempted a boot w/the nfs server's ip address instead of hostname (although technically i guess "nfs-home" is an alias). no change, /home was still not mounted automatically on boot by mountall. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384502 Title: fstab entry for nfs /home fails to mount on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384502] [NEW] fstab entry for nfs /home fails to mount on boot
Public bug reported: i'm uncertain exactly when this issue started as we use cfengine (verifies all expected mounts in place, manually mounts those that are not). from a note i have i believe it goes back as far as lucid. the symptom is that an /etc/fstab entry for an nfs-mounted /home is not mounted during the system boot. once the system is network-accessible, manually running `mount -tnfs -av` as root (or using cfengine or any number of other solutions) is sufficient. per lp#836533 i added "--verbose" to /etc/init/mountall.conf and will attach the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the smoking gun appears to be: mount.nfs: Failed to resolve server nfs-home: Temporary failure in name resolution ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mountall 2.53 ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8 Uname: Linux 3.13.0-38.65-generic x86_64 .run.mount.utab: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Oct 22 16:35:47 2014 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf nomdmonisw bootdegraded=true SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mountall (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384502 Title: fstab entry for nfs /home fails to mount on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot
** Attachment added: ".etc.network.interfaces" https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242075/+files/.etc.network.interfaces -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384502 Title: fstab entry for nfs /home fails to mount on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot
** Attachment added: ".var.log.upstart.mountall.log" https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242076/+files/.var.log.upstart.mountall.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384502 Title: fstab entry for nfs /home fails to mount on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383921] Re: kipmi0 process hangs with ipmitool
the workaround red hat suggests (forcing a hot-add/hot-remove cycle of the IPMI interface) appears to work. the same page claims the issue was resolved w/kernel-2.6.32-504.el6 from Errata RHSA-2014-1392 (released 2014-10-14). however, i'm unable to pinpoint the resolution in the release or technical notes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383921 Title: kipmi0 process hangs with ipmitool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383921] Re: kipmi0 process hangs with ipmitool
i've installed and rebooted 16 of the 14.04 hosts so that they are now running w/the 3.13.0-38.65-generic #lp1383921 kernel. i'll update the ticket if i see the symptoms recur on this set. the remaining 8 can't be rebooted until early next week. thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383921 Title: kipmi0 process hangs with ipmitool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383921] [NEW] kipmi0 process hangs with ipmitool
Public bug reported: we're in the process of migrating from 12.04 to 14.04 and are noticing a problem apparently related to the kernel and ipmi. after an indeterminate period of regular ipmi queries (e.g., nagios checks using ipmitool) the kipmi0 process pegs a cpu to ~100% usage and further ipmitool commands hang. the former is not a huge problem as the process is niced and its cpu usage can be limited using the /sys/module/ipmi_si/parameters/kipmid_max_busy_us interface. however, ipmitool's hanging severely degrades hardware monitoring. this problem initially reared its head in our enviroment on a handful of 12.04 hosts on which hwe kernels were installed. of the dozen deployed 14.04 hosts, four have started displaying these symptoms in the past week. all of the 12.04+hwe hosts were eventually affected; i believe that given enough time all of the 14.04 hosts would be, as well. a reboot clears it up until its recurrence. red hat has a bug logged that appears to match this: https://bugzilla.redhat.com/show_bug.cgi?id=1090619 unfortunately the work-around and proposed fix (from a duplicate bug) are currently non- public. it does look like they were able to identify the "ipmi: simplify locking" patch from commit id f60adf42ad55405d1b17e9e5c33fdb63f1eb8861 as the culprit. i have just finished building a kernel from linux-source-3.13.0=3.13.0-37.64 w/this patch reversed and will deploy it to see if the problem is alleviated. thank you for your time and effort. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 18 13:11 seq crw-rw 1 root audio 116, 33 Oct 18 13:11 timer AplayDevices: aplay: device_list:268: no soundcards found... ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 ArecordDevices: arecord: device_list:268: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Oct 21 12:55:43 2014 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro X8DT6 PciMultimedia: ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf nomdmonisw bootdegraded=true RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0c dmi.board.asset.tag: 1234567890 dmi.board.name: X8DT6 dmi.board.vendor: Supermicro dmi.board.version: 1234567890 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 1234567890 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0c:bd05/15/2012:svnSupermicro:pnX8DT6:pvr1234567890:rvnSupermicro:rnX8DT6:rvr1234567890:cvnSupermicro:ct17:cvr1234567890: dmi.product.name: X8DT6 dmi.product.version: 1234567890 dmi.sys.vendor: Supermicro ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383921 Title: kipmi0 process hangs with ipmitool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368991] Re: scsi_transport_sas: move bsg destructor into sas_rphy_remove
the kernel from linux-image-3.13.0-37-generic does indeed eliminate that error. thank you! tag updated to: verification-done-trusty ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368991 Title: scsi_transport_sas: move bsg destructor into sas_rphy_remove To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1368991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368991] [NEW] scsi_transport_sas: move bsg destructor into sas_rphy_remove
Public bug reported: hello - we had a freshly installed 14.04.1 server run into disk access issues after swapping out a hard drive. on further investigation, whenever a drive is pulled (on both the mptsas and mpt2sas systems i can test) the included warning is logged. the message is reproducible simply by pulling a drive, but i have not seen a recurrence of the issue where other drives become unresponsive. the attached upstream patch ( https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?id=6aa6caff30f5dcb9e55b03b9710c30b83750cae5 ) has been applied to both 3.12.23 and 3.14.7. when i applied it locally to the packaged linux-source the resulting kernel does not log these warnings. as it is a fairly trivial patch that has already been applied to other kernel versions upstream, i'm hopeful that it could be included as an SRU. thank you for your time and effort! andy kern :warn : [Thu Sep 11 14:50:08 2014] [ cut here ] kern :warn : [Thu Sep 11 14:50:08 2014] WARNING: CPU: 0 PID: 27756 at /build/buildd/linux-3.13.0/fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0() kern :warn : [Thu Sep 11 14:50:08 2014] sysfs group 81cabde0 not found for kobject 'end_device-6:1:23' kern :warn : [Thu Sep 11 14:50:08 2014] Modules linked in: drbd lru_cache libcrc32c 8021q garp mrp autofs4 ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsv3 sch_sfq nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache bridge stp llc bonding gpio_ich joydev intel_powerclamp dm_multipath coretemp scsi_dh kvm_intel kvm i7core_edac lpc_ich vhost_net edac_core ioatdma serio_raw vhost macvtap macvlan mac_hid ipmi_si ipmi_devintf usbkbd ses enclosure raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq raid1 igb raid0 mptsas i2c_algo_bit mptscsih ahci multipath dca ptp mptbase libahci psmouse linear scsi_transport_sas pps_core kern :warn : [Thu Sep 11 14:50:08 2014] CPU: 0 PID: 27756 Comm: kworker/u49:6 Not tainted 3.13.0-35-generic #62-Ubuntu kern :warn : [Thu Sep 11 14:50:08 2014] Hardware name: Supermicro X8DT3/X8DT3, BIOS 2.0a09/14/2010 kern :warn : [Thu Sep 11 14:50:08 2014] Workqueue: mpt/0 mptsas_firmware_event_work [mptsas] kern :warn : [Thu Sep 11 14:50:08 2014] 0009 880126a01ac8 8171e320 880126a01b10 kern :warn : [Thu Sep 11 14:50:08 2014] 880126a01b00 8106775d 81cabde0 kern :warn : [Thu Sep 11 14:50:08 2014] 880bf9410c10 880bf986e400 5003048000d2e6da 880126a01b60 kern :warn : [Thu Sep 11 14:50:08 2014] Call Trace: kern :warn : [Thu Sep 11 14:50:08 2014] [] dump_stack+0x45/0x56 kern :warn : [Thu Sep 11 14:50:08 2014] [] warn_slowpath_common+0x7d/0xa0 kern :warn : [Thu Sep 11 14:50:08 2014] [] warn_slowpath_fmt+0x4c/0x50 kern :warn : [Thu Sep 11 14:50:08 2014] [] ? sysfs_get_dirent_ns+0x4e/0x70 kern :warn : [Thu Sep 11 14:50:08 2014] [] sysfs_remove_group+0xc6/0xd0 kern :warn : [Thu Sep 11 14:50:08 2014] [] dpm_sysfs_remove+0x43/0x50 kern :warn : [Thu Sep 11 14:50:08 2014] [] device_del+0x45/0x1c0 kern :warn : [Thu Sep 11 14:50:08 2014] [] device_unregister+0x1e/0x60 kern :warn : [Thu Sep 11 14:50:08 2014] [] bsg_unregister_queue+0x5e/0xa0 kern :warn : [Thu Sep 11 14:50:08 2014] [] sas_rphy_free+0xac/0xe0 [scsi_transport_sas] kern :warn : [Thu Sep 11 14:50:08 2014] [] sas_port_delete+0x35/0x170 [scsi_transport_sas] kern :warn : [Thu Sep 11 14:50:08 2014] [] ? sysfs_remove_link+0x23/0x30 kern :warn : [Thu Sep 11 14:50:08 2014] [] mptsas_del_end_device+0x185/0x270 [mptsas] kern :warn : [Thu Sep 11 14:50:08 2014] [] mptsas_hotplug_work+0x1f4/0x9b0 [mptsas] kern :warn : [Thu Sep 11 14:50:08 2014] [] mptsas_firmware_event_work+0x3e1/0xf4c [mptsas] kern :warn : [Thu Sep 11 14:50:08 2014] [] ? native_sched_clock+0x13/0x80 kern :warn : [Thu Sep 11 14:50:08 2014] [] ? sched_clock+0x9/0x10 kern :warn : [Thu Sep 11 14:50:08 2014] [] ? sched_clock_cpu+0xb5/0x100 kern :warn : [Thu Sep 11 14:50:08 2014] [] ? __switch_to+0x126/0x4c0 kern :warn : [Thu Sep 11 14:50:08 2014] [] process_one_work+0x182/0x450 kern :warn : [Thu Sep 11 14:50:08 2014] [] worker_thread+0x121/0x410 kern :warn : [Thu Sep 11 14:50:08 2014] [] ? rescuer_thread+0x430/0x430 kern :warn : [Thu Sep 11 14:50:08 2014] [] kthread+0xd2/0xf0 kern :warn : [Thu Sep 11 14:50:08 2014] [] ? kthread_create_on_node+0x1c0/0x1c0 kern :warn : [Thu Sep 11 14:50:08 2014] [] ret_from_fork+0x7c/0xb0 kern :warn : [Thu Sep 11 14:50:08 2014] [] ? kthread_create_on_node+0x1c0/0x1c0 kern :warn : [Thu Sep 11 14:50:08 2014] ---[ end trace ad4ab1f037505d41 ]--- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11
[Bug 1003656] Re: bridge-utils/vlan udev hooks prevent execution of upstart hook, slowing down boot
looks good in my testing, too. with bridge-utils 1.5-2ubuntu7 the previously failing versions of my interfaces file work. our current live version of the interfaces continues to work, and a variant w/o the "pre- up" workaround from my initial report works as well. thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: bridge-utils/vlan udev hooks prevent execution of upstart hook, slowing down boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003656] Re: bond entries in /etc/network/interfaces fail without indent (when adding a bond the bridge fails to acquire a dhcp address)
can this move out of "Incomplete" status? as noted in my last comment the suggested fix appears to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: bond entries in /etc/network/interfaces fail without indent (when adding a bond the bridge fails to acquire a dhcp address) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1040254] Re: disk device-paths using e.g., /dev/disk/by-id not supported (contrary to manpage)
** Patch added: "fai-abspath.patch" https://bugs.launchpad.net/bugs/1040254/+attachment/3272256/+files/fai-abspath.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1040254 Title: disk device-paths using e.g., /dev/disk/by-id not supported (contrary to manpage) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fai/+bug/1040254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1040254] [NEW] disk device-paths using e.g., /dev/disk/by-id not supported (contrary to manpage)
Public bug reported: this was discussed in a pair of email threads some months ago. the patch (attached) from https://lists.uni-koeln.de/pipermail/linux- fai/2011-November/009355.html resolves the initial problem but does not address the further issues raised by the original poster in https://lists.uni-koeln.de/pipermail/linux-fai/2012-January/009448.html for my purposes this patch is sufficient. it does not looks to have been included in the 4.0.3 release. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fai-setup-storage 3.4.8ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-25.40-virtual 3.2.18 Uname: Linux 3.2.0-25-virtual x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Wed Aug 22 11:57:44 2012 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.utf8 SHELL=/usr/bin/zsh SourcePackage: fai UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fai (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1040254 Title: disk device-paths using e.g., /dev/disk/by-id not supported (contrary to manpage) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fai/+bug/1040254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
as a counter-example, our original deployment of eight 12.04 guests on 12.04 hosts were dropping off the network regularly. when the guests were reinstalled as 10.04 (on the same hosts, with the same workload) the problem did not recur. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
we had 12.04 vms experiencing these hangs regularly (sometimes only staying online for hours). after enabling vhost_net there was a period of weeks without issue but a few days one of them hung again with the same (or very similar) symptoms. an ifdown/ifup from within the guest brought it back on the network. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964989] Re: Ganeti initialization fails because PyCurl is linked against GnuTLS
i noticed a related failure and these errors after installing a ganeti host as precise and then attempting a master-failover to it. compiling the python-pycurl package against openssl and installing it on this new precise host allows master-failover to succeed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964989 Title: Ganeti initialization fails because PyCurl is linked against GnuTLS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ganeti/+bug/964989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1021506] Re: dirinstall on 12.04 appears to require `fai-divert -a /sbin/initctl`
** Patch added: "one-line change to /usr/lib/fai/updatebase to additionally divert /sbin/initctl" https://bugs.launchpad.net/bugs/1021506/+attachment/3214485/+files/fai_updatebase.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021506 Title: dirinstall on 12.04 appears to require `fai-divert -a /sbin/initctl` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fai/+bug/1021506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1021506] [NEW] dirinstall on 12.04 appears to require `fai-divert -a /sbin/initctl`
Public bug reported: i've been starting down the migration path from one lts release to another and trying out vm installs using fai 3.4.8ubuntu2 on precise hosts. the vms (ganeti-managed) are built using fai dirinstall. it appears that upstart in precise behaves differently than lucid with respect to chroots (looks like it started supporting chroot "sessions" in natty). in my testing this caused problems with both lucid and precise guests. when performing a lucid dirinstall i ended up w/atd and acpid processes running outside the chroot. with a precise dirinstall init complained that it had had its "Configuration directory deleted" (referencing the path to the chroot) and was left in a somewhat confused state, logging errs like: init: Failed to spawn network-interface (tap0) pre-start process: unable to execute: No such file or directory on vm bring-up. my workaround for this was to add a hook to updatebase containing: fai-divert -a /sbin/initctl should /sbin/initctl be added to the list of automatic diversions in updatebase? thank you. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fai-client 3.4.8ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jul 5 15:36:35 2012 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.utf8 SHELL=/usr/bin/zsh SourcePackage: fai UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.fai.fai.conf: [modified] mtime.conffile..etc.fai.fai.conf: 2012-06-19T10:48:39.830062 ** Affects: fai (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021506 Title: dirinstall on 12.04 appears to require `fai-divert -a /sbin/initctl` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fai/+bug/1021506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003656] Re: bond entries in /etc/network/interfaces fail without indent (when adding a bond the bridge fails to acquire a dhcp address)
it appears that the suggested edit to /lib/udev/rules.d/40-bridge- network-interface.rules fixed the problem i was seeing (don't have the vlan-related file on the system). thank you! the interfaces.fail and interfaces.nospc files both now work as expected, as does our standard interfaces configuration (the attached files were simplified versions of this). the whitespace/indentation question isn't a big deal, but it is a source of confusion. without your fix, the only version of the file that i could get to work was the interfaces.utf8 (comment #4). but it isn't strictly related to indentation: both interfaces.fail (using ascii whitespace indentation) and interfaces.nospc (no indentation) failed. for whatever reason, the apparent indentation using the non-printing characters in interfaces.utf8 worked. thanks again... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: bond entries in /etc/network/interfaces fail without indent (when adding a bond the bridge fails to acquire a dhcp address) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003656] Re: bond entries in /etc/network/interfaces fail without indent (when adding a bond the bridge fails to acquire a dhcp address)
thanks for looking into this. one thing worth noting is that the ascii version of the file attached in comment #5 (interfaces.fail) is indented but non-working. in fact, i only found that the utf8 version worked by accident; i cut'n'pasted what i had posted in the original report back into my interfaces and suddenly it worked! eventually i found the non- printing characters, but was left with no real understanding of the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: bond entries in /etc/network/interfaces fail without indent (when adding a bond the bridge fails to acquire a dhcp address) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
i believe that we're seeing the same problem with ganeti-managed kvm instances running on 12.04 utilizing a bridged network. in an initial deployment of 8 guests (also 12.04) we had half of them drop off the network within a few hours. there is a weak correlation between high network load in the guests and the network dropping. in some but not all cases from the kvm instance's console i was able to ifdown/ifup its interface and bring it back online. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/997978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932166] Re: ganeti2 can not determine kvm version
i can confirm that the patch allows an instance to start. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932166 Title: ganeti2 can not determine kvm version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ganeti/+bug/932166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003656] Re: when adding a bond the bridge fails to acquire a dhcp address
sorry, on closer inspection the interfaces.utf8 file has some non- printing characters. an interfaces file with no leading spaces still fails (attached). so, despite that red herring, i think the root problem remains. i'm presently unsure why the utf version of the file works. it doesn't seem to be simply ignoring the lines with the extra leading characters, because when i grep those lines out of the interfaces file and reboot the result is just an eth0 and eth1. it's also worth noting this is only a problem at boot-time. issuing an ifdown/ifup br0 once the system has killed off bridge-network-interface gives a working network. ** Attachment added: "interfaces.nospc" https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+attachment/3163770/+files/interfaces.nospc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: when adding a bond the bridge fails to acquire a dhcp address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003656] Re: when adding a bond the bridge fails to acquire a dhcp address
interfaces.fail does not work. as best i can tell the encoding is the only difference between them. ** Attachment added: "failing version; interfaces.fail: ASCII text" https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+attachment/3163697/+files/interfaces.fail -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: when adding a bond the bridge fails to acquire a dhcp address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003656] Re: when adding a bond the bridge fails to acquire a dhcp address
i believe that i've narrowed it down a bit. it seems improbable, but from what i can tell it is related to the character encoding of the file. i'm including 2 versions of the interfaces file. interfaces.utf8 works. ** Attachment added: "working version; interfaces.utf8: UTF-8 Unicode text" https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+attachment/3163691/+files/interfaces.utf8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: when adding a bond the bridge fails to acquire a dhcp address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003656] Re: when adding a bond the bridge fails to acquire a dhcp address
contents of /var/log/upstart attached. as a note our legacy naming for the bridge is "br_phys" so there is some output related to trials using that name instead of "br0". ** Attachment added: "_var_log_upstart.tar.gz" https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+attachment/3163676/+files/_var_log_upstart.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: when adding a bond the bridge fails to acquire a dhcp address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003656] Re: when adding a bond the bridge fails to acquire a dhcp address
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: when adding a bond the bridge fails to acquire a dhcp address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003656] [NEW] when adding a bond the bridge fails to acquire a dhcp address
Public bug reported: we're trying to migrate our network configuration from lucid to precise. in 10.04 we tied eth0+eth1 together into bond0, then set br0 up on top of that and assigned an address via dhcp. in 12.04 this only works if br0 is configured with a static ip address. it fails when trying to use dhcp. to simplify testing i've removed eth1 from the configuration (sanity checked against http://www.stgraber.org/2012/01/04/networking- in-ubuntu-12-04-lts/ ): auto lo iface lo inet loopback auto eth0 iface eth0 inet manual bond-master bond0 auto bond0 iface bond0 inet manual bond-slaves none bond-mode 802.3ad bond-miimon 100 auto br0 iface br0 inet dhcp bridge_ports bond0 bridge_stp off the above results in a system w/o network connectivity. the dhcp server reports requests from an unexpected mac addr (different each boot). udevd logs "timeout 'bridge-network-interface'". poking around a little before the timeout shows the following 2 groups of processes: |-ifup,1361 --allow auto eth0 | `-sh,1363 -c run-parts /etc/network/if-pre-up.d | `-run-parts,1364 /etc/network/if-pre-up.d | `-ifenslave,1392 /etc/network/if-pre-up.d/ifenslave | `-sleep,2380 0.1 | |-udevd,599 --daemon | | `-bridge-network-,1429 /lib/udev/bridge-network-interface | | `-ifup,1457 --allow auto br0 | | `-sh,1540 -c dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.br0.pid -lf /var/lib/dhcp/dhclient.br0.leases -1 br0 | | `-dhclient3,1541 -e IF_METRIC=100 -pf /var/run/dhclient.br0.pid -lf /var/lib/dhcp/dhclient.br0.leases -1 br0 the ifenslave appears to be looping over that `sleep` (testing for /run/network/ifenslave.bond0) until it is killed and the dhclient is making its request w/the unexpected mac addr (also reported in `ip link show br0`). interestingly br0's mac addr matches that of eth0 (as expected) once bridge-network-interface has timed out and been killed. a workaround appears to be adding the line: pre-up /sbin/ifup --allow auto bond0 to the "auto br0" stanza. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: bridge-utils 1.5-2ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 23 13:44:43 2012 ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: bridge-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bridge-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: when adding a bond the bridge fails to acquire a dhcp address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 462171] Re: 'grub-install --no-floppy /dev/md0' fails
still unresolved in 12.04: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04 LTS Release:12.04 Codename: precise # grub-install --version grub-install (GRUB) 1.99-21ubuntu3 # grub-install --no-floppy "/dev/md0" /usr/sbin/grub-setup: warn: Attempting to install GRUB to a partitionless disk or to a partition. This is a BAD idea.. /usr/sbin/grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. /usr/sbin/grub-setup: error: will not proceed with blocklists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/462171 Title: 'grub-install --no-floppy /dev/md0' fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/462171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 229699] Re: "setting locale failed" if using other keyboard layout then language
i'm still seeing this on a newly-built 12.04 server (installed using fai). the`locale-gen` workaround takes care of it for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/229699 Title: "setting locale failed" if using other keyboard layout then language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/229699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924028] [NEW] sgdisk 0.8.1-1build1: "--largest-new=0" option not working as documented
Public bug reported: the man page for sgdisk(8) states that for the "--largest-new=num" option "A num value of 0 causes the program to use the first available partition number." this does not appear to be the case. using a value of 0 returns the following error: % sgdisk --version GPT fdisk (sgdisk) version 0.8.1 % sudo /sbin/sgdisk /dev/xenvg/9e46d655-f4b5-49bd-9e78-7df0a143119a.disk0 --largest-new=0 Could not create partition 0 from 34 to 16777182 Error encountered; not saving changes. values >0 work and the "--new=partnum:start:end" option (also supporting 0 for the first available partition number) works as expected. from a look at the source code (gdisk-0.8.1/gptcl.cc around lines 276-307; disclaimer: i am not a coder) it appears that "largestPartNum" is tested differently than "partNum" and that the "< 0" check for largestPartNum will always evaluate as false. thank you. % lsb_release -rd Description:Ubuntu 10.04.3 LTS Release:10.04 % apt-cache policy gdisk gdisk: Installed: 0.8.1-1build1 Candidate: 0.8.1-1build1 Version table: *** 0.8.1-1build1 0 100 /var/lib/dpkg/status 0.5.1-1 0 500 http://apt-mirror.us.archive.org/ubuntu/ lucid/universe Packages ** Affects: gdisk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924028 Title: sgdisk 0.8.1-1build1: "--largest-new=0" option not working as documented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdisk/+bug/924028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663564] Re: Don't report persistentconns as activeconns
** Patch added: "ipvsadm-activeconn.patch" https://bugs.launchpad.net/bugs/663564/+attachment/1702170/+files/ipvsadm-activeconn.patch -- Don't report persistentconns as activeconns https://bugs.launchpad.net/bugs/663564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663564] [NEW] Don't report persistentconns as activeconns
Public bug reported: Binary package hint: ipvsadm Description:Ubuntu 10.04.1 LTS Release:10.04 ipvsadm: Installed: 1:1.25.clean-1 Candidate: 1:1.25.clean-1 Version table: *** 1:1.25.clean-1 0 500 http://apt-mirror1.us.archive.org/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status there is "what appears to be a typo in the netlink client code whereby the activeconns is read as activeconns and then overwritten by persistentconns. The result is that the active connection count reported by ipvsadm -L is wrong if the code is compiled to use the netlink interface." (description taken from http://archive.linuxvirtualserver.org/html/lvs- devel/2010-02/msg6.html) the attached patch is taken from https://bugzilla.redhat.com/show_bug.cgi?id=573921 (the same patch as from the lvs-devel link but with unmangled whitespace) ** Affects: ipvsadm (Ubuntu) Importance: Undecided Status: New -- Don't report persistentconns as activeconns https://bugs.launchpad.net/bugs/663564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 462171] Re: 'grub-install --no-floppy /dev/md0' fails
this remains a problem in 10.04.1 and likely in maverick as well: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 10.04.1 LTS Release:10.04 Codename: lucid # grub-install --version grub-install (GNU GRUB 1.98-1ubuntu5) # grub-install --no-floppy "(md0)" /usr/sbin/grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea.. /usr/sbin/grub-setup: error: embedding is not possible, but this is required when the root device is on a RAID array or LVM volume. i also tested 1.98-1ubuntu7 from lucid-updates and 1.98+20100804-5ubuntu3 with the same results. this appears to be an ubuntu-specific issue introduced between 1.97~beta4-1ubuntu2 and 1.97~beta4-1ubuntu3 (as mentioned in the original report). on a whim i tried the straight-up debian version of the package (1.98+20100804-5) which installed to md0 with "No error reported". the workaround from http://ubuntu- ky.ubuntuforums.org/showthread.php?p=9638149 was helpful. -- 'grub-install --no-floppy /dev/md0' fails https://bugs.launchpad.net/bugs/462171 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619582] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 caused by running lshw-gtk launched from gksu
i recently compiled and installed the maverick 2.6.35.2 kernel on a server running jaunty. i believe that i am encountering the same (or a very similar) issue. when booted with the new kernel, the server hangs with a kernel oops when lshw is run, apparently while probing the Framebuffer device. i have attached the console output. please let me know if there is other useful information i can provide. thank you for your time and effort. ** Attachment added: "oops.txt.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/619582/+attachment/1505952/+files/oops.txt.gz -- BUG: unable to handle kernel NULL pointer dereference at 0008 caused by running lshw-gtk launched from gksu https://bugs.launchpad.net/bugs/619582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193810] [NEW] support for booting in emergency (-b) mode
Public bug reported: Binary package hint: upstart the sysvinit implementation of init supported booting in emergency (-b) mode where it would "Boot directly into a single user shell without running any other startup scripts." i have found this useful in the past and was wondering if the functionality would (or could) be included in upstart? thanks! andy ** Affects: upstart (Ubuntu) Importance: Undecided Status: New -- support for booting in emergency (-b) mode https://bugs.launchpad.net/bugs/193810 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
