Unable to telnet

[Mike Ingram]

I was trying to load patches on HP-UX 11.0, but it failed, so I cancelled out.
Now I am unable to telnet to the machine, and get the following message on the client:

telnetd: /dev/pts/ta: No such file or directory
.
Connection to host lost.

The telnetd process is not running on the host and I cannot find any error message relating to it in the syslog or rc.log
the /dev/pts directory has only files names 0 thu to 49
Any ideas on what is wrong and how to fix it?
Thanks.

[Devender Khatana]

Hi,

There is no way of canceling a patch installation in between. Allthough it is quite possible that your seesion got disconnected in between somehow. A simple procedure for rectifying this would be to uninstall that patch / bundle through swremove. You can also check installation through swverify.

Moreover the no. of pty device files in /dev/pty depends on npty kernel parameter and are created everytime your system is rebooted.

Did your server rebooted after patch application?

HTH,
Devender

[Mike Ingram]

The patch installation failed with the following message:
Compiling /stand/build/conf.c...
Loading the kernel...
/usr/ccs/bin/ld: Unsatisfied symbols:
pread (first referenced in /usr/conf/lib/libhp-ux.a(init_sent.o)) (code)
pwrite (first referenced in /usr/conf/lib/libhp-ux.a(init_sent.o)) (code)
*** Error exit code 1

I then cancelled and now cannot telnet.
Does this help you or do you need more info?
Thanks.

[Devender Khatana]

Hi,

It has not be able to compile the new kernel because of this error. Previous kernel must have got copied to vmunix.prev before attempting to compile new kernel. You can try booting your system through that kernel and it should work fine. Also see the contents of /stand and try to boot from the old kernel.

HTH,
Devender

[Ermin Borovac]

telnetd uses device files in /dev/pts named t.

It looks like some of these have gone missing.

Kernel parameter related to this is nstrtel.

Check its value with

# kmtune -q nstrtel

Then run the following command to create telnet device files (substitute with value of corresponding kernel parameter).

# insf -d tels -s -e -v

[Devesh Pant_1]

Pretty much you will have to bring down the box if it is still in use. Boot it up to a single user mode.
Did you try using the GSP ?

Devesh

[Ermin Borovac · Accepted solution]

Regarding your kernel recompilation problem, it's probably been caused by reinstallation of patch PHKL_18543 (line in the sand -- LITS).

You should run check_patches to check integrity of all patches on your system. This utility will tell you what you need to reinstall.

# /usr/contrib/bin/check_patches

Offending patches (all except PHKL_18543) should be reinstalled with

# swinstall -x autoreboot=true -x reinstall=true -x reinstall_files=true -s

My guess is that you will need to reinstall PHKL_22589.

[Mike Ingram_1]

Hi All,

Thanks for your contributions, but I am going around in circles.
Ermin, the original problem was from the PHKL_18543 reload, and it has got to the point now where the easiest thing is going to be a reload of the OS then the various apps can be copied from backup.
Very frustrating!

Cheers.

[Rajeev Shukla]

Hi Mike,

Telnet service is started by inetd daemon
check if inet daemon is running or not and if not start using
/usr/sbin/inetd

If the patch reinstallation failed, you should have your old kernel in /stand
Did you try terminating the boot sequence and boot using the old kernel

Also try creating the device files again using
insf -e

Cheers
Rajeev

[Isralyn Manalac_1]

Hi Mike,

Just to add a note re: PHKL_18543. When you reinstall it (as your case seems to point in that direction), make sure that you have all the dependencies for that patch. Next time, be wary of LITS patches like PHKL_18543.


As it seems you need to recreate your pts files, would you consider restoring your Ignite tape? I think it's much easier (and safer) that way because cancelling out on a patch installation must have left some things undone.

Regards,

Isralyn

[Mike Ingram]

Thanks for all the suggestions, but the easy way out for me was a rebuild!