Beiträge von yarvv

    Hi all!

    I`m using RAID5 on 6 drives. 2 connected to motherboard SATA ports and 4 - to SATA (non-raid) controller. All drives are OK (SMART, surface scanning, etc) but 2 drives connected to MB SATA are failed several times cause RAID degrade. Every time deleting drive and rebuilding RAID is OK. I think some hardware problems exists with MB ports or in case this mixed connection.


    I`m planning to replace SATA controller with more SATA ports and to connect all RAID drives directly to new controller.


    Is it safe operation?

    Will be RAID re-assebled automatically with changed devices ID or I need to assemble it manually with config files manipulation?

    You probably have a proxy set or your network is causing the issue.

    It seems problem found!


    Internet provider blocks network resources very selective. No problems accessing github repos via browser, but OMV-s connections don`t works or unstable.

    Using HTTP proxy (external) it was possible to establish a stable connection to repos and repair half-installed and failed packets.

    as promised...


    1. Installing OMV from DVD (+ administration settings - certificate, password etc) - it`s OK

    2. No updates installing, no plugins installing, checking updates - it`s OK

    3. Turn on "Community-maintained updates." (off by defaut), save, check updates - "Could not handshake" and "no Release file"

    4. Turn off "Community-maintained updates.", reset, save, check updates - "Could not handshake" and "no Release file"

    5. Turn off "Community-maintained updates.", reset SEVERAL TIMES, check updates - it`s OK (may be timeout exists)

    6. Install OMV-Extras via terminal - "Could not handshake" and "no Release file", but OMV-Extras presents in Plugins

    7. Trying to add Extras plugin repo - unsuccesfull, "Could not handshake" and "no Release file", only way to revert config

    8. While OMV-Extras is added, OMV-FIRSTAID don`t works (!) - see output

    9. After uninstall OMV-Extras via web-admin - OMV-FIRSTAID is OK

    10. The probability of successfully updates (or plugins) checking after this config manipulations about 5-10%


    I remember - it was NEW fresh installation


    Something wrong with new repos!

    The story was continued...


    I shut down computer, change system SSD, plug-out all RADI5 drives and make fresh install fom actual iso-distributive.


    1. Installing OMV from DVD (+ administration settings - certificate, password etc) - it`s OK

    2. Installing OMV-Extras plug-in - it`s OK

    3. Checking and installing all available updates - Installation finished with errors and the same error appears with "Could not handshake" and "no Release file"


    I will try to investigate what update causing error (Fresh install again and install updates one-by-one) and inform in next post

    If the system time is correct, I don't know what else could be causing this. I would make sure ntp (chrony) is running and maybe try the apt-clean button in omv-extras.

    Time is correct. Apt-clean I tried at first - no result. I will try to restore system from backup (january 2021, but exist at least) and change repos again or make new installation and re-mount RAID5 volume.


    Thanks!

    I assure you that those repos have a Release files - https://github.com/OpenMediaVa…debian/dists/usul/Release and https://download.docker.com/li…bian/dists/buster/Release. Make sure the time on your system is correct. Disable the testing and extras repos as well. There is nothing in them. And I don't know where you are located but github is blocked in China. Probably some other places as well.

    I`m in Moscow, Russia. No problems accessing repos links via browser (other computer, but the same LAN, same router, same outgoing IP). I trying to disable all repos by OMV web-admin, but save config changes caused the same errors, and only way - to roll-back (revert) config (see screemshot).



    "Could not handshake: Error in the pull function" - may be somewhat with certificates or keys

    This is my home LAN. No proxy configured on OMV and no proxy exist on network, only router with NAT. Also no ACL, no packet filtering etc.


    E-mail notification text:


    Hi!

    Need some assistance.

    After repos moving to github my OMV fails to update.


     dpkg -l|grep -i openmedia  output (may be useful):

    sudo salt-call -l debug --local --retcode-passthrough state.apply omv.deploy.omvextras output - see attach:


    debug output.txt

    Possibly errors in debug output:


    Err:18 https://openmediavault.github.io/packages usul Release

    Could not handshake: Error in the pull function. [IP: 185.199.108.153 443]

    Ign:19 https://openmediavault-plugin-…github.io/packages/debian usul-extras InRelease

    Err:20 https://openmediavault.github.io/packages usul-proposed Release

    Could not handshake: Error in the pull function. [IP: 185.199.108.153 443]

    Err:21 https://openmediavault-plugin-…github.io/packages/debian usul Release

    Could not handshake: Error in the pull function. [IP: 185.199.108.153 443]

    Err:22 https://openmediavault-plugin-…github.io/packages/debian usul-testing Release

    Could not handshake: Error in the pull function. [IP: 185.199.108.153 443]

    Err:23 https://openmediavault-plugin-…github.io/packages/debian usul-extras Release

    Could not handshake: Error in the pull function. [IP: 185.199.108.153 443]


    How can I repair updates?

    votdev could you please have a look to validate the suspected root cause " "monit" service checks proftpd`s state every 30 sec and cause this error"?

    Deep inspection configs and logs!


    1 - Simulating problem re-enabling port 21 check in monit config...


    Time in logs is corresponding


    every 30 sec monit detects error and restarts proftpd


    /var/log/syslog:


    Jan 9 20:01:09 slavaya-omv monit[27662]: Monit daemon with pid [27662] stopped

    Jan 9 20:01:09 slavaya-omv monit[27662]: '\slavaya-omv.local' Monit 5.26.0 stopped

    Jan 9 20:01:09 slavaya-omv monit[10898]: Stopping daemon monitor: monit.

    Jan 9 20:01:09 slavaya-omv systemd[1]: monit.service: Succeeded.

    Jan 9 20:01:09 slavaya-omv systemd[1]: Stopped LSB: service and resource monitoring daemon.

    Jan 9 20:01:29 slavaya-omv systemd[1]: Starting LSB: service and resource monitoring daemon...

    Jan 9 20:01:29 slavaya-omv monit[10990]: Starting Monit 5.26.0 daemon with http interface at /run/monit.sock

    Jan 9 20:01:29 slavaya-omv monit[10987]: Starting daemon monitor: monit.

    Jan 9 20:01:29 slavaya-omv systemd[1]: Started LSB: service and resource monitoring daemon.

    Jan 9 20:01:29 slavaya-omv monit[10992]: '\slavaya-omv.local' Monit 5.26.0 started

    Jan 9 20:01:34 slavaya-omv monit[10992]: 'proftpd' failed protocol test [FTP] at [localhost]:21 [TCP/IP] -- FTP: error receiving data -- Resource temporarily unavailable

    Jan 9 20:01:34 slavaya-omv proftpd[10994]: 192.168.254.112 (127.0.0.1[127.0.0.1]) - mod_tls.c: error initializing session: Отказано в доступе

    Jan 9 20:02:09 slavaya-omv monit[10992]: 'proftpd' failed protocol test [FTP] at [localhost]:21 [TCP/IP] -- FTP: error receiving data -- Resource temporarily unavailable

    Jan 9 20:02:09 slavaya-omv proftpd[11049]: 192.168.254.112 (127.0.0.1[127.0.0.1]) - mod_tls.c: error initializing session: Отказано в доступе

    Jan 9 20:02:45 slavaya-omv monit[10992]: 'proftpd' failed protocol test [FTP] at [localhost]:21 [TCP/IP] -- FTP: error receiving data -- Resource temporarily unavailable

    Jan 9 20:02:45 slavaya-omv monit[10992]: 'proftpd' trying to restart

    Jan 9 20:02:45 slavaya-omv monit[10992]: 'proftpd' stop: '/etc/init.d/proftpd stop'

    Jan 9 20:02:45 slavaya-omv proftpd[11103]: 192.168.254.112 (127.0.0.1[127.0.0.1]) - mod_tls.c: error initializing session: Отказано в доступе

    Jan 9 20:02:45 slavaya-omv systemd[1]: Stopping LSB: Starts ProFTPD daemon...

    Jan 9 20:02:45 slavaya-omv proftpd[31802]: 192.168.254.112 - ProFTPD killed (signal 15)

    Jan 9 20:02:45 slavaya-omv proftpd[31802]: 192.168.254.112 - ProFTPD 1.3.6 standalone mode SHUTDOWN

    Jan 9 20:02:45 slavaya-omv proftpd[11121]: Stopping ftp server: proftpd.

    Jan 9 20:02:45 slavaya-omv systemd[1]: proftpd.service: Succeeded.

    Jan 9 20:02:45 slavaya-omv systemd[1]: Stopped LSB: Starts ProFTPD daemon.

    Jan 9 20:02:45 slavaya-omv monit[10992]: 'proftpd' start: '/etc/init.d/proftpd restart'

    Jan 9 20:02:45 slavaya-omv systemd[1]: Starting LSB: Starts ProFTPD daemon...

    Jan 9 20:02:45 slavaya-omv proftpd[11150]: 192.168.254.112 - ProFTPD 1.3.6 (stable) (built Tue Mar 10 2020 23:03:08 UTC) standalone mode STARTUP

    Jan 9 20:02:45 slavaya-omv proftpd[11140]: Starting ftp server: proftpd.

    Jan 9 20:02:45 slavaya-omv systemd[1]: Started LSB: Starts ProFTPD daemon.

    Jan 9 20:03:21 slavaya-omv monit[10992]: 'proftpd' failed protocol test [FTP] at [localhost]:21 [TCP/IP] -- FTP: error receiving data -- Resource temporarily unavailable

    Jan 9 20:03:21 slavaya-omv monit[10992]: 'proftpd' trying to restart

    Jan 9 20:03:21 slavaya-omv monit[10992]: 'proftpd' stop: '/etc/init.d/proftpd stop'

    Jan 9 20:03:21 slavaya-omv proftpd[11196]: 192.168.254.112 (127.0.0.1[127.0.0.1]) - mod_tls.c: error initializing session: Отказано в доступе

    Jan 9 20:03:21 slavaya-omv systemd[1]: Stopping LSB: Starts ProFTPD daemon...

    Jan 9 20:03:21 slavaya-omv proftpd[11150]: 192.168.254.112 - ProFTPD killed (signal 15)

    Jan 9 20:03:21 slavaya-omv proftpd[11150]: 192.168.254.112 - ProFTPD 1.3.6 standalone mode SHUTDOWN

    Jan 9 20:03:21 slavaya-omv proftpd[11214]: Stopping ftp server: proftpd.

    Jan 9 20:03:21 slavaya-omv systemd[1]: proftpd.service: Succeeded.

    Jan 9 20:03:21 slavaya-omv systemd[1]: Stopped LSB: Starts ProFTPD daemon.

    Jan 9 20:03:21 slavaya-omv monit[10992]: 'proftpd' start: '/etc/init.d/proftpd restart'

    Jan 9 20:03:21 slavaya-omv systemd[1]: Starting LSB: Starts ProFTPD daemon...

    Jan 9 20:03:21 slavaya-omv proftpd[11242]: 192.168.254.112 - ProFTPD 1.3.6 (stable) (built Tue Mar 10 2020 23:03:08 UTC) standalone mode STARTUP

    Jan 9 20:03:21 slavaya-omv proftpd[11234]: Starting ftp server: proftpd.

    Jan 9 20:03:21 slavaya-omv systemd[1]: Started LSB: Starts ProFTPD daemon.

    Jan 9 20:03:57 slavaya-omv monit[10992]: 'proftpd' failed protocol test [FTP] at [localhost]:21 [TCP/IP] -- FTP: error receiving data -- Resource temporarily unavailable

    Jan 9 20:03:57 slavaya-omv monit[10992]: 'proftpd' trying to restart

    Jan 9 20:03:57 slavaya-omv monit[10992]: 'proftpd' stop: '/etc/init.d/proftpd stop'

    Jan 9 20:03:57 slavaya-omv proftpd[11289]: 192.168.254.112 (127.0.0.1[127.0.0.1]) - mod_tls.c: error initializing session: Отказано в доступе

    Jan 9 20:03:57 slavaya-omv systemd[1]: Stopping LSB: Starts ProFTPD daemon...

    Jan 9 20:03:57 slavaya-omv proftpd[11242]: 192.168.254.112 - ProFTPD killed (signal 15)

    Jan 9 20:03:57 slavaya-omv proftpd[11242]: 192.168.254.112 - ProFTPD 1.3.6 standalone mode SHUTDOWN

    Jan 9 20:03:57 slavaya-omv proftpd[11307]: Stopping ftp server: proftpd.

    Jan 9 20:03:57 slavaya-omv systemd[1]: proftpd.service: Succeeded.

    Jan 9 20:03:57 slavaya-omv systemd[1]: Stopped LSB: Starts ProFTPD daemon.

    Jan 9 20:03:57 slavaya-omv monit[10992]: 'proftpd' start: '/etc/init.d/proftpd restart'

    Jan 9 20:03:57 slavaya-omv systemd[1]: Starting LSB: Starts ProFTPD daemon...

    Jan 9 20:03:57 slavaya-omv proftpd[11334]: 192.168.254.112 - ProFTPD 1.3.6 (stable) (built Tue Mar 10 2020 23:03:08 UTC) standalone mode STARTUP

    Jan 9 20:03:57 slavaya-omv proftpd[11326]: Starting ftp server: proftpd.

    Jan 9 20:03:57 slavaya-omv systemd[1]: Started LSB: Starts ProFTPD daemon.

    Jan 9 20:04:33 slavaya-omv monit[10992]: 'proftpd' failed protocol test [FTP] at [localhost]:21 [TCP/IP] -- FTP: error receiving data -- Resource temporarily unavailable

    Jan 9 20:04:33 slavaya-omv monit[10992]: 'proftpd' trying to restart

    Jan 9 20:04:33 slavaya-omv monit[10992]: 'proftpd' stop: '/etc/init.d/proftpd stop'

    Jan 9 20:04:33 slavaya-omv proftpd[11381]: 192.168.254.112 (127.0.0.1[127.0.0.1]) - mod_tls.c: error initializing session: Отказано в доступе

    Jan 9 20:04:33 slavaya-omv systemd[1]: Stopping LSB: Starts ProFTPD daemon.......


    see attach - 10000 char limit

    The same problem!


    FTP service is ON, TLS/SSL is ON, TLS/SSL is required, passive mode ON, no masqerade


    Deep investigation results:

    1 - proftpd binded on port 21 or the any other - no effect, error exist

    2 - only if "Implicit SSL" in SSL/TLS settings is ON error exist, but without this parameter not works my FTPS uploads by CURL (?)

    3 - "monit" service checks proftpd`s state every 30 sec and cause this error


    /var/log/proftpd/tls.log fragment:

    ......

    >>2021-01-08 23:00:06,612 mod_tls/2.7[30134]: TLSOption UseImplicitSSL in effect, starting SSL/TLS handshake

    >>2021-01-08 23:00:11,613 mod_tls/2.7[30134]: unable to accept TLS connection: system call error: [0] Выполнено


    4 - if disable port check in "monit" config, all works fine


    /etc/monit/conf.d/openmediavault-proftpd.conf string:

    .....

    >> # if failed port 21 protocol ftp for 3 cycles then restart


    It is no true solution, but is acceptable in this moment