Upgrade issues OMV 3.x -> 4.x .... some issues

Michelle_Br · 14. Mai 2020

root@server:~# /usr/bin/fail2ban-client -x start

ERROR Found no accessible config files for 'fail2ban' under /etc/fail2ban

ERROR No section: 'Definition'

ERROR Found no accessible config files for 'filter.d/sshd-ddos' under /etc/fail2ban

ERROR No section: 'Definition'

ERROR Unable to read the filter

ERROR Errors in jail 'ssh-ddos'. Skipping...

Hi everybody *smiling

At first - my English is not so good and so i hope, you can understand me. My mother´s language is German.

I´ve posted my case here

Upgrade OMV 3.0 -> OMV 4.x

I´m not so experienced with Linux. A longer time i had fear to do the upgrade procedure. But now OMV 5.x is out and i had fear, that there will be no more upgrade possibility from 3.x to 4.x in the nearest future and i´ll have to do a new installation.

So i dared now - but there were some issues i´ve posted @Technikaffe.de

Some issues i could solve with the friends over there - but some issues are actual:

If i open the GUI there is "Arrakis" v4.1.35-1 installed.

I had the "php-5" - issue and a lot of mails from my server every day was sent about that. I found, that "apt-get pure "php5*" should solve that.

"dpkg -l | grep php" now shows me:

Code

root@server:~# dpkg -l | grep php
ii  libapache2-mod-php7.0                                       7.0.33-0+deb9u7                   amd64        server-side, HTML-embedded scripting language (Apache 2 module)
ii  php                                                         1:7.0+49                          all          server-side, HTML-embedded scripting language (default)
ii  php-bcmath                                                  1:7.0+49                          all          Bcmath module for PHP [default]
ii  php-cgi                                                     1:7.0+49                          all          server-side, HTML-embedded scripting language (CGI binary) (default)
ii  php-common                                                  1:49                              all          Common files for PHP packages
ii  php-fpm                                                     1:7.0+49                          all          server-side, HTML-embedded scripting language (FPM-CGI binary) (default)
ii  php-mbstring                                                1:7.0+49                          all          MBSTRING module for PHP [default]
ii  php-pam                                                     1.0.3-1                           amd64        pam module for PHP 7
ii  php-sabre-dav                                               1.8.12-3                          all          WebDAV Framework for PHP
ii  php-sabre-vobject                                           2.1.7-3                           all          library to parse and manipulate iCalendar and vCard objects
ii  php-symfony-class-loader                                    2.8.7+dfsg-1.3+deb9u3             all          load PHP classes automatically
ii  php-symfony-polyfill-apcu                                   1.2.0-1                           all          Symfony polyfill backporting apcu_* functions to lower PHP versions
ii  php-xml                                                     1:7.0+49                          all          DOM, SimpleXML, WDDX, XML, and XSL module for PHP [default]
ii  php7.0                                                      7.0.33-0+deb9u7                   all          server-side, HTML-embedded scripting language (metapackage)
ii  php7.0-bcmath                                               7.0.33-0+deb9u7                   amd64        Bcmath module for PHP
ii  php7.0-cgi                                                  7.0.33-0+deb9u7                   amd64        server-side, HTML-embedded scripting language (CGI binary)
ii  php7.0-cli                                                  7.0.33-0+deb9u7                   amd64        command-line interpreter for the PHP scripting language
ii  php7.0-common                                               7.0.33-0+deb9u7                   amd64        documentation, examples and common module for PHP
ii  php7.0-fpm                                                  7.0.33-0+deb9u7                   amd64        server-side, HTML-embedded scripting language (FPM-CGI binary)
ii  php7.0-json                                                 7.0.33-0+deb9u7                   amd64        JSON module for PHP
ii  php7.0-mbstring                                             7.0.33-0+deb9u7                   amd64        MBSTRING module for PHP
ii  php7.0-mysql                                                7.0.33-0+deb9u7                   amd64        MySQL module for PHP
ii  php7.0-opcache                                              7.0.33-0+deb9u7                   amd64        Zend OpCache module for PHP
ii  php7.0-pgsql                                                7.0.33-0+deb9u7                   amd64        PostgreSQL module for PHP
ii  php7.0-readline                                             7.0.33-0+deb9u7                   amd64        readline module for PHP
ii  php7.0-sqlite3                                              7.0.33-0+deb9u7                   amd64        SQLite3 module for PHP
ii  php7.0-xml                                                  7.0.33-0+deb9u7                   amd64        DOM, SimpleXML, WDDX, XML, and XSL module for PHP

