STREAMS/UX error

[Rudeboy_1]

Hi All,

Wonder if anyone can help with a problem I've got.

Yesterday I was doing a large ftp transfer from a particular server when the server stopped accepting any telnet connections. The ftp transfer also stopped. I tried logging in at the console but the command line gave no response to any commands (e.g ls, bdf - no output).

I then resorted to the Microsoft approach to troubleshooting, i.e. powered off and powered on again. The machine appears to boot OK but before getting to the login prompt I start getting the following message repeatedly scrolling up the screen:

**********************STREAMS/UX********************
Wed Jun 26 BST 2002 10:07:01.140103 ERROR Subsys:STREAMS LOC:00123 47877 10:07:02 6722756 1 T.. 5306 5 ar_rput_dlpi: DL_UDERROR_IND, dl_dest_addr_lenght 8 dl_errorno 4

I can just about make out the login prompt betwen these messages and manage to login OK, but still can't use any commands from the command line.

I'm well and truly stuck, any ideas folks? TIA.

[Tom Geudens]

Hi,
The following post describes a similar problem :
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x3c2ecb60e503d6118ff40090279cd0f9,00.html

Hope this helps,
Tom

[Rudeboy_1]

Thanks for the response, I'll try booting from system.prev and let you know how I get on!

[Rudeboy_1]

Tried booting from system.prev but same result. I can use the command line between error messages now though!

Any more ideas? Patches maybe?

[Tom Geudens]

Hi,
Same post, the reply that got the 10 points.
I also saw another post that had a patch for this ... mmm ... found it doing "ERROR Subsys STREAMS" search on the forums.

Regards,
Tom

[Rudeboy_1]

Yes, I tried the link from the 10 point answer on the other question but it just takes you to the patch database main page......I just noticed the url string contains PHNE_24413 so I'll give this patch a try.

[Rudeboy_1]

I ended up opening a call with HP for this, they told me that the error message inicated a problem with external hardware (i.e. not the server or lan card but the UTP or network port, hub/switch etc).

It turned out to be a faulty network port. Thanks for the help Tom.