Public bug reported:
Was upgrading the system from 18.04 to 20.04. Got a warning that it was
trying to remove the running kernel so I followed the recommendation and
aborted the removal.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-unsigned-5.4.0-47-generic 5.4.0-47.51~1
The "bad" unit had been running for about 2 months without the
application running, we started the application yesterday and noticed
this unexpected behavior. Two units in its cluster running the older
kernel which have been running the application , one for 48 consecutive
days and the other for
Ok, kill this one. Apparently something got hosed in the kernel and
rebooting the box made this behavior go away. It had been running for
about two months and began exhibiting this behavior yesterday.
Rebooting the server restored the expected behavior.
Chalk this one up to gremlins, I suppose.
Public bug reported:
I have an interface with a /32 IP address. It is just an interface that
sends out some multicast for some server clustering. Everything works
fine up to 2.6.35-28-server #49
Suddenly at 2.6.38-13-server #53 we get a change in IGMP behavior that
is breaking our stuff.
I ha
I rebooted a oneiric server today that I had not booted since December.
Bond interface gets created but the ethernet interfaces wont bind. it
sits there saying that it is waiting for a slave to bind for 60 seconds
and continues. The bonding module gets loaded, the interface is
configured, just th
