Intrusion Detection Problem when set banned permanen ( -1 )

› VitalPBX Community Support › General Discussion › Intrusion Detection Problem when set banned permanen ( -1 )

Up
0
Down
  • Post
    • September 30, 2019 at 7:25 am
    Up
    0
    Down
    kadalmen
    Participant

    Hello,

    Please help. Intrusion Detection Problem when set banned permanen ( -1 ).

    [root@vitalpbx ~]# service firewalld status
    Redirecting to /bin/systemctl status firewalld.service
    ● firewalld.service – firewalld – dynamic firewall daemon
    Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
    Active: active (running) since Mon 2019-09-30 02:38:48 EDT; 35min ago
    Docs: man:firewalld(1)
    Main PID: 11961 (firewalld)
    CGroup: /system.slice/firewalld.service
    └─11961 /usr/bin/python -Es /usr/sbin/firewalld –nofork –nopid

    Sep 30 03:14:14 vitalpbx.local firewalld[11961]: ERROR: ‘/usr/sbin/iptables-restore -w -n’ failed: iptables-restore v1.4.21: Set fail2ban-apache-overflows doesn’t exist.

    Error occurred at line: 2…
    Sep 30 03:14:14 vitalpbx.local firewalld[11961]: ERROR: COMMAND_FAILED: ‘/usr/sbin/iptables-restore -w -n’ failed: iptables-restore v1.4.21: Set fail2ban-apache-overflows doesn’t exist.

    Error occurred at line: 2…
    Sep 30 03:14:15 vitalpbx.local firewalld[11961]: ERROR: ‘/usr/sbin/iptables-restore -w -n’ failed: iptables-restore v1.4.21: Set fail2ban-apache-modsecurity doesn’t exist.

    Error occurred at line: 2…
    Sep 30 03:14:15 vitalpbx.local firewalld[11961]: ERROR: COMMAND_FAILED: ‘/usr/sbin/iptables-restore -w -n’ failed: iptables-restore v1.4.21: Set fail2ban-apache-modsecurity…sn’t exist.

    Error occurred at line: 2…
    Sep 30 03:14:15 vitalpbx.local firewalld[11961]: ERROR: ‘/usr/sbin/iptables-restore -w -n’ failed: iptables-restore v1.4.21: Set fail2ban-apache-shellshock doesn’t exist.

    Error occurred at line: 2…
    Sep 30 03:14:15 vitalpbx.local firewalld[11961]: ERROR: COMMAND_FAILED: ‘/usr/sbin/iptables-restore -w -n’ failed: iptables-restore v1.4.21: Set fail2ban-apache-shellshock doesn’t exist.

    Error occurred at line: 2…
    Sep 30 03:14:16 vitalpbx.local firewalld[11961]: ERROR: ‘/usr/sbin/iptables-restore -w -n’ failed: iptables-restore v1.4.21: Set fail2ban-asterisk-vpbx doesn’t exist.

    Error occurred at line: 2…
    Sep 30 03:14:16 vitalpbx.local firewalld[11961]: ERROR: COMMAND_FAILED: ‘/usr/sbin/iptables-restore -w -n’ failed: iptables-restore v1.4.21: Set fail2ban-asterisk-vpbx doesn’t exist.

    Error occurred at line: 2…
    Sep 30 03:14:17 vitalpbx.local firewalld[11961]: ERROR: ‘/usr/sbin/iptables-restore -w -n’ failed: iptables-restore v1.4.21: Set fail2ban-vitalpbx-gui doesn’t exist.

    Error occurred at line: 2…
    Sep 30 03:14:17 vitalpbx.local firewalld[11961]: ERROR: COMMAND_FAILED: ‘/usr/sbin/iptables-restore -w -n’ failed: iptables-restore v1.4.21: Set fail2ban-vitalpbx-gui doesn’t exist.

    Error occurred at line: 2…
    Hint: Some lines were ellipsized, use -l to show in full.

     

    Thank you

    0
Viewing 1 replies (of 1 total)
  • Replies
    • October 8, 2019 at 5:43 pm
    Up
    0
    Down
    Jose Miguel Rivera
    Keymaster
    NI

    Try performing a full update of your system and then, you will need to restart the server.

    Let me know if the problem persist.

    0
Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.