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.
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 {
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
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-3ubuntu
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:
** 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
*** 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: linu
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 thi
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
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
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/+sour
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 le
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
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
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 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
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 Ubu
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 1671
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 man
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 change
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
# re
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
** 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
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 r
24 matches
Mail list logo
