open Port 22 prevents Autoshutdown Plugin from doing its work

  • Hi!


    I´m on a fresh installation of OMV 3.0.59.


    Now the autoshutdown plugin doesn´t work on this fresh installation (never had problem with this in the past)


    The protocol says that there is a connection from my server on SSH Port 22 but i´ve no clue what process this might be and i neither set the plugin to check that port.


    Does some1 have a conclusion for this?


    Thx in advance!

  • Hi,


    can you post a screenshot of your autoshutdown config and the log file?


    Maybe I can help you.

    OMV 6.x with bpo Kernel running on:
    Board: ASRock H410M-ITX and Intel Pentium G6400T
    RAM: 16GB DDR4-3000 Corsair
    Case: Coolermaster Elite 120 Advanced
    HDD: 1x 250GB NVME SSD Transcend and 2x 6TB 3.5" Seagate IronWolf ST6000VN001 + 1x 4TB 3.5" Seagate ST40000VN008

  • OK, I didn't knew that... ^^


    I think Port 22 is set by default with a few other ports. Port 22 is used for SSH connection. If you where connected through putty or some other terminal app, this might be the reason your machine won't shutdown.

    OMV 6.x with bpo Kernel running on:
    Board: ASRock H410M-ITX and Intel Pentium G6400T
    RAM: 16GB DDR4-3000 Corsair
    Case: Coolermaster Elite 120 Advanced
    HDD: 1x 250GB NVME SSD Transcend and 2x 6TB 3.5" Seagate IronWolf ST6000VN001 + 1x 4TB 3.5" Seagate ST40000VN008

  • And that's the problem.


    The Logfile says there is a connection on SSH Port 22 but I am not connected and the plugin isn't configured to monitor that port neither.


    Gesendet von meinem LG-D855 mit Tapatalk

    • Offizieller Beitrag

    What is the output of: ss -n | grep ESTAB

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • You could try to list all connected users by


    who -a


    or list all established ssh connections with


    netstat -tnpa | grep 'ESTABLISHED.*sshd' I'm guessing you're from Germany, so you can replace "ESTABLISHED" with VERBUNDEN ;)

    OMV 6.x with bpo Kernel running on:
    Board: ASRock H410M-ITX and Intel Pentium G6400T
    RAM: 16GB DDR4-3000 Corsair
    Case: Coolermaster Elite 120 Advanced
    HDD: 1x 250GB NVME SSD Transcend and 2x 6TB 3.5" Seagate IronWolf ST6000VN001 + 1x 4TB 3.5" Seagate ST40000VN008

    • Offizieller Beitrag

    The script itself uses the command I asked for but I don't think it is the best way to do it. Especially if the system is using a different language. Personally, I think the autoshutdown script needs to be re-written and in a different language like python. Unfortunately, I don't have time and don't use this plugin.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!


  • Ok


    I'll try that in the evening :)


    Gesendet von meinem LG-D855 mit Tapatalk

  • so here is my config....



    and here is a actual logfile wigh ghosting connection on port 22 which is not configured


  • Thanks for that.


    Do you know what device in your network have the IP 192.168.178.28?


    Did you copy your OMV config from a previous installation?

    OMV 6.x with bpo Kernel running on:
    Board: ASRock H410M-ITX and Intel Pentium G6400T
    RAM: 16GB DDR4-3000 Corsair
    Case: Coolermaster Elite 120 Advanced
    HDD: 1x 250GB NVME SSD Transcend and 2x 6TB 3.5" Seagate IronWolf ST6000VN001 + 1x 4TB 3.5" Seagate ST40000VN008

  • Sounds really strange.... ?(


    Why should your system establish an SSH connection to somwhere else....


    Have you tried editing the port settings for the autoshutdown plugin in the webgui? Try adding a value -> save -> deleting the value -> saving again....
    Maybe the cofig was not saved correct.

    OMV 6.x with bpo Kernel running on:
    Board: ASRock H410M-ITX and Intel Pentium G6400T
    RAM: 16GB DDR4-3000 Corsair
    Case: Coolermaster Elite 120 Advanced
    HDD: 1x 250GB NVME SSD Transcend and 2x 6TB 3.5" Seagate IronWolf ST6000VN001 + 1x 4TB 3.5" Seagate ST40000VN008

  • I got it now - it was my fault :P


    You have to define at least on port that the plugin checks for activity and it seems like i´ve missed to configure this for the first time....


    i´ve entered http port 80 now and everything works as it should :)

  • Hallo zusammen,


    ich habe dasselbe Problem. Was kann ich tun damit das Plugin wieder das NAS runterfährt?
    Hier mein Log


    [spoiler
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
    Feb 4 15:20:48 openmediavault autoshutdown.sh[1175]: logger: autoshutdown[1175]: INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
    Feb 4 15:20:48 openmediavault autoshutdown.sh[1175]: logger: autoshutdown[1175]: INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
    Feb 4 15:20:48 openmediavault autoshutdown.sh[1175]: logger: autoshutdown[1175]: INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
    Feb 4 15:20:48 openmediavault autoshutdown.sh[1175]: logger: autoshutdown[1175]: INFO: ' X Version: 0.9.9.10'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' X Version: 0.9.9.10'
    Feb 4 15:20:48 openmediavault autoshutdown.sh[1175]: logger: autoshutdown[1175]: INFO: ' Initialize logging to local6'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' Initialize logging to local6'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' /etc/autoshutdown.conf loaded'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' ------------------------------------------------------'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' Checking config'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' LOADPROCNAMES is set to: 'smbd,nfsd,transmission-daemon,mt-daapd,forked-daapd' (default)'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' TEMPPROCNAMES is disabled - No processes being checked'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: WARN: ' Invalid parameter list format: NSOCKETNUMBERS [nsocket1,nsocket2,nsocket3,...]'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: WARN: ' You set it to '', which is not a correct syntax. Maybe it's empty? Only Port-Numbers with at least 2 digits are allowed.'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: WARN: ' Setting NSOCKETNUMBERS to 21,22 (FTP and SSH)'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' SHUTDOWNCOMMAND is set to 'pm-suspend''
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' Your Kernel supports the following modes from pm-utils:'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' Kernel supports SUSPEND (SUSPEND to RAM)'
    Feb 4 15:20:48 openmediavault logger: autoshutdown[1175]: INFO: ' Kernel supports HIBERNATE (SUSPEND to DISK)'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: INFO: ' Kernel supports HYBRID-SUSPEND (to DISK & to RAM)'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: WARN: ' LOADAVERAGECHECK is set to false'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: WARN: ' Ignoring LOADAVERAGE'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: INFO: ' ------------------------------------------------------'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: INFO: ' Reading NICs ,IPs, ...'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: INFO: ' NIC 'bond0' not found, skipping 'bond0''
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: INFO: ' NIC 'eth0' not found, skipping 'eth0''
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: INFO: ' NIC 'eth1' found: try to get IP'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: INFO: ' _check_networkconfig(): Run: #1: IP-Adress found'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: INFO: ' 'eth1' has IP: 192.168.10.32'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: INFO: ' /tmp/autoshutdown created'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: INFO: '---------------- script started ----------------------'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: INFO: ' 2 test cycles until shutdown is issued.'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: DEBUG: ' _check_ul_dl_rate(): /tmp/autoshutdown/txrx created successfully'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: DEBUG: ' _check_hddio(): /tmp/autoshutdown/hddio created successfully'
    Feb 4 15:20:49 openmediavault logger: autoshutdown[1175]: INFO: ' Waiting 5 min until the first check'
    Feb 4 15:25:49 openmediavault logger: autoshutdown[1175]: INFO: ' script is doing checks for NIC: eth1 - 192.168.10.32'
    Feb 4 15:25:49 openmediavault logger: autoshutdown[1175]: INFO: '------------------------------------------------------'
    Feb 4 15:25:49 openmediavault logger: autoshutdown[1175]: INFO: ' new supervision cycle started - check active hosts or processes'
    Feb 4 15:25:49 openmediavault logger: autoshutdown[1175]: INFO: ' retrieve list of active IPs for 'eth1' ...'
    Feb 4 15:25:49 openmediavault logger: autoshutdown[1175]: INFO: ' PINGLIST: /tmp/autoshutdown/pinglist does not exist. Skip fpinging hosts'
    Feb 4 15:25:49 openmediavault logger: autoshutdown[1175]: INFO: ' No active IPs in the specified IP-Range found'
    Feb 4 15:25:49 openmediavault logger: autoshutdown[1175]: INFO: ' Check Connections for 'eth1''
    Feb 4 15:25:49 openmediavault logger: autoshutdown[1175]: INFO: ' _check_net_status(): Found active connection on port 22 (SSH) from 192.168.10.32'
    Feb 4 15:25:49 openmediavault logger: autoshutdown[1175]: INFO: ' Found 1 active socket(s) from Port(s): 22'
    Feb 4 15:25:49 openmediavault logger: autoshutdown[1175]: INFO: ' sleep for 300s.'
    Feb 4 15:30:49 openmediavault logger: autoshutdown[1175]: INFO: '------------------------------------------------------'
    Feb 4 15:30:49 openmediavault logger: autoshutdown[1175]: INFO: ' new supervision cycle started - check active hosts or processes'
    Feb 4 15:30:49 openmediavault logger: autoshutdown[1175]: INFO: ' retrieve list of active IPs for 'eth1' ...'
    Feb 4 15:30:49 openmediavault logger: autoshutdown[1175]: INFO: ' PINGLIST: /tmp/autoshutdown/pinglist does not exist. Skip fpinging hosts'
    Feb 4 15:30:49 openmediavault logger: autoshutdown[1175]: INFO: ' No active IPs in the specified IP-Range found'
    Feb 4 15:30:49 openmediavault logger: autoshutdown[1175]: INFO: ' Check Connections for 'eth1''
    Feb 4 15:30:49 openmediavault logger: autoshutdown[1175]: INFO: ' _check_net_status(): Found active connection on port 22 (SSH) from 192.168.10.32'
    Feb 4 15:30:49 openmediavault logger: autoshutdown[1175]: INFO: ' Found 1 active socket(s) from Port(s): 22'
    Feb 4 15:30:49 openmediavault logger: autoshutdown[1175]: INFO: ' sleep for 300s.'
    ][/spoiler]


    Ich habe auf meinem Laptop cygwin installiert zum rsync. Kann es sein das dies der Grund ist? Im Plugin habe ich aber alle Sockets und IP-Bereich leer gelassen.
    Wo liegt der Fehler? OMV habe ich neu installiert!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!