1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. If you had a PIAF Forum account in the vBulletin days, log in with your old credentials. Otherwise, sign up again and we'll get you back in business as soon as we can.
  3. A serious FreePBX vulnerability has been reported. Update your Framework Module immediately. Click here for details.
  4. Critical FreePBX vulnerability! Update your server immediately. Details here.

GO HERE fail2ban not start

Discussion in 'Help' started by centoasa, Mar 23, 2014.

  1. centoasa Member

    I've just update-fixes, update-source to latest asterisk (11.7.0), but none, fail2ban don't start. Where is the issue? I've piaf green on orale virtualbox (update at latest)
  2. atsak Guru

    What does the log say about why it will not start? Why did you run the update-source program - was something not working?
  3. centoasa Member

    All works fine first of update, but in other thread I've seen to update-source to solve fail2ban issue.
    While piaf is starting, the log say me fail2ban [error]
    where I can found detailed logs to see further information about this issue?
  4. atsak Guru

    \var\log
  5. centoasa Member

    Here is my latest boot:
    %G Welcome to CentOS
    Starting udev: %G[ OK ]

    Setting hostname pbx.local: [ OK ]

    Setting up Logical Volume Management: No volume groups found
    [ OK ]

    Checking filesystems
    /dev/sda2: clean, 198886/1105920 files, 1469280/4415488 blocks
    /dev/sda1: clean, 44/25688 files, 48886/102400 blocks
    [ OK ]

    Remounting root filesystem in read-write mode: [ OK ]

    Mounting local filesystems: [ OK ]

    Enabling local filesystem quotas: [ OK ]

    Enabling /etc/fstab swaps: [ OK ]

    Entering non-interactive startup
    Bringing up loopback interface: [ OK ]

    Bringing up interface eth0: Determining if ip address 192.168.1.253 is already in use for device eth0...
    [ OK ]

    Starting pppoe-server: [ OK ]

    Starting auditd: [ OK ]

    Starting portreserve: [ OK ]

    Starting system logger: [ OK ]

    Loading DAHDI hardware modules:
    wct4xxp: [ OK ]

    wcte12xp: [ OK ]

    wct1xxp: [ OK ]

    wcte11xp: [ OK ]

    wctdm24xxp: [ OK ]

    wcfxo: [ OK ]

    wctdm: [ OK ]

    wcb4xxp: [ OK ]

    wctc4xxp: [ OK ]

    xpp_usb: [ OK ]


    Running dahdi_cfg: [ OK ]

    Starting irqbalance: [ OK ]

    Starting named: [ OK ]

    Starting rpcbind: [ OK ]

    ip6tables: Applying firewall rules: [ OK ]

    iptables: Applying firewall rules: [ OK ]

    Starting NFS statd: [ OK ]

    Starting system message bus: [ OK ]

    Starting cups: [ OK ]
    Mounting filesystems: [ OK ]

    Starting acpi daemon: [ OK ]

    Starting HAL daemon: [ OK ]

    Retrigger failed udev events[ OK ]

    Loading autofs4: [ OK ]

    Starting automount: [ OK ]

    Starting sshd: [ OK ]

    Starting xinetd: [ OK ]

    Starting ntpd: [ OK ]

    Starting mysqld: [ OK ]

    Starting sendmail: [ OK ]

    Starting sm-client: [ OK ]

    Starting httpd: Warning: DocumentRoot [/var/www/html/restapps/] does not exist
    Warning: DocumentRoot [/var/www/html/restapi/] does not exist
    [ OK ]

    Starting crond: [ OK ]

    Starting fail2ban: [FAILED]

    Starting atd: [ OK ]

    Starting HylaFAX queue manager (faxq): [ OK ]

    Starting HylaFAX server (hfaxd): [ OK ]

    Starting IAXmodem: [ OK ]

    Starting Filesystem event daemon (incrond): [ OK ]


    Please wait...

    SETTING FILE PERMISSIONS
    chattr: Operation not supported while reading flags on /var/www/html/provisioning
    chattr: Operation not supported while reading flags on /var/www/html/wcb.php
    Permissions OK
    Removing any dangling symlinks
    Dangling symlinks removed

    STARTING ASTERISK
    Asterisk Started

    STARTING FOP SERVER
    FOP Server Started
    Stopping fail2ban: [FAILED]

    Starting fail2ban: [FAILED]

    iptables: Setting chains to policy ACCEPT: nat mangle filter [ OK ]

    iptables: Flushing firewall rules: [ OK ]

    iptables: Unloading modules: [ OK ]

    iptables: Applying firewall rules: [ OK ]

    ip6tables: Setting chains to policy ACCEPT: filter [ OK ]

    ip6tables: Flushing firewall rules: [ OK ]

    ip6tables: Unloading modules: [ OK ]

    ip6tables: Applying firewall rules: [ OK ]

    iptables: Setting chains to policy ACCEPT: mangle filter [ OK ]

    iptables: Flushing firewall rules: [ OK ]

    iptables: Unloading modules: [ OK ]

    iptables: Applying firewall rules: [ OK ]

    No IPtables problems found.
    job 90 at 2014-03-22 17:54
    Starting nrservice services:
  6. atsak Guru

    You need the log that shows why fail2ban failed to start. I think it's called messages or something.
  7. centoasa Member

    I've 4 files named "messages": I've open them but nothing talk about "fail2ban"
    ps: into /var/log/asterisk I've a file called fail2ban of 194Mb: is it normal?
  8. atsak Guru


    Might be. Any clues in that file?
  9. Hyksos Guru

Share This Page