Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

can not connect using telnet !!!

Status
Not open for further replies.

biswajit123

Technical User
Oct 1, 2002
11
IN
Hello

When I try to telnet my server running solaris it shows

"SunOS 5.7 | ld.so.1: login: fatal: libc.so.1: open failed: Too many open files | Connection closed by foreign host."

what could be the problem? Can anybody help?

Regards
Biswajit
IISc
 
Did you open the telnetd service for Sun Solaris 8 ?
Because by default, you unable to telnet to Sun Solaris 8.Please check your telnetd service.
Good Luck
 
hi

I have checked, the telnetd service is enabled.
Even few days back it was working fine.

Thanks
Biswajit
 
biswajit123,

The "too many open files" part of the message makes me think the problem may be running out of memory that might be caused by a runaway process.

Can you log in at the console?
 
Try incresing the number of file descriptors for ur file system.. use ulimit cmd for the same.. I had this trouble sometme back and got it solved this way.. Well, as bi said, memory also could be the botleneck..

Regds,

- Hemant
Networking and Systems Integration Group
Satyam Computer Services Ltd
 
A process has too many open files at once. The system imposes a per-process soft limit on open files, OPEN_MAX (usualy 64), which can be increased, and a per-process hard limit (usualy 1024), which can not be increased.

You can control the soft limit from the shell. In the C shell use the "limit" command to increase the number of descriptors. In the Bourne or Korn shells, use
the "ulimit -n" command to increase the number of file descriptors.

If the window system refuses to start new application because of this error, increase the open file limit in your login shell before starting the window system.
 
it is a file descriptor issue. You can't allocate anymore...
set the proper kernel variable and reboot..
you may be able to use the adb and set the kernel value that way... also.


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top