Reputation
1,378
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
4 17
Impact
~55k people reached

May
25
comment ntpd error: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING
@SergeySerov port 123 is being used by httpd so that port is already used. I thought you figured that out
May
25
comment ntpd error: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING
You might check what's keeping port 123 busy using lsof -i :123
Mar
27
awarded  Popular Question
Mar
19
awarded  Citizen Patrol
Feb
3
awarded  Popular Question
Nov
29
awarded  Constituent
Nov
25
awarded  Caucus
Nov
11
comment With two NIC cards, in Linux (Debian), how do I keep the NICs from getting the same ip address?
can you show your /etc/network/interfaces file.
Oct
14
answered Hourly Clamscan cron script failes at reading file list
Oct
7
awarded  Excavator
Oct
7
revised Enforcing lock screen after idle time via GPO
Missed step "Policies"
Oct
7
suggested approved edit on Enforcing lock screen after idle time via GPO
Sep
24
awarded  Autobiographer
Aug
23
comment Can not connect mongoDB remotely on centos
127.0.0.1 is a non routable address. This won't work unless it listens to a routable address or 0.0.0.0:27017
Aug
22
comment Open Specific Linux Port
@krisFR I think I did. I replied based on the pastebin.com paste. But I think you already provided the answer. It's the 127.0.0.1
Aug
22
comment Open Specific Linux Port
@dev Line 37 and 44 are the same. Then on line 38 you've fail2-ban which will do nothing if your sshd runs on port 2012 Then, where is the output of lsof -i :2012. Also Can you show the output of grep -E '(^Port|[^#]ListenAddress)' /etc/ssh/sshd_config And as KrisFR is suggesting, sshd is running on the loopback address which is not routable. You've probably set ListenAddress in sshd_config
Aug
22
comment Open Specific Linux Port
show iptables-save -c , lsof -i :2012 and netstat -tan output
Aug
21
comment script to count the occurence of the particular string in the given time interval
I edited my answer. The "${1%:*}" removes the last two digits including the colon. So that means seconds were removed.
Aug
21
revised script to count the occurence of the particular string in the given time interval
deleted 10 characters in body
Aug
20
comment No matter what I do, Apache2 is using the event MPM. Ubuntu Server 14.04
Can you show what apache2 -l lists?