Telnet service_limit error
Posted by Planet Malaysia on August 26, 2009
Previously I posted Inactive TELNET session timeout, How To Check Number of SSH and Telnet session and today I would like to share something related to TELNET again. In fact, I know telnet is NOT secure.
Referring to /var/log/xinetd.log(telnet parked under xinetd services), if you found something look like FAIL: telnet service_limit mean telnet instances are over limit.
09/8/26@10:43:23: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:23: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:24: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:24: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:25: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:25: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:26: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:26: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:27: FAIL: telnet service_limit from=192.168.10.180
In order to check TELNET instances limit, view /etc/xinetd.conf and look for “instances = xx“. If “instances = 10” which mean you’re limit to 10 TELNET session on your server. Configure ‘best’ number of instances as per your reference for solving this kind of issue.
man xinetd
If the number of server instances is lowered, some arbitrarily picked servers will be killed to satisfy the limit; this will happen after any servers are terminated because of failing the remote location or access time checks.
Possibly Related Posts:
- WP Contact Form III – You do not have sufficient permissions to access this page Error
- WP Cache Error “semget() failed: Permission denied” Solved
- Google Public DNS Down?
- lppasswd: Unable to open passwd file: Permission denied
- Missing /var/log/lastlog
Comments
Leave a Reply