My server today has started throwing all kinds of problems.  The biggest one being I'm getting execution error server error messages.  Additionally I am getting callback trace messages.  I cant start new containers, install new ones, or even stop current ones.

 

attached are the sys logs and diagnostic logs

 

Any assistance in forcing this thing back into proper behavior would be greatly appreciated.

chipshop-syslog-20220726-0224.zip chipshop-diagnostics-20220725-2152.zip

 

so i am redoing the docker.img file, would you recommend switching to ipvlan instead of mac?

 

EDIT

so turns out ipvlan isnt really an option as it seems to actually be causing more harm than good.

Edited July 26, 20223 yr by OmegaXis

11 minutes ago, OmegaXis said:

would you recommend switching to ipvlan instead of mac?

For many, this change alone eliminates the call traces which are caused by macvlan.  It is certainly worth a try and easy to do.

2 minutes ago, Hoopster said:

For many, this change alone eliminates the call traces which are caused by macvlan.  It is certainly worth a try and easy to do.

for me, i ended up being able to install 2 docker containers before I started getting the following messages
 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='magnetman' --net='br0' --ip='192.168.128.2' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="chipshop" -e HOST_CONTAINERNAME="magnetman" -e 'TCP_PORT_443'='8186' -e 'HOSTNAME'='magnetman.moroneylabs.net' -e 'REVERSE_PROXY'='moroneylabs.net' -e 'REVERSE_PROXY_TLS_PORT'='443' -e 'IFRAME'='false' -e 'ALLOW_NEW_ACCOUNTS'='false' -e 'WEBRTC'='true' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='https://[IP]:[PORT:8086]' -l net.unraid.docker.icon='https://github.com/Muwahhidun/logo/blob/main/meshcentral-logo.png?raw=true' -v '/mnt/user/appdata/meshcentral/meshcentral-data':'/opt/meshcentral/meshcentral-data':'rw' -v '/mnt/user/appdata/meshcentral/meshcentral-files ':'/opt/meshcentral/meshcentral-files ':'rw' 'typhonragewind/meshcentral'

2e85e8df3209379e15387668a7a77667df706d67b2d612ac9af7ee4a174801fd
docker: Error response from daemon: failed to create the ipvlan port: device or resource busy.

The command failed.

 

Not really worth it for me

3 minutes ago, OmegaXis said:

docker: Error response from daemon: failed to create the ipvlan port: device or resource busy.

Hmmm.  I have personally never seen that error and I have had docker set to ipvlan for months now.  However, I solved the call trace problem a couple of years ago (before ipvlan was an option) by setting up a vlan for docker containers to which I wanted to assign static IP addresses.

I honestly think what happened was either splunk or checkmk docker images went rouge and caused all kinds of havok on the server.  I think the best thing is to just attempt to run those via a vm instead of docker.