Alles anzeigen

Is that right so far?

2. problem..... services

Some of them are coloured red - but for instance NFS seems to be running well?!

Could you help me with that?

3. problem .... Fail2Ban

If i try to activate any Jail-config - it is not possible ... for instance OMV-WebGUI

Details:

journalctl -u fail2ban -b

Code

root@server:~# journalctl -u fail2ban -b
-- Logs begin at Thu 2020-05-14 18:10:29 CEST, end at Thu 2020-05-14 18:12:01 CEST. --
Mai 14 18:10:34 server systemd[1]: Starting Fail2Ban Service...
Mai 14 18:10:35 server fail2ban-client[1542]: ERROR  Found no accessible config files for 'fail2ban' under /etc/fail2ban
Mai 14 18:10:35 server fail2ban-client[1542]: ERROR  No section: 'Definition'
Mai 14 18:10:35 server fail2ban-client[1542]: ERROR  Found no accessible config files for 'filter.d/sshd-ddos' under /etc/fail2ban
Mai 14 18:10:35 server fail2ban-client[1542]: ERROR  No section: 'Definition'
Mai 14 18:10:35 server fail2ban-client[1542]: ERROR  Unable to read the filter
Mai 14 18:10:35 server fail2ban-client[1542]: ERROR  Errors in jail 'ssh-ddos'. Skipping...
Mai 14 18:10:35 server systemd[1]: fail2ban.service: Control process exited, code=exited status=255
Mai 14 18:10:35 server systemd[1]: Failed to start Fail2Ban Service.
Mai 14 18:10:35 server systemd[1]: fail2ban.service: Unit entered failed state.
Mai 14 18:10:35 server systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Mai 14 18:10:35 server systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart.
Mai 14 18:10:35 server systemd[1]: Stopped Fail2Ban Service.
Mai 14 18:10:35 server systemd[1]: Starting Fail2Ban Service...
Mai 14 18:10:35 server fail2ban-client[1809]: ERROR  Found no accessible config files for 'fail2ban' under /etc/fail2ban
Mai 14 18:10:35 server fail2ban-client[1809]: ERROR  No section: 'Definition'
Mai 14 18:10:35 server fail2ban-client[1809]: ERROR  No section: 'Definition'
Mai 14 18:10:35 server fail2ban-client[1809]: ERROR  Found no accessible config files for 'filter.d/sshd-ddos' under /etc/fail2ban
Mai 14 18:10:35 server fail2ban-client[1809]: ERROR  No section: 'Definition'
Mai 14 18:10:35 server fail2ban-client[1809]: ERROR  Unable to read the filter
Mai 14 18:10:35 server fail2ban-client[1809]: ERROR  Errors in jail 'ssh-ddos'. Skipping...
Mai 14 18:10:35 server systemd[1]: fail2ban.service: Control process exited, code=exited status=255
Mai 14 18:10:35 server systemd[1]: Failed to start Fail2Ban Service.
Mai 14 18:10:35 server systemd[1]: fail2ban.service: Unit entered failed state.
Mai 14 18:10:35 server systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Mai 14 18:10:35 server systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart.
Mai 14 18:10:35 server systemd[1]: Stopped Fail2Ban Service.
Mai 14 18:10:35 server systemd[1]: Starting Fail2Ban Service...
Mai 14 18:10:35 server fail2ban-client[2089]: ERROR  Found no accessible config files for 'fail2ban' under /etc/fail2ban
Mai 14 18:10:35 server fail2ban-client[2089]: ERROR  No section: 'Definition'
Mai 14 18:10:35 server fail2ban-client[2089]: ERROR  No section: 'Definition'
Mai 14 18:10:35 server fail2ban-client[2089]: ERROR  No section: 'Definition'
Mai 14 18:10:35 server fail2ban-client[2089]: ERROR  Found no accessible config files for 'filter.d/sshd-ddos' under /etc/fail2ban
Mai 14 18:10:35 server fail2ban-client[2089]: ERROR  No section: 'Definition'
Mai 14 18:10:35 server fail2ban-client[2089]: ERROR  Unable to read the filter
Mai 14 18:10:35 server fail2ban-client[2089]: ERROR  Errors in jail 'ssh-ddos'. Skipping...
Mai 14 18:10:35 server systemd[1]: fail2ban.service: Control process exited, code=exited status=255
Mai 14 18:10:35 server systemd[1]: Failed to start Fail2Ban Service.
Mai 14 18:10:35 server systemd[1]: fail2ban.service: Unit entered failed state.
lines 1-40

