OMV 6 autoshutdown plugin not finding connections on docker ports

funnybones24 · May 4th 2022

I've got some containers on docker running and im accessing them but it isnt showing as connected on the logs and therefore is shutting down while they are in use. in the spoiler has the a snippet from one of the logs while in fake mode. is there any extra config i have to do on docker for it to pick up the activity on those ports?

Display Spoiler

Code

May  4 19:18:01 server autoshutdown[385904]: root: INFO: 'FAKE-Mode: main(): New supervision cycle started, checking system activity'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: __run_check(): Calling: _check_net_status()'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 22: Found active connections:'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): tcp 0 0 192.168.1.24:ssh 192.168.1.16:62508'
May  4 19:18:01 server autoshutdown[385904]: root: INFO: 'FAKE-Mode: _check_net_status(): Found 1 active connection(s) on port 22 (SSH) from: 192.168.1.16'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 80: Found active connections:'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): tcp 0 0 192.168.1.24:http 192.168.1.16:62510'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): tcp 0 0 192.168.1.24:http 192.168.1.16:62511'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): tcp 0 0 192.168.1.24:http 192.168.1.16:62512'
May  4 19:18:01 server autoshutdown[385904]: root: INFO: 'FAKE-Mode: _check_net_status(): Found 3 active connection(s) on port 80 (HTTP) from: 192.168.1.16'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 81: Found no active connections'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 90: Found no active connections'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 445: Found no active connections'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 7878: Found no active connections'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 8000: Found no active connections'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 8096: Found no active connections'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 8920: Found no active connections'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 8989: Found no active connections'
May  4 19:18:01 server autoshutdown[385904]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 9000: Found no active connections'
May  4 19:18:01 server autoshutdown[385904]: root: INFO: 'FAKE-Mode: _check_net_status(): Found 4 active socket(s) from port(s): 22,80,81,90,445,7878,8000,8096,8920,8989,9000'
May  4 19:18:01 server autoshutdown[385904]: root: INFO: 'FAKE-Mode: main(): Active check failed, 5 cycles until shutdown ...'
May  4 19:18:01 server autoshutdown[385904]: root: INFO: 'FAKE-Mode: main(): Sleep for 60s'

Display More

nrand · May 5th 2022

Hi, I cannot tell much from this log as it found active connection using the standard port check not the docker port check. To know what is happening I need a log were you are only connected to one of the container (Jellyfin). Note this must not be a container that is is using '--network host'. This should then make the script runt the container port checks.

Also what version of OMV are you using and what version on Autoshutdown ?

funnybones24 · May 16th 2022

Quote from nrand

Hi, I cannot tell much from this log as it found active connection using the standard port check not the docker port check. To know what is happening I need a log were you are only connected to one of the container (Jellyfin). Note this must not be a container that is is using '--network host'. This should then make the script runt the container port checks.

Also what version of OMV are you using and what version on Autoshutdown ?

Sorry for the late delay, expected to get an email notification for this thread.

All my containers are running on a stack which uses a bridge network. The logs are attached below

Im running on OMV version 6.0.27-1 with Autoshutdown version 6.0.8

Code

May 16 21:50:12 server autoshutdown[538955]: root: INFO: 'FAKE-Mode: main(): New supervision cycle started, checking system activity'
May 16 21:50:12 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: __run_check(): Calling: _check_net_status()'
May 16 21:50:12 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 22: Found no active connections'
May 16 21:50:12 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 80: Found no active connections'
May 16 21:50:12 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 81: Found no active connections'
May 16 21:50:12 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 90: Found no active connections'
May 16 21:50:12 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 7878: Found no active connections'
May 16 21:50:12 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 8000: Found no active connections'
May 16 21:50:12 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 8096: Found no active connections'
May 16 21:50:12 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 8920: Found no active connections'
May 16 21:50:12 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 8989: Found no active connections'
May 16 21:50:12 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 9000: Found no active connections'
May 16 21:50:12 server autoshutdown[538955]: root: INFO: 'FAKE-Mode: _check_net_status(): Found 0 active socket(s) from port(s): 22,80,81,90,7878,8000,8096,8920,8989,9000'
May 16 21:50:12 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: __run_check(): Calling: _check_container_status()'
May 16 21:50:12 server autoshutdown[538955]: root: INFO: 'FAKE-Mode: _check_container_status(): Check status of container engine: docker'
May 16 21:50:13 server autoshutdown[548643]: Error: an inet prefix is expected rather than "90:80".
May 16 21:50:13 server autoshutdown[548643]: Cannot parse dst/src address.
May 16 21:50:13 server autoshutdown[548654]: Error: an inet prefix is expected rather than "8989:8989".
May 16 21:50:13 server autoshutdown[548654]: Cannot parse dst/src address.
May 16 21:50:13 server autoshutdown[548666]: Error: an inet prefix is expected rather than "7878:7878".
May 16 21:50:13 server autoshutdown[548666]: Cannot parse dst/src address.
May 16 21:50:13 server autoshutdown[548677]: Error: an inet prefix is expected rather than "8096:8096".
May 16 21:50:13 server autoshutdown[548677]: Cannot parse dst/src address.
May 16 21:50:13 server autoshutdown[538955]: root: INFO: 'FAKE-Mode: _check_container_status(): Found 0 active socket(s) from port(s): 22,80,81,90,7878,8000,8096,8920,8989,9000'
May 16 21:50:13 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: __run_check(): Calling: _check_container_status()'
May 16 21:50:13 server autoshutdown[538955]: root: DEBUG: 'FAKE-Mode: __run_check(): Calling: _check_users_status()'
May 16 21:50:13 server autoshutdown[538955]: root: INFO: 'FAKE-Mode: _check_users_status(): There are no users connected -> next check'

