TIPS Odd issue with add-fqdn / add-ip on 16-15 (takes too long)

[AndyInNYC]

If I add a fqdn or ip via ./add-fqdn or ./add-ip the process ends correctly, But I get to this line:

Redirecting to /bin/systemctl restart fail2ban.service and then 3 minutes pass and then I get

Taking too long? Customize the chown command, See http://wiki.freepbx.org/display/FOP/FreePBX+Chown+Conf

and then it eventually finishes. This is running on a 4 core Intel machine with an SSD, so I don't think it is a processor problem.

Are there logs I can view to see the problem or changes (via the url which doesn't tell me what changes to actually make <g>)?

Andrew

 

[kenn10]

Sounds similar to the CentOS 7 issues I experienced on one of my cloud providers. I seriously think there is something weird in CentOS 7 causing issues with all the systemctl commands. In my case, it tries to start fail2ban and times out. Fail2ban will not start. I've had to abandon that VPS until we can figure out what the issues are.

 

[AndyInNYC]

Well, this is running Centos7. Anyone else having weird issues?

 

[kenn10]

Well, this is running Centos7. Anyone else having weird issues?

Use systemctl status fail2ban.service and make sure you see "(running)" near the top of the output of that command. If so, you're OK except for the slowness of adding the FQDN.

 $ systemctl status fail2ban.service
* fail2ban.service - Fail2Ban Service
   Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2019-09-27 00:01:06 EDT; 18h ago
     Docs: man:fail2ban(1)
  Process: 31053 ExecStop=/usr/bin/fail2ban-client stop (code=exited, status=0/SUCCESS)
  Process: 31084 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=0/SUCCESS)
 Main PID: 31087 (fail2ban-server)
   CGroup: /system.slice/fail2ban.service
           `-31087 /usr/bin/python2 -s /usr/bin/fail2ban-server -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x -b

Those of use having issues have experienced it on the low-end boxes like Hosting73. Vultr cloud works fine. Since you're on a standalone box, you make be OK just running slow.

 

[AndyInNYC]

I figured out the problem (I think).

The service is running correctly systemctl status fail2ban.service reports all good.

My router reserves the IP of the phone system as .29 and uses the text 'PhoneSystem'

I added this to my hosts file and my speed is back to normal.

Andrew

 

[Eliad]

I have a question a little off topic. How do you remove an entry which was added by ./add-ip?
There is ./del-acct but this seems to be working for the entries added by the ./add-fqdn

 

[AndyInNYC]

./del-acct will kill either and remove them from your iptables whitelist.

Andrew

 

[wardmundy]

If I add a fqdn or ip via ./add-fqdn or ./add-ip the process ends correctly, But I get to this line:

Redirecting to /bin/systemctl restart fail2ban.service and then 3 minutes pass and then I get

Taking too long? Customize the chown command, See http://wiki.freepbx.org/display/FOP/FreePBX+Chown+Conf

and then it eventually finishes. This is running on a 4 core Intel machine with an SSD, so I don't think it is a processor problem.

Are there logs I can view to see the problem or changes (via the url which doesn't tell me what changes to actually make <g>)?

Andrew

Sounds like you don't have an FQDN assigned to your server. Once you do, add it to the 127.0.0.1 line in *etc*hosts just after 127.0.0.1. Also issue command: hostname FQDN.

 

[AndyInNYC]

Thanks Ward. I think my earlier response indicated that this is what I did. My response was truncated because I keep getting errors while posting.

 

[Eliad]

./del-acct will kill either and remove them from your iptables whitelist.

Andrew

thanks, it worked,