Alles anzeigen

Michelle_Br · 14. Mai 2020

more about that.....

/usr/bin/fail2ban-client -x start

Code

root@server:~# /usr/bin/fail2ban-client -x start
ERROR  Found no accessible config files for 'fail2ban' under /etc/fail2ban
ERROR  No section: 'Definition'
ERROR  No section: 'Definition'
ERROR  No section: 'Definition'
ERROR  No section: 'Definition'
ERROR  No section: 'Definition'
ERROR  No section: 'Definition'
ERROR  No section: 'Definition'
ERROR  Found no accessible config files for 'filter.d/sshd-ddos' under /etc/fail2ban
ERROR  No section: 'Definition'
ERROR  No section: 'Definition'

Alles anzeigen

systemctl status fail2ban.service

Code

root@server:~# systemctl restart fail2ban.service
Job for fail2ban.service failed because the control process exited with error code.
See "systemctl status fail2ban.service" and "journalctl -xe" for details.
root@server:~# ^C
root@server:~# systemctl status fail2ban.service
● fail2ban.service - Fail2Ban Service
   Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-05-14 18:19:30 CEST; 4min 1s ago
     Docs: man:fail2ban(1)
  Process: 12358 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)

Mai 14 18:19:30 server systemd[1]: Failed to start Fail2Ban Service.
Mai 14 18:19:30 server systemd[1]: fail2ban.service: Unit entered failed state.
Mai 14 18:19:30 server systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Mai 14 18:19:30 server systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart.
Mai 14 18:19:30 server systemd[1]: Stopped Fail2Ban Service.
Mai 14 18:19:30 server systemd[1]: fail2ban.service: Start request repeated too quickly.
Mai 14 18:19:30 server systemd[1]: Failed to start Fail2Ban Service.
Mai 14 18:19:30 server systemd[1]: fail2ban.service: Unit entered failed state.
Mai 14 18:19:30 server systemd[1]: fail2ban.service: Failed with result 'exit-code'.
root@server:~#

Alles anzeigen

Could you help me, please?

Michelle_Br · 15. Mai 2020

Is there anybody who could help me, please? *smiling

ryecoaaron · 15. Mai 2020

Zitat von Michelle_Br

Is that right so far?

Seems ok

Zitat von Michelle_Br

Some of them are coloured red - but for instance NFS seems to be running well?!

Enable nfs and then disable it. If it has no shares, it isn't hurting anything though.

Zitat von Michelle_Br

If i try to activate any Jail-config - it is not possible ... for instance OMV-WebGUI

I would purge the plugin and re-install. I've never used it so I can't help much (even though I maintain the plugin).

Michelle_Br · 17. Mai 2020

Hi ryecoaaron

Thank you very much for your help. *smiling

NFS....

All of my old / actual shares are NFS and they are running. With my Sat-tuner VU+ Duo² everythings seems to be ok.

Fail2Ban....

Could you tell me the correct procedure to purge it well - and the same for installing it new, please?

ryecoaaron · 18. Mai 2020

Zitat von Michelle_Br

Could you tell me the correct procedure to purge it well - and the same for installing it new, please?

Uninstall it from the plugins tab and reboot. Then install it from the plugins tab.

Michelle_Br · 19. Mai 2020

Thank you very much .... i thought in that case it is better to purge it via terminal.

But .... there are errors, too..... i´ve done as you discribed:

Code

root@server:~# systemctl status fail2ban.service
● fail2ban.service - Fail2Ban Service
   Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-05-19 12:41:59 CEST; 4min 55s ago
     Docs: man:fail2ban(1)
  Process: 12041 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)