Display More

funnybones24 · May 17th 2022

Found the issue.

It was because the stack was creating a new network automatically as i didnt specify one in the docker compose. because of this it wasnt finding the ip address of the container in the newly created bridge network as it was looking in .NetworkSettings.IPAddress of the docker container inspect result but in the generated one this value was blank and the ip address was not blank in .NetworkSettings.Networks.{name of generated network}.IPAddress.

The solution was to change the containers to use the default bridge network or add network_mode: bridge to the service in the docker compose file.

I assume creating a network manually will not have this value empty and is an issue just with the automatically generated network.

Heres what it looks like in the logs with port 8096 and 9000 in use and 8989 not in use all on the default bridge network

Code

May 16 23:37:42 server autoshutdown[615657]: root: INFO: 'FAKE-Mode: main(): New supervision cycle started, checking system activity'
May 16 23:37:42 server autoshutdown[615657]: root: DEBUG: 'FAKE-Mode: __run_check(): Calling: _check_net_status()'
May 16 23:37:42 server autoshutdown[615657]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 90: Found no active connections'
May 16 23:37:42 server autoshutdown[615657]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 7878: Found no active connections'
May 16 23:37:42 server autoshutdown[615657]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 8096: Found no active connections'
May 16 23:37:42 server autoshutdown[615657]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 8989: Found no active connections'
May 16 23:37:42 server autoshutdown[615657]: root: DEBUG: 'FAKE-Mode: _check_net_status(): Port 9000: Found no active connections'
May 16 23:37:42 server autoshutdown[615657]: root: INFO: 'FAKE-Mode: _check_net_status(): Found 0 active socket(s) from port(s): 90,7878,8096,8989,9000'
May 16 23:37:42 server autoshutdown[615657]: root: DEBUG: 'FAKE-Mode: __run_check(): Calling: _check_container_status()'
May 16 23:37:42 server autoshutdown[615657]: root: INFO: 'FAKE-Mode: _check_container_status(): Check status of container engine: docker'
May 16 23:37:43 server autoshutdown[615657]: root: INFO: 'FAKE-Mode: _check_container_status(): Found 5 active connection(s) on port 8096 (jellyfin) from: 192.168.1.16'
May 16 23:37:43 server autoshutdown[619691]: Error: an inet prefix is expected rather than "7878:7878".
May 16 23:37:43 server autoshutdown[619691]: Cannot parse dst/src address.
May 16 23:37:43 server autoshutdown[619704]: Error: an inet prefix is expected rather than "90:80".
May 16 23:37:43 server autoshutdown[619704]: Cannot parse dst/src address.
May 16 23:37:44 server autoshutdown[615657]: root: INFO: 'FAKE-Mode: _check_container_status(): Found 2 active connection(s) on port 9000 (portainer) from: 192.168.1.16'
May 16 23:37:44 server autoshutdown[615657]: root: INFO: 'FAKE-Mode: _check_container_status(): Found 7 active socket(s) from port(s): 90,7878,8096,8989,9000'
May 16 23:37:44 server autoshutdown[615657]: root: INFO: 'FAKE-Mode: main(): Active check failed, 5 cycles until shutdown ...'
May 16 23:37:44 server autoshutdown[615657]: root: INFO: 'FAKE-Mode: main(): Sleep for 60s'

Display More

Participate now!