If you fail to log in 3 times in a row, you are sure that your username and password are correct, then you should stop logging in and contact customer service.
Ask them if there is a problem with their server or with your account. Remember not to keep trying after several failures, this may cause your account to be closed or cancelled.
iptables -I INPUT -p tcp –dport some_port -j LOG then tail -f /var/log/messages Afterwards, to see how much data has been hit by that rule: iptables -L -n -v Or you could run tcpdump and grep out the ports.
· Linux logs can be viewed with the command cd/var/log, then by typing the command ls to see the logs stored under this directory. One of the most important logs to view is the syslog, which logs everything but auth-related messages.
· Log files are accessed using root privileges. By definition, root is the default account that has access to all Linux files. Use the following example line command to access the respective file: sudo less [log name here].log. This command displays a timeline of all information related to that operation.
You should find all that output in /var/log/messages. If it has rotated you need to look in /var/log/message.1. Grep out the time range to a separate file that you can examine more easily. A command like grep ‘Jun 7 22:’ /var/log/messages > ~/messages.tmp should work. Look for references to eth0 in the file. You may also see a reference to repeated messages which may be close to the line …
Note that those are network card kernel module messages so they are driver dependant. They may not exist at all or may change according to the different module active on you server. If you can, run a tail -F /var/log/messages and quickly unplug/re-plug the cable (to see if those events are logged).