F5F Stay Refreshed Software Operating Systems Kernel panic issue – synchronization problems on Ubuntu 20.04

Kernel panic issue – synchronization problems on Ubuntu 20.04

Kernel panic issue – synchronization problems on Ubuntu 20.04

F
Freckin
Junior Member
36
10-03-2020, 08:13 PM
#1
Hello everyone! Thanks for checking this out as I’m getting familiar with managing my own server to host several versions of one app with varied settings. What’s required is assigning a unique IPv4 address to each app, so the server must have multiple IPs configured in the netplan file. Generally, when I set up the server from the ground up, I follow these steps: - Permit SSH root access - Configure netplan - Modify limits.conf in etc/security to allow more open files - Update and upgrade apt - Install necessary packages using apt-get - Set up a swap file - Adjust IP tables so each app uses its own internal port, with iptables directing traffic accordingly. I’m not sure what’s triggering this kernel panic, as the servers have been running for about nine months—some longer, some shorter. After a restart, they start crashing into this issue after a day or so. I’d really appreciate any guidance here! Thanks for your time and any additional details that could help.
F
Freckin
10-03-2020, 08:13 PM #1

Hello everyone! Thanks for checking this out as I’m getting familiar with managing my own server to host several versions of one app with varied settings. What’s required is assigning a unique IPv4 address to each app, so the server must have multiple IPs configured in the netplan file. Generally, when I set up the server from the ground up, I follow these steps: - Permit SSH root access - Configure netplan - Modify limits.conf in etc/security to allow more open files - Update and upgrade apt - Install necessary packages using apt-get - Set up a swap file - Adjust IP tables so each app uses its own internal port, with iptables directing traffic accordingly. I’m not sure what’s triggering this kernel panic, as the servers have been running for about nine months—some longer, some shorter. After a restart, they start crashing into this issue after a day or so. I’d really appreciate any guidance here! Thanks for your time and any additional details that could help.

A
AntekGamingHD
Junior Member
34
10-10-2020, 01:03 PM
#2
Review your package managers for a kernel update; if found, revert it. Regressions can occur, so ensure your systems are stable before testing on a separate machine.
A
AntekGamingHD
10-10-2020, 01:03 PM #2

Review your package managers for a kernel update; if found, revert it. Regressions can occur, so ensure your systems are stable before testing on a separate machine.

S
Siberian02
Member
157
10-10-2020, 03:05 PM
#3
I discovered the system ran kernel version 5.4.0-122 on July 12th via unattended upgrades on one of the servers. Upon checking boot options, I noticed entries like `:~# sudo grep 'menuentry \|submenu ' /boot/grub/grub.cfg | cut -f2 -d "' Ubuntu Advanced options for Ubuntu`. I modified the Grub configuration for the older kernel still present, hoping it resolves the issue. Appreciate your help!
S
Siberian02
10-10-2020, 03:05 PM #3

I discovered the system ran kernel version 5.4.0-122 on July 12th via unattended upgrades on one of the servers. Upon checking boot options, I noticed entries like `:~# sudo grep 'menuentry \|submenu ' /boot/grub/grub.cfg | cut -f2 -d "' Ubuntu Advanced options for Ubuntu`. I modified the Grub configuration for the older kernel still present, hoping it resolves the issue. Appreciate your help!

C
chikimonster
Member
151
10-15-2020, 12:15 PM
#4
The system doesn't match the expected operating system version across servers. There are multiple physical servers or a virtualized setup in place.
C
chikimonster
10-15-2020, 12:15 PM #4

The system doesn't match the expected operating system version across servers. There are multiple physical servers or a virtualized setup in place.

_
_PrincessZ_
Junior Member
16
10-15-2020, 01:25 PM
#5
This is quite a small version bump, if it does fix it, it should be fairly trivial to trace.
_
_PrincessZ_
10-15-2020, 01:25 PM #5

This is quite a small version bump, if it does fix it, it should be fairly trivial to trace.

X
XshalevX
Member
73
10-17-2020, 05:21 AM
#6
Various physical servers operated on the same Ubuntu 20.04 environment, with minor hardware variations present. The majority were equipped with AMD Epyc 7313 processors, offering configurations such as 16 cores/32 threads, clock speeds around 3.7 GHz, and storage solutions including a 128 GB ECC SSD with NVMe technology.
X
XshalevX
10-17-2020, 05:21 AM #6

Various physical servers operated on the same Ubuntu 20.04 environment, with minor hardware variations present. The majority were equipped with AMD Epyc 7313 processors, offering configurations such as 16 cores/32 threads, clock speeds around 3.7 GHz, and storage solutions including a 128 GB ECC SSD with NVMe technology.

M
193
10-18-2020, 07:20 AM
#7
The problem has been resolved; all servers remain operational. Currently, the fix is in place. Please allow some time to review the changes between versions to identify any issues. Thank you for your feedback!
M
McGamerPro2000
10-18-2020, 07:20 AM #7

The problem has been resolved; all servers remain operational. Currently, the fix is in place. Please allow some time to review the changes between versions to identify any issues. Thank you for your feedback!