telnet failed in hpux v.3

[Valik_1]

Hi there!
After a sudden shutdown (electricity failed) I got a problem with telnet login.
Server wrote
Trying...
Connected to *****
Escape character is '^]'.
Local flow control off
Connection closed by foreign host.

Servers syslog says that:

telnetd[11750]: I_LINK_DEV ioctl failed: Invalid argumentn

and many other strange things.. :(
pls help

[Torsten.]

"... many other strange things ..."

What is it?
Failed hardware and/or LAN connection, LAN switches ...

[Valik_1]

dont know yet
but another one is
vmunix: WARNING: VxVM vxio V-5-0-23 Open on an spurious volume device (0x3000007) encountered. This device may be valid, but has not yet been configured in the kernel.

[Robert-Jan Goossens]

Valik,

do you have a console login?

Post the ls -la of below file.

# ll /dev/telnetm
crw-rw-rw- 1 root sys 72 0x000059 Nov 6 12:56 /dev/telnetm

Could you copy/paste all 'strange things'?

Regards,
Robert-Jan

[Ramesh S]

Hi

Please run

# netstat -a | grep -i telnet

to check the tlnet daemon is running on the server.

Thanks & Regards

Ramesh

[VK2COT]

Hello,

Most probable cause is corruption of devices
in /dev. It could be a couple of other
issues as well (for example, corrupted
/etc/services, /etc/inetd.conf, /var/adm/inetd.sec, and so on).


If you search this Forum by keyword
"I_LINK_DEV", you will find excellent
reference like:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=135934

It also looks like you might have bigger
corruption since you said lot of strange
things happening now...

In the worst case, you might look at
Ignite recovery if a major problem
is detected.

Best wishes,

VK2COT

[Valik_1]

crw-rw-rw- 1 root sys 72 0x000068 Dec 27 12:55 /dev/telnetm

ok.. will try to attach syslog output

[Robert-Jan Goossens]

Warning Message at Boot Time Problem
A message such as the following is displayed if an attempt is made to open a volume at boot
time before any disk group has been imported.

WARNING: VxVM vxio V-5-0-23 Open on an spurious volume device (hex_id) encountered. This device may be valid, but has not yet been configured
in the kernel.

Workaround
This message can be ignored. Once the disk group has been imported successfully, there
should be no problem in accessing its volumes.

You may have to import a/some diskgroups.

[Ramesh S]

Hi

I got a document which says

The usual documented causes for I_LINK_DEV ioctl failed telnet errors is a failed/incomplete telnet patch install
where the binaries, lib, and kernel do not match versions. In this instance, they did not apply. Recreating the device files
corrected the problem.

In this instance, recreating the device files resolved the problem:

#infs -d tels

#insf -d telm

You could try this...

Thanks & Regards

Ramesh

[Valik_1]

Ramesh, it helps! Many thx!!!