[Bug 1714139] [NEW] will not boot after logout grub reloader
Public bug reported: I tried to install but it says will not boot because ofgrub ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubiquity 17.04.9 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CasperVersion: 1.380 Date: Thu Aug 31 11:56:32 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity quiet splash oem-config/enable=true --- LiveMediaBuild: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lubuntu ubiquity-17.04.9 zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714139 Title: will not boot after logout grub reloader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1714139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241180] Re: Oversized copypaste dialog in calculator
It also affects me, i'm using fresh 13.10 with XMir server and 3.11 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241180 Title: Oversized copypaste dialog in calculator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1241180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990661] Re: lightdm zombie process created while press escape button on Login screen
Any progress on patching this on Precise? Robert was pinged about this back on 9/12 since it wasn't ready before 12.04.1 but could be patched now. I've seen no update/response since... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990661 Title: lightdm zombie process created while press escape button on Login screen To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/990661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1110947] [NEW] nvidia-current logging into console
Public bug reported: On my Lenovo IdeaPad Y550 with GeForce GT240M I can't get nvidia proprietary drivers to work. On kernel 2.6 everything works fine. On 3.x - it doesn't work. Google says nothing, askubuntu and #ubuntu on irc says nothing. I don't have an Optimus. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-current 295.40-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Uname: Linux 3.2.0-36-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 295.40 Thu Apr 5 21:37:00 PDT 2012 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] Date: Thu Jan 31 02:23:32 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-current, 295.40, 3.2.0-36-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 240M] [10de:0a34] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:38ff] InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:nvidia_experimental_304 - NVIDIA accelerated graphics driver (**experimental** beta) (Proprietary, Disabled, Not in use) xorg:nvidia_experimental_310 - NVIDIA accelerated graphics driver (**experimental** beta) (Proprietary, Disabled, Not in use) MachineType: LENOVO 20017 MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-36-generic root=UUID=fa2def3b-e3b7-4665-b919-91c2001c03b1 ro quiet splash vt.handoff=7 SourcePackage: nvidia-graphics-drivers UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 15CN35WW(V2.08) dmi.board.name: KIWB1 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr15CN35WW(V2.08):bd03/15/2010:svnLENOVO:pn20017:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 20017 dmi.product.version: Lenovo IdeaPad Y550 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.nvidia.current.hybrid.conf: [deleted] version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise referred-by-support ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1110947 Title: nvidia-current logging into console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1110947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103656] Re: Update Precise drbd8-utils to 8.3.13 for the 12.04.2 release
I'm not the reporter but I am a daily user of DRBD on precise. If someone is running the old kernel then they should use the matching older version of drbd8-utils. So if the module in the kernel is 8.3.11 then the tools should be also or if the module is 8.3.13 then the tools should be 8.3.13 also. I'm a total newbie about packaging but is there a way to make it so drbd8-utils version 8.3.11 is required to be upgraded if you go to kernel = 3.5 and drbd is installed? And if you install/downgrade to kernel 3.5 drbd8-utils must be downgraded to 8.3.11 at the same time if installed - through dependencies or something? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1103656 Title: Update Precise drbd8-utils to 8.3.13 for the 12.04.2 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1103656/+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 1103656] Re: Update Precise drbd8-utils to 8.3.13 for the 12.04.2 release
I'm not the reporter but I am a daily user of DRBD on precise. If someone is running the old kernel then they should use the matching older version of drbd8-utils. So if the module in the kernel is 8.3.11 then the tools should be also or if the module is 8.3.13 then the tools should be 8.3.13 also. I'm a total newbie about packaging but is there a way to make it so drbd8-utils version 8.3.11 is required to be upgraded if you go to kernel = 3.5 and drbd is installed? And if you install/downgrade to kernel 3.5 drbd8-utils must be downgraded to 8.3.11 at the same time if installed - through dependencies or something? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103656 Title: Update Precise drbd8-utils to 8.3.13 for the 12.04.2 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1103656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966039] Re: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update()
Any chance of a patch to at least quiet this down? Or some additional info we can provide to try to fix the problem?? These are writing to log every 15 seconds: Dec 25 23:25:27 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Dec 25 23:25:42 Condor snmpd[3908]: c64 32 bit check failed Dec 25 23:25:57 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Dec 25 23:26:12 Condor snmpd[3908]: c64 32 bit check failed Dec 25 23:26:27 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Dec 25 23:26:42 Condor snmpd[3908]: c64 32 bit check failed Dec 25 23:26:57 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Dec 25 23:27:12 Condor snmpd[3908]: c64 32 bit check failed Dec 25 23:27:27 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Ubuntu 12.04 Precise with all available updates applied running the latest Lucid kernel: linux-image-2.6.32-45-server 2.6.32-45.101 Linux kernel image for version 2.6.32 on x86_64 snmpd5.4.3~dfsg-2.4ubuntu1.1 SNMP (Simple Network Management Protocol) agents ** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/966039 Title: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/966039/+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 966039] Re: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update()
Any chance of a patch to at least quiet this down? Or some additional info we can provide to try to fix the problem?? These are writing to log every 15 seconds: Dec 25 23:25:27 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Dec 25 23:25:42 Condor snmpd[3908]: c64 32 bit check failed Dec 25 23:25:57 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Dec 25 23:26:12 Condor snmpd[3908]: c64 32 bit check failed Dec 25 23:26:27 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Dec 25 23:26:42 Condor snmpd[3908]: c64 32 bit check failed Dec 25 23:26:57 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Dec 25 23:27:12 Condor snmpd[3908]: c64 32 bit check failed Dec 25 23:27:27 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Ubuntu 12.04 Precise with all available updates applied running the latest Lucid kernel: linux-image-2.6.32-45-server 2.6.32-45.101 Linux kernel image for version 2.6.32 on x86_64 snmpd5.4.3~dfsg-2.4ubuntu1.1 SNMP (Simple Network Management Protocol) agents ** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966039 Title: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/966039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057651] Re: crm_simulate segfaults
This is a known bug in Pacemaker version 1.1.6 I understand that with the LTS release there may be no hope of getting the package upgraded to 1.1.7 but we should at least be able to get this bug fixed I would hope. Patch to fix this is here: https://github.com/beekhof/pacemaker/commit/2bdb230 Output of $crm_simulate -L: *** glibc detected *** crm_simulate: double free or corruption (out): 0x01585e00 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x7e626)[0x7fef66e82626] /usr/lib/libcib.so.1(+0xc259)[0x7fef6775f259] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x373d3)[0x7fef66b463d3] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_hash_table_remove_all+0x1d)[0x7fef66b4724d] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_hash_table_destroy+0xe)[0x7fef66b472de] /usr/lib/libcib.so.1(cib_new_variant+0x155)[0x7fef6775f9fb] /usr/lib/libcib.so.1(cib_file_new+0x28)[0x7fef67765aad] /usr/lib/libcib.so.1(cib_new+0x62)[0x7fef6775f70c] crm_simulate[0x40614f] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7fef66e2576d] crm_simulate[0x402279] === Memory map: 0040-00409000 r-xp fb:05 541771 /usr/sbin/crm_simulate 00608000-00609000 r--p 8000 fb:05 541771 /usr/sbin/crm_simulate 00609000-0060a000 rw-p 9000 fb:05 541771 /usr/sbin/crm_simulate 0157e000-0181c000 rw-p 00:00 0 [heap] 7fef6399a000-7fef639af000 r-xp fb:05 393311 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fef639af000-7fef63bae000 ---p 00015000 fb:05 393311 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fef63bae000-7fef63baf000 r--p 00014000 fb:05 393311 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fef63baf000-7fef63bb rw-p 00015000 fb:05 393311 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fef63bb-7fef63bb3000 r-xp fb:05 393398 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0 7fef63bb3000-7fef63db2000 ---p 3000 fb:05 393398 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0 7fef63db2000-7fef63db3000 r--p 2000 fb:05 393398 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0 7fef63db3000-7fef63db4000 rw-p 3000 fb:05 393398 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0 7fef63db4000-7fef63dbc000 r-xp fb:05 525256 /usr/lib/x86_64-linux-gnu/libltdl.so.7.3.0 7fef63dbc000-7fef63fbc000 ---p 8000 fb:05 525256 /usr/lib/x86_64-linux-gnu/libltdl.so.7.3.0 7fef63fbc000-7fef63fbd000 r--p 8000 fb:05 525256 /usr/lib/x86_64-linux-gnu/libltdl.so.7.3.0 7fef63fbd000-7fef63fbe000 rw-p 9000 fb:05 525256 /usr/lib/x86_64-linux-gnu/libltdl.so.7.3.0 7fef63fbe000-7fef63fcf000 r-xp fb:05 525504 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0 7fef63fcf000-7fef641ce000 ---p 00011000 fb:05 525504 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0 7fef641ce000-7fef641cf000 r--p 0001 fb:05 525504 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0 7fef641cf000-7fef641d rw-p 00011000 fb:05 525504 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0 7fef641d-7fef6424a000 r-xp fb:05 393527 /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0 7fef6424a000-7fef6444a000 ---p 0007a000 fb:05 393527 /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0 7fef6444a000-7fef6444b000 r--p 0007a000 fb:05 393527 /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0 7fef6444b000-7fef6444e000 rw-p 0007b000 fb:05 393527 /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0 7fef6444e000-7fef6445e000 r-xp fb:05 525508 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.12 7fef6445e000-7fef6465d000 ---p 0001 fb:05 525508 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.12 7fef6465d000-7fef6465e000 r--p f000 fb:05 525508 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.12 7fef6465e000-7fef6465f000 rw-p 0001 fb:05 525508 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.12 7fef6465f000-7fef64666000 r-xp fb:05 403340 /lib/x86_64-linux-gnu/librt-2.15.so 7fef64666000-7fef64865000 ---p 7000 fb:05 403340 /lib/x86_64-linux-gnu/librt-2.15.so 7fef64865000-7fef64866000 r--p 6000 fb:05 403340 /lib/x86_64-linux-gnu/librt-2.15.so 7fef64866000-7fef64867000 rw-p 7000 fb:05 403340 /lib/x86_64-linux-gnu/librt-2.15.so 7fef64867000-7fef6487f000 r-xp fb:05 403404 /lib/x86_64-linux-gnu/libpthread-2.15.so 7fef6487f000-7fef64a7e000 ---p 00018000 fb:05 403404 /lib/x86_64-linux-gnu/libpthread-2.15.so 7fef64a7e000-7fef64a7f000 r--p 00017000 fb:05 403404
[Bug 912254] Re: Please upgrade the drbd module to 8.3.13
No log files available - known issue that was patched in 8.3.13 as noted in comment #3 above. Especially important since the new default scheduler of cfq in Precise is known to cause the bug. ** Changed in: drbd8 (Ubuntu) Status: Triaged = Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/912254 Title: Please upgrade the drbd module to 8.3.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/912254/+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 912254] Re: Please upgrade the drbd module to 8.3.13
No log files available - known issue that was patched in 8.3.13 as noted in comment #3 above. Especially important since the new default scheduler of cfq in Precise is known to cause the bug. ** Changed in: drbd8 (Ubuntu) Status: Triaged = Confirmed ** 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/912254 Title: Please upgrade the drbd module to 8.3.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/912254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010602] Re: samba logs are not being reported in logwatch
I will give it a whirl... not sure the exact (best) steps but I assume: Submit a bug against Logwatch at SourceForge.net Follow/answer questions there as needed. If it gets patched then would I need to try to get Debian to pickup the patch before Ubuntu would consider an SRU to 12.04? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+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 1010625] Re: named logs are not being reported in logwatch
I will look into it this week and respond accordingly -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010625 Title: named logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010625/+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 1010602] Re: samba logs are not being reported in logwatch
Just for the record and if anyone wants to check on it. Upstream bug submitted: http://sourceforge.net/tracker/?func=detailaid=3536008group_id=312875atid=1316824# ** Bug watch added: SourceForge.net Tracker #3536008 http://sourceforge.net/support/tracker.php?aid=3536008 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+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 1010602] Re: samba logs are not being reported in logwatch
I will give it a whirl... not sure the exact (best) steps but I assume: Submit a bug against Logwatch at SourceForge.net Follow/answer questions there as needed. If it gets patched then would I need to try to get Debian to pickup the patch before Ubuntu would consider an SRU to 12.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010625] Re: named logs are not being reported in logwatch
I will look into it this week and respond accordingly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010625 Title: named logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010602] Re: samba logs are not being reported in logwatch
Just for the record and if anyone wants to check on it. Upstream bug submitted: http://sourceforge.net/tracker/?func=detailaid=3536008group_id=312875atid=1316824# ** Bug watch added: SourceForge.net Tracker #3536008 http://sourceforge.net/support/tracker.php?aid=3536008 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010602] [NEW] samba logs are not being reported in logwatch
Public bug reported: After upgrading from 10.04 to 12.04 samba logs no longer show up in logwatch reports. There was a change to /usr/share/logwatch/default.conf/logfiles/samba.conf between 10.04 and 12.04: LogFile=samba/* was changed to LogFile=samba/*.log In the samba package the default smb.conf file has logging defined as (no change 10.04-12.04): log file = /var/log/samba/log.%m Since files are log.* they are no longer parsed by logwatch because logwatch only looks for *.log 1. Description:Ubuntu 12.04 LTS Release:12.04 2. logwatch: Installed: 7.4.0+svn20111221rev79-1ubuntu1 Candidate: 7.4.0+svn20111221rev79-1ubuntu1 Version table: *** 7.4.0+svn20111221rev79-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status samba: Installed: 2:3.6.3-2ubuntu2.1 Candidate: 2:3.6.3-2ubuntu2.2 Version table: 2:3.6.3-2ubuntu2.2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages *** 2:3.6.3-2ubuntu2.1 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 2:3.6.3-2ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 3. Logwatch reports/emails should contain samba log information. 4. No samba log information shows up in logwatch reports/emails. Possible fix is to distribute the attached samba.conf in /usr/share/logwatch/dist.conf/logfiles/ It contains LogFile=samba/* which would revert logwatch's behavior to what it was in 10.04 for samba logs. This will allow any type of log file naming you wish in your samba config in the /var/log/samba/ folder to be correctly parsed by logwatch. ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New ** Tags: regression -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+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 1010602] Re: samba logs are not being reported in logwatch
** Attachment added: Fix to revert back to prior working settings https://bugs.launchpad.net/bugs/1010602/+attachment/3181066/+files/samba.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+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 1010602] Re: samba logs are not being reported in logwatch
Here is the source commit that changed the samba.conf. The reason listed was: samba.conf patch to deal with cores dir -mgt I have no idea what that means honestly but maybe it would be of help to know... http://logwatch.svn.sourceforge.net/viewvc/logwatch?view=revisionrevision=5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+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 1010625] [NEW] named logs are not being reported in logwatch
Public bug reported: After upgrading from 10.04 to 12.04 named logs no longer show up in logwatch reports. Not sure if this should be filed as a bug against rsyslog or logwatch. There was a change to /etc/rsyslog.d/50-default.conf between 10.04 and 12.04 and a bunch of the seperate log files are now commented out and most things are only in /var/log/syslog Since the /usr/share/logwatch/default.conf/services/named.conf lists messages as the log file it never reports any log data. I changed my /etc/rsyslog.d/50-default.conf by uncommenting these lines (match the config in 10.04): daemon. lpr. user. mail.info mail.warn *.=debug *.=info The last one above sends most stuff to the messages file so named logs entries show up in logwatch reports after making the above changes. Part of me believes rsyslog should be considered the problem but on the other hand if rsyslog is correct then logwatch's named.conf needs to be overiden in dist.conf to correct for the rsyslog change. 1. Description: Ubuntu 12.04 LTS Release: 12.04 2. logwatch: Installed: 7.4.0+svn20111221rev79-1ubuntu1 Candidate: 7.4.0+svn20111221rev79-1ubuntu1 Version table: *** 7.4.0+svn20111221rev79-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status bind9: Installed: 1:9.8.1.dfsg.P1-4 Candidate: 1:9.8.1.dfsg.P1-4ubuntu0.1 Version table: 1:9.8.1.dfsg.P1-4ubuntu0.1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages *** 1:9.8.1.dfsg.P1-4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status rsyslog: Installed: 5.8.6-1ubuntu8 Candidate: 5.8.6-1ubuntu8 Version table: *** 5.8.6-1ubuntu8 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status 3. Logwatch reports/emails should contain named log information. 4. No named log information shows up in logwatch reports/emails. ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010625 Title: named logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010625/+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 1010602] [NEW] samba logs are not being reported in logwatch
Public bug reported: After upgrading from 10.04 to 12.04 samba logs no longer show up in logwatch reports. There was a change to /usr/share/logwatch/default.conf/logfiles/samba.conf between 10.04 and 12.04: LogFile=samba/* was changed to LogFile=samba/*.log In the samba package the default smb.conf file has logging defined as (no change 10.04-12.04): log file = /var/log/samba/log.%m Since files are log.* they are no longer parsed by logwatch because logwatch only looks for *.log 1. Description:Ubuntu 12.04 LTS Release:12.04 2. logwatch: Installed: 7.4.0+svn20111221rev79-1ubuntu1 Candidate: 7.4.0+svn20111221rev79-1ubuntu1 Version table: *** 7.4.0+svn20111221rev79-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status samba: Installed: 2:3.6.3-2ubuntu2.1 Candidate: 2:3.6.3-2ubuntu2.2 Version table: 2:3.6.3-2ubuntu2.2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages *** 2:3.6.3-2ubuntu2.1 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 2:3.6.3-2ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 3. Logwatch reports/emails should contain samba log information. 4. No samba log information shows up in logwatch reports/emails. Possible fix is to distribute the attached samba.conf in /usr/share/logwatch/dist.conf/logfiles/ It contains LogFile=samba/* which would revert logwatch's behavior to what it was in 10.04 for samba logs. This will allow any type of log file naming you wish in your samba config in the /var/log/samba/ folder to be correctly parsed by logwatch. ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New ** Tags: regression -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010602] Re: samba logs are not being reported in logwatch
** Attachment added: Fix to revert back to prior working settings https://bugs.launchpad.net/bugs/1010602/+attachment/3181066/+files/samba.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010602] Re: samba logs are not being reported in logwatch
Here is the source commit that changed the samba.conf. The reason listed was: samba.conf patch to deal with cores dir -mgt I have no idea what that means honestly but maybe it would be of help to know... http://logwatch.svn.sourceforge.net/viewvc/logwatch?view=revisionrevision=5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010625] [NEW] named logs are not being reported in logwatch
Public bug reported: After upgrading from 10.04 to 12.04 named logs no longer show up in logwatch reports. Not sure if this should be filed as a bug against rsyslog or logwatch. There was a change to /etc/rsyslog.d/50-default.conf between 10.04 and 12.04 and a bunch of the seperate log files are now commented out and most things are only in /var/log/syslog Since the /usr/share/logwatch/default.conf/services/named.conf lists messages as the log file it never reports any log data. I changed my /etc/rsyslog.d/50-default.conf by uncommenting these lines (match the config in 10.04): daemon. lpr. user. mail.info mail.warn *.=debug *.=info The last one above sends most stuff to the messages file so named logs entries show up in logwatch reports after making the above changes. Part of me believes rsyslog should be considered the problem but on the other hand if rsyslog is correct then logwatch's named.conf needs to be overiden in dist.conf to correct for the rsyslog change. 1. Description: Ubuntu 12.04 LTS Release: 12.04 2. logwatch: Installed: 7.4.0+svn20111221rev79-1ubuntu1 Candidate: 7.4.0+svn20111221rev79-1ubuntu1 Version table: *** 7.4.0+svn20111221rev79-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status bind9: Installed: 1:9.8.1.dfsg.P1-4 Candidate: 1:9.8.1.dfsg.P1-4ubuntu0.1 Version table: 1:9.8.1.dfsg.P1-4ubuntu0.1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages *** 1:9.8.1.dfsg.P1-4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status rsyslog: Installed: 5.8.6-1ubuntu8 Candidate: 5.8.6-1ubuntu8 Version table: *** 5.8.6-1ubuntu8 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status 3. Logwatch reports/emails should contain named log information. 4. No named log information shows up in logwatch reports/emails. ** Affects: logwatch (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/1010625 Title: named logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000355] Re: [SRU] drbd fence-peer breaks when using kernel 2.6.32-41
Hans - The patch is awaiting verification testing. I was unable to test the proposed fix since I had mitigated the bug already on my servers by the time it was available. Looks like tmortensen has tested it so I would expect you to see the patch available soon! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1000355 Title: [SRU] drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+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 1000355] Re: [SRU] drbd fence-peer breaks when using kernel 2.6.32-41
Hans - The patch is awaiting verification testing. I was unable to test the proposed fix since I had mitigated the bug already on my servers by the time it was available. Looks like tmortensen has tested it so I would expect you to see the patch available soon! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000355 Title: [SRU] drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000355] [NEW] drbd fence-peer breaks when using kernel 2.6.32-41
Public bug reported: Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8 Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685 This causes the drbd fencing script's exit codes to be incorrectly interpreted which then breaks the drbd fencing: To replicate: Have fencing enabled in drbd config: In handlers section: fence-peer /usr/lib/drbd/crm-fence-peer.sh In the disk section: fencing resource-only; Have both drbd nodes uptodate with one primary one secondary Make the fence-peer get executed. I did this by: Having drbd under pacemaker control. Both pacemaker nodes were online and in-sync. Drbd in primary on node 1. Put node 1 in standby. Fence-peer will get executed. Fence handler will report fence-peer exited with 0 (broken) - such as this: May 15 09:45:17 kernel: [56645.420714] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 May 15 09:45:17 kernel: [56645.420920] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 exit code 0 (0x0) May 15 09:45:17 kernel: [56645.420925] block drbd0: fence-peer helper broken, returned 0 If you log debug output of fence-peer script (crm-fence-peer.sh) when executed it exits 4 not the kernel reported 0. This commit in drbd git should fix this behavior: http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43 This will cause complete failure of a drbd setup using fencing to auto-recover or continue without manual intervention and repair. ** Affects: drbd8 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1000355 Title: drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+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 1000355] Re: drbd fence-peer breaks when using kernel 2.6.32-41
Unfortunately unable to collect such log files due to the nature of the bug and changes since to bring systems back to working order. I might have further info I could give - if there are specific questions I will try to answer. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1000355 Title: drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+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 1000355] Re: drbd fence-peer breaks when using kernel 2.6.32-41
** Description changed: Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8 Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685 This causes the drbd fencing script's exit codes to be incorrectly interpreted which then breaks the drbd fencing: + + This also affects linux source in all distributions after Lucid + with the applicable kernel versions patched in bug 963685 above since + the drbd kernel module is mainlined in those more recent kernel versions + To replicate: Have fencing enabled in drbd config: In handlers section: fence-peer /usr/lib/drbd/crm-fence-peer.sh In the disk section: fencing resource-only; Have both drbd nodes uptodate with one primary one secondary Make the fence-peer get executed. I did this by: Having drbd under pacemaker control. Both pacemaker nodes were online and in-sync. Drbd in primary on node 1. Put node 1 in standby. Fence-peer will get executed. Fence handler will report fence-peer exited with 0 (broken) - such as this: May 15 09:45:17 kernel: [56645.420714] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 May 15 09:45:17 kernel: [56645.420920] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 exit code 0 (0x0) May 15 09:45:17 kernel: [56645.420925] block drbd0: fence-peer helper broken, returned 0 If you log debug output of fence-peer script (crm-fence-peer.sh) when executed it exits 4 not the kernel reported 0. - This commit in drbd git should fix this behavior: http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43 - - This will cause complete failure of a drbd setup using fencing to auto-recover or continue without manual intervention and repair. + This will cause complete failure of a drbd setup using fencing to auto- + recover or continue without manual intervention and repair. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1000355 Title: drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+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 1000355] Re: drbd fence-peer breaks when using kernel 2.6.32-41
** Changed in: drbd8 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1000355 Title: drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+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 1000355] [NEW] drbd fence-peer breaks when using kernel 2.6.32-41
Public bug reported: Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8 Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685 This causes the drbd fencing script's exit codes to be incorrectly interpreted which then breaks the drbd fencing: To replicate: Have fencing enabled in drbd config: In handlers section: fence-peer /usr/lib/drbd/crm-fence-peer.sh In the disk section: fencing resource-only; Have both drbd nodes uptodate with one primary one secondary Make the fence-peer get executed. I did this by: Having drbd under pacemaker control. Both pacemaker nodes were online and in-sync. Drbd in primary on node 1. Put node 1 in standby. Fence-peer will get executed. Fence handler will report fence-peer exited with 0 (broken) - such as this: May 15 09:45:17 kernel: [56645.420714] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 May 15 09:45:17 kernel: [56645.420920] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 exit code 0 (0x0) May 15 09:45:17 kernel: [56645.420925] block drbd0: fence-peer helper broken, returned 0 If you log debug output of fence-peer script (crm-fence-peer.sh) when executed it exits 4 not the kernel reported 0. This commit in drbd git should fix this behavior: http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43 This will cause complete failure of a drbd setup using fencing to auto-recover or continue without manual intervention and repair. ** Affects: drbd8 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Also affects: linux (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/1000355 Title: drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000355] Re: drbd fence-peer breaks when using kernel 2.6.32-41
Unfortunately unable to collect such log files due to the nature of the bug and changes since to bring systems back to working order. I might have further info I could give - if there are specific questions I will try to answer. ** 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/1000355 Title: drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000355] Re: drbd fence-peer breaks when using kernel 2.6.32-41
** Description changed: Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8 Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685 This causes the drbd fencing script's exit codes to be incorrectly interpreted which then breaks the drbd fencing: + + This also affects linux source in all distributions after Lucid + with the applicable kernel versions patched in bug 963685 above since + the drbd kernel module is mainlined in those more recent kernel versions + To replicate: Have fencing enabled in drbd config: In handlers section: fence-peer /usr/lib/drbd/crm-fence-peer.sh In the disk section: fencing resource-only; Have both drbd nodes uptodate with one primary one secondary Make the fence-peer get executed. I did this by: Having drbd under pacemaker control. Both pacemaker nodes were online and in-sync. Drbd in primary on node 1. Put node 1 in standby. Fence-peer will get executed. Fence handler will report fence-peer exited with 0 (broken) - such as this: May 15 09:45:17 kernel: [56645.420714] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 May 15 09:45:17 kernel: [56645.420920] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 exit code 0 (0x0) May 15 09:45:17 kernel: [56645.420925] block drbd0: fence-peer helper broken, returned 0 If you log debug output of fence-peer script (crm-fence-peer.sh) when executed it exits 4 not the kernel reported 0. - This commit in drbd git should fix this behavior: http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43 - - This will cause complete failure of a drbd setup using fencing to auto-recover or continue without manual intervention and repair. + This will cause complete failure of a drbd setup using fencing to auto- + recover or continue without manual intervention and repair. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000355 Title: drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000355] Re: drbd fence-peer breaks when using kernel 2.6.32-41
** Changed in: drbd8 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000355 Title: drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990742] Re: slapd fails to upgrade: requires libsasl2-2 (= 2.1.24) installed
I was finally able to get the half upgraded system fixed using the proposed package. After that was running for a bit I went ahead and upgraded another server in my cluster running the same services. I used the proposed libsasl2-2 package and the upgrade completed start to finish without a hiccup. So on 2 servers using the proposed packaged solved the issue without any side affects. Thanks! ** Tags removed: verification-needed ** Tags added: verification-done ** Description changed: I was trying to apt-get install dpkg to work around #944452 and got the following while trying to upgrade slapd: Setting up slapd (2.4.28-1.1ubuntu4) ... Use of uninitialized value $type in ucfirst at /usr/share/perl5/Debconf/AutoSelect.pm line 35. Â Â Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.4.21-0ubuntu5.7... done. Â Â Moving old database directories to /var/backups: Â Â Loading from /var/backups/slapd-2.4.21-0ubuntu5.7: Â Â - directory dc=interlinx,dc=bc,dc=ca... failed. Loading the database from the LDIF dump failed with the following error while running slapadd: 4f9c4903 slap_sasl_init: auxprop add plugin failed slapadd: slap_init failed! dpkg: error processing slapd (--configure): Â subprocess installed post-installation script returned error exit status 1 This looks to be related to http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=665473 where message #10 (http://bugs.debian.org /cgi-bin/bugreport.cgi?bug=665473#10) in that bug says: This looks like a repeat of bug #628237. However, slapd 2.4.28-1.1/amd64 has a dependency on libsasl2-2 (= 2.1.24), ... Looking at the package info for slapd: Package: slapd Priority: optional Section: net Installed-Size: 4064 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Debian OpenLDAP Maintainers pkg-openldap-de...@lists.alioth.debian.org Architecture: i386 Source: openldap Version: 2.4.28-1.1ubuntu4 Replaces: ldap-utils ( 2.2.23-3), libldap2 Provides: ldap-server, libslapi-2.4-2 Depends: libc6 (= 2.15), libdb5.1, libldap-2.4-2 (= 2.4.28-1.1ubuntu4), libltdl7 (= 2.4.2), libodbc1 (= 2.2.11) | unixodbc (= 2.2.11), libperl5.14 (= 5.14.2), libsasl2-2, libslp1, libwrap0 (= 7.6-4~), coreutils (= 4.5.1-1), psmisc, perl ( 5.8.0) | libmime-base64-perl, adduser, lsb-base (= 3.2-13) We can see that it's not requiring a newer libsasl2-2. At this point I did an apt-get install libsasl2-2 and it installed the new libsasl2-2 and allowed the configuration of slapd to finish. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: slapd 2.4.28-1.1ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat Apr 28 15:56:29 2012 ProcEnviron: Â LANG=en_CA.UTF-8 Â SHELL=/bin/bash SourcePackage: openldap - -- SRU Justification -- [Impact] slapd's maintainer scripts make use of utilities like slapcat and slapadd which require a running slapd server, however, the relationship between slapd and libsasl2-2 packages do not take into account a binary incompatability introduced with 2.4.28-1.1. As a result, libsasl2-2 is not upgraded until after slapd, slapd fails to start (with error msg cited in the bugs), and maintainer scripts fail during upgrades with a debconf error like: http://paste.ubuntu.com/965636/ [Development Fix] The issue has been sorted in Debian and in Quantal with the recent merges. A thorough explanation of the fix is available at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628237#163 . The solution is to update cyrus-sasl2 with: - - Breaks: 'slapd 2.4.25-4' on libsasl2-2 - - shlib dependency on 2.1.24 for libsasl2-2 + Â Â - Breaks: 'slapd 2.4.25-4' on libsasl2-2 + Â Â - shlib dependency on 2.1.24 for libsasl2-2 Both of which have been applied to packaging in Debian and synced into Ubuntu Quantal. A no-change rebuild of openldap against the new sasl dependency is required as well. [Stable Fix] - The two one-liners from above should be back-ported from 2.1.25.dfsg1-4 packaging and applied + The two one-liners from above should be back-ported from 2.1.25.dfsg1-4 packaging and applied to cyrus-sasl2 packaging in Precise. A no-change rebuild of openldap against the newly updated dependency is required as well. [Test Case] - To reproduce, install slapd on a lucid installation, populate a minimal LDAP directory and do-release-upgrade. A script to populate a minimal database can be found at http://paste.ubuntu.com/965633/. + To reproduce, install slapd on a lucid installation, populate a minimal LDAP directory and do-release-upgrade. A script to populate a minimal database can be found at http://paste.ubuntu.com/965633/. [Regression Potential] Minimal. Packaging changes ensure proper ordering of upgrades during dist-upgrade and do not touch original source tree.
[Bug 990742] Re: slapd fails to upgrade: requires libsasl2-2 (= 2.1.24) installed
I was finally able to get the half upgraded system fixed using the proposed package. After that was running for a bit I went ahead and upgraded another server in my cluster running the same services. I used the proposed libsasl2-2 package and the upgrade completed start to finish without a hiccup. So on 2 servers using the proposed packaged solved the issue without any side affects. Thanks! ** Tags removed: verification-needed ** Tags added: verification-done ** Description changed: I was trying to apt-get install dpkg to work around #944452 and got the following while trying to upgrade slapd: Setting up slapd (2.4.28-1.1ubuntu4) ... Use of uninitialized value $type in ucfirst at /usr/share/perl5/Debconf/AutoSelect.pm line 35. Â Â Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.4.21-0ubuntu5.7... done. Â Â Moving old database directories to /var/backups: Â Â Loading from /var/backups/slapd-2.4.21-0ubuntu5.7: Â Â - directory dc=interlinx,dc=bc,dc=ca... failed. Loading the database from the LDIF dump failed with the following error while running slapadd: 4f9c4903 slap_sasl_init: auxprop add plugin failed slapadd: slap_init failed! dpkg: error processing slapd (--configure): Â subprocess installed post-installation script returned error exit status 1 This looks to be related to http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=665473 where message #10 (http://bugs.debian.org /cgi-bin/bugreport.cgi?bug=665473#10) in that bug says: This looks like a repeat of bug #628237. However, slapd 2.4.28-1.1/amd64 has a dependency on libsasl2-2 (= 2.1.24), ... Looking at the package info for slapd: Package: slapd Priority: optional Section: net Installed-Size: 4064 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Debian OpenLDAP Maintainers pkg-openldap-de...@lists.alioth.debian.org Architecture: i386 Source: openldap Version: 2.4.28-1.1ubuntu4 Replaces: ldap-utils ( 2.2.23-3), libldap2 Provides: ldap-server, libslapi-2.4-2 Depends: libc6 (= 2.15), libdb5.1, libldap-2.4-2 (= 2.4.28-1.1ubuntu4), libltdl7 (= 2.4.2), libodbc1 (= 2.2.11) | unixodbc (= 2.2.11), libperl5.14 (= 5.14.2), libsasl2-2, libslp1, libwrap0 (= 7.6-4~), coreutils (= 4.5.1-1), psmisc, perl ( 5.8.0) | libmime-base64-perl, adduser, lsb-base (= 3.2-13) We can see that it's not requiring a newer libsasl2-2. At this point I did an apt-get install libsasl2-2 and it installed the new libsasl2-2 and allowed the configuration of slapd to finish. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: slapd 2.4.28-1.1ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat Apr 28 15:56:29 2012 ProcEnviron: Â LANG=en_CA.UTF-8 Â SHELL=/bin/bash SourcePackage: openldap - -- SRU Justification -- [Impact] slapd's maintainer scripts make use of utilities like slapcat and slapadd which require a running slapd server, however, the relationship between slapd and libsasl2-2 packages do not take into account a binary incompatability introduced with 2.4.28-1.1. As a result, libsasl2-2 is not upgraded until after slapd, slapd fails to start (with error msg cited in the bugs), and maintainer scripts fail during upgrades with a debconf error like: http://paste.ubuntu.com/965636/ [Development Fix] The issue has been sorted in Debian and in Quantal with the recent merges. A thorough explanation of the fix is available at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628237#163 . The solution is to update cyrus-sasl2 with: - - Breaks: 'slapd 2.4.25-4' on libsasl2-2 - - shlib dependency on 2.1.24 for libsasl2-2 + Â Â - Breaks: 'slapd 2.4.25-4' on libsasl2-2 + Â Â - shlib dependency on 2.1.24 for libsasl2-2 Both of which have been applied to packaging in Debian and synced into Ubuntu Quantal. A no-change rebuild of openldap against the new sasl dependency is required as well. [Stable Fix] - The two one-liners from above should be back-ported from 2.1.25.dfsg1-4 packaging and applied + The two one-liners from above should be back-ported from 2.1.25.dfsg1-4 packaging and applied to cyrus-sasl2 packaging in Precise. A no-change rebuild of openldap against the newly updated dependency is required as well. [Test Case] - To reproduce, install slapd on a lucid installation, populate a minimal LDAP directory and do-release-upgrade. A script to populate a minimal database can be found at http://paste.ubuntu.com/965633/. + To reproduce, install slapd on a lucid installation, populate a minimal LDAP directory and do-release-upgrade. A script to populate a minimal database can be found at http://paste.ubuntu.com/965633/. [Regression Potential] Minimal. Packaging changes ensure proper ordering of upgrades during dist-upgrade and do not touch original source tree.
[Bug 975126] Re: can't remove package firebird2.1-server-common
It isn't fixed in Ubuntu but it has been patched in Debian. Patched version is 2.1.4.18393-0.ds2-7 Not sure how we get someone to try get this in as an SRU patch since it prevents anyone from removing or upgrading firebird2.1. I manually applied the fix mentioned in the Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660592 and it worked great on both servers I upgraded to firebird2.5-super. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/975126 Title: can't remove package firebird2.1-server-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firebird2.1/+bug/975126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 975126] Re: can't remove package firebird2.1-server-common
Cannot upgrade from firebird2.1-super to firebird2.5-super on 12.04 due to this: root@server:~# apt-get install firebird2.5-super Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: firebird2.5-server-common libfbclient2 Suggested packages: firebird2.5-doc The following packages will be REMOVED: firebird2.1-server-common The following NEW packages will be installed: firebird2.5-server-common firebird2.5-super libfbclient2 0 upgraded, 3 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 336 kB/4,278 kB of archives. After this operation, 10.4 MB of additional disk space will be used. Do you want to continue [Y/n]? Get:1 http://us.archive.ubuntu.com/ubuntu/ precise/universe libfbclient2 amd64 2.5.1.26351.ds4-2build1 [336 kB] Fetched 336 kB in 1s (289 kB/s) Preconfiguring packages ... (Reading database ... 103354 files and directories currently installed.) Removing firebird2.1-server-common ... rmdir: unrecognized option '--ignore-if-not-empty' Try `rmdir --help' for more information. dpkg: error processing firebird2.1-server-common (--remove): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: firebird2.1-server-common E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/975126 Title: can't remove package firebird2.1-server-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firebird2.1/+bug/975126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990742] Re: slapd fails to upgrade: requires libsasl2-2 (= 2.1.24) installed
I (mostly) figured out how to do-release-upgrade using proposed repo with some help from the Ubuntu-HA group. However I believe proposed is missing the second fix needed - the no change rebuild of openldap? Still getting errors: Traceback (most recent call last): File /usr/bin/apt-listchanges, line 237, in module main() File /usr/bin/apt-listchanges, line 48, in main debs = apt_listchanges.read_apt_pipeline(config) File /usr/share/apt-listchanges/apt_listchanges.py, line 83, in read_apt_pipeline return map(lambda pkg: filenames[pkg], order) File /usr/share/apt-listchanges/apt_listchanges.py, line 83, in lambda return map(lambda pkg: filenames[pkg], order) KeyError: 'slapd' dpkg: dependency problems prevent configuration of slapd: slapd depends on libldap-2.4-2 (= 2.4.21-0ubuntu5.7); however: Version of libldap-2.4-2 on system is 2.4.28-1.1ubuntu4. slapd depends on libperl5.10 (= 5.10.1); however: Package libperl5.10 is not installed. libsasl2-2 (2.1.25.dfsg1-3ubuntu0.1) breaks slapd (= 2.4.25-3) and is installed. Version of slapd to be configured is 2.4.21-0ubuntu5.7. dpkg: error processing slapd (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: slapd E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990742 Title: slapd fails to upgrade: requires libsasl2-2 (= 2.1.24) installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/990742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990742] Re: slapd fails to upgrade: requires libsasl2-2 (= 2.1.24) installed
I have my server in that state now unfortunately so I should be able to test. How would I tested proposed while trying to do-release-upgrade? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/990742 Title: slapd fails to upgrade: requires libsasl2-2 (= 2.1.24) installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/990742/+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 990742] Re: slapd fails to upgrade: requires libsasl2-2 (= 2.1.24) installed
I have my server in that state now unfortunately so I should be able to test. How would I tested proposed while trying to do-release-upgrade? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990742 Title: slapd fails to upgrade: requires libsasl2-2 (= 2.1.24) installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/990742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994837] [NEW] package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1
Public bug reported: Upgrading from 10.04 LTS to 12.04 LTS. Upgrade failed after slapd failed to install. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: slapd 2.4.21-0ubuntu5.7 ProcVersionSignature: Ubuntu 2.6.32-40.87-server 2.6.32.57+drm33.23 Uname: Linux 2.6.32-40-server x86_64 Architecture: amd64 Date: Fri May 4 17:06:45 2012 ErrorMessage: ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.2) SourcePackage: openldap Title: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/994837 Title: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/994837/+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 994837] Re: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/994837 Title: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/994837/+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 994837] [NEW] package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1
Public bug reported: Upgrading from 10.04 LTS to 12.04 LTS. Upgrade failed after slapd failed to install. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: slapd 2.4.21-0ubuntu5.7 ProcVersionSignature: Ubuntu 2.6.32-40.87-server 2.6.32.57+drm33.23 Uname: Linux 2.6.32-40-server x86_64 Architecture: amd64 Date: Fri May 4 17:06:45 2012 ErrorMessage: ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.2) SourcePackage: openldap Title: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994837 Title: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/994837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994837] Re: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation 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/994837 Title: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/994837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 917319] Re: serverguide - Network Auth - Samba and LDAP - incorrect ldapadd command when adding samba schema
** Description changed:
Description:Ubuntu 10.04.3 LTS
Release:10.04
Step 5 of the Samba and LDAP section of the Server Guide (in Network
- Authentication) shows the old way (incorrect) which doesn't work. Also
- the line after describing what it should look like when complete has the
- wrong name in it.
+ Authentication) shows the old way (incorrect) to modify config which
+ doesn't work. Also the line after describing what it should look like
+ when complete has the wrong name in it. *update* the next bullet after
+ step 5 about adding indexes contains a ldapmodify and ldapsearch that
+ are both using the older incorrect commands.
5. Finally, using the ldapadd utility, add the new schema to the directory:
- ldapadd -x -D cn=admin,cn=config -W -f /tmp/cn\=samba.ldif -- way
prior to make cn=config changes
+ ldapadd -x -D cn=admin,cn=config -W -f /tmp/cn\=samba.ldif -- way
prior to make cn=config changes
There should now be a dn: cn={X}misc,cn=schema,cn=config, where X is the
next sequential schema, entry in the cn=config tree. -- cn={X}misc is wrong
Should be:
5. Finally, using the ldapadd utility, add the new schema to the directory:
- sudo ldapadd -Y EXTERNAL -H ldapi:/// -f /tmp/cn\=samba.ldif--
current way to modify cn=config
+ sudo ldapadd -Y EXTERNAL -H ldapi:/// -f /tmp/cn\=samba.ldif--
current way to modify cn=config
There should now be a dn: cn={X}samba,cn=schema,cn=config, where X is the
next sequential schema, entry in the cn=config tree. -- cn={X}samba
+
+ *update*
+ The two incorrect commands:
+ ldapmodify -x -D cn=admin,cn=config -W -f samba_indexes.ldif
+
+ ldapsearch -xLLL -D cn=admin,cn=config -x -b cn=config -W
+ olcDatabase={1}hdb
+
+ Corrected:
+ ldapmodify -Y EXTERNAL -H ldapi:/// -f samba_indexes.ldif
+
+ ldapsearch -LLL -Y EXTERNAL -H ldapi:/// -b cn=config olcDatabase={1}hdb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917319
Title:
serverguide - Network Auth - Samba and LDAP - incorrect ldapadd
command when adding samba schema
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/917319/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 917319] [NEW] serverguide - Network Auth - Samba and LDAP - incorrect ldapadd command when adding samba schema
Public bug reported:
Description:Ubuntu 10.04.3 LTS
Release:10.04
Step 5 of the Samba and LDAP section of the Server Guide (in Network
Authentication) shows the old way (incorrect) which doesn't work. Also
the line after describing what it should look like when complete has the
wrong name in it.
5. Finally, using the ldapadd utility, add the new schema to the directory:
ldapadd -x -D cn=admin,cn=config -W -f /tmp/cn\=samba.ldif -- way
prior to make cn=config changes
There should now be a dn: cn={X}misc,cn=schema,cn=config, where X is the next
sequential schema, entry in the cn=config tree. -- cn={X}misc is wrong
Should be:
5. Finally, using the ldapadd utility, add the new schema to the directory:
sudo ldapadd -Y EXTERNAL -H ldapi:/// -f /tmp/cn\=samba.ldif-- current
way to modify cn=config
There should now be a dn: cn={X}samba,cn=schema,cn=config, where X is the
next sequential schema, entry in the cn=config tree. -- cn={X}samba
** Affects: ubuntu-docs (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/917319
Title:
serverguide - Network Auth - Samba and LDAP - incorrect ldapadd
command when adding samba schema
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/917319/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 821732] Re: Drop raexecupstart.patch and fix_lrmd_leak.patch to not cause socket leak in lrmd.
Not sure these symptoms would be the same on the later versions but on Lucid I also encountered the following due to this bug: service corosync stop - never completes. Hangs waiting for crmd to shutdown (over 6 hours without a change) crm ra info ocf:xx:xx - hangs the crm shell crm configure primitive p_test ocf: - hung when trying to use tab completion of ocf:tab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/821732 Title: Drop raexecupstart.patch and fix_lrmd_leak.patch to not cause socket leak in lrmd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/821732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
I have tested this a couple times a week since the fix was proposed and I have had no ill effects and it has fixed the problem. Hopefully we can get this update out to all! If there is any other info I can provide please let me know. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
I have tested this a couple times a week since the fix was proposed and I have had no ill effects and it has fixed the problem. Hopefully we can get this update out to all! If there is any other info I can provide please let me know. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Ubuntu-ha] [Bug 799711] Re: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up
Henning You are probably right that this isn't the right place to continue with non-bug questions though Andres or others could answer that more acurately. I would recommend drbd-users mailing list as there are many experts there for config and troubleshooting. Also the pacemaker mailing lists is a good one. *snip* I don't have any idea why your getting the broken pipe... but do you have STONITH/fencing configured?! Normally when you have a comm link break like that then you would want Pacemaker to STONITH the disconnected node. Prior to the STONITH which ever DRBD node is going to survive should fence the resource preventing it from becoming primary until it is UpToDate. I use the fence peer handler in DRBD set to resource only and then have STONITH configure in Pacemaker. This way I can have a break in DRBD that doesn't automatically STONITH the node (but prevents the borked DRBD from coming up as Master and causing split brain) unless the Cluster communications are also dead at which point Pacemaker will shoot the node. I think the lack of fencing/STONITH is causing the split brain because both nodes do their own thing when not communicating which causes the diverging data set. This causes a split brain every time this happens even though there are no writes on the devices yet. You have your split brain handling configured like this still?: after-sb-0pri disconnect; after-sb-1pri consensus; after-sb-2pri disconnect; Your are telling it to disconnect regardless of changes with these split brain lines (I believe it's part of the cause). Have you considered using some more agressive split brain handling if your going with dual primary? They can be controversial topic due to data loss but... In the users guide at the bottom of this page it lists split brain behaviors that are considered OK for dual primary/clustered filesystem setups: http://www.drbd.org/users-guide/s-configure-split-brain-behavior.html after-sb-0pri discard-zero-changes; after-sb-1pri discard-secondary; after-sb-2pri disconnect; You would likely hit sb-1pri if you had fencing. It would go something like this: Break in comms Node 1 is fenced preventing it from becoming master Pacemaker shoots node 1 Node 1 reboots and (if setup to auto start the cluster) pacemaker accepts the node back into the cluster Drbd links up and finds Node 1 is diverged Node 1 is fenced so it is not master right now Considers the after-sb-1pri rule - this assumes that since it's dual primary if you have one primary then the dataset on that primary is always good and there is no need to perserve the secondary data so just overwrite it. Basically executes the commands you did manually and discards the Node 1 data. Once Node 1 is UpToDate DRBD removes the fencing and allows Node 1 to become master I hope all of that wasn't too confusing! Jake -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/799711 Title: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Ubuntu-ha] [Bug 799711] Re: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up
Henning You are probably right that this isn't the right place to continue with non-bug questions though Andres or others could answer that more acurately. I would recommend drbd-users mailing list as there are many experts there for config and troubleshooting. Also the pacemaker mailing lists is a good one. *snip* I don't have any idea why your getting the broken pipe... but do you have STONITH/fencing configured?! Normally when you have a comm link break like that then you would want Pacemaker to STONITH the disconnected node. Prior to the STONITH which ever DRBD node is going to survive should fence the resource preventing it from becoming primary until it is UpToDate. I use the fence peer handler in DRBD set to resource only and then have STONITH configure in Pacemaker. This way I can have a break in DRBD that doesn't automatically STONITH the node (but prevents the borked DRBD from coming up as Master and causing split brain) unless the Cluster communications are also dead at which point Pacemaker will shoot the node. I think the lack of fencing/STONITH is causing the split brain because both nodes do their own thing when not communicating which causes the diverging data set. This causes a split brain every time this happens even though there are no writes on the devices yet. You have your split brain handling configured like this still?: after-sb-0pri disconnect; after-sb-1pri consensus; after-sb-2pri disconnect; Your are telling it to disconnect regardless of changes with these split brain lines (I believe it's part of the cause). Have you considered using some more agressive split brain handling if your going with dual primary? They can be controversial topic due to data loss but... In the users guide at the bottom of this page it lists split brain behaviors that are considered OK for dual primary/clustered filesystem setups: http://www.drbd.org/users-guide/s-configure-split-brain-behavior.html after-sb-0pri discard-zero-changes; after-sb-1pri discard-secondary; after-sb-2pri disconnect; You would likely hit sb-1pri if you had fencing. It would go something like this: Break in comms Node 1 is fenced preventing it from becoming master Pacemaker shoots node 1 Node 1 reboots and (if setup to auto start the cluster) pacemaker accepts the node back into the cluster Drbd links up and finds Node 1 is diverged Node 1 is fenced so it is not master right now Considers the after-sb-1pri rule - this assumes that since it's dual primary if you have one primary then the dataset on that primary is always good and there is no need to perserve the secondary data so just overwrite it. Basically executes the commands you did manually and discards the Node 1 data. Once Node 1 is UpToDate DRBD removes the fencing and allows Node 1 to become master I hope all of that wasn't too confusing! Jake -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/799711 Title: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Still working good - no issues. I've changed/rebooted both nodes and it takes snapshots, re-syncs, then removes snapshots (at least 30 times since applying the patch) without a hitch. Thanks again for your help! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Still working good - no issues. I've changed/rebooted both nodes and it takes snapshots, re-syncs, then removes snapshots (at least 30 times since applying the patch) without a hitch. Thanks again for your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806145] Re: Lacks a status action in the init script
Have an updated patch that returns properly when Arpwatch isn't running. Will upload soon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806145 Title: Lacks a status action in the init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arpwatch/+bug/806145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 799711] Re: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up
I know how it might not look like a Pacemaker problem but I believe it is. Pacemaker is in charge of everything. As I put in the comment before I believe this line disallows Drbd2 to be master on node 2: location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1 Since everything else relies on Drbd2 being promoted to master (o2cb, dlmcontrol, filesystem via order and colocation constraints) none of those service will be started on node 2. Therefore you cannot have ocfs2_controld running on node 2 because Drbd2 is never master which means it could not be contacted. This would generate the errors in your logs... at least that's what I think! Though I'm not sure why dlm_controld.pcmk is running... Hopefully it help! Jake -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/799711 Title: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Ok looks good. No zombie processes. I updated and restarted node 1 - drbd initiated snapsho on startup, synced properly (wouldn't get that far before) and then removed them. After doing that on node 1 I updated and restarted node 2 (causing everything to fail to node 1) and everything moved and resynced after restart properly. Only thing I don't understand/like is the following in the syslog: Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 3 (/) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 4 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 6 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 7 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1761]: File descriptor 7 (/etc) leaked on lvdisplay invocation. Parent PID 1761: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 8 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 9 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 10 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Thanks Adam/Andres I've got to remember: Google first, ask second - always not just mostly! I'll report in again in about a week on this. I am doing a lot of reconfig, add resources, testing, and failing of my pacemaker cluster so I will report on how the snapshot patch holds up. It *should* get a good workout! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+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 799711] Re: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up
I know how it might not look like a Pacemaker problem but I believe it is. Pacemaker is in charge of everything. As I put in the comment before I believe this line disallows Drbd2 to be master on node 2: location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1 Since everything else relies on Drbd2 being promoted to master (o2cb, dlmcontrol, filesystem via order and colocation constraints) none of those service will be started on node 2. Therefore you cannot have ocfs2_controld running on node 2 because Drbd2 is never master which means it could not be contacted. This would generate the errors in your logs... at least that's what I think! Though I'm not sure why dlm_controld.pcmk is running... Hopefully it help! Jake -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/799711 Title: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Ok looks good. No zombie processes. I updated and restarted node 1 - drbd initiated snapsho on startup, synced properly (wouldn't get that far before) and then removed them. After doing that on node 1 I updated and restarted node 2 (causing everything to fail to node 1) and everything moved and resynced after restart properly. Only thing I don't understand/like is the following in the syslog: Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 3 (/) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 4 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 6 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 7 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1761]: File descriptor 7 (/etc) leaked on lvdisplay invocation. Parent PID 1761: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 8 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 9 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 10 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Thanks Adam/Andres I've got to remember: Google first, ask second - always not just mostly! I'll report in again in about a week on this. I am doing a lot of reconfig, add resources, testing, and failing of my pacemaker cluster so I will report on how the snapshot patch holds up. It *should* get a good workout! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Andres - have you had a chance to review my last update? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Still the same thing - zombie processes for lvm snapshots with 100% cpu. Script still doesn't have the changes in the patch applied - still looks identical as my post #8. root@Vulture:~# apt-cache policy drbd8-source drbd8-source: Installed: 2:8.3.7-1ubuntu2.3 Candidate: 2:8.3.7-1ubuntu2.3 Version table: *** 2:8.3.7-1ubuntu2.3 0 500 http://ppa.launchpad.net/gandelman-a/ppa/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 2:8.3.7-1ubuntu2.2 0 500 http://ppa.launchpad.net/andreserl/ppa/ubuntu/ lucid/main Packages 2:8.3.7-1ubuntu2.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 2:8.3.7-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Thanks Adam - thought that was weird. Only update available was drbd8-source after adding your ppa. Maybe because I use amd64 builds? I noticed it says need to be built next to those in your ppa. I'll check again in the morning. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+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 806677] Re: status_of_proc returns incorrect number
Anyone have any thoughts? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806677 Title: status_of_proc returns incorrect number To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/806677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Andres - have you had a chance to review my last update? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806677] Re: status_of_proc returns incorrect number
Found an error in my patch that was causing the incorrect output - not a problem with init-functions. ** Changed in: lsb (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806677 Title: status_of_proc returns incorrect number To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/806677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Still the same thing - zombie processes for lvm snapshots with 100% cpu. Script still doesn't have the changes in the patch applied - still looks identical as my post #8. root@Vulture:~# apt-cache policy drbd8-source drbd8-source: Installed: 2:8.3.7-1ubuntu2.3 Candidate: 2:8.3.7-1ubuntu2.3 Version table: *** 2:8.3.7-1ubuntu2.3 0 500 http://ppa.launchpad.net/gandelman-a/ppa/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 2:8.3.7-1ubuntu2.2 0 500 http://ppa.launchpad.net/andreserl/ppa/ubuntu/ lucid/main Packages 2:8.3.7-1ubuntu2.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 2:8.3.7-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Thanks Adam - thought that was weird. Only update available was drbd8-source after adding your ppa. Maybe because I use amd64 builds? I noticed it says need to be built next to those in your ppa. I'll check again in the morning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 799711] Re: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up
You have a location constraint for msDrbd2 that requires it to be master on node 1 only. I would assume it's leftover from your master/slave setup: location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1 I would remove that and see what happens. Also a few other things: In ordering statements the action performed on the first item is applied to all the others unless explicitly defined. In the statement below if msDrbd2 is not master it will promote it to master and once that finished it will then try to take the same promote action on cloneDlm also. If all items required a start action then you could not define the action at all or only on define it on the first and it would be fine but if you have mixed actions then all must be defined. It should be changed to match the second statement. order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm:start In this ordering statement I think you meant to put before not after... :-) order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm Also to follow-up on Ante's comment - you were following DRBD users guide for Legacy non-Pacmaker setup. I don't know if you found it but here is the direct link to the Pacemaker config in the DRBD users guide: http://www.drbd.org/users-guide/s-ocfs2-pacemaker.html Last - once you have it functioning well you can group the primitives for Dlm and o2cb before you clone them and then eliminate a couple order and colo statements. Then you can combine the colocation and ordering statements for Drbd, the ocfs control group clone and the file system into one of each. I.E. group g_ocfs2control p_controld p_o2cb clone cl_ocfs2control g_ocfs2control \ meta globally-unique=false interleave=true target-role=Started colocation c_fs_srv_on_ocfs2control_on_drbd_srv_master inf: cl_fs_srv cl_ocfs2control ms_drbd_srv:Master order o_drbd_srv_master_before_ocfs2control_before_fs_srv 0: ms_drbd_srv:promote cl_ocfs2control:start cl_fs_srv:start Hope that helps! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/799711 Title: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+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 799711] Re: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up
Whoops! I put them backwards too! In this ordering statement I think you meant to put before not after... :-) order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm I meant it should be after not before! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/799711 Title: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Hi Andres, So I gave it a try and now I'm racking my brain because I thought I knew what I was doing but it didn't behave as I expected and I don't know if it's my ignorance or a problem so I'll let you be the judge! Executed the following on both nodes, one after the other finished: Added your PPA. apt-get update; apt-get upgrade Edit /etc/drbd.d/global_common.conf and uncomment before and after-resync-target shutdown -r now Ended up with all kinds of errors and zombie lvm processes and drbd complaining etc. after restart. Looked at the lvm scripts in question - /usr/lib/drbd/snapshot-resync-target-lvm.sh The changes from the patch are not there... if I understand what the patch was supposed to do. First - The meat of the patch was to remove a couple of shift lines from the case statement among other things correct? Second - doing the apt-get upgrade should have replaced the patched script? Node 2: root@Vulture:~# apt-cache policy drbd8-source drbd8-source: Installed: 2:8.3.7-1ubuntu2.2 Candidate: 2:8.3.7-1ubuntu2.2 Version table: *** 2:8.3.7-1ubuntu2.2 0 500 http://ppa.launchpad.net/andreserl/ppa/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 2:8.3.7-1ubuntu2.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 2:8.3.7-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages Node 1: root@Condor:~# apt-cache policy drbd8-source drbd8-source: Installed: 2:8.3.7-1ubuntu2.2 Candidate: 2:8.3.7-1ubuntu2.2 Version table: *** 2:8.3.7-1ubuntu2.2 0 500 http://ppa.launchpad.net/andreserl/ppa/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 2:8.3.7-1ubuntu2.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 2:8.3.7-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages root@Vulture:~# cat /usr/lib/drbd/snapshot-resync-target-lvm.sh | grep -A 20 case case $1 in -p|--percent) SNAP_PERC=$2 shift ;; -a|--additional) SNAP_ADDITIONAL=$2 shift 2 ;; -n|--disconnect-on-error) DISCONNECT_ON_ERROR=1 shift ;; -v|--verbose) BE_VERBOSE=1 shift ;; --) shift break ;; Thoughts?? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+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 799711] Re: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up
You have a location constraint for msDrbd2 that requires it to be master on node 1 only. I would assume it's leftover from your master/slave setup: location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1 I would remove that and see what happens. Also a few other things: In ordering statements the action performed on the first item is applied to all the others unless explicitly defined. In the statement below if msDrbd2 is not master it will promote it to master and once that finished it will then try to take the same promote action on cloneDlm also. If all items required a start action then you could not define the action at all or only on define it on the first and it would be fine but if you have mixed actions then all must be defined. It should be changed to match the second statement. order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm:start In this ordering statement I think you meant to put before not after... :-) order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm Also to follow-up on Ante's comment - you were following DRBD users guide for Legacy non-Pacmaker setup. I don't know if you found it but here is the direct link to the Pacemaker config in the DRBD users guide: http://www.drbd.org/users-guide/s-ocfs2-pacemaker.html Last - once you have it functioning well you can group the primitives for Dlm and o2cb before you clone them and then eliminate a couple order and colo statements. Then you can combine the colocation and ordering statements for Drbd, the ocfs control group clone and the file system into one of each. I.E. group g_ocfs2control p_controld p_o2cb clone cl_ocfs2control g_ocfs2control \ meta globally-unique=false interleave=true target-role=Started colocation c_fs_srv_on_ocfs2control_on_drbd_srv_master inf: cl_fs_srv cl_ocfs2control ms_drbd_srv:Master order o_drbd_srv_master_before_ocfs2control_before_fs_srv 0: ms_drbd_srv:promote cl_ocfs2control:start cl_fs_srv:start Hope that helps! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/799711 Title: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 799711] Re: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up
Whoops! I put them backwards too! In this ordering statement I think you meant to put before not after... :-) order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm I meant it should be after not before! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/799711 Title: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806145] Re: Lacks a status action in the init script
Maybe someone else could take a look at the return code issue. I looked through the init script for NTP and how it calls status_of_proc and mine is identical. However if ntp is not running and you execute /etc/init.d/ntp status; echo return $? you get return 3 which is the proper response per LSB standard. But if you execute the same with my patched script - /etc/init.d/arpwatch status; echo return $? you get return 0... Not sure what I'm missing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806145 Title: Lacks a status action in the init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arpwatch/+bug/806145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806677] Re: status_of_proc returns incorrect number
I tried some further testing and comparison today: I looked through the init script for NTP and how it calls status_of_proc and my patch for Arpwatch looks identical. However if ntp is not running and you execute /etc/init.d/ntp status; echo return $? you get return 3 which is the proper response per LSB standard. But if you execute the same with my patched Arpwatch script - /etc/init.d/arpwatch status; echo return $? you get return 0... Not sure what I'm missing or if it's really a problem in init- functions... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806677 Title: status_of_proc returns incorrect number To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/806677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Hi Andres, So I gave it a try and now I'm racking my brain because I thought I knew what I was doing but it didn't behave as I expected and I don't know if it's my ignorance or a problem so I'll let you be the judge! Executed the following on both nodes, one after the other finished: Added your PPA. apt-get update; apt-get upgrade Edit /etc/drbd.d/global_common.conf and uncomment before and after-resync-target shutdown -r now Ended up with all kinds of errors and zombie lvm processes and drbd complaining etc. after restart. Looked at the lvm scripts in question - /usr/lib/drbd/snapshot-resync-target-lvm.sh The changes from the patch are not there... if I understand what the patch was supposed to do. First - The meat of the patch was to remove a couple of shift lines from the case statement among other things correct? Second - doing the apt-get upgrade should have replaced the patched script? Node 2: root@Vulture:~# apt-cache policy drbd8-source drbd8-source: Installed: 2:8.3.7-1ubuntu2.2 Candidate: 2:8.3.7-1ubuntu2.2 Version table: *** 2:8.3.7-1ubuntu2.2 0 500 http://ppa.launchpad.net/andreserl/ppa/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 2:8.3.7-1ubuntu2.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 2:8.3.7-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages Node 1: root@Condor:~# apt-cache policy drbd8-source drbd8-source: Installed: 2:8.3.7-1ubuntu2.2 Candidate: 2:8.3.7-1ubuntu2.2 Version table: *** 2:8.3.7-1ubuntu2.2 0 500 http://ppa.launchpad.net/andreserl/ppa/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 2:8.3.7-1ubuntu2.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 2:8.3.7-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages root@Vulture:~# cat /usr/lib/drbd/snapshot-resync-target-lvm.sh | grep -A 20 case case $1 in -p|--percent) SNAP_PERC=$2 shift ;; -a|--additional) SNAP_ADDITIONAL=$2 shift 2 ;; -n|--disconnect-on-error) DISCONNECT_ON_ERROR=1 shift ;; -v|--verbose) BE_VERBOSE=1 shift ;; --) shift break ;; Thoughts?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806145] Re: Lacks a status action in the init script
Patch to implement status_of_proc() LSB init Function. Everything works as defined in LSB standard with the exception of the return code of status when daemon is not running. It is reported incorrectly as 0 instead of 3. I believe this is because of a bug in /lib/lsb/init-functions in the pidofproc() section. I will post a bug there shortly. ** Patch added: Patch to add status to init script https://bugs.launchpad.net/ubuntu/+source/arpwatch/+bug/806145/+attachment/2194363/+files/LP806145.patch ** Changed in: arpwatch (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806145 Title: Lacks a status action in the init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arpwatch/+bug/806145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806677] [NEW] status_of_proc returns incorrect number
Public bug reported: I was patching the init script for Arpwatch so that it would be LSB compliant (adding status) and came across this issue. I believe it differs from the similarly named bug with code 3/4 problems. Arpwatch not running. Using the status_of_proc function. Return code is 0. According to the LSB standard it should be a return code 3. In the pidofproc() section the match is on line 97 which in turn returns code 3 on line 98. However when testing this pidofproc() function it first returns the 3 from line 98 and then it returns 0 from line 100. No idea why it returns 0 after returning 3? And then if it returned 0 why is it matching on the final else in status_of_proc (anything but 0 or 4?) lines 183/184? if [ -x /bin/pidof -a ! $specified ]; then status=0 /bin/pidof -o %PPID -x $1 || status=$? if [ $status = 1 ]; then return 3 # program is not running fi return 0 fi The bug for the related Arpwatch package is LP: 806145. 1) Description: Ubuntu 10.04.2 LTS Release: 10.04 2)lsb-base: Installed: 4.0-0ubuntu8 Candidate: 4.0-0ubuntu8 Version table: *** 4.0-0ubuntu8 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status ** Affects: lsb (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/806677 Title: status_of_proc returns incorrect number To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/806677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806145] [NEW] Lacks a status action in the init script
Public bug reported: Arpwatch is not LSB compliant since it lacks a status action in its' init script. 1) Description:Ubuntu 10.04.2 LTS Release:10.04 2) Installed: 2.1a15-1.1 Candidate: 2.1a15-1.1 Version table: *** 2.1a15-1.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status 3) Expect output from $/etc/init.d/arpwatch status or $service arpwatch status such as Arpwatch is running (pid ) 4) If you pass the status parameter to the init script you get the usage output. ** Affects: arpwatch (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/806145 Title: Lacks a status action in the init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arpwatch/+bug/806145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806177] [NEW] Misspelling in init.d
Public bug reported: In init.d/arpwatch - misspelling of arpwatch on line 14 1) Description: Ubuntu 10.04.2 LTS Release: 10.04 2) Installed: 2.1a15-1.1 Candidate: 2.1a15-1.1 Version table: *** 2.1a15-1.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status ** Affects: arpwatch (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/806177 Title: Misspelling in init.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arpwatch/+bug/806177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806177] Re: Misspelling in init.d
** Patch added: Patch to fix spelling https://bugs.launchpad.net/ubuntu/+source/arpwatch/+bug/806177/+attachment/2193134/+files/LP806177.patch ** Changed in: arpwatch (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806177 Title: Misspelling in init.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arpwatch/+bug/806177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Not to be a pain but any update on this? If it is put to SRU Proposed I would gladly test it. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Andres, There hasn't been any activity (that I can see) on this since you submitted the SRU. Do you have any further info or idea when this would be mainstream available for 10.04? Or would you be willing to put up a patched package on the Ubuntu-HA PPA for Lucid? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Andres, This is a real pain for those of us who would like to ensure that we don't lose data due to a failure during re-sync. If we don't take a snapshot prior to a re-sync of the secondary and there was a failure it could be catastrophic. I'm pretty sure Lars put out a patch which is mentioned in the original bug report. I realize getting this into 10.04 can be a long process. Any chance in the mean time you would be willing to put up a patched version in the HA PPA? I could patch it myself however if you put it up at least it would be there for those that don't know how or don't want to modify their packages outside of apt. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Excellent! Thank you Andres -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Andres, This is a real pain for those of us who would like to ensure that we don't lose data due to a failure during re-sync. If we don't take a snapshot prior to a re-sync of the secondary and there was a failure it could be catastrophic. I'm pretty sure Lars put out a patch which is mentioned in the original bug report. I realize getting this into 10.04 can be a long process. Any chance in the mean time you would be willing to put up a patched version in the HA PPA? I could patch it myself however if you put it up at least it would be there for those that don't know how or don't want to modify their packages outside of apt. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 777928] [NEW] launchpad bug notifications not working
Public bug reported: Bug is related to the Launchpad bug system. What happens: Bug is reported such as bug 744293. There are subscribers listed for the bug who are notified and below that on the bug page there are Also Notified ppl/groups. Using the bug I listed as an example I would assume that since I am a member of Ubuntu-HA and Ubuntu-HA was listed under Also Notified for said bug I would receive an email notification about this bug. I didn't. Maybe this is by design? Maybe the Also Notified means something different? Maybe the group being listed doesn't mean every member is notified only the owner? Thanks! ** Affects: 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/777928 Title: launchpad bug notifications not working -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Excellent! Thank you Andres -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 571612] Re: dlm_controld.pcmk segfault
Andres, Good point - I actually don't even have redhat-cluster installed... What led me to this bug report is following the Pacemaker, DRBD8, and OCFS2 test case in the wiki from Ubuntu-HA and other info online. I encountered the segfault problem and did a little digging to come across this bug. Although I'm not sure fact that I don't have redhat-cluster installed makes this bug invalid. I believe I encountered the bug due to the libdlm3-packemaker package I installed (from ppa:ubuntu-ha/lucid-cluster) for DLM to work in pacemaker has this problem? Correct me if I'm wrong in that assumption? Here's what I think are the relevant packages I have installed: libdlm3-pacemaker3.0.7-0ubuntu0ppa2.2 RHCS compatibility package -- dlm_controld f ocfs2-tools 1.4.3-1ubuntu0ppa4 tools for managing OCFS2 cluster pacemaker 1.0.8+hg15494-2ubuntu2 HA cluster resource manager I may be way off but is it possible to apply the patch against libdlm3-pacemaker package instead of redhat-cluster package? I am just in the testing phases right now with pacemaker/drbd/ocsf2 on a couple servers so I can definitely test a fix for you. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/571612 Title: dlm_controld.pcmk segfault -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 571612] Re: dlm_controld.pcmk segfault
Any update on this? It's been 8 months since found and reported. Any info would be great as it is a real pain! Anyone who uses link aggregation (me), bridging, and vlans are affect due to the time required to bring up the network after reboot. Corosync comes up and dlm segfaults (something to do with network not actually being completely started?). I want a node to be able to completely recover after being fenced or the like and with this problem it won't start all it's resources again due to the segfault without restarting corosync. I believe it is fixed in the 3.0.12 which is in Maverick - maybe this could be backported? Or the above referenced patch... I can figure out how to apply the patch myself but I would rather stay in sync with the HA packages... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/571612 Title: dlm_controld.pcmk segfault -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 571612] Re: dlm_controld.pcmk segfault
Great! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/571612 Title: dlm_controld.pcmk segfault -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 684194] [NEW] Samba Print Server - error in comments
Public bug reported: Binary package hint: ubuntu-docs In the Official Doc's under Samba Print Server there is a typo. https://help.ubuntu.com/10.04/serverguide/C/samba-printserver.html In the Configuration section it says to change security to share: It should say change security to user The code windows shows correctly as security = user ** Affects: ubuntu-docs (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/684194 Title: Samba Print Server - error in comments -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 684194] Re: Samba Print Server - error in comments
Or maybe I read it wrong and the code window has the typo and should be security = share depending upon how the doc is targeted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/684194 Title: Samba Print Server - error in comments -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490370] [NEW] Cannot start guest when apparmor is running
Public bug reported:
When I try to start a Windows XP virtual machine (kvm) it fails with the
following error:
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 493, in run_domain
vm.startup()
File /usr/share/virt-manager/virtManager/domain.py, line 558, in startup
self.vm.create()
File /usr/lib/python2.6/dist-packages/libvirt.py, line 293, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error cannot parse QEMU version number in ''
If I stop AppArmor it starts fine.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
Cannot start guest when apparmor is running
https://bugs.launchpad.net/bugs/490370
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 490370] Re: Cannot start guest when apparmor is running
** Attachment added: Guest XML definition file http://launchpadlibrarian.net/36260352/winXPpro.xml -- Cannot start guest when apparmor is running https://bugs.launchpad.net/bugs/490370 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 490370] Re: Cannot start guest when apparmor is running
Host: Linux IT02 2.6.31-14-server #48-Ubuntu SMP Fri Oct 16 15:07:34 UTC 2009 x86_64 GNU/Linux Package versions: libvirt-bin 0.7.0-1ubuntu13.1 libvirt0 0.7.0-1ubuntu13.1 python-libvirt 0.7.0-1ubuntu13.1 python-virtinst 0.400.3-4ubuntu1 qemu-kvm 0.11.0-0ubuntu6.3 ubuntu-virt-server 1.2 virt-manager 0.7.0-3ubuntu1 virt-viewer 0.0.3-6ubuntu7.xul191.1 kvm 1:84+dfsg-0ubuntu16+0.11.0+0ubuntu6.3 qemu-kvm 0.11.0-0ubuntu6.3 -- Cannot start guest when apparmor is running https://bugs.launchpad.net/bugs/490370 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 490370] Re: Cannot start guest when apparmor is running
No files in /var/log/apparmor/ Entry in kern.log: (Repeats everytime I tried to start guest - pid/parent varied but the rest is identical - if more are needed let me know) Nov 30 10:11:12 IT02 kernel: [ 405.887561] type=1503 audit(1259593872.142:29): operation=exec pid=2402 parent=1933 profile=/usr/sbin/libvirtd requested_mask=x:: denied_mask=x:: fsuid=0 ouid=0 name=/etc/libvirt/qemu/kvm -- Cannot start guest when apparmor is running https://bugs.launchpad.net/bugs/490370 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 490370] Re: Cannot start guest when apparmor is running
That is where the XML definitions resides on my system... r...@it02:/home/jsmith# ls /etc/libvirt/ libvirtd.conf qemu qemu.conf storage r...@it02:/home/jsmith# ls /etc/libvirt/qemu autostart KarmicBeta1.xml kvm networks winXPpro.xml r...@it02:/home/jsmith# A bit of history (and maybe my problem isn't apparmor's problem specifically...) The host system is an upgrade from 9.04. When it was 9.04 I uninstalled the distribution installs of kvm, libvirt, and virt manager and compiled and installed them from source to get some of the newer features available. I later removed the compiled versions and re-installed the distribution version. All of this was done before upgrading to 9.10. Maybe this caused some of the issue(s)? -- Cannot start guest when apparmor is running https://bugs.launchpad.net/bugs/490370 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