Mai 19 12:41:58 server systemd[1]: Failed to start Fail2Ban Service.
Mai 19 12:41:58 server systemd[1]: fail2ban.service: Unit entered failed state.
Mai 19 12:41:58 server systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Mai 19 12:41:59 server systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart.
Mai 19 12:41:59 server systemd[1]: Stopped Fail2Ban Service.
Mai 19 12:41:59 server systemd[1]: fail2ban.service: Start request repeated too quickly.
Mai 19 12:41:59 server systemd[1]: Failed to start Fail2Ban Service.
Mai 19 12:41:59 server systemd[1]: fail2ban.service: Unit entered failed state.
Mai 19 12:41:59 server systemd[1]: fail2ban.service: Failed with result 'exit-code'.
root@server:~#

Alles anzeigen

Code

root@server:~# journalctl -xe
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Mai 19 12:46:30 server systemd[15744]: Startup finished in 17ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
--
-- Kernel start-up required KERNEL_USEC microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 17671 microseconds.
Mai 19 12:46:30 server systemd[1]: Started User Manager for UID 0.
-- Subject: Unit user@0.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit user@0.service has finished starting up.
--
-- The start-up result is done.
Mai 19 12:46:46 server monit[1964]: 'filesystem_media_1ba0979d-6327-4ee2-be9a-faf65b6e2c58' space usage 99.8% matches resource limit [space usage>85.0%]
Mai 19 12:46:46 server monit[1964]: 'filesystem_media_1fe63d1e-ca10-4934-b128-ba09ebc693e4' space usage 99.8% matches resource limit [space usage>85.0%]
Mai 19 12:47:01 server CRON[16284]: pam_unix(cron:session): session opened for user root by (uid=0)
Mai 19 12:47:01 server CRON[16285]: (root) CMD (   test -x /usr/sbin/wakealarm && /usr/sbin/wakealarm > /dev/null 2>&1)
Mai 19 12:47:01 server wakealarm[16286]: CRITICAL - Unable to load wakealarm table.
Mai 19 12:47:01 server wakealarm[16286]: INFO - No alarm set previously.
Mai 19 12:47:01 server CRON[16284]: pam_unix(cron:session): session closed for user root
Mai 19 12:47:16 server monit[1964]: 'filesystem_media_1ba0979d-6327-4ee2-be9a-faf65b6e2c58' space usage 99.8% matches resource limit [space usage>85.0%]
Mai 19 12:47:16 server monit[1964]: 'filesystem_media_1fe63d1e-ca10-4934-b128-ba09ebc693e4' space usage 99.8% matches resource limit [space usage>85.0%]
Mai 19 12:47:47 server monit[1964]: 'filesystem_media_1ba0979d-6327-4ee2-be9a-faf65b6e2c58' space usage 99.8% matches resource limit [space usage>85.0%]
Mai 19 12:47:47 server monit[1964]: 'filesystem_media_1fe63d1e-ca10-4934-b128-ba09ebc693e4' space usage 99.8% matches resource limit [space usage>85.0%]
Mai 19 12:48:01 server CRON[17074]: pam_unix(cron:session): session opened for user root by (uid=0)
Mai 19 12:48:01 server CRON[17075]: (root) CMD (   test -x /usr/sbin/wakealarm && /usr/sbin/wakealarm > /dev/null 2>&1)
Mai 19 12:48:01 server wakealarm[17076]: CRITICAL - Unable to load wakealarm table.
Mai 19 12:48:01 server wakealarm[17076]: INFO - No alarm set previously.
Mai 19 12:48:01 server CRON[17074]: pam_unix(cron:session): session closed for user root
lines 1433-1473/1473 (END)

Alles anzeigen

ryecoaaron · 19. Mai 2020

Unfortunately, I don't use fail2ban but the service can't start. So, I would say there is some config that is bad. I would:

sudo apt-get purge fail2ban openmediavault-fail2ban

sudo rm -rfv /etc/fail2ban

reboot

Then try re-installing.

Michelle_Br · 19. Mai 2020

You are my hero!!!!!! *smiling

THAT was the solution!

I´m so glad that you helped me .... thank you so much!

Upgrade issues OMV 3.x -> 4.x .... some issues

Jetzt mitmachen!

Ähnliche Themen

OMV / FreeIPA Integration

ZFS pool not mounting on boot

Debian 10 - OMV 4.x