autoshutdown shuts down OMV even though client is still active

I have autoshutdown installed and active. It used to work fine, up to a point where it started to shut down OMV even though the client PC ist still active.

What kind of info is required ? Who can help me.

Here is part of my log:

Zitat

Oct 19 20:48:16 openmediavault logger: autoshutdown[10027]: INFO: '------------------------------------------------------'
Oct 19 20:48:16 openmediavault logger: autoshutdown[10027]: INFO: ' new supervision cycle started - check active hosts or processes'
Oct 19 20:48:16 openmediavault logger: autoshutdown[10027]: INFO: ' retrieve list of active IPs for 'eth0' ...'
Oct 19 20:48:17 openmediavault logger: autoshutdown[10027]: INFO: ' No active IPs in the specified IP-Range found'
Oct 19 20:48:17 openmediavault logger: autoshutdown[10027]: INFO: ' Check Connections for 'eth0''
Oct 19 20:48:17 openmediavault logger: autoshutdown[10027]: INFO: ' _check_net_status(): Found active connection on port 80 (HTTP) from ::ffff:192.168.2.60'
Oct 19 20:48:17 openmediavault logger: autoshutdown[10027]: INFO: ' Found 1 active socket(s) from Port(s): 21,22,80,139,445,3689,6991,9091,49152'
Oct 19 20:48:17 openmediavault logger: autoshutdown[10027]: INFO: ' sleep for 60s.'

Alles anzeigen

What suprises me is marked line, as I'm checking for my client computer with this line: IP-BEREICH: 60..69
and my client PC has an IP of 192.168.2.60, so it should be found.

Hi david, Servus Solo !

I did enable debug mode and it's a whole lot of data. But , in my opinion, the important line resurfaces over and over again:

Zitat

Oct 19 20:48:16 openmediavault logger: autoshutdown[10027]: INFO: '------------------------------------------------------'
Oct 19 20:48:16 openmediavault logger: autoshutdown[10027]: INFO: ' new supervision cycle started - check active hosts or processes'
Oct 19 20:48:16 openmediavault logger: autoshutdown[10027]: INFO: ' retrieve list of active IPs for 'eth0' ...'
Oct 19 20:48:17 openmediavault logger: autoshutdown[10027]: INFO: ' No active IPs in the specified IP-Range found'
Oct 19 20:48:17 openmediavault logger: autoshutdown[10027]: INFO: ' Check Connections for 'eth0''
Oct 19 20:48:17 openmediavault logger: autoshutdown[10027]: INFO: ' _check_net_status(): Found active connection on port 80 (HTTP) from ::ffff:192.168.2.60'
Oct 19 20:48:17 openmediavault logger: autoshutdown[10027]: INFO: ' Found 1 active socket(s) from Port(s): 21,22,80,139,445,3689,6991,9091,49152'
Oct 19 20:48:17 openmediavault logger: autoshutdown[10027]: INFO: ' sleep for 60s.'

Alles anzeigen

As I said, I did include IP-Range from 60..69 . OMV autoshutdown does see my client, when port 80 is in use, but it does not see the IP alone.
I guess port 80 is used for OMV webadmin. So as long as I am locked into OMV via webadmin, OMV stays alive, but as soon as I disconnect webadmin / close my browser, OMV will shut down.
I would like to show you two my autoshutdown settings:

Zitat

root@openmediavault:~# cat /etc/autoshutdown.conf
# This configuration file is auto-generated.
# WARNING: Do not edit this file, your changes will be lost.
ENABLE="true"
CYCLES=5
SLEEP=60
RANGE="60..69"
SHUTDOWNCOMMAND="pm-hibernate"
CHECKCLOCKACTIVE="false"
UPHOURS="6..20"
NSOCKETNUMBERS="21,22,80,139,445,3689,6991,9091,49152"
ULDLCHECK="false"
ULDLRATE=50
LOADAVERAGECHECK="true"
LOADAVERAGE=40
HDDIOCHECK="false"
HDDIO_RATE=0
SYSLOG="true"
VERBOSE="false"
FAKE="false"

Alles anzeigen

Zitat

your log ID is: jIdqotoC, please refer to this log ID in your posts.

this is my log-file from within OMV. But it's a complete one, not specific to autoshutdown. I could not create a autoshutdown specific log-file with auto upload. I do have it though as .zip file. Just tell me where to put it.

Zitat

root@openmediavault:~# ping -c 4 192.168.2.60
PING 192.168.2.60 (192.168.2.60) 56(84) bytes of data.

--- 192.168.2.60 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3023ms

Zitat

root@openmediavault:~# ping -c 4 192.168.2.60
PING 192.168.2.60 (192.168.2.60) 56(84) bytes of data.
64 bytes from 192.168.2.60: icmp_req=1 ttl=128 time=0.345 ms
64 bytes from 192.168.2.60: icmp_req=2 ttl=128 time=0.360 ms
64 bytes from 192.168.2.60: icmp_req=3 ttl=128 time=0.341 ms
64 bytes from 192.168.2.60: icmp_req=4 ttl=128 time=0.244 ms

--- 192.168.2.60 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 0.244/0.322/0.360/0.049 ms

Alles anzeigen

I had unknowingly two firewalls active: Windows Firewall and Bitdefender Firewall.
Bidefender had the right settings to approve a ping call but Windows Firawall did not.
So I turned of Windows Firewall and there you go: ping works fine!
I think that fixed it. If so I will mark threat as solved in about 30 min.

Zitat

Oct 21 21:57:25 openmediavault logger: autoshutdown[4519]: INFO: ' new supervision cycle started - check active hosts or processes'
Oct 21 21:57:25 openmediavault logger: autoshutdown[4519]: INFO: ' retrieve list of active IPs for 'eth0' ...'
Oct 21 21:57:27 openmediavault logger: autoshutdown[4519]: INFO: ' Found IP 192.168.2.60 as active host.'
Oct 21 21:57:27 openmediavault logger: autoshutdown[4519]: INFO: ' sleep for 60s.'
Oct 21 21:58:27 openmediavault logger: autoshutdown[4519]: INFO: '------------------------------------------------------'
Oct 21 21:58:27 openmediavault logger: autoshutdown[4519]: INFO: ' new supervision cycle started - check active hosts or processes'
Oct 21 21:58:27 openmediavault logger: autoshutdown[4519]: INFO: ' retrieve list of active IPs for 'eth0' ...'
Oct 21 21:58:28 openmediavault logger: autoshutdown[4519]: INFO: ' Found IP 192.168.2.60 as active host.'
Oct 21 21:58:28 openmediavault logger: autoshutdown[4519]: INFO: ' sleep for 60s.'

Alles anzeigen

Yes, that was it !
Thank You Solo0815, I would never have doubble checked on the firewalls, because that was where I first looked and switching off Bitdefender Firewall did not help in the least!
No wonder when Windows Firewall was up as well !