[Bug 1885990] Re: server: Match has no effect in include file (upstream 3122)
Why is this marked as "fix released"? It's still broken on Ubuntu 20.04 LTS, the fix has not been released into it. At the very least, the behavior does not match what is described in the sshd_config man page. Nowhere does it mention that Match blocks don't work inside Include files. Not only that, the config passes config test, and a LogLevel VERBOSE will say that the Match section has been processed, but then it has really been silently ignored! It took me hours to debug this issue back to a post on the mailing list, to the upstream fix, to this bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885990 Title: server: Match has no effect in include file (upstream 3122) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1885990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
TJ's howto from comment #47 is much better as it allows installing directly to the target disk, mine needs you to install it to a second disk and copies over to the target disk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
By the way, PureOS has the same bug, so I think it goes all the way up to Debian. Here's a guide I created on how to move a unencrypted install to fully encrypted (works with Ubuntu as well): https://github.com/jjakob/wiki/wiki/Migrating-an-unencrypted-PureOS- Debian-install-to-fully-encrypted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
My attempts to install 20.04 beta desktop or 18.04 LTS netinstall expert mode with full disk LUKS encryption failed. 1. Tried installing 20.04 Desktop ISO: - selected manual partitioning - created a single partition spanning the entire disk - created a volume for encryption on the partition (LUKS) - the LUKS was created, but there is no way to select the sda1_crypt volume as physical device for LVM. The option is absent from the list! So I go manually: - exit out of the installation - open a terminal, create the LVM VG and two LVs: root and swap - start the installer again, now the LVM volumes are displayed - select the root volume to be used as ext4 on / - select swap LV to be used as swap - proceed with installation normally, it finishes without errors. - on reboot, grub drops to rescue shell, unable to find the "lvm" root disk. Probably due to missing GRUB_ENABLE_CRYPTODISK=y in /etc/default/grub. 2. Tried the 18.04 LTS netinstall booted over PXE: - selected Advanced options, Expert Install - used manual partitioning to create the same "MBR->partition1->LUKS->LVM->LVs root and swap" layout as above. - installation proceeds fine until the "Install GRUB bootloader to the master boot record", where it errors: "grub-install /dev/sda failed". I try different combinations of grub options here, none work. So I'm unable to create a bootable system. I could probably make the 2nd way work if I switched to the console, found out why it errors, fixed it, and installed it manually. But that's not expected of a normal user! So now, in 2020, we have no way to install Ubuntu without unencrypted /boot. I have numerous machines that I either installed this way in the past, or manually copied over installations to hand-created LUKS and LVM, and with minor tweaks (chrooting into the copied system, adding GRUB_ENABLE_CRYPTODISK=y and tweaking fstab and crypttab) I can get them to boot fine. I can swear this used to work on 14.04 and before, so this is a regression! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 617101] Re: package g15daemon 1.9.5.3-8ubuntu1 failed to install/upgrade: if g15daemon fails to start
Still not fixed in Xenial/16.04LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/617101 Title: package g15daemon 1.9.5.3-8ubuntu1 failed to install/upgrade: if g15daemon fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/g15daemon/+bug/617101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660146] [NEW] Warning: failed to disable LRO
Public bug reported: The following warning is printed when bringing up network interfaces. It seems to have no effect on system operation. [ 17.731877] 8021q: adding VLAN 0 to HW filter on device eth3 [ 17.732141] bonding: bond0: enslaving eth3 as a backup interface with a down link. [ 17.751594] device bond0.42 entered promiscuous mode [ 17.753413] [ cut here ] [ 17.753422] WARNING: CPU: 2 PID: 1728 at /build/linux-Mxzr_W/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90() [ 17.753423] netdevice: bond0.42 [ 17.753423] failed to disable LRO! [ 17.753425] Modules linked in: 8021q garp mrp ipmi_devintf xfs libcrc32c bonding bridge stp llc dcdbas kvm_amd kvm dm_multipath scsi_dh amd64_edac_mod serio_raw k10temp edac_core snd_usb_audio edac_mce_amd snd_usbmidi_lib snd_hwdep snd_rawmidi snd_seq_device snd_pcm snd_page_alloc snd_timer snd soundcore joydev gspca_sonixj gspca_main radeon videodev ipmi_si floppy(+) ttm drm_kms_helper drm mac_hid i2c_algo_bit shpchp i2c_piix4 ses enclosure hpsa hid_generic usbhid hid qla2xxx bnx2 megaraid_sas e1000e scsi_transport_fc psmouse ptp cciss scsi_tgt pps_core sata_svw [ 17.753464] CPU: 2 PID: 1728 Comm: brctl Not tainted 3.13.0-85-generic #129-Ubuntu [ 17.753466] Hardware name: Dell Inc. PowerEdge 2970/0Y436H, BIOS 4.2.1 04/14/2010 [ 17.753467] 880425943c70 8172b6a7 880425943cb8 [ 17.753471] 0009 880425943ca8 810699cd 880427d37000 [ 17.753473] 880427c02880 880427d37000 880425cd7d40 [ 17.753476] Call Trace: [ 17.753482] [] dump_stack+0x64/0x82 [ 17.753487] [] warn_slowpath_common+0x7d/0xa0 [ 17.753489] [] warn_slowpath_fmt+0x4c/0x50 [ 17.753491] [] dev_disable_lro+0x87/0x90 [ 17.753500] [] br_add_if+0x1f3/0x430 [bridge] [ 17.753505] [] add_del_if+0x5d/0x90 [bridge] [ 17.753510] [] br_dev_ioctl+0x5b/0x90 [bridge] [ 17.753513] [] dev_ifsioc+0x313/0x360 [ 17.753517] [] ? dev_get_by_name_rcu+0x69/0x90 [ 17.753519] [] dev_ioctl+0xe5/0x5b0 [ 17.753523] [] ? evict+0x11b/0x1b0 [ 17.753526] [] sock_do_ioctl+0x45/0x50 [ 17.753528] [] sock_ioctl+0x1f0/0x2c0 [ 17.753530] [] do_vfs_ioctl+0x2e0/0x4c0 [ 17.753534] [] ? fput+0xe/0x10 [ 17.753537] [] ? task_work_run+0xb1/0xd0 [ 17.753539] [] SyS_ioctl+0x81/0xa0 [ 17.753542] [] system_call_fastpath+0x1a/0x1f [ 17.753544] ---[ end trace 20d17e724d7c2871 ]--- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-85-generic 3.13.0-85.129 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 15 00:01 seq crw-rw 1 root audio 116, 33 Aug 15 00:01 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-85-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sun Jan 29 15:40:46 2017 HibernationDevice: RESUME=UUID=99cc685a-4300-462b-a2b5-07757d70dc71 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge 2970 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=cd62ebf0-580a-417b-b167-bba9126b89c0 ro splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2015-01-26 (733 days ago) dmi.bios.date: 04/14/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.2.1 dmi.board.name: 0Y436H dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr4.2.1:bd04/14/2010:svnDellInc.:pnPowerEdge2970:pvr:rvnDellInc.:rn0Y436H:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge 2970 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1660146 Title: Warning: failed to disable LRO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393842] Re: libvirt does not grant qemu-guest-agent channel perms
Still getting this bug in Trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393842 Title: libvirt does not grant qemu-guest-agent channel perms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1393842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643514] [NEW] package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1642966 *** https://bugs.launchpad.net/bugs/1642966 Public bug reported: This is otherwise a duplicate of #1642966, but for a different version of cups 2.1.3-4ubuntu0.1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: E [20/Nov/2016:20:34:39 +0100] Missing value on line 666 of /var/cache/cups/job.cache. E [20/Nov/2016:20:34:39 +0100] Missing value on line 679 of /var/cache/cups/job.cache. E [21/Nov/2016:11:49:19 +0100] Missing value on line 666 of /var/cache/cups/job.cache. E [21/Nov/2016:11:49:19 +0100] Missing value on line 679 of /var/cache/cups/job.cache. Date: Sat Nov 19 15:29:36 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-03-08 (988 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140308) Lpstat: device for HP-LaserJet-5P: socket://10.10.0.153:9100 device for HP-LaserJet-5P-2: usb://HP/LaserJet%205P device for laserjetknjiznica: socket://10.1.151.20:9100 device for Samsung-ML-1640: socket://10.10.0.20:9100 MachineType: Hewlett-Packard HP ProBook 4710s Papersize: a4 PpdFiles: HP-LaserJet-5P: HP LaserJet 5P Foomatic/ljet4 (recommended) Samsung-ML-1640: Samsung ML-1640, 2.0.0 laserjetknjiznica: HP LaserJet P3010 Series Postscript (recommended) HP-LaserJet-5P-2: HP LaserJet 5P Foomatic/ljet4 (recommended) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash radeon.dpm=0 elevator=noop nomdmonddf nomdmonisw vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash radeon.dpm=0 elevator=noop nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-10-12 (39 days ago) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3074 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU9465LRD dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4710s:pvrF.18:rvnHewlett-Packard:rn3074:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4710s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2014-03-13T12:40:56.850454 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-from-proposed xenial ** This bug has been marked a duplicate of bug 1642966 package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643514 Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1643514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302416] Re: deja-dup monitor was taking 6GB of memory
Happened right now on Xenial 16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302416 Title: deja-dup monitor was taking 6GB of memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1302416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559435] [NEW] Please make compression options customizable
Public bug reported: Currently, using LZ4 as compression type produces an unbootable system, as lz4 is called without the legacy format option -l, which is required to produce a kernel readable image. Also, using lzop there is a very long delay (over one minute) when updating initramfs, as by default the maximum compression setting -9 is passed with no way for the user to change it. Making the compression options customizable (as e.g. mkinitcpio does) would be very useful for advanced users who wish to fine tune their systems for e.g. faster boot times, smaller image sizes, etc. The default options should also be described in mkinitramfs.conf or the man page so users have a starting point for customization without having to go through the source code. For example: https://wiki.archlinux.org/index.php/mkinitcpio#COMPRESSION_OPTIONS ** Affects: initramfs-tools (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/1559435 Title: Please make compression options customizable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1559435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273201] Re: bridge_ignore_without_connections.patch breaks NM created bridge at boot
Any news on fixing the bug? Yesterday a new version of network-manager 0.9.8.8-0ubuntu7.2 got pushed out, replacing the version from cschieli's ppa 0.9.8.8-0ubuntu7.1+athome1, causing the bridges to break once again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273201 Title: bridge_ignore_without_connections.patch breaks NM created bridge at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1355819] [NEW] virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build
*** This bug is a duplicate of bug 1355732 *** https://bugs.launchpad.net/bugs/1355732 Public bug reported: The error occurred when upgrading to 14.04 LTS enablement stack. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6 ProcVersionSignature: Ubuntu 3.11.0-24.42~precise1-generic 3.11.10.11 Uname: Linux 3.11.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-33-generic Date: Tue Aug 12 15:34:22 2014 MarkForUpload: True PackageArchitecture: all PackageVersion: 4.1.12-dfsg-2ubuntu0.6 SourcePackage: virtualbox Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build UpgradeStatus: Upgraded to precise on 2014-04-02 (132 days ago) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1355819 Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1355819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290110] Re: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s and many others]
** Changed in: linux (Ubuntu) Status: Confirmed = 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/1290110 Title: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s and many others] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1290110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290110] Re: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s and many others]
For me this bug is definitely fixed in 3.15-rc6, and AFAIK from this release onwards, so daily build of mainline should also work. Of course the patch is not yet backported, which it urgently must be. For now just install latest mainline from instructions on Ubuntu wiki. If there is still a fault when you try 3.15-rc6 this must be an unrelated bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290110 Title: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s and many others] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1290110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290110] Re: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s and many others]
I mean the kernel, of course. There is no need to reinstall Ubuntu 14.04 daily (in fact it would be pointless as the bug is still there). I've had it since alpha and it works fine with kernel 3.15-rc6 installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290110 Title: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s and many others] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1290110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290110] Re: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s]
** Tags removed: kernel-bug-exists-upstream kernel-bug-reported-upstream ** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.15-rc6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290110 Title: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1290110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290110] Re: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s]
The bug is fixed in 3.15-rc6. The patch is at https://patchwork.kernel.org/patch/4124871/ and a patch adapted for 3.14.4 is here: https://bugzilla.kernel.org/attachment.cgi?id=136881 A backport to 3.13 is needed for it to get into Trusty AFAIK... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290110 Title: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1290110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290110] Re: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s]
Changed URL to HTTPS ** Bug watch added: Linux Kernel Bug Tracker #71711 http://bugzilla.kernel.org/show_bug.cgi?id=71711 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290110 Title: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1290110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290110] Re: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s]
** Bug watch added: Linux Kernel Bug Tracker #71711 http://bugzilla.kernel.org/show_bug.cgi?id=71711 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=71711 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290110 Title: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1290110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290110] Re: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s]
** 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/1290110 Title: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297254] Re: Unity Top-Menu Bar Not Showing Window Control Buttons
I have the same problem, but oddly enough in Chromium - LibreOffice is OK. So I don't think this is related to LibreOffice. This only happens when maximised. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297254 Title: Unity Top-Menu Bar Not Showing Window Control Buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1297254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290110] Re: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s]
Thank you. I will report the bug upstream. I have done a bit of investigation on which cooling devices correspond to different fan speeds. IMO the cooling device to trip point mappings are wrong (do not change fan speed linearly with accordance to temperature/trip points). And I've also found that thermal zone 5 temperature corresponds exactly to the processor fan speed. This should definitely be reported as fan speed, not temperature. Should I also detail my findings here, or post them to the kernel mailing list? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290110 Title: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063445] Re: Wireless not connecting, disconnecting
Hi, I haven't had any problems with wireless for a while now... I think things just started working after a upgrade a bit after I posted this bug. I can't remember when exactly it was (maybe a couple of months). So if you're having problems, I suggest you open a new bug... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063445 Title: Wireless not connecting, disconnecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1063445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290110] Re: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s]
Hi, I've tested the latest mainline kernel (v3.16-rc6-trusty) and the bug is still present. Also it seems that the fan speed does not change relative to temperature any more after OS startup. ** Tags added: kernel-bug-exists-upstream ** 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/1290110 Title: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290110] [NEW] Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s]
Public bug reported: After resume from suspend, the fan (there is only one) first speeds up to about a normal speed and then slows down in a couple of seconds to a complete stop. It doesn't spin up again even if the temperatures shoot way up (monitoring using indicator-sensors or lm-sensors, both use acpitz info). There are 2 ways to get the fan spinning again: - reboot the system - echo 1 /sys/class/thermal/cooling_device[4|12...don't remember which]/curr_state This is happening on a clean install of Trusty from daily build that also has the updates-proposed source enabled. Previously the laptop ran 13.10 and suspend and resume worked fine. Only thing is, I also updated the BIOS during formatting for Trusty, which could cause this issue but I'm leaning more towards an ACPI issue (the latest BIOS is from 2010 and someone would have probably noticed a problem with the fan?) Attached is the output from cd /sys/class/thermal grep . */* 2/dev/null after first boot and after resume suspend; as can be seen, after resume all fan states are 0 whereas on boot some are also 1. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-16-generic 3.13.0-16.36 [modified: boot/vmlinuz-3.13.0-16-generic] ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jernej 2582 F pulseaudio /dev/snd/controlC0: jernej 2582 F pulseaudio CurrentDesktop: Unity CurrentDmesg: [ 78.199783] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 104.824460] audit_printk_skb: 147 callbacks suppressed [ 104.824464] type=1400 audit(1394393526.590:61): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=1986 comm=apparmor_parser [ 104.824472] type=1400 audit(1394393526.590:62): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=1986 comm=apparmor_parser [ 104.824884] type=1400 audit(1394393526.590:63): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=1986 comm=apparmor_parser Date: Sun Mar 9 20:46:48 2014 HibernationDevice: RESUME=UUID=79b35f90-100a-4582-9b65-a84fbedf5bf7 InstallationDate: Installed on 2014-03-08 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140308) MachineType: Hewlett-Packard HP ProBook 4710s ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-16-generic root=UUID=9561bd56-ffa3-4f61-91cf-019c359ed8e8 ro quiet splash radeon.dpm=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-16-generic N/A linux-backports-modules-3.13.0-16-generic N/A linux-firmware 1.126 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3074 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU9465LRD dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4710s:pvrF.18:rvnHewlett-Packard:rn3074:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4710s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty ** Attachment added: /sys/class/thermal after normal boot, fan works https://bugs.launchpad.net/bugs/1290110/+attachment/4015401/+files/sys-class-thermal-onboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290110 Title: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290110] Re: Fan stops after resume from suspend leading to overheating; requires reboot to fix
** Attachment added: /sys/class/thermal after resume, fan doesn't work https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290110/+attachment/4015418/+files/sys-class-thermal-aftersuspend ** Summary changed: - Fan stops after resume from suspend leading to overheating; requires reboot to fix + Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290110 Title: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276725] Re: package firmware-b43-installer 1:017-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 8 zurück
Exact same problem here. Only APT is set to use the proxy in /etc/apt/apt.conf.d/01proxy: Acquire::http::Proxy http://apt-cacher.lan:3142/;; System-wide proxy is disabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276725 Title: package firmware-b43-installer 1:017-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 8 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1276725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197878] Re: SNMPv3 not working with APC
Also relevant: http://www.mail-archive.com/nut-upsuser@lists.alioth.debian.org/msg07865.html Looks like I'll need a newer version of NUT anyway... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/1197878 Title: SNMPv3 not working with APC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1197878] Re: SNMPv3 not working with APC
Also relevant: http://www.mail-archive.com/nut-upsuser@lists.alioth.debian.org/msg07865.html Looks like I'll need a newer version of NUT anyway... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1197878 Title: SNMPv3 not working with APC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197878] Re: SNMPv3 not working with APC
I am confirming HW compatibility for AP9619 (AP9617, AP9618, AP9619 series). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/1197878 Title: SNMPv3 not working with APC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1197878] Re: SNMPv3 not working with APC
Sorry, but these cards don't support AES, only DES (AP9617,AP9618,AP9619). I have managed to fix the communication problem by using simple passwords without any special characters. upsdrvctl still outputs some unhandled ASNs, but it seems to have no influence on NUT working. This is with mibs = auto: Network UPS Tools - UPS driver controller 2.6.3 0.00 If you're not a NUT core developer 0.000585 Starting UPS: ups1 0.000627 exec: /lib/nut/snmp-ups -a ups1 Network UPS Tools - Generic SNMP UPS driver 0.58 (2.6.3) No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.7'! Please report it to NUT developers, with the 'mib' paramater for your devices Detected Smart-UPS 3000 RM on host 10.0.0.6 (mib: apcc 1.1) [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.3.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.3.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.3.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.4.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.4.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.4.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.5.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.5.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.5.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.6.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.6.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.6.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.7.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.7.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.7.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.8.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.8.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.8.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.2.1.4.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.2.1.4.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.3.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.3.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.3.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.4.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.4.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.4.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.5.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.5.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.5.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.6.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.6.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.6.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.7.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.7.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.7.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.8.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.8.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.8.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.9.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.9.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.9.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.10.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.10.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.10.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.11.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.11.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.11.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.12.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.12.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.12.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.2.1.1.0 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.2.1.2.0 So somehow special characters in passwords break SNMP communication in snmp-ups (which works with command-line tools like snmpget). Also with mibs = apcc I
[Bug 1197878] Re: SNMPv3 not working with APC
Sorry, but these cards don't support AES, only DES (AP9617,AP9618,AP9619). I have managed to fix the communication problem by using simple passwords without any special characters. upsdrvctl still outputs some unhandled ASNs, but it seems to have no influence on NUT working. This is with mibs = auto: Network UPS Tools - UPS driver controller 2.6.3 0.00 If you're not a NUT core developer 0.000585 Starting UPS: ups1 0.000627 exec: /lib/nut/snmp-ups -a ups1 Network UPS Tools - Generic SNMP UPS driver 0.58 (2.6.3) No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.7'! Please report it to NUT developers, with the 'mib' paramater for your devices Detected Smart-UPS 3000 RM on host 10.0.0.6 (mib: apcc 1.1) [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.3.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.3.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.3.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.4.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.4.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.4.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.5.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.5.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.5.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.6.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.6.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.6.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.7.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.7.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.7.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.8.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.8.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.8.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.2.1.4.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.2.1.4.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.3.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.3.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.3.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.4.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.4.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.4.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.5.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.5.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.5.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.6.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.6.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.6.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.7.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.7.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.7.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.8.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.8.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.8.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.9.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.9.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.9.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.10.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.10.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.10.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.11.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.11.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.11.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.12.1.1.1 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.12.1.1.2 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.12.1.1.3 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.2.1.1.0 [ups1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.2.1.2.0 So somehow special characters in passwords break SNMP communication in snmp-ups (which works with command-line tools like snmpget). Also with mibs = apcc I
[Bug 1197878] Re: SNMPv3 not working with APC
I am confirming HW compatibility for AP9619 (AP9617, AP9618, AP9619 series). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1197878 Title: SNMPv3 not working with APC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197878] Re: SNMPv3 not working with APC
After some digging I found someone having an identical problem on the nut-upsdev mailing lists: http://www.mail-archive.com/nut-upsdev@lists.alioth.debian.org/msg03451.html The problem was ultimately not resolved, hence I deem that the status could be elevated to Confirmed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/1197878 Title: SNMPv3 not working with APC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1197878] Re: SNMPv3 not working with APC
After some digging I found someone having an identical problem on the nut-upsdev mailing lists: http://www.mail-archive.com/nut-upsdev@lists.alioth.debian.org/msg03451.html The problem was ultimately not resolved, hence I deem that the status could be elevated to Confirmed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1197878 Title: SNMPv3 not working with APC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197878] Re: SNMPv3 not working with APC
Here is the output when mibs=auto (tried also with no mibs= line in
ups.conf, but the output is the same):
/lib/nut/snmp-ups -a ups1 -DDD
Network UPS Tools - Generic SNMP UPS driver 0.58 (2.6.3)
0.00 debug level is '3'
0.001183 SNMP UPS driver : entering upsdrv_initups()
0.001207 SNMP UPS driver : entering nut_snmp_init(snmp-ups)
0.735157 SNMP UPS driver : entering load_mib2nut(auto)
0.735196 trying the new match_sysoid() method
0.735221 Entering nut_snmp_get_str()
0.735251 nut_snmp_get(.1.3.6.1.2.1.1.2.0)
6.762884 Can't get sysOID value
6.762917 load_mib2nut: trying classic method with 'apcc' mib
6.762922 Entering nut_snmp_get_str()
6.762929 nut_snmp_get(.1.3.6.1.4.1.318.1.1.1.1.1.1.0)
12.768293 load_mib2nut: trying classic method with 'mge' mib
12.768353 Entering nut_snmp_get_str()
12.768369 nut_snmp_get(.1.3.6.1.4.1.705.1.1.1.0)
18.774670 load_mib2nut: trying classic method with 'netvision' mib
18.774719 Entering nut_snmp_get_str()
18.774734 nut_snmp_get(.1.3.6.1.4.1.4555.1.1.1.1.1.1.0)
24.780316 load_mib2nut: trying classic method with 'pw' mib
24.780365 Entering nut_snmp_get_str()
24.780381 nut_snmp_get(1.3.6.1.4.1.534.1.1.2.0)
30.785826 load_mib2nut: trying classic method with 'aphel_genesisII' mib
30.785875 Entering nut_snmp_get_str()
30.785891 nut_snmp_get(.1.3.6.1.4.1.17373.3.1.1.0)
36.792281 load_mib2nut: trying classic method with 'aphel_revelation' mib
36.792328 Entering nut_snmp_get_str()
36.792344 nut_snmp_get(.1.3.6.1.4.1.534.6.6.6.1.1.12.0)
42.799464 load_mib2nut: trying classic method with 'eaton_epdu' mib
42.799517 Entering nut_snmp_get_str()
42.799533 nut_snmp_get(.1.3.6.1.4.1.534.6.6.7.1.2.1.2.0)
48.805451 load_mib2nut: trying classic method with 'raritan' mib
48.805477 Entering nut_snmp_get_str()
48.805483 nut_snmp_get(.1.3.6.1.4.1.13742.1.1.12.0)
54.811904 load_mib2nut: trying classic method with 'baytech' mib
54.811961 Entering nut_snmp_get_str()
54.811977 nut_snmp_get(.1.3.6.1.4.1.4779.1.3.5.2.1.24.1)
60.818242 load_mib2nut: trying classic method with 'cpqpower' mib
60.818291 Entering nut_snmp_get_str()
60.818306 nut_snmp_get(1.3.6.1.4.1.232.165.3.1.1.0)
66.825054 load_mib2nut: trying classic method with 'bestpower' mib
66.825093 Entering nut_snmp_get_str()
66.825104 nut_snmp_get(.1.3.6.1.4.1.2947.1.1.2.0)
72.832071 load_mib2nut: trying classic method with 'cyberpower' mib
72.832107 Entering nut_snmp_get_str()
72.832116 nut_snmp_get(.1.3.6.1.4.1.3808.1.1.1.1.1.1.0)
78.838672 load_mib2nut: trying classic method with 'ietf' mib
78.838721 Entering nut_snmp_get_str()
78.838737 nut_snmp_get(1.3.6.1.2.1.33.1.1.1.0)
84.845475 No supported device detected
tcpdump:
23:34:01.428044 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UD
P (17), length 92)
10.0.10.10.33452 10.0.0.6.161: [bad udp cksum 0x1e69 - 0x1554!] { SNMPv3
{ F=r } { USM B=0 T=0 U= } { ScopedPDU E= C= { GetRequest(14) R=545426911 } }
}
23:34:01.446834 IP (tos 0x0, ttl 63, id 27, offset 0, flags [none], proto UDP (1
7), length 147)
10.0.0.6.161 10.0.10.10.33452: [no cksum] { SNMPv3 { F= } { USM B=115
T=627920 U= } { ScopedPDU E=0x800x000x010x3E0x030x000xC00xB70x7E0xC80xFB C= {
Report(35) R=545426911 .1.3.6.1.6.3.15.1.1.4.0=23 } } }
23:34:01.447188 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 172)
10.0.10.10.33452 10.0.0.6.161: [bad udp cksum 0x1eb9 - 0xc96a!] {
SNMPv3 { F=apr } { USM B=115 T=627920 U=apc_ups_1_authpriv } { ScopedPDU
[!scopedPDU]c5_8e_3f_a3_9b_8d_15_2e_56_e0_49_96_7e_f2_27_c0_72_89_5f_28_48_04_c3_f0_d1_25_76_77_58_17_54_ac_8f_83_59_e6_69_24_d4_1a_9d_b7_96_13_e3_6f_b6_d9}
}
[...more packets from server to UPS without any response...]
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1197878
Title:
SNMPv3 not working with APC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1197878] Re: SNMPv3 not working with APC
Here is the output when mibs=auto (tried also with no mibs= line in
ups.conf, but the output is the same):
/lib/nut/snmp-ups -a ups1 -DDD
Network UPS Tools - Generic SNMP UPS driver 0.58 (2.6.3)
0.00 debug level is '3'
0.001183 SNMP UPS driver : entering upsdrv_initups()
0.001207 SNMP UPS driver : entering nut_snmp_init(snmp-ups)
0.735157 SNMP UPS driver : entering load_mib2nut(auto)
0.735196 trying the new match_sysoid() method
0.735221 Entering nut_snmp_get_str()
0.735251 nut_snmp_get(.1.3.6.1.2.1.1.2.0)
6.762884 Can't get sysOID value
6.762917 load_mib2nut: trying classic method with 'apcc' mib
6.762922 Entering nut_snmp_get_str()
6.762929 nut_snmp_get(.1.3.6.1.4.1.318.1.1.1.1.1.1.0)
12.768293 load_mib2nut: trying classic method with 'mge' mib
12.768353 Entering nut_snmp_get_str()
12.768369 nut_snmp_get(.1.3.6.1.4.1.705.1.1.1.0)
18.774670 load_mib2nut: trying classic method with 'netvision' mib
18.774719 Entering nut_snmp_get_str()
18.774734 nut_snmp_get(.1.3.6.1.4.1.4555.1.1.1.1.1.1.0)
24.780316 load_mib2nut: trying classic method with 'pw' mib
24.780365 Entering nut_snmp_get_str()
24.780381 nut_snmp_get(1.3.6.1.4.1.534.1.1.2.0)
30.785826 load_mib2nut: trying classic method with 'aphel_genesisII' mib
30.785875 Entering nut_snmp_get_str()
30.785891 nut_snmp_get(.1.3.6.1.4.1.17373.3.1.1.0)
36.792281 load_mib2nut: trying classic method with 'aphel_revelation' mib
36.792328 Entering nut_snmp_get_str()
36.792344 nut_snmp_get(.1.3.6.1.4.1.534.6.6.6.1.1.12.0)
42.799464 load_mib2nut: trying classic method with 'eaton_epdu' mib
42.799517 Entering nut_snmp_get_str()
42.799533 nut_snmp_get(.1.3.6.1.4.1.534.6.6.7.1.2.1.2.0)
48.805451 load_mib2nut: trying classic method with 'raritan' mib
48.805477 Entering nut_snmp_get_str()
48.805483 nut_snmp_get(.1.3.6.1.4.1.13742.1.1.12.0)
54.811904 load_mib2nut: trying classic method with 'baytech' mib
54.811961 Entering nut_snmp_get_str()
54.811977 nut_snmp_get(.1.3.6.1.4.1.4779.1.3.5.2.1.24.1)
60.818242 load_mib2nut: trying classic method with 'cpqpower' mib
60.818291 Entering nut_snmp_get_str()
60.818306 nut_snmp_get(1.3.6.1.4.1.232.165.3.1.1.0)
66.825054 load_mib2nut: trying classic method with 'bestpower' mib
66.825093 Entering nut_snmp_get_str()
66.825104 nut_snmp_get(.1.3.6.1.4.1.2947.1.1.2.0)
72.832071 load_mib2nut: trying classic method with 'cyberpower' mib
72.832107 Entering nut_snmp_get_str()
72.832116 nut_snmp_get(.1.3.6.1.4.1.3808.1.1.1.1.1.1.0)
78.838672 load_mib2nut: trying classic method with 'ietf' mib
78.838721 Entering nut_snmp_get_str()
78.838737 nut_snmp_get(1.3.6.1.2.1.33.1.1.1.0)
84.845475 No supported device detected
tcpdump:
23:34:01.428044 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UD
P (17), length 92)
10.0.10.10.33452 10.0.0.6.161: [bad udp cksum 0x1e69 - 0x1554!] { SNMPv3
{ F=r } { USM B=0 T=0 U= } { ScopedPDU E= C= { GetRequest(14) R=545426911 } }
}
23:34:01.446834 IP (tos 0x0, ttl 63, id 27, offset 0, flags [none], proto UDP (1
7), length 147)
10.0.0.6.161 10.0.10.10.33452: [no cksum] { SNMPv3 { F= } { USM B=115
T=627920 U= } { ScopedPDU E=0x800x000x010x3E0x030x000xC00xB70x7E0xC80xFB C= {
Report(35) R=545426911 .1.3.6.1.6.3.15.1.1.4.0=23 } } }
23:34:01.447188 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 172)
10.0.10.10.33452 10.0.0.6.161: [bad udp cksum 0x1eb9 - 0xc96a!] {
SNMPv3 { F=apr } { USM B=115 T=627920 U=apc_ups_1_authpriv } { ScopedPDU
[!scopedPDU]c5_8e_3f_a3_9b_8d_15_2e_56_e0_49_96_7e_f2_27_c0_72_89_5f_28_48_04_c3_f0_d1_25_76_77_58_17_54_ac_8f_83_59_e6_69_24_d4_1a_9d_b7_96_13_e3_6f_b6_d9}
}
[...more packets from server to UPS without any response...]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197878
Title:
SNMPv3 not working with APC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197878] [NEW] SNMPv3 not working with APC
Public bug reported:
I'm trying to connect to an AP9619 management card with SNMPv3 authPriv,
but the snmp-ups driver fails to start.
When running the driver directly:
$ sudo /lib/nut/snmp-ups -a ups1 -DDD
Network UPS Tools - Generic SNMP UPS driver 0.58 (2.6.3)
0.00 debug level is '3'
0.001185 SNMP UPS driver : entering upsdrv_initups()
0.001251 SNMP UPS driver : entering nut_snmp_init(snmp-ups)
0.076190 SNMP UPS driver : entering load_mib2nut(apcc)
0.076219 load_mib2nut: trying classic method with 'apcc' mib
0.076265 Entering nut_snmp_get_str()
0.076280 nut_snmp_get(.1.3.6.1.4.1.318.1.1.1.1.1.1.0)
6.103015 Unknown mibs value: apcc
tcpdump output while running the aforementioned driver:
17:42:51.178566 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 92)
10.0.10.10.57051 10.0.0.6.161: [bad udp cksum 0x1e69 - 0x7e35!] {
SNMPv3 { F=r } { USM B=0 T=0 U= } { ScopedPDU E= C= { GetRequest(14)
R=235897244 } } }
17:42:51.199124 IP (tos 0x0, ttl 63, id 15, offset 0, flags [none], proto UDP
(17), length 147)
10.0.0.6.161 10.0.10.10.57051: [no cksum] { SNMPv3 { F= } { USM B=115
T=520500 U= } { ScopedPDU E= 0x800x000x010x3E0x030x000xC00xB70x7E0xC80xFB C= {
Report(35) R=235897244 .1.3.6.1.6.3.15.1.1.4.0=12 } } }
17:42:51.199480 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 180)
10.0.10.10.57051 10.0.0.6.161: [bad udp cksum 0x1ec1 - 0xf39d!] {
SNMPv3 { F=apr } { USM B=115 T=520500 U=apc_ups_1_authpriv } { ScopedPDU
[!scoped
PDU]f2_ac_c6_d7_3f_1d_ec_bf_df_c6_f0_81_44_cf_b8_7f_18_8c_73_54_b2_a0_7e_f7_68_1c_ee_a8_4e_36_a6_51_24_64_80_e3_c8_12_67_64_b0_68_c3_eb_e4_f7_53_b6_1d_47_3c_17_87_f5_d6_fe}
}
[the last packet repeated 5 times, with T=T+1 and different ScopedPDUs each
time]
...
When setting nut to use SNMPv1, the GetRequests are for a different OID,
no response from the UPS as v1 is disabled:
16:42:32.323542 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 77)
10.0.10.10.54510 10.0.0.6.161: [bad udp cksum 0x1e5a - 0xa2d0!] {
SNMPv1 { GetRequest(34) R=1587461727 .1.3.6.1.4.1.318.1.1.1.1.1.1.0 } }
If I query the UPS with the same OID, but v3 protocol, I get a normal
response from the UPS:
$ snmpget -Cf -v 3 -u apc_ups_1_authpriv -l authPriv -a MD5 -A 'auth password
obfuscated' -X 'priv password obfuscated' 10.0.0.6
.1.3.6.1.4.1.318.1.1.1.1.1.1.0
SNMPv2-SMI::enterprises.318.1.1.1.1.1.1.0 = STRING: Smart-UPS 3000 RM
So I think snmp-ups is querying the wrong OIDs somehow, or something else is
not right.
Also might be relevant, my authPriv passwords have special characters in them,
like dots, colons, semicolons, parents, dashes, more/less, equals). The
passwords obviously work with the normal snmpget command. There is no mention
in the documentation, config files or man pages whether qouting is required
around the passwords in ups.conf when using passwords containing special
characters, so I tried them plain, double or single quoted with no difference.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nut-snmp 2.6.3-1ubuntu1.1
ProcVersionSignature: Ubuntu 3.5.0-32.53~precise1-generic 3.5.7.11
Uname: Linux 3.5.0-32-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
Date: Thu Jul 4 17:33:46 2013
KernelVersion: Linux PE2970 3.5.0-32-generic #53~precise1-Ubuntu SMP Wed May 29
20:33:37 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
MarkForUpload: True
SourcePackage: nut
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: nut (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1197878
Title:
SNMPv3 not working with APC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1197878] [NEW] SNMPv3 not working with APC
Public bug reported:
I'm trying to connect to an AP9619 management card with SNMPv3 authPriv,
but the snmp-ups driver fails to start.
When running the driver directly:
$ sudo /lib/nut/snmp-ups -a ups1 -DDD
Network UPS Tools - Generic SNMP UPS driver 0.58 (2.6.3)
0.00 debug level is '3'
0.001185 SNMP UPS driver : entering upsdrv_initups()
0.001251 SNMP UPS driver : entering nut_snmp_init(snmp-ups)
0.076190 SNMP UPS driver : entering load_mib2nut(apcc)
0.076219 load_mib2nut: trying classic method with 'apcc' mib
0.076265 Entering nut_snmp_get_str()
0.076280 nut_snmp_get(.1.3.6.1.4.1.318.1.1.1.1.1.1.0)
6.103015 Unknown mibs value: apcc
tcpdump output while running the aforementioned driver:
17:42:51.178566 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 92)
10.0.10.10.57051 10.0.0.6.161: [bad udp cksum 0x1e69 - 0x7e35!] {
SNMPv3 { F=r } { USM B=0 T=0 U= } { ScopedPDU E= C= { GetRequest(14)
R=235897244 } } }
17:42:51.199124 IP (tos 0x0, ttl 63, id 15, offset 0, flags [none], proto UDP
(17), length 147)
10.0.0.6.161 10.0.10.10.57051: [no cksum] { SNMPv3 { F= } { USM B=115
T=520500 U= } { ScopedPDU E= 0x800x000x010x3E0x030x000xC00xB70x7E0xC80xFB C= {
Report(35) R=235897244 .1.3.6.1.6.3.15.1.1.4.0=12 } } }
17:42:51.199480 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 180)
10.0.10.10.57051 10.0.0.6.161: [bad udp cksum 0x1ec1 - 0xf39d!] {
SNMPv3 { F=apr } { USM B=115 T=520500 U=apc_ups_1_authpriv } { ScopedPDU
[!scoped
PDU]f2_ac_c6_d7_3f_1d_ec_bf_df_c6_f0_81_44_cf_b8_7f_18_8c_73_54_b2_a0_7e_f7_68_1c_ee_a8_4e_36_a6_51_24_64_80_e3_c8_12_67_64_b0_68_c3_eb_e4_f7_53_b6_1d_47_3c_17_87_f5_d6_fe}
}
[the last packet repeated 5 times, with T=T+1 and different ScopedPDUs each
time]
...
When setting nut to use SNMPv1, the GetRequests are for a different OID,
no response from the UPS as v1 is disabled:
16:42:32.323542 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 77)
10.0.10.10.54510 10.0.0.6.161: [bad udp cksum 0x1e5a - 0xa2d0!] {
SNMPv1 { GetRequest(34) R=1587461727 .1.3.6.1.4.1.318.1.1.1.1.1.1.0 } }
If I query the UPS with the same OID, but v3 protocol, I get a normal
response from the UPS:
$ snmpget -Cf -v 3 -u apc_ups_1_authpriv -l authPriv -a MD5 -A 'auth password
obfuscated' -X 'priv password obfuscated' 10.0.0.6
.1.3.6.1.4.1.318.1.1.1.1.1.1.0
SNMPv2-SMI::enterprises.318.1.1.1.1.1.1.0 = STRING: Smart-UPS 3000 RM
So I think snmp-ups is querying the wrong OIDs somehow, or something else is
not right.
Also might be relevant, my authPriv passwords have special characters in them,
like dots, colons, semicolons, parents, dashes, more/less, equals). The
passwords obviously work with the normal snmpget command. There is no mention
in the documentation, config files or man pages whether qouting is required
around the passwords in ups.conf when using passwords containing special
characters, so I tried them plain, double or single quoted with no difference.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nut-snmp 2.6.3-1ubuntu1.1
ProcVersionSignature: Ubuntu 3.5.0-32.53~precise1-generic 3.5.7.11
Uname: Linux 3.5.0-32-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
Date: Thu Jul 4 17:33:46 2013
KernelVersion: Linux PE2970 3.5.0-32-generic #53~precise1-Ubuntu SMP Wed May 29
20:33:37 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
MarkForUpload: True
SourcePackage: nut
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: nut (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/1197878
Title:
SNMPv3 not working with APC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178721] Re: multipathd fails to create mappings when multipath.conf is present
Thank you for your help. I wasn't aware of the limitation (incompatibility) caused by co-deploying LVM and multipath, it was my assumption that multipath would be configured to take precedence over LVM for having PVs on multipath block devices, as having it the other way around, as in multiple paths over LVM logical volumes would not make sense. I can assume that this would be a pretty common scenario, as for example, you may have one volume mapped from SAN over FC on which the tools that LVM offers would be valuable. It would seem that a simple check at boot time, checking whether LVM and multipath are co-deployed, starting multipath first, letting it create paths and then adding those found to LVM's filter. I understand however that this is in no way common usage and requires a skillful enough administrator to be aware of the possible scenarios caused. Regarding the multipath config itself, this is the default config, functionally the same as the one proposed for MSA2012fc by HP. The virtual one is of course bogus... not to be used, just to demonstrate the failure mode. The actual servers will have a dual-port FC HBA with each port going to separate zones on a switch, with itself being connected with 2 cables each to the 2 controllers (4 in total) of the SAN, so there will be 2 paths for each volume. This is required for this SAN in order to have redundancy for controller failure. I just tried this with the physical server, and it still doesn't work as it should. In lvm.conf, blacklisted all the sd* devices and allowed only /dev/disk/by-id. Or should even the id's of the MP volumes be blacklisted, only allowing the one single PV's id? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1178721 Title: multipathd fails to create mappings when multipath.conf is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1178721] Re: multipathd fails to create mappings when multipath.conf is present
http://h2.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=encc=ustaskId=115prodSeriesId=3559651prodTypeId=18964objectID=c01476873 This is the config recommended by HP for our SAN (2000 series is down there), mine is functionally the same. There is no way to sense the priorities of the paths for this SAN, wouldn't that mean that if one path were lost, some of the IO would get lost as well, or would the protocol sense that and retry. Just wondering. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1178721 Title: multipathd fails to create mappings when multipath.conf is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1178721] Re: multipathd fails to create mappings when multipath.conf is present
Thank you for your help. I wasn't aware of the limitation (incompatibility) caused by co-deploying LVM and multipath, it was my assumption that multipath would be configured to take precedence over LVM for having PVs on multipath block devices, as having it the other way around, as in multiple paths over LVM logical volumes would not make sense. I can assume that this would be a pretty common scenario, as for example, you may have one volume mapped from SAN over FC on which the tools that LVM offers would be valuable. It would seem that a simple check at boot time, checking whether LVM and multipath are co-deployed, starting multipath first, letting it create paths and then adding those found to LVM's filter. I understand however that this is in no way common usage and requires a skillful enough administrator to be aware of the possible scenarios caused. Regarding the multipath config itself, this is the default config, functionally the same as the one proposed for MSA2012fc by HP. The virtual one is of course bogus... not to be used, just to demonstrate the failure mode. The actual servers will have a dual-port FC HBA with each port going to separate zones on a switch, with itself being connected with 2 cables each to the 2 controllers (4 in total) of the SAN, so there will be 2 paths for each volume. This is required for this SAN in order to have redundancy for controller failure. I just tried this with the physical server, and it still doesn't work as it should. In lvm.conf, blacklisted all the sd* devices and allowed only /dev/disk/by-id. Or should even the id's of the MP volumes be blacklisted, only allowing the one single PV's id? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178721 Title: multipathd fails to create mappings when multipath.conf is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178721] Re: multipathd fails to create mappings when multipath.conf is present
http://h2.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=encc=ustaskId=115prodSeriesId=3559651prodTypeId=18964objectID=c01476873 This is the config recommended by HP for our SAN (2000 series is down there), mine is functionally the same. There is no way to sense the priorities of the paths for this SAN, wouldn't that mean that if one path were lost, some of the IO would get lost as well, or would the protocol sense that and retry. Just wondering. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178721 Title: multipathd fails to create mappings when multipath.conf is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178721] [NEW] multipathd fails to create mappings when multipath.conf is present
Public bug reported:
I have a SAN connected via a dual-port HBA that I'm trying to get to
work with multipath.
I'm running 12.04.2 installed via netboot (clean install).
Setup options: partitioning=guided with LVM (onto internal DRAC 6/i RAID)
packages=Basic server,OpenSSH,Virtual machine host
Out of the box things work okay:
root@PE2950:~# multipath -ll
3600c0ff000d5ae56aabb85510100 dm-3 HP,MSA2012fc
size=1.4T features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 3:0:0:1 sdb 8:16 active ready running
`- 4:0:1:1 sdc 8:32 active ready running
mappings are created:
root@PE2950:~# ll /dev/mapper/
total 0
drwxr-xr-x 2 root root 140 maj 10 16:57 ./
drwxr-xr-x 16 root root 4460 maj 10 16:57 ../
brw-rw 1 root disk 252, 2 maj 10 16:57 360022190ba84f800113787c003d70474
lrwxrwxrwx 1 root root7 maj 10 16:57 3600c0ff000d5ae56aabb85510100
- ../dm-3
crw--- 1 root root 10, 236 maj 9 23:13 control
lrwxrwxrwx 1 root root7 maj 9 23:14 PE2950-root - ../dm-1
lrwxrwxrwx 1 root root7 maj 9 23:14 PE2950-swap - ../dm-0
Then I created /etc/multipath.conf with following contents (mostly
copied from running multipathd config):
multipath.conf:
--
defaults {
verbosity 2
}
blacklist {
devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*
devnode ^hd[a-z]
devnode ^dcssblk[0-9]*
devnode ^cciss!c[0-9]d[0-9]*
device {
vendor DGC
product LUNZ
}
device {
vendor EMC
product LUNZ
}
device {
vendor IBM
product S/390.*
}
device {
vendor IBM
product S/390.*
}
device {
vendor STK
product Universal Xport
}
device {
vendor DELL
product PERC.*
}
}
blacklist_exceptions {
}
devices {
device {
vendor HP
product MSA2[02]12fc|MSA2012i
path_grouping_policy multibus
getuid_callout /lib/udev/scsi_id --whitelisted
--device=/dev/%n
path_selector round-robin 0
path_checker tur
checker tur
features 0
hardware_handler 0
prio const
failback immediate
no_path_retry 18
rr_min_io 100
}
}
multipaths {
}
(point is in trying to turn off the feature 'queue_if_no_path')
root@PE2950:~# ll /etc/multipath.conf
-rw-r--r-- 1 root root 0 maj 10 17:14 /etc/multipath.conf
Have to reboot:
root@PE2950:~$ reboot
Things get ugly - no more mappings:
root@PE2950:~# multipath -ll
root@PE2950:~#
root@PE2950:~# ls -la /dev/mapper/
total 0
drwxr-xr-x 2 root root 100 maj 10 17:23 .
drwxr-xr-x 16 root root4420 maj 10 17:23 ..
crw--- 1 root root 10, 236 maj 10 17:22 control
lrwxrwxrwx 1 root root 7 maj 10 17:22 PE2950-root - ../dm-1
lrwxrwxrwx 1 root root 7 maj 10 17:22 PE2950-swap - ../dm-0
syslog:
--snip--
May 10 17:23:33 PE2950 udevd[380]: '/lib/udev/dmsetup_env 252 2'(err) 'Device
does not exist.'
May 10 17:23:33 PE2950 udevd[380]: '/lib/udev/dmsetup_env 252 2'(err) 'Command
failed'
May 10 17:23:33 PE2950 scsi_id[1156]: custom logging function 0x7f93cbe8d010
registered
May 10 17:23:33 PE2950 udevd[380]: '/lib/udev/dmsetup_env 252 2'(err) 'Device
does not exist.'
May 10 17:23:33 PE2950 udevd[380]: '/lib/udev/dmsetup_env 252 2'(err) 'Command
failed'
May 10 17:23:33 PE2950 udevd[380]: '/lib/udev/dmsetup_env 252 2'(out) 'DM_NAME='
May 10 17:23:33 PE2950 udevd[380]: '/lib/udev/dmsetup_env 252 2' [1154] exit
with return code 0
--snip--
May 10 17:23:33 PE2950 kernel: [ 90.706237] device-mapper: multipath
round-robin: version 1.0.0 loaded
May 10 17:23:33 PE2950 kernel: [ 90.706403] device-mapper: table: 252:2:
multipath: not enough path parameters
May 10 17:23:33 PE2950 kernel: [ 90.706405] device-mapper: ioctl: error
adding target to table
--snip--
May 10 17:23:33 PE2950 udevd[379]: no db file to read
/run/udev/data/+bdi:252:2: No such file or directory
May 10 17:23:33 PE2950 udevd[378]: '/sbin/blkid -o udev -p
/dev/.tmp-block-252:2'(err) 'error: /dev/.tmp-block-252:2: No such device or
address'
--snip--
May 10 17:23:33 PE2950 udevd[378]: '/lib/udev/dmsetup_env 252 2'(err) 'Device
does not exist.'
May 10 17:23:33 PE2950 udevd[378]: '/lib/udev/dmsetup_env 252 2'(err) 'Command
failed'
May 10 17:23:33 PE2950 udevd[378]: '/lib/udev/dmsetup_env 252 2'(err) 'Device
does not exist.'
May 10 17:23:33 PE2950 udevd[378]: '/lib/udev/dmsetup_env 252 2'(err) 'Command
failed'
May 10 17:23:33 PE2950 udevd[378]: '/lib/udev/dmsetup_env 252 2'(out) 'DM_NAME='
May 10 17:23:33 PE2950 udevd[378]: '/lib/udev/dmsetup_env 252 2' [1173] exit
with return code 0
--snip--
May 10
[Bug 1178721] Re: multipathd fails to create mappings when multipath.conf is present
** Attachment added: udev log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+attachment/3672267/+files/udev.multipath-BROKEN -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1178721 Title: multipathd fails to create mappings when multipath.conf is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1178721] [NEW] multipathd fails to create mappings when multipath.conf is present
Public bug reported:
I have a SAN connected via a dual-port HBA that I'm trying to get to
work with multipath.
I'm running 12.04.2 installed via netboot (clean install).
Setup options: partitioning=guided with LVM (onto internal DRAC 6/i RAID)
packages=Basic server,OpenSSH,Virtual machine host
Out of the box things work okay:
root@PE2950:~# multipath -ll
3600c0ff000d5ae56aabb85510100 dm-3 HP,MSA2012fc
size=1.4T features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 3:0:0:1 sdb 8:16 active ready running
`- 4:0:1:1 sdc 8:32 active ready running
mappings are created:
root@PE2950:~# ll /dev/mapper/
total 0
drwxr-xr-x 2 root root 140 maj 10 16:57 ./
drwxr-xr-x 16 root root 4460 maj 10 16:57 ../
brw-rw 1 root disk 252, 2 maj 10 16:57 360022190ba84f800113787c003d70474
lrwxrwxrwx 1 root root7 maj 10 16:57 3600c0ff000d5ae56aabb85510100
- ../dm-3
crw--- 1 root root 10, 236 maj 9 23:13 control
lrwxrwxrwx 1 root root7 maj 9 23:14 PE2950-root - ../dm-1
lrwxrwxrwx 1 root root7 maj 9 23:14 PE2950-swap - ../dm-0
Then I created /etc/multipath.conf with following contents (mostly
copied from running multipathd config):
multipath.conf:
--
defaults {
verbosity 2
}
blacklist {
devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*
devnode ^hd[a-z]
devnode ^dcssblk[0-9]*
devnode ^cciss!c[0-9]d[0-9]*
device {
vendor DGC
product LUNZ
}
device {
vendor EMC
product LUNZ
}
device {
vendor IBM
product S/390.*
}
device {
vendor IBM
product S/390.*
}
device {
vendor STK
product Universal Xport
}
device {
vendor DELL
product PERC.*
}
}
blacklist_exceptions {
}
devices {
device {
vendor HP
product MSA2[02]12fc|MSA2012i
path_grouping_policy multibus
getuid_callout /lib/udev/scsi_id --whitelisted
--device=/dev/%n
path_selector round-robin 0
path_checker tur
checker tur
features 0
hardware_handler 0
prio const
failback immediate
no_path_retry 18
rr_min_io 100
}
}
multipaths {
}
(point is in trying to turn off the feature 'queue_if_no_path')
root@PE2950:~# ll /etc/multipath.conf
-rw-r--r-- 1 root root 0 maj 10 17:14 /etc/multipath.conf
Have to reboot:
root@PE2950:~$ reboot
Things get ugly - no more mappings:
root@PE2950:~# multipath -ll
root@PE2950:~#
root@PE2950:~# ls -la /dev/mapper/
total 0
drwxr-xr-x 2 root root 100 maj 10 17:23 .
drwxr-xr-x 16 root root4420 maj 10 17:23 ..
crw--- 1 root root 10, 236 maj 10 17:22 control
lrwxrwxrwx 1 root root 7 maj 10 17:22 PE2950-root - ../dm-1
lrwxrwxrwx 1 root root 7 maj 10 17:22 PE2950-swap - ../dm-0
syslog:
--snip--
May 10 17:23:33 PE2950 udevd[380]: '/lib/udev/dmsetup_env 252 2'(err) 'Device
does not exist.'
May 10 17:23:33 PE2950 udevd[380]: '/lib/udev/dmsetup_env 252 2'(err) 'Command
failed'
May 10 17:23:33 PE2950 scsi_id[1156]: custom logging function 0x7f93cbe8d010
registered
May 10 17:23:33 PE2950 udevd[380]: '/lib/udev/dmsetup_env 252 2'(err) 'Device
does not exist.'
May 10 17:23:33 PE2950 udevd[380]: '/lib/udev/dmsetup_env 252 2'(err) 'Command
failed'
May 10 17:23:33 PE2950 udevd[380]: '/lib/udev/dmsetup_env 252 2'(out) 'DM_NAME='
May 10 17:23:33 PE2950 udevd[380]: '/lib/udev/dmsetup_env 252 2' [1154] exit
with return code 0
--snip--
May 10 17:23:33 PE2950 kernel: [ 90.706237] device-mapper: multipath
round-robin: version 1.0.0 loaded
May 10 17:23:33 PE2950 kernel: [ 90.706403] device-mapper: table: 252:2:
multipath: not enough path parameters
May 10 17:23:33 PE2950 kernel: [ 90.706405] device-mapper: ioctl: error
adding target to table
--snip--
May 10 17:23:33 PE2950 udevd[379]: no db file to read
/run/udev/data/+bdi:252:2: No such file or directory
May 10 17:23:33 PE2950 udevd[378]: '/sbin/blkid -o udev -p
/dev/.tmp-block-252:2'(err) 'error: /dev/.tmp-block-252:2: No such device or
address'
--snip--
May 10 17:23:33 PE2950 udevd[378]: '/lib/udev/dmsetup_env 252 2'(err) 'Device
does not exist.'
May 10 17:23:33 PE2950 udevd[378]: '/lib/udev/dmsetup_env 252 2'(err) 'Command
failed'
May 10 17:23:33 PE2950 udevd[378]: '/lib/udev/dmsetup_env 252 2'(err) 'Device
does not exist.'
May 10 17:23:33 PE2950 udevd[378]: '/lib/udev/dmsetup_env 252 2'(err) 'Command
failed'
May 10 17:23:33 PE2950 udevd[378]: '/lib/udev/dmsetup_env 252 2'(out) 'DM_NAME='
May 10 17:23:33 PE2950 udevd[378]: '/lib/udev/dmsetup_env 252 2' [1173] exit
with return code 0
--snip--
May 10
[Bug 1178721] Re: multipathd fails to create mappings when multipath.conf is present
** Attachment added: udev log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+attachment/3672267/+files/udev.multipath-BROKEN -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178721 Title: multipathd fails to create mappings when multipath.conf is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1178721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063445] Re: Wireless not connecting, disconnecting
This seems like a problem with DHCP (this is on an unencrypted network): Oct 9 12:07:32 acer dhclient: Internet Systems Consortium DHCP Client 4.1-ESV-R4 Oct 9 12:07:32 acer dhclient: Copyright 2004-2011 Internet Systems Consortium. Oct 9 12:07:32 acer dhclient: All rights reserved. Oct 9 12:07:32 acer dhclient: For info, please visit https://www.isc.org/software/dhcp/ Oct 9 12:07:32 acer dhclient: Oct 9 12:07:32 acer NetworkManager[915]: info (wlan0): DHCPv4 state changed nbi - preinit Oct 9 12:07:32 acer dhclient: Listening on LPF/wlan0/00:23:4d:38:09:45 Oct 9 12:07:32 acer dhclient: Sending on LPF/wlan0/00:23:4d:38:09:45 Oct 9 12:07:32 acer dhclient: Sending on Socket/fallback Oct 9 12:07:32 acer dhclient: DHCPREQUEST of 192.168.1.79 on wlan0 to 255.255.255.255 port 67 Oct 9 12:07:33 acer dhclient: DHCPNAK from 192.168.1.75 Oct 9 12:07:33 acer NetworkManager[915]: info (wlan0): DHCPv4 state changed preinit - expire Oct 9 12:07:33 acer dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 Oct 9 12:07:33 acer NetworkManager[915]: info (wlan0): DHCPv4 state changed expire - preinit Oct 9 12:07:33 acer avahi-daemon[734]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::223:4dff:fe38:945. Oct 9 12:07:33 acer avahi-daemon[734]: New relevant interface wlan0.IPv6 for mDNS. Oct 9 12:07:33 acer avahi-daemon[734]: Registering new address record for fe80::223:4dff:fe38:945 on wlan0.*. Oct 9 12:07:36 acer dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 Oct 9 12:07:42 acer kernel: [ 2265.920079] wlan0: no IPv6 routers present Oct 9 12:07:44 acer dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 Oct 9 12:07:55 acer dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19 Oct 9 12:08:14 acer dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19 Oct 9 12:08:18 acer NetworkManager[915]: warn (wlan0): DHCPv4 request timed out. Oct 9 12:08:18 acer NetworkManager[915]: info (wlan0): canceled DHCP transaction, DHCP client pid 3878 dhclient sends a request for .79 (I'm assuming this is its last known dhcp address), which is denied by the server on .75. The client then sends a DHCPDISCOVER which should be replied to by a DHCP offer by the server, but it never is, so the discovery times out. A manual address setting works, so it does seem to confirm this. If there is nothing wrong with the server, my thoughts would be that there is something wrong with the discover packets (malformed maybe), or something is eating up the offers on route back from the server. --- Also, a WPA-PSK TKIP network: Oct 2 20:03:36 acer dhclient: Internet Systems Consortium DHCP Client 4.1-ESV-R4 Oct 2 20:03:36 acer dhclient: Copyright 2004-2011 Internet Systems Consortium. Oct 2 20:03:36 acer dhclient: All rights reserved. Oct 2 20:03:36 acer dhclient: For info, please visit https://www.isc.org/software/dhcp/ Oct 2 20:03:36 acer dhclient: Oct 2 20:03:36 acer NetworkManager[912]: info (wlan0): DHCPv4 state changed nbi - preinit Oct 2 20:03:36 acer dhclient: Listening on LPF/wlan0/00:23:4d:38:09:45 Oct 2 20:03:36 acer dhclient: Sending on LPF/wlan0/00:23:4d:38:09:45 Oct 2 20:03:36 acer dhclient: Sending on Socket/fallback Oct 2 20:03:36 acer dhclient: DHCPREQUEST of 192.168.1.22 on wlan0 to 255.255.255.255 port 67 Oct 2 20:03:37 acer wpa_supplicant[990]: Michael MIC failure detected Oct 2 20:03:37 acer wpa_supplicant[990]: WPA: Sending EAPOL-Key Request (error=1 pairwise=1 ptk_set=1 len=99) Oct 2 20:03:37 acer wpa_supplicant[990]: Michael MIC failure detected Oct 2 20:03:37 acer wpa_supplicant[990]: WPA: Sending EAPOL-Key Request (error=1 pairwise=1 ptk_set=1 len=99) Oct 2 20:03:37 acer wpa_supplicant[990]: TKIP countermeasures started Oct 2 20:03:37 acer kernel: [ 7529.682694] wlan0: deauthenticated from 00:18:4d:7e:06:84 (Reason: 14) Oct 2 20:03:37 acer kernel: [ 7529.704466] wlan0: deauthenticating from 00:18:4d:7e:06:84 by local choice (reason=14) Michael MIC failures from wpa_supplicant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063445 Title: Wireless not connecting, disconnecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1063445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063445] Re: Wireless not connecting, disconnecting
I was plugged in when trying, not on battery, and it can be seen from lspci that power management is/was off ... (power supply state doesn't change this). It should work regardless, a netbook with no working wireless when on battery wouldn't be really useful :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063445 Title: Wireless not connecting, disconnecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1063445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063445] [NEW] Wireless not connecting, disconnecting
Public bug reported: When trying to connect to almost any wireless network, it never connects, the indicator just keeps moving until it says Disconnected a minute or so later. This happens 100% of the time with all encryped networks, and 99% of the time with unencrypted networks. I have so far have not been able to connect to an encrypted network, only unencrypted after several tries. The very rare case when it does actually manage to connect (this is usually after trying to connect for an hour or so, many times beforehand, switching on/off the wireless with the hardware switch), it actually stays connected until you manually disconnect, and is also quite stable (downloads and PPTP connections work with no problem). Attached is a snippet of the old syslog from a few days ago when I was trying to connect, the current syslog doesn't have any relevant info as I am not near a wireless network currently. I will be in a position to do further testing tomorrow, if needed. The system is a netbook: Acer Aspire one, with Atheros AR5BXB63 wireless card --- $ lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 --- network-manager: Installed: 0.9.4.0-0ubuntu4.1 Candidate: 0.9.4.0-0ubuntu4.1 Version table: *** 0.9.4.0-0ubuntu4.1 0 500 http://si.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.4.0-0ubuntu3 0 500 http://si.archive.ubuntu.com/ubuntu/ precise/main i386 Packages --- $ modinfo ath5k filename: /lib/modules/3.2.0-31-generic-pae/kernel/drivers/net/wireless/ath/ath5k/ath5k.ko license:Dual BSD/GPL description:Support for 5xxx series of Atheros 802.11 wireless LAN cards. author: Nick Kossifidis author: Jiri Slaby srcversion: FA2500C2D3C1A3B6094E37C alias: pci:v168Cd001Dsv*sd*bc*sc*i* alias: pci:v168Cd001Csv*sd*bc*sc*i* alias: pci:v168Cd001Bsv*sd*bc*sc*i* alias: pci:v168Cd001Asv*sd*bc*sc*i* alias: pci:v168Cd0019sv*sd*bc*sc*i* alias: pci:v168Cd0018sv*sd*bc*sc*i* alias: pci:v168Cd0017sv*sd*bc*sc*i* alias: pci:v168Cd0016sv*sd*bc*sc*i* alias: pci:v168Cd0015sv*sd*bc*sc*i* alias: pci:v168Cd0014sv*sd*bc*sc*i* alias: pci:v168Cd1014sv*sd*bc*sc*i* alias: pci:v10B7d0013sv*sd*bc*sc*i* alias: pci:vA727d0013sv*sd*bc*sc*i* alias: pci:v168Cd0013sv*sd*bc*sc*i* alias: pci:v168Cd0012sv*sd*bc*sc*i* alias: pci:v168Cd0011sv*sd*bc*sc*i* alias: pci:v168Cd0007sv*sd*bc*sc*i* alias: pci:v168Cd0207sv*sd*bc*sc*i* depends:mac80211,cfg80211,ath intree: Y vermagic: 3.2.0-31-generic-pae SMP mod_unload modversions 686 parm: nohwcrypt:Disable hardware encryption. (bool) parm: all_channels:Expose all channels the device can use. (bool) parm: fastchanswitch:Enable fast channel switching for AR2413/AR5413 radios. (bool) $ iwconfig lono wireless extensions. virbr0no wireless extensions. wlan0 IEEE 802.11bg ESSID:Prospero632 Mode:Managed Frequency:2.462 GHz Access Point: 02:30:B4:0B:56:50 Bit Rate=1 Mb/s Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=13/70 Signal level=-97 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:1 Invalid misc:2 Missed beacon:0 eth0 no wireless extensions. $ lspci -v (omitted irrelevant devices) 03:00.0 Ethernet controller: Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: Foxconn International, Inc. Device e008 Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at 5520 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 2 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [90] MSI-X: Enable- Count=1 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Kernel driver in use: ath5k Kernel modules: ath5k - ProblemType: Bug DistroRelease: Ubuntu 12.04 Package:
[Bug 1063445] Re: Wireless not connecting, disconnecting
** Attachment added: Syslog snippet with relevant log output https://bugs.launchpad.net/bugs/1063445/+attachment/3384090/+files/syslog.snip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063445 Title: Wireless not connecting, disconnecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1063445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063445] Re: Wireless not connecting, disconnecting
** Description changed: When trying to connect to almost any wireless network, it never connects, the indicator just keeps moving until it says Disconnected a minute or so later. This happens 100% of the time with all encryped networks, and 99% of the time with unencrypted networks. I have so far have not been able to connect to an encrypted network, only unencrypted after several tries. - The very rare case when it does actually manage to connect (this is usually after trying to connect for an hour or so, many times beforehand, switching on/off the wireless with the hardware switch), it actually stays connected until you manually disconnect, and is also quite stable (downloads and PPTP connections work with no problem). + The very rare case when it does actually manage to connect (this is usually after trying to connect for an hour or so, many times beforehand, switching on/off the wireless with the hardware switch), it actually stays connected until you manually disconnect, and is also quite stable (downloads and PPTP connections work with no problem). Attached is a snippet of the old syslog from a few days ago when I was trying to connect, the current syslog doesn't have any relevant info as I am not near a wireless network currently. I will be in a position to do further testing tomorrow, if needed. The system is a netbook: Acer Aspire one, with Atheros AR5BXB63 wireless card - - + --- $ lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 + --- + network-manager: + Installed: 0.9.4.0-0ubuntu4.1 + Candidate: 0.9.4.0-0ubuntu4.1 + Version table: + *** 0.9.4.0-0ubuntu4.1 0 + 500 http://si.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages + 100 /var/lib/dpkg/status + 0.9.4.0-0ubuntu3 0 + 500 http://si.archive.ubuntu.com/ubuntu/ precise/main i386 Packages + --- + $ modinfo ath5k - network-manager: - Installed: 0.9.4.0-0ubuntu4.1 - Candidate: 0.9.4.0-0ubuntu4.1 - Version table: - *** 0.9.4.0-0ubuntu4.1 0 - 500 http://si.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages - 100 /var/lib/dpkg/status - 0.9.4.0-0ubuntu3 0 - 500 http://si.archive.ubuntu.com/ubuntu/ precise/main i386 Packages + filename: /lib/modules/3.2.0-31-generic-pae/kernel/drivers/net/wireless/ath/ath5k/ath5k.ko + license:Dual BSD/GPL + description:Support for 5xxx series of Atheros 802.11 wireless LAN cards. + author: Nick Kossifidis + author: Jiri Slaby + srcversion: FA2500C2D3C1A3B6094E37C + alias: pci:v168Cd001Dsv*sd*bc*sc*i* + alias: pci:v168Cd001Csv*sd*bc*sc*i* + alias: pci:v168Cd001Bsv*sd*bc*sc*i* + alias: pci:v168Cd001Asv*sd*bc*sc*i* + alias: pci:v168Cd0019sv*sd*bc*sc*i* + alias: pci:v168Cd0018sv*sd*bc*sc*i* + alias: pci:v168Cd0017sv*sd*bc*sc*i* + alias: pci:v168Cd0016sv*sd*bc*sc*i* + alias: pci:v168Cd0015sv*sd*bc*sc*i* + alias: pci:v168Cd0014sv*sd*bc*sc*i* + alias: pci:v168Cd1014sv*sd*bc*sc*i* + alias: pci:v10B7d0013sv*sd*bc*sc*i* + alias: pci:vA727d0013sv*sd*bc*sc*i* + alias: pci:v168Cd0013sv*sd*bc*sc*i* + alias: pci:v168Cd0012sv*sd*bc*sc*i* + alias: pci:v168Cd0011sv*sd*bc*sc*i* + alias: pci:v168Cd0007sv*sd*bc*sc*i* + alias: pci:v168Cd0207sv*sd*bc*sc*i* + depends:mac80211,cfg80211,ath + intree: Y + vermagic: 3.2.0-31-generic-pae SMP mod_unload modversions 686 + parm: nohwcrypt:Disable hardware encryption. (bool) + parm: all_channels:Expose all channels the device can use. (bool) + parm: fastchanswitch:Enable fast channel switching for AR2413/AR5413 radios. (bool) - - 03:00.0 Ethernet controller: Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01) - Subsystem: Foxconn International, Inc. Device e008 - Flags: bus master, fast devsel, latency 0, IRQ 18 - Memory at 5520 (64-bit, non-prefetchable) [size=64K] - Capabilities: access denied - Kernel driver in use: ath5k - Kernel modules: ath5k - - + $ iwconfig lono wireless extensions. virbr0no wireless extensions. - wlan0 IEEE 802.11bg ESSID:Prospero632 - Mode:Managed Frequency:2.462 GHz Access Point: 02:30:B4:0B:56:50 - Bit Rate=1 Mb/s Tx-Power=20 dBm -
