[Bug 1960036] Re: [SRU] Doesn't regain quorum when tracked process restarts with PID > 32767
version tested: 2.0.19-2ubuntu0.2 tested keepalived ability to regain quorum after the tracked process (with high numbers pid) restarts. Based on my testing the version tested fixes the reported issue. I do not know if it introduces new bugs. I only tested to see if it fixes the reported issue. Note: after downgrading back to 2.0.19-2ubuntu0.1 the issue re appears. testing output ``` pre patch pp01 stop haproxy service Feb 16 11:30:26 pp01 systemd[1]: Stopping HAProxy Load Balancer... Feb 16 11:30:26 pp01 systemd[1]: haproxy.service: Succeeded. Feb 16 11:30:26 pp01 systemd[1]: Stopped HAProxy Load Balancer. Feb 16 11:30:27 pp01 Keepalived_vrrp[18854]: Quorum lost for tracked process track_haproxy Feb 16 11:30:27 pp01 Keepalived_vrrp[18854]: (LB_VIP) Changing effective priority from 111 to 101 Feb 16 11:30:31 pp01 Keepalived_vrrp[18854]: (LB_VIP) Master received advert from 10.4.150.182 with higher priority 110, ours 101 Feb 16 11:30:31 pp01 Keepalived_vrrp[18854]: (LB_VIP) Entering BACKUP STATE Feb 16 11:30:54 pp01 systemd[1]: Starting HAProxy Load Balancer... Feb 16 11:30:54 pp01 systemd[1]: Started HAProxy Load Balancer. start haproxy service -- nothing restart haproxy service eb 16 11:32:15 pp01 systemd[1]: Stopping Keepalive Daemon (LVS and VRRP)... Feb 16 11:32:16 pp01 Keepalived_vrrp[18854]: Released DBus Feb 16 11:32:16 pp01 Keepalived_vrrp[18854]: Stopped Feb 16 11:32:16 pp01 Keepalived[18853]: Stopped Keepalived v2.0.19 (10/19,2019) Feb 16 11:32:16 pp01 systemd[1]: keepalived.service: Succeeded. Feb 16 11:32:16 pp01 systemd[1]: Stopped Keepalive Daemon (LVS and VRRP). Feb 16 11:32:16 pp01 systemd[1]: Started Keepalive Daemon (LVS and VRRP). Feb 16 11:32:16 pp01 Keepalived[511543]: Starting Keepalived v2.0.19 (10/19,2019) Feb 16 11:32:16 pp01 Keepalived[511543]: Running on Linux 5.11.0-1028-aws #31~20.04.1-Ubuntu SMP Fri Jan 14 14:37:50 UTC 2022 (built for Linux 5.4.151) Feb 16 11:32:16 pp01 Keepalived[511543]: Command line: '/usr/sbin/keepalived' '--dont-fork' Feb 16 11:32:16 pp01 Keepalived[511543]: Opening file '/etc/keepalived/keepalived.conf'. Feb 16 11:32:16 pp01 Keepalived[511543]: Starting VRRP child process, pid=511544 Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: Registering Kernel netlink reflector Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: Registering Kernel netlink command channel Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: Opening file '/etc/keepalived/keepalived.conf'. Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: (LB_VIP) Changing effective priority from 101 to 111 Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: Registering gratuitous ARP shared channel Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: (LB_VIP) Entering BACKUP STATE (init) Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: Acquired DBus bus org.keepalived.Vrrp1 Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: Acquired the name org.keepalived.Vrrp1 on the session bus Feb 16 11:32:17 pp01 Keepalived_vrrp[511544]: (LB_VIP) received lower priority (110) advert from 10.4.150.182 - discarding Feb 16 11:32:20 pp01 Keepalived_vrrp[511544]: message repeated 3 times: [ (LB_VIP) received lower priority (110) advert from 10.4.150.182 - discarding] Feb 16 11:32:20 pp01 Keepalived_vrrp[511544]: (LB_VIP) Entering MASTER STATE pp02 stop haproxy service Feb 16 11:30:28 pp02 Keepalived_vrrp[399]: (LB_VIP) received lower priority (101) advert from 10.4.150.181 - discarding Feb 16 11:30:30 pp02 Keepalived_vrrp[399]: message repeated 2 times: [ (LB_VIP) received lower priority (101) advert from 10.4.150.181 - discarding] Feb 16 11:30:31 pp02 Keepalived_vrrp[399]: (LB_VIP) Entering MASTER STATE start haproxy service -- nothing restart haproxy service Feb 16 11:32:20 pp02 Keepalived_vrrp[399]: (LB_VIP) Master received advert from 10.4.150.181 with higher priority 111, ours 110 Feb 16 11:32:20 pp02 Keepalived_vrrp[399]: (LB_VIP) Entering BACKUP STATE - post patch pp01 stop haproxy service eb 16 11:35:03 pp01 systemd[1]: Stopping HAProxy Load Balancer... Feb 16 11:35:03 pp01 systemd[1]: haproxy.service: Succeeded. Feb 16 11:35:03 pp01 systemd[1]: Stopped HAProxy Load Balancer. Feb 16 11:35:04 pp01 Keepalived_vrrp[511912]: Quorum lost for tracked process track_haproxy Feb 16 11:35:04 pp01 Keepalived_vrrp[511912]: (LB_VIP) Changing effective priority from 111 to 101 Feb 16 11:35:07 pp01 Keepalived_vrrp[511912]: (LB_VIP) Master received advert from 10.4.150.182 with higher priority 110, ours 101 Feb 16 11:35:07 pp01 Keepalived_vrrp[511912]: (LB_VIP) Entering BACKUP STATE start haproxy service Feb 16 11:35:45 pp01 systemd[1]: Starting HAProxy Load Balancer... Feb 16 11:35:45 pp01 Keepalived_vrrp[511912]: Quorum gained for tracked process track_haproxy Feb 16 11:35:45 pp01 Keepalived_vrrp[511912]: (LB_VIP) Changing effective priority from 101 to 111 Feb 16 11:35:46 pp01 systemd[1]: Started HAProxy Load Balancer. Feb 16 11:35:46 pp01 Keepalived_vrrp[511912]: (LB_VIP) received lower priority (110) advert
[Bug 1960036] Re: Doesnt regain quorum when tracked process restarts
Here are both of the keepalived configs, Both after about as basic as
they get. I am not sure how to force the high pid's. If you need more
information from me, just let me know.
primary keepalived config (update ips to match your environment)
```
# Global Settings for notifications
global_defs {
enable_script_security
script_user keepalived_script
enable_dbus
}
vrrp_track_process track_haproxy {
process haproxy
weight 10
delay 1
}
# Configuration for Virtual Interface
vrrp_instance LB_VIP {
interface ens5
state MASTER
priority 101
virtual_router_id 51
authentication {
auth_type PASS
auth_pass somepassword # Password for accessing vrrpd. Same on all
devices, only up to 8 chars
}
unicast_src_ip 10.1.1.3 # Private IP address of primary
unicast_peer {
10.1.1.4 # Private IP address of the secondary haproxy
}
# The virtual ip address shared between the two loadbalancers
virtual_ipaddress {
10.1.1.2
}
# Use the Defined Script to Check whether to initiate a fail over
#track_script {
#chk_haproxy
#}
track_process {
track_haproxy
}
}
```
backup keepalived config
```
# Global Settings for notifications
global_defs {
enable_script_security
script_user keepalived_script
enable_dbus
}
vrrp_track_process track_haproxy {
process haproxy
weight 10
delay 1
}
# Configuration for Virtual Interface
vrrp_instance LB_VIP {
interface ens5
state BACKUP
priority 100
virtual_router_id 51
authentication {
auth_type PASS
auth_pass somepass # Password for accessing vrrpd. Same on all
devices, only up to 8 chars
}
unicast_src_ip 10.1.1.4 # Private IP address of primary
unicast_peer {
10.1.1.3 # Private IP address of the secondary haproxy
}
# The virtual ip address shared between the two loadbalancers
virtual_ipaddress {
10.1.1.2
}
track_process {
track_haproxy
}
}
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960036
Title:
Doesnt regain quorum when tracked process restarts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1960036/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960036] [NEW] Doesnt regain quorum when tracked process restarts
Public bug reported: Keepalived doesn't regain quorum when using tracked process due to a bug in high numbered pids The upstream has already fixed in a patch release 2.0.20 https://serverfault.com/questions/993432/keepalived-doesnt-gain-quorum- when-tracked-process-comes-up Could we please get the 2.0.20 released to 20.04 ** Affects: keepalived (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/1960036 Title: Doesnt regain quorum when tracked process restarts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1960036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
After testing I can confirm that this new version by all accounts fixes the reported bug. Stopping and starting a systemd resource with timeout = "10s" does not fail with timeouts I tested this by installing the original 2.0.3-3ubuntu3, and reproducing the bug. then I upgraded to 2.0.3-3ubuntu4 (the proposed) and cannot reproduce the bug. Marking this as resolved ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881762 Title: resource timeout not respecting units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895010] Re: ocfs2 shared volume causing hang
hopefully this ticket gets some notice soon as this bug appears to be a kernel level regression in a "major" kernel level feature: ocfs2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895010 Title: ocfs2 shared volume causing hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895010] Re: ocfs2 shared volume causing hang
** 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/1895010 Title: ocfs2 shared volume causing hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894247] Re: virtual machine locks up when accessing mounted share
*** This bug is a duplicate of bug 1895010 *** https://bugs.launchpad.net/bugs/1895010 I cannot run then command as the vm where the issue occurred is no longer running the problematic kernel. And yes this appears by all intents and purpose to be a kernel level regression ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** This bug has been marked a duplicate of bug 1895010 ocfs2 shared volume causing hang -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894247 Title: virtual machine locks up when accessing mounted share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894247] Re: virtual machine locks up when accessing mounted share
at the time when i filed the bug I had not yet determined that it was a kernel issue. I am now sure, and there is a proper kernel bug filed for the issue: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1895010, close, marked as duplicate, etc. Do as you see fit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894247 Title: virtual machine locks up when accessing mounted share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895010] [NEW] ocfs2 shared volume causing hang
Public bug reported: This vm is running on a vmware backed system with a multiwriter shared volume mounted via ocfs2. in kernel version 4.4.0-187 or -189 any attempt at writting to the volume results in kernel errors root@hostname:/mnt/NewsroomImageShare# touch text.txt Killed kernel version 186 this issue does not occur. root@hostname:~# lsb_release -rd Description:Ubuntu 16.04.7 LTS Release:16.04 package ii linux-image-4.4.0-187-generic 4.4.0-187.217 amd64Signed kernel image generic what I expect to happen: writing to a ocfs2 shared disk should not crash what happens: writting to an ocfs2 shared disk crashes the terminal/ssh session, and make the vm unusable. and logs errors in dmesg [Sep 3 04:09] general protection fault: [#1] SMP [ +0.000346] Modules linked in: mptctl ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs vmw_balloon joydev input_leds serio_raw shpchp i2c_piix4 vmw_vsock_vmci_transport vsock vmw_vmci mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse vmwgfx ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci vmxnet3 libahci mptspi mptscsih drm pata_acpi mptbase scsi_transport_spi fjes [ +0.001534] CPU: 0 PID: 1553 Comm: java Not tainted 4.4.0-189-generic #219-Ubuntu [ +0.49] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018 [ +0.67] task: 880073863900 ti: 8800798e task.ti: 8800798e [ +0.47] RIP: 0010:[] [] _raw_spin_lock+0xe/0x70 [ +0.86] RSP: 0018:8800798e3998 EFLAGS: 00010206 [ +0.35] RAX: 0002 RBX: 6d612d7972616e69 RCX: [ +0.46] RDX: 8000 RSI: 0009 RDI: 6d612d7972616ef1 [ +0.45] RBP: 8800798e3998 R08: R09: [ +0.45] R10: 880075729060 R11: 8000 R12: 6d612d7972616ef1 [ +0.44] R13: 8800748aeaa8 R14: 880076399650 R15: [ +0.46] FS: 7f9a50ad9700() GS:88007b60() knlGS: [ +0.51] CS: 0010 DS: ES: CR0: 80050033 [ +0.37] CR2: 7f9a1d4f2000 CR3: 79936000 CR4: 00160670 [ +0.000160] Stack: [ +0.19] 8800798e39b8 8123953e 0009 8800748ae000 [ +0.55] 8800798e3a38 c057bb77 c053309a [ +0.54] 88007958e498 88007958e4e0 0001 88007958e3c8 [ +0.55] Call Trace: [ +0.25] [] igrab+0x1e/0x50 [ +0.84] [] ocfs2_get_system_file_inode+0x67/0x300 [ocfs2] [ +0.88] [] ? ocfs2_read_virt_blocks+0x1ca/0x310 [ocfs2] [ +0.72] [] ? dx_leaf_sort_swap+0x40/0x40 [ocfs2] [ +0.75] [] ocfs2_reserve_suballoc_bits+0x4e/0x430 [ocfs2] [ +0.74] [] ocfs2_steal_resource+0x9b/0x130 [ocfs2] [ +0.001659] [] ocfs2_reserve_new_inode+0xb5/0x370 [ocfs2] [ +0.001326] [] ocfs2_mknod+0x4be/0x10e0 [ocfs2] [ +0.001622] [] ? ocfs2_should_refresh_lock_res+0x113/0x160 [ocfs2] [ +0.001571] [] ocfs2_create+0x4c/0x160 [ocfs2] [ +0.001318] [] vfs_create+0x12d/0x190 [ +0.001218] [] path_openat+0x1232/0x1360 [ +0.001255] [] ? file_update_time+0xcc/0x110 [ +0.001167] [] do_filp_open+0x91/0x100 [ +0.001132] [] ? new_sync_write+0xa5/0xf0 [ +0.001131] [] ? __alloc_fd+0xc7/0x190 [ +0.001072] [] do_sys_open+0x138/0x2a0 [ +0.001040] [] SyS_open+0x1e/0x20 [ +0.001028] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [ +0.001041] Code: e2 fe 8d 72 02 0f b7 f6 0f 1f 80 00 00 00 00 eb d2 66 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 b8 00 00 02 00 0f c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 41 89 d0 0f b7 [ +0.003174] RIP [] _raw_spin_lock+0xe/0x70 [ +0.001007] RSP [ +0.002867] ---[ end trace 6fd21d2a8e763939 ]--- - [Sep 4 03:56] (java,5847,1):ocfs2_reserve_suballoc_bits:796 ERROR: status = -22 [ +0.98] (java,5847,1):ocfs2_reserve_new_inode:1120 ERROR: status = -22 [ +0.47] (java,5847,1):ocfs2_reserve_new_inode:1132 ERROR: status = -22 [ +0.46] (java,5847,1):ocfs2_mknod:314 ERROR: status = -22 [ +0.49] (java,5847,1):ocfs2_mknod:499 ERROR: status = -22 [ +0.40] (java,5847,1):ocfs2_create:679 ERROR: status = -22 [ +8.987127] (java,2088,0):ocfs2_reserve_suballoc_bits:796 ERROR: status = -22 [ +0.93] (java,2088,0):ocfs2_reserve_new_inode:1120 ERROR: status = -22 [ +0.000146] (java,2088,0):ocfs2_reserve_new_inode:1132 ERROR: status = -22 [ +0.47] (java,2088,0):ocfs2_mknod:314
[Bug 1894988] [NEW] ocfs2 crashing
Public bug reported: a ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-176-generic 4.4.0-176.206 ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 Date: Wed Sep 9 12:48:41 2020 InstallationDate: Installed on 2016-10-21 (1418 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug xenial ** Changed in: linux-signed (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/1894988 Title: ocfs2 crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1894988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894988] Re: ocfs2 crashing
filed against wrong kernel version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894988 Title: ocfs2 crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1894988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894247] [NEW] virtual machine locks up when accessing mounted share
Public bug reported: I have a virtual machine that locks up every time any file access is done to the mounted ocsfs2 shared volume. the volume is backed by vmware multiwriter virtual disk. I do not have a lot of diagnostics other than the various dmesg logs it seems to be an ocfs2 issue or at least ocfs2 is "crashing" when this happens the ssh session locks up and is un usable. and as a result of monitoring services that try to read disk status the cpu load goes high attempts to reboot the vm during this state sometimes result in user@hostname:~$ sudo shutdown -r now Failed to start reboot.target: Connection timed out See system logs and 'systemctl status reboot.target' for details. lsb_release -rd Description:Ubuntu 16.04.7 LTS Release:16.04 apt-cache policy ocfs2-tools ocfs2-tools: Installed: 1.6.4-3.1 number #1 [Sep 4 14:33] BUG: unable to handle kernel paging request at c0504088 [ +0.000101] IP: [] _raw_spin_lock+0xe/0x70 [ +0.000100] PGD 1e0f067 PUD 1e11067 PMD 33756067 PTE 778f3061 [ +0.48] Oops: 0003 [#1] SMP [ +0.27] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue mptctl configfs vmw_balloon joydev input_leds serio_raw i2c_piix4 shpchp mac_hid vmw_vsock_vmci_transport vsock vmw_vmci ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse mptspi mptscsih mptbase scsi_transport_spi vmwgfx ahci ttm drm_kms_helper syscopyarea vmxnet3 sysfillrect sysimgblt fb_sys_fops libahci drm pata_acpi fjes [ +0.000591] CPU: 0 PID: 5568 Comm: touch Not tainted 4.4.0-189-generic #219-Ubuntu [ +0.49] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018 [ +0.67] task: 880034f25580 ti: 8800767c4000 task.ti: 8800767c4000 [ +0.47] RIP: 0010:[] [] _raw_spin_lock+0xe/0x70 [ +0.57] RSP: 0018:8800767c7998 EFLAGS: 00010286 [ +0.35] RAX: 0002 RBX: c0504000 RCX: [ +0.45] RDX: 8000 RSI: 0009 RDI: c0504088 [ +0.44] RBP: 8800767c7998 R08: R09: [ +0.45] R10: 880078ea5f00 R11: 8000 R12: c0504088 [ +0.44] R13: 880077a63aa8 R14: 880077a510d0 R15: [ +0.47] FS: 7fe66bc9e700() GS:88007b60() knlGS: [ +0.50] CS: 0010 DS: ES: CR0: 80050033 [ +0.000117] CR2: c0504088 CR3: 763c CR4: 00160670 [ +0.000203] Stack: [ +0.18] 8800767c79b8 8123953e 0009 880077a63000 [ +0.55] 8800767c7a38 c0582b77 c053a09a [ +0.54] 8800784b7c98 8800784b7ce0 0001 8800784b7bc8 [ +0.54] Call Trace: [ +0.84] [] igrab+0x1e/0x50 [ +0.000393] [] ocfs2_get_system_file_inode+0x67/0x300 [ocfs2] [ +0.001444] [] ? ocfs2_read_virt_blocks+0x1ca/0x310 [ocfs2] [ +0.001374] [] ? dx_leaf_sort_swap+0x40/0x40 [ocfs2] [ +0.001347] [] ocfs2_reserve_suballoc_bits+0x4e/0x430 [ocfs2] [ +0.001329] [] ocfs2_steal_resource+0x9b/0x130 [ocfs2] [ +0.001313] [] ocfs2_reserve_new_inode+0xb5/0x370 [ocfs2] [ +0.001294] [] ocfs2_mknod+0x4be/0x10e0 [ocfs2] [ +0.001296] [] ? ocfs2_should_refresh_lock_res+0x113/0x160 [ocfs2] [ +0.001300] [] ocfs2_create+0x4c/0x160 [ocfs2] [ +0.001279] [] vfs_create+0x12d/0x190 [ +0.001790] [] path_openat+0x1232/0x1360 [ +0.001198] [] do_filp_open+0x91/0x100 [ +0.001217] [] ? do_mmap+0x309/0x480 [ +0.001132] [] ? __alloc_fd+0xc7/0x190 [ +0.001110] [] do_sys_open+0x138/0x2a0 [ +0.001099] [] ? __do_page_fault+0x1c1/0x410 [ +0.001043] [] SyS_open+0x1e/0x20 [ +0.001029] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [ +0.001036] Code: e2 fe 8d 72 02 0f b7 f6 0f 1f 80 00 00 00 00 eb d2 66 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 b8 00 00 02 00 0f c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 41 89 d0 0f b7 [ +0.003175] RIP [] _raw_spin_lock+0xe/0x70 [ +0.001009] RSP [ +0.000996] CR2: c0504088 [ +0.002732] ---[ end trace c3584abd4a8a5250 ]--- #2 [Sep 3 04:09] general protection fault: [#1] SMP [ +0.000346] Modules linked in: mptctl ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs vmw_balloon joydev input_leds serio_raw shpchp i2c_piix4 vmw_vsock_vmci_transport vsock vmw_vmci mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov
[Bug 1551973] Re: multiple messages in the form of ''Couldn't open dir /proc/[some pid]/fd: No such file or directory'' are displayed and mess up the table
Description:Ubuntu 16.04.6 LTS nethogs 0.8.1-0.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551973 Title: multiple messages in the form of ''Couldn't open dir /proc/[some pid]/fd: No such file or directory'' are displayed and mess up the table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nethogs/+bug/1551973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] [NEW] resource timeout not respecting units
Public bug reported: While working on pacemaker, i discovered a issue with timeouts haproxy_stop_0 on primary 'OCF_TIMEOUT' (198): call=583, status='Timed Out', exitreason='', last-rc-change='1970-01-04 17:21:18 -05:00', queued=44ms, exec=176272ms this lead me down the path of finding that setting a timeout unit value was not doing anything primitive haproxy systemd:haproxy \ op monitor interval=2s \ op start interval=0s timeout=500s \ op stop interval=0s timeout=500s \ meta migration-threshold=2 primitive haproxy systemd:haproxy \ op monitor interval=2s \ op start interval=0s timeout=500 \ op stop interval=0s timeout=500 \ meta migration-threshold=2 the two above configs result in the same behaviour, pacemaker/crm seems to be ignoring the "s" I file a bug with pacemaker itself https://bugs.clusterlabs.org/show_bug.cgi?id=5429 but this lead to the following responsed, copied from the ticket:
[Bug 1190696] Re: updatedb.mlocate uses 100% of the hdd IO. The OS is completely unusable.
I have this issue on 16.04 (recently in place upgraded from 14.04), it makes the physical machine basically useless. And this issue persists for hours. Today is the second time it has happened on the same machine. last time I kill the process after some number of hours of waiting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190696 Title: updatedb.mlocate uses 100% of the hdd IO. The OS is completely unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1190696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710296] Re: script hangs and never finishes
this issue persist jason@server03:~$ pgrep check-new-re 765 1925 1952 3852 4072 5238 5467 5646 6464 6753 9409 12877 14336 15288 16599 17057 18756 20018 20029 20174 20255 20726 22315 22523 22855 24292 24876 25964 26093 27981 28489 29387 30350 32556 jason@server03:~$ pgrep check-new-re | wc -l 34 jason@server03:~$ ps -ef | grep check-new-re root 765 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 1925 1 0 Feb04 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 1952 1 0 Mar11 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 3852 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 4072 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 5238 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 5467 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 5646 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 6464 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 6753 1 0 Jan21 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 9409 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 12877 1 0 Feb25 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 14336 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 15288 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 16599 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 17057 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 18756 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 20018 1 0 Mar18 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 20029 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 20174 1 0 Jan28 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 20255 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 20726 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 22315 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 22523 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 22855 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 24292 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 24876 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 25964 1 0 Jan14 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 26093 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 27981 1 0 Mar04 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 28489 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 29387 1 0 Feb18 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 30350 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 32556 1 0 2017 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q every week it runs and leaves behind another process, this is crazy. What is causing this bug, and how do I fix it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710296 Title: script hangs and never finishes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1710296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710296] Re: script hangs and never finishes
This is becoming a persistent problem on numerous servers that I monitoring/maintain. I am seriously considering disabling this cron. Is there anyway I could get some traction on this issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710296 Title: script hangs and never finishes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1710296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710296] Re: script hangs and never finishes
user@somenode:~$ ps -ef | grep check-new root 5102 1 0 Jul30 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 9228 1 0 Jul16 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 16718 1 0 Jul02 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 18286 1 0 Aug20 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 40711 1 0 Jun25 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 42309 1 0 Jul23 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 44891 1 0 Jun18 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 49048 1 0 Jun11 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 56328 1 0 Aug27 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 67336 1 0 Aug06 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 89995 1 0 Jul09 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 130476 1 0 Aug13 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q user@somenode:~$ lsb_release -d Description:Ubuntu 16.04.2 LTS user@somenode:~$ dpkg -l | grep ubuntu-re ii ubuntu-release-upgrader-core 1:16.04.21 all manage release upgrades user@somenode:~$ sudo strace -p 130476 strace: Process 130476 attached futex(0x115c510, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, ^Cstrace: Process 130476 detached I can now confirm that this also occurs on 16.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710296 Title: script hangs and never finishes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1710296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710296] Re: script hangs and never finishes
Hello, the ticket is still marked as incomplete, what additional information do you need from me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710296 Title: script hangs and never finishes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1710296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710296] Re: script hangs and never finishes
Yes i can connect to the changelog server. user@archive:~$ wget http://changelogs.ubuntu.com/meta-release-lts --2017-08-15 11:12:37-- http://changelogs.ubuntu.com/meta-release-lts Resolving changelogs.ubuntu.com (changelogs.ubuntu.com)... 91.189.95.15, 2001:67c:1560:8008::11 Connecting to changelogs.ubuntu.com (changelogs.ubuntu.com)|91.189.95.15|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 3683 (3.6K) Saving to: ‘meta-release-lts’ 100%[===>] 3,683 --.-K/s in 0s 2017-08-15 11:12:37 (278 MB/s) - ‘meta-release-lts’ saved [3683/3683] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710296 Title: script hangs and never finishes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1710296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710296] Re: script hangs and never finishes
user@mm02archive:~# cat /etc/update-manager/release-upgrades # Default behavior for the release upgrader. [DEFAULT] # Default prompting behavior, valid options: # # never - Never check for a new release. # normal - Check to see if a new release is available. If more than one new # release is found, the release upgrader will attempt to upgrade to # the release that immediately succeeds the currently-running # release. # lts- Check to see if a new LTS release is available. The upgrader # will attempt to upgrade to the first LTS release available after # the currently-running one. Note that this option should not be # used if the currently-running release is not itself an LTS # release, since in that case the upgrader won't be able to # determine if a newer release is available. Prompt=lts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710296 Title: script hangs and never finishes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1710296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710296] [NEW] script hangs and never finishes
Public bug reported: The /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q job that runs weekly appears to hang and never complets, slowly building up the number of hanging processes user@archive:~$ ps -ef | grep check-new root 1618 1 0 Feb26 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 3489 1 0 Jul09 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 5951 1 0 Mar19 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 14385 1 0 Apr02 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 14490 1 0 Jul23 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 15157 1 0 Apr30 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 17853 1 0 Jun04 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 21845 1 0 Jun11 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 22240 1 0 May21 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 22607 1 0 Jul02 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 23452 1 0 Apr16 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 27171 1 0 Feb19 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 28447 1 0 Jun18 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 29531 1 0 Mar05 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 30531 1 0 Jun25 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 31763 1 0 May14 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 32360 1 0 May07 ?00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q user@archive:~$ sudo strace -p 32360 Process 32360 attached futex(0x27b0fd0, FUTEX_WAIT_PRIVATE, 0, NULL Running Trusty user@archive:~$ lsb_release -d Description:Ubuntu 14.04.5 LTS user@archive:~$ dpkg -l | grep ubuntu-re ii ubuntu-release-upgrader-core 1:0.220.9 all manage release upgrades user@archive:~$ apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:0.220.9 Candidate: 1:0.220.9 Version table: *** 1:0.220.9 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.220.2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Any assistance in resolving these hanging processes that grow for no apparent reason. I could simply disable the cron job, but i am trying to get to the root of the issues and resolve it. Expected behaviour: The script should terminate and close the process. what happened: the script hang and runs in background forever. ** Affects: ubuntu-release-upgrader (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/1710296 Title: script hangs and never finishes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1710296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425995] [NEW] mysql fails to start on reboot
Public bug reported: ubuntu 14.04 lts after rebooting the system, mysql fails to start correctly and does no create the appropriate .sock file. the mysqld process is running. ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) mysql should restart correctly after a system reboot ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mysql-server 5.5.41-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Thu Feb 26 10:39:25 2015 Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d..keepme: MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: False PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: mysql-5.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1425995 Title: mysql fails to start on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1425995/+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 1425995] [NEW] mysql fails to start on reboot
Public bug reported: ubuntu 14.04 lts after rebooting the system, mysql fails to start correctly and does no create the appropriate .sock file. the mysqld process is running. ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) mysql should restart correctly after a system reboot ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mysql-server 5.5.41-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Thu Feb 26 10:39:25 2015 Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d..keepme: MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: False PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: mysql-5.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425995 Title: mysql fails to start on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1425995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425995] Re: mysql fails to start on reboot
** Description changed: ubuntu 14.04 lts after rebooting the system, mysql fails to start correctly and does no create the appropriate .sock file. the mysqld process is running. ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) mysql should restart correctly after a system reboot + this issue does not occur everytime, and seems like a potential race condition issue. + restarting the mysql service after boot fixes the issue (service mysql restart) + + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mysql-server 5.5.41-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Thu Feb 26 10:39:25 2015 Logs.var.log.daemon.log: - - MySQLConf.etc.mysql.conf.d..keepme: + + MySQLConf.etc.mysql.conf.d..keepme: MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf: - [mysqld_safe] - syslog + [mysqld_safe] + syslog MySQLVarLibDirListing: False PackageArchitecture: all ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=en_CA.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=en_CA.UTF-8 + SHELL=/bin/bash SourcePackage: mysql-5.5 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425995 Title: mysql fails to start on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1425995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
