Getting "Invalid ELF header magic: != \x7fELF" after system update

ottobaer

Hi,

I’m currently using Arch with mailcow - I know it’s not supported, but I wanted to see if someone could help me anyway.

After an update I get the following messages in dmesg

“[ 613.763330] Invalid ELF header magic: != \x7fELF”

Docker version 24.0.7, build afdd53b4e3
Docker Compose version 2.23.3
Kernel 6.6.10

Anyone has an idea?

esackbauer

This was already discussed some time ago, and this is Arch specific, and had no solution:
https://community.mailcow.email/d/2287-what-is-this-odd-invalid-elf-header/5

maybl8

From this it looks like a smbclient issue
https://bbs.archlinux.org/viewtopic.php?id=135844
I get the same errors but my mailcow is working just fine.
My system:

Host: PowerEdge T30
              Kernel: 6.1.70-1-lts
             Uptime: 5 days, 17 hours, 24 mins
            Packages: 856 (pacman)
             Shell: bash 5.2.21
          Resolution: 1920x1080
          DE: Xfce 4.18
          WM: Xfwm4
          WM Theme: Default
          Theme: Adwaita [GTK2/3]
          Icons: elementary [GTK2], Adwaita [GTK3]
         Terminal: alacritty
      CPU: Intel Pentium G4400 (2) @ 3.300GHz
     GPU: Intel HD Graphics 510
 Memory: 6.24GiB / 31.22GiB (19%)
GPU Driver: Dell HD Graphics 510 [1028:07c5]
   CPU Usage: 17%
   Disk (/): 19G / 40G (50%)
   Font: Sans 10 [GTK2], Cantarell 11 [GTK3]
   Public IP: 47.200.48.82

ottobaer

maybl8

I don’t think it has something to do with smbclient - I have another installation that has the same packages installed as my mailcow server, but I don’t get these messages. I’m sure it has something to do with the docker Version and some prebuilt binaries in the docker images, but this might be a hassle to dissect since you would need to inspect all of the containers one by one.

For now I will wait either until 2027 (when Ubuntu LTS 22.04 becomes obsolete and Mailcow needs to adapt to a newer docker Version) or something breaks hard and I need to install Ubuntu to get a supported distro.

If I have time I will try to set up some mailcow instance on my local arch installation to look around a bit.

[unknown]

Just tested it on my local PC with Arch and it works without this message - really strange. I assume there is also a question of what hardware you use?

ottobaer

FYI - I could isolate it to the netfilter container, I assume it’s something in the python script that doesn’t like the glibc version. I will keep this thread updated if I have more information. Might be useful to everyone who uses Arch here.

ottobaer

After I found some more time to debug I think I fixed the problem.

Somehow this elf warning was triggered by some iptables modules that where not loaded automatically.

Basically I had the same error as described here

mailcow/mailcow-dockerized4802

The fix was to insmod the missing modules manually.

modprobe -v ip6table_filter
modprobe -v iptable_filter
docker-compose restart netfilter-mailcow

and it works as expected.

netfilter-mailcow-1  | Using IPTables backend
netfilter-mailcow-1  | Clearing all bans
netfilter-mailcow-1  | Initializing mailcow netfilter chain
netfilter-mailcow-1  | Watching Redis channel F2B_CHANNEL