[Bug 1799068] Re: gs 9.25 in ubuntu package crashes (but not same version from git repo)
After upgrading to latest version today,the error is gone. libgs9-common: Installed: 9.25~dfsg+1-0ubuntu0.18.04.2 Candidate: 9.25~dfsg+1-0ubuntu0.18.04.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799068 Title: gs 9.25 in ubuntu package crashes (but not same version from git repo) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1799068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)
To whom it may concern, I have uploaded xorg-server 1.20.8 packages for Ubuntu 18.04.5 amd64 (with the patch from https://bugs.freedesktop.org/show_bug.cgi?id=865 applied) to https://drive.google.com/drive/folders/1s4NavrQ4LBrafbTBd3ASRZ22vK7Nblvc?usp=sharing Generally, to get the topic issue fixed, you need to install only one of the packages: xserver-xorg-core- hwe-18.04_1.20.8-2ubuntu2.2~18.04.1_amd64.deb To apply the patch and build the binaries and packages, I used my script mentioned in comment #25. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)
I uploaded xorg-server 1.19.3 packages for 16.04.3 i386 with included patch from https://bugs.freedesktop.org/show_bug.cgi?id=865 to https://drive.google.com/open?id=0B_avx7RnFL6Ub1hESFZLT21iaG8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511975] Re: /lib/systemd/system/console-setup.service has incorrect ExecStart
On my 16.04.3 (keyboard-configuration 1.108ubuntu15.3) the subject line is: ExecStart=/bin/setupcon --save So, it might have already been fixed, but further version range clarification is probably needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511975 Title: /lib/systemd/system/console-setup.service has incorrect ExecStart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1511975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)
Here's my script based on the gist mentioned on comment #21 https://github.com/plastikat/patch-xkb-layout-switch It tries to be generic. It uses a separate configuration file for each platform, which means it is extensible. It is still apt-based, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573181] Re: Samba crashes wit "signal 11" error
Sadly this fix doesn't work for me. [2016/05/04 20:12:19.872964, 0] ../lib/util/fault.c:78(fault_report) === [2016/05/04 20:12:19.873006, 0] ../lib/util/fault.c:79(fault_report) INTERNAL ERROR: Signal 11 in pid 6369 (4.3.9-Ubuntu) Please read the Trouble-Shooting section of the Samba HOWTO [2016/05/04 20:12:19.873032, 0] ../lib/util/fault.c:81(fault_report) === [2016/05/04 20:12:19.873051, 0] ../source3/lib/util.c:789(smb_panic_s3) PANIC (pid 6369): internal error However, it looks like this issue is somehow connected to the usage of ldapsam as password backend. It works with a fresh configuration, if i enable our passdb backend = ldapsam: "" the error comes up again. The configuration works like a charm with samba 4.1.6 but not with 4.3.8 or 4.3.9 kind regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573181 Title: Samba crashes wit "signal 11" error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1573181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573181] Re: Samba crashes wit "signal 11" error
Hi! found a solution for me as well it turns out that the line ldapsam:trusted = yes is the key. after turnig it into a comment, samba works again. kind regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573181 Title: Samba crashes wit "signal 11" error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1573181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573181] Re: Samba crashes wit "signal 11" error
I've tried to purge the old (4.1.6) version and clean install of 4.3.8 no success still got === [2016/04/21 14:34:21.966214, 0] ../lib/util/fault.c:79(fault_report) INTERNAL ERROR: Signal 11 in pid 25664 (4.3.8-Ubuntu) Please read the Trouble-Shooting section of the Samba HOWTO [2016/04/21 14:34:21.966270, 0] ../lib/util/fault.c:81(fault_report) === [2016/04/21 14:34:21.966293, 0] ../source3/lib/util.c:789(smb_panic_s3) PANIC (pid 25664): internal error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573181 Title: Samba crashes wit "signal 11" error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1573181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321958] Re: resize2fs does not start to actually grow an ext4
according to http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.42.13 this BUG is fixed in e2fsprogs 1.42.12 or higher. "Fix a 32/64-bit overflow bug that could cause resize2fs to loop forever. (Addresses-Launchpad-Bug: #1321958)" is it possible to backport the newest e2fsprogs package to trusty ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321958 Title: resize2fs does not start to actually grow an ext4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365020] Re: option "subject-match" not working
Hi tested today with network-manager 1.0.4-0ubuntu5 Problem still exists. Note: the new Network-manager created the lines "altsubject-matches" and "phase2-altsubject-matches" I tried them an the "subject-match" line. I can still connect with "radius.uni-konstanz.de" (the right name" and "nonsense.foo.bar" which is definitely NOT part of the string. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1365020 Title: option "subject-match" not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1365020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365020] Re: option "subject-match" not working
tried again with network-manager 0.9.8.8-0ubuntu28 problem still exists. the subject-match line is read by network-manager but has no effect at all. If i created a wpa_suplicant configuration instead the string is verified and the connection will not be established with the wrong string.So i can confirm wpa_supplicant working properly but network-manager is still broken somehow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1365020 Title: option "subject-match" not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1365020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065848] Re: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount.
Hi! still no luck - somehow /var/lib/nfs cannot be unmounted after cleanly after ocf:heartbeat:nfsserver was started Jun 6 06:18:44 blofecn2 pacemaker-controld[7732]: notice: Requesting local execution of stop operation for nfs_daemon on blofecn-node2 Jun 6 06:18:44 blofecn2 nfsserver(nfs_daemon)[3258604]: INFO: Stopping NFS server ... Jun 6 06:18:44 blofecn2 systemd[1]: Stopping NFS server and services... ... Jun 6 06:18:44 blofecn2 kernel: [1208580.651530] nfsd: last server has exited, flushing export cache Jun 6 06:18:44 blofecn2 systemd[1]: nfs-server.service: Deactivated successfully. Jun 6 06:18:44 blofecn2 systemd[1]: Stopped NFS server and services. Jun 6 06:18:44 blofecn2 systemd[1]: Stopping NFSv4 ID-name mapping service... Jun 6 06:18:44 blofecn2 systemd[1]: Stopping NFS Mount Daemon... Jun 6 06:18:44 blofecn2 rpc.mountd[21260]: Caught signal 15, un-registering and exiting. Jun 6 06:18:44 blofecn2 rpc.idmapd[21256]: exiting on signal 15 Jun 6 06:18:44 blofecn2 nfsserver(nfs_daemon)[3258604]: INFO: Stopping sm-notify Jun 6 06:18:44 blofecn2 systemd[1]: nfs-mountd.service: Deactivated successfully. Jun 6 06:18:44 blofecn2 systemd[1]: Stopped NFS Mount Daemon. Jun 6 06:18:44 blofecn2 systemd[1]: nfs-mountd.service: Consumed 8.098s CPU time. Jun 6 06:18:44 blofecn2 systemd[1]: nfs-idmapd.service: Main process exited, code=exited, status=1/FAILURE Jun 6 06:18:44 blofecn2 systemd[1]: nfs-idmapd.service: Failed with result 'exit-code'. Jun 6 06:18:44 blofecn2 systemd[1]: Stopped NFSv4 ID-name mapping service. Jun 6 06:18:44 blofecn2 systemd[1]: nfs-idmapd.service: Consumed 1.673s CPU time. Jun 6 06:18:44 blofecn2 nfsserver(nfs_daemon)[3258604]: INFO: Stopping rpc.statd Jun 6 06:18:45 blofecn2 nfsserver(nfs_daemon)[3258604]: INFO: Stop: umount (1/10 attempts) Jun 6 06:18:45 blofecn2 systemd[1]: var-lib-nfs-rpc_pipefs.mount: Deactivated successfully. Jun 6 06:18:46 blofecn2 nfsserver(nfs_daemon)[3258604]: ERROR: Failed to unmount /var/lib/nfs Jun 6 06:18:46 blofecn2 nfsserver(nfs_daemon)[3258604]: ERROR: Failed to unmount a bind mount Jun 6 06:18:46 blofecn2 pacemaker-execd[7728]: notice: nfs_daemon_stop_0[3258604] error output [ umount: /var/lib/nfs: target is busy. ] Jun 6 06:18:46 blofecn2 pacemaker-execd[7728]: notice: nfs_daemon_stop_0[3258604] error output [ ocf-exit-reason:Failed to unmount a bind mount ] Jun 6 06:18:46 blofecn2 pacemaker-controld[7732]: notice: Result of stop operation for nfs_daemon on blofecn-node2: error (Failed to unmount a bind mount) Jun 6 06:18:46 blofecn2 pacemaker-controld[7732]: notice: blofecn-node2-nfs_daemon_stop_0:455 [ umount: /var/lib/nfs: target is busy.\nocf-exit-reason:Failed to unmount a bind mount\n ] pcs resource config nfs_daemon Resource: nfs_daemon (class=ocf provider=heartbeat type=nfsserver) Attributes: nfs_no_notify=true nfs_shared_infodir=/var/lib/nfs Operations: monitor interval=10s timeout=20s (nfs_daemon-monitor-interval-10s) start interval=0s timeout=40s (nfs_daemon-start-interval-0s) stop interval=0s timeout=20s (nfs_daemon-stop-interval-0s) So it seems the issue is not the bind mount. But something holding /var/lib/nfs active after the resource was started so it cannot be stopped without fencing. How to debug that ? Best wishes Jacob -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065848 Title: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2065848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065848] Re: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount.
Hi i think nfsserver(nfs_daemon)[3258604]: ERROR: Failed to unmount /var/lib/nfs is a key here. since /var/lib/nfs is no longer a bind mount in my case. the rsoruce should not be trying to unmount it in the first place. I'll try to change the helper file in this regard and try again next week Jacob -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065848 Title: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2065848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065848] Re: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount.
Hi So think i found the core issue: ocf:heartbeat:nfsserver checks the EXEC_Mode by checking some scripts and if none of them works switches to systemd. the nfs-kernel-server package in ubuntu however offers /etc/init.d/nfs-kernel-server as a way to interact with the service. Therefore the EXEC-Mode will always be 1 (the "script" mode). This is perfectly fine at the start of the resource, creates an issue at the stopping however. Sicne EXEC_mode is 1 in function "nfsserver_stop () the "case $EXEC_MODE" structure is omitted. so the "nfs_exec stop nfsdcld" command will never be executed. Without stopping nfsdcld however /var/lib/nfs is busy an causes the resource to exit with error. I'll try to mask my /etc/init.d/nfs-kernel-server script and will report back (next week) Best wishes Jacob -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065848 Title: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2065848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1988366] Re: python-rtslib-fb needs to handle new attribute cpus_allowed_list
Hi since i'm also affected by this bug/issue i wonder if there is anything i can do to help. Any news on that or are there packages i can test ? Kind regards Jacob Becker -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1988366 Title: python-rtslib-fb needs to handle new attribute cpus_allowed_list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-rtslib-fb/+bug/1988366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065848] Re: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount.
Hi yes, on the resource-agents side the commit is sufficient. Steps to repoduce: install ubuntu 22.04 with pacemaker, corosync, nfs-kernel-server and resource-agents. configure a ocf:heartbeat:nfsserver resource _with_ nfs_shared_infodir parameter. start an the try to stop the resource. after a successful stop you will still se a mounted /var/lib/nfs. if your nfs_shared_infodir path is on a mounted resource itself, this resource cannot be stopped, since it is still mounted. for testing purpose its sufficient to check is the mount still is there. you most likely see a pacemaker-execd[]: notice: nfs_daemon_stop_0[65992] error output [ umount: /var/lib/nfs: target is busy. ] line in the log although the resource is considered stopped without error. Kind regards Jacob -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065848 Title: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2065848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1988366] Re: python-rtslib-fb needs to handle new attribute cpus_allowed_list
Hi Mauricio, i can confirm the the issue with clearconfig no longer happens. (NotADirectoryError: [Errno 20] Not a directory: '/sys/kernel/config/target/iscsi/cpus_allowed_list') instead it gives a smooth "All configuration cleared" with no errors at all. :-) This is obviously not a thorough test, but i looks ok. cheers, Jacob -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1988366 Title: python-rtslib-fb needs to handle new attribute cpus_allowed_list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-rtslib-fb/+bug/1988366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065848] Re: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount.
Hi again it turns out that disabling /etc/init.d/nfs-kernel-server (by removing or renaming it) is sufficient to avoid this bug. no further changes (beside the one Mitchell made) on ofc:heartbeat:nfsserver are necessary. I'm not sure about how to address this properly. If hwe Kernel is used /etc/init.d/nfs-kernel-server shoud NOT be used or should be removed completely to avoid this. But this is not an issue with ocf:heartbeat:nfsserver in itself. Best wishes Jacob -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065848 Title: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2065848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065848] Re: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount.
Hi Mitchell, if you are not using the "nfs_shared_infodir" parameter, removing the init script is sufficent. However, if the parameter is used an a custom place is provided do_unbind will make an uncecked umount of /var/lib/nfs. Any issues there will not return an error. This is independent of the EXEC_Mode. So you have this potential issue even with systemd and a removed /etc/init.d/nfs-kernel-server script. Best wishes Jacob -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065848 Title: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2065848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065848] [NEW] An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount.
Public bug reported: The resource "ocf:heartbeat:nfsserver" is considered stopped even the process returned an error: pacemaker-execd[7831]: notice: nfs_daemon_stop_0[65992] error output [ umount: /var/lib/nfs: target is busy. ] Beacause it is considered successfully stopped a later unmount of an LVM resource failed: LVM-activate(LVM_nfs_infodir_LV)[69671]: ERROR: PARTIAL MODE. Incomplete logical volumes will be processed. Logical volume DCSS_VG/nfs_infodir contains a filesystem in use. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS" resource-agents-base/jammy-updates,now 1:4.7.0-1ubuntu7.2 all [installed,automatic] Cluster Resource Agents curated by Ubuntu resource-agents-common/jammy-updates,now 1:4.7.0-1ubuntu7.2 amd64 [installed,automatic] Common files used by the Cluster Resource Agents resource-agents-extra/jammy-updates,now 1:4.7.0-1ubuntu7.2 amd64 [installed] Cluster Resource Agents ** Affects: resource-agents (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/2065848 Title: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2065848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065848] Re: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount.
This is identical to RedHat Bug 1924363 https://bugzilla.redhat.com/show_bug.cgi?id=1924363 ** Bug watch added: Red Hat Bugzilla #1924363 https://bugzilla.redhat.com/show_bug.cgi?id=1924363 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065848 Title: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2065848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065848] Re: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount.
Hi! Yes, i can test the package thank you in advance Jacob -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065848 Title: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2065848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065848] Re: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount.
Hi Mitchell, i installed the package and tried to shutdowwn the resource-group. Still got the error however: May 23 06:32:53 blofecn2 nfsserver(nfs_daemon)[1282251]: INFO: Stopping rpc.statd May 23 06:32:54 blofecn2 nfsserver(nfs_daemon)[1282251]: INFO: Stop: umount (1/10 attempts) May 23 06:32:54 blofecn2 systemd[1]: export_root-nfs_infodir-rpc_pipefs.mount: Deactivated successfully. May 23 06:32:54 blofecn2 systemd[1]: var-lib-nfs-rpc_pipefs.mount: Deactivated successfully. May 23 06:32:55 blofecn2 nfsserver(nfs_daemon)[1282251]: ERROR: Failed to unmount /var/lib/nfs May 23 06:32:55 blofecn2 nfsserver(nfs_daemon)[1282251]: ERROR: Failed to unmount a bind mount May 23 06:32:55 blofecn2 pacemaker-execd[7826]: notice: nfs_daemon_stop_0[1282251] error output [ umount: /var/lib/nfs: target is busy. ] May 23 06:32:55 blofecn2 pacemaker-execd[7826]: notice: nfs_daemon_stop_0[1282251] error output [ ocf-exit-reason:Failed to unmount a bind mount ] May 23 06:32:55 blofecn2 pacemaker-controld[7829]: notice: Result of stop operation for nfs_daemon on blofecn-node2: error (Failed to unmount a bind mount) May 23 06:32:55 blofecn2 pacemaker-controld[7829]: notice: blofecn-node2-nfs_daemon_stop_0:491 [ umount: /var/lib/nfs: target is busy.\nocf-exit-reason:Failed to unmount a bind mount\n ] May 23 06:32:55 blofecn2 pacemaker-controld[7829]: notice: Transition 675 aborted by operation nfs_daemon_stop_0 'modify' on blofecn-node2: Event failed May 23 06:32:55 blofecn2 pacemaker-controld[7829]: notice: Transition 675 action 133 (nfs_daemon_stop_0 on blofecn-node2): expected 'ok' but got 'error' May 23 06:32:55 blofecn2 pacemaker-controld[7829]: notice: Transition 675 (Complete=22, Pending=0, Fired=0, Skipped=0, Incomplete=35, Source=/var/lib/pacemaker/pengine/pe-input-1098.bz2): Compl ete May 23 06:32:55 blofecn2 pacemaker-attrd[7827]: notice: Setting fail-count-nfs_daemon#stop_0[blofecn-node2]: (unset) -> INFINITY May 23 06:32:55 blofecn2 pacemaker-attrd[7827]: notice: Setting last-failure-nfs_daemon#stop_0[blofecn-node2]: (unset) -> 1716438775 May 23 06:32:55 blofecn2 sbd[7086]: warning: inquisitor_child: pcmk health check: UNHEALTHY May 23 06:32:55 blofecn2 sbd[7086]: warning: inquisitor_child: Servant pcmk is outdated (age: 602589) May 23 06:32:55 blofecn2 pacemaker-schedulerd[7828]: warning: Unexpected result (error: Failed to unmount a bind mount) was recorded for stop of nfs_daemon on blofecn-node2 at May 23 06:32:53 2 024 May 23 06:32:55 blofecn2 pacemaker-schedulerd[7828]: warning: Unexpected result (error: Failed to unmount a bind mount) was recorded for stop of nfs_daemon on blofecn-node2 at May 23 06:32:53 2 024 May 23 06:32:55 blofecn2 pacemaker-schedulerd[7828]: warning: Cluster node blofecn-node2 will be fenced: nfs_daemon failed there After that i looked at the mounts a little closer. My issue seems to be the following: /dev/mapper/DCSS_VG-nfs_infodir on /export_root/nfs_infodir type ext4 (rw,relatime) /dev/mapper/DCSS_VG-nfs_infodir on /var/lib/nfs type ext4 (rw,relatime) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) sunrpc on /export_root/nfs_infodir/rpc_pipefs type rpc_pipefs (rw,relatime) rpc_pipefs is mounted twice, becaufe i originally set the nfs_shared_infodir to /export_root/nfs_infodir an mounted the Filesystem there, a bind mount to /var/lib/nfs also creates a second pipefs mount. I now switched my nfs_shared_infodir directly to /var/lib/nfs by updating the resources. Now i have only one pipefs mount: /dev/mapper/DCSS_VG-nfs_infodir on /var/lib/nfs type ext4 (rw,relatime) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) Since i can only test on Thursday i'll report back after 6th of june if this is working Best wishes Jacob -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065848 Title: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2065848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
