ping: sendto: No buffer space available

[Tom Danzig]

Had a 10.20 server die this AM. Could not access via network at all (i.e. ping). When I tried to ping the loopback to check TCP/IP, got the following:

PING 127.0.0.1: 64 byte packets
ping: sendto: No buffer space available
ping: wrote 127.0.0.1 64 chars, ret=-1
ping: sendto: No buffer space available
ping: wrote 127.0.0.1 64 chars, ret=-1
ping: sendto: No buffer space available
ping: wrote 127.0.0.1 64 chars, ret=-1

----127.0.0.1 PING Statistics----
3 packets transmitted, 0 packets received, 100% packet loss

Linkloop to the mac from another server was OK. Link light on card OK. I reset the LAN card via lanadmin which didn't help (one wouldn't expect it to if the loopback can't be pinged). ifconfig said lan card was up.

Anyone ever see this issue before? Sounds like some issue with the TCP/IP stack. Had to reboot to fix, however, I want to prevent the issue from arising in the future.

I have looked at the latest recommended ARPA transport patch (PHNE_19936) which I do not have installed, however, there is no mention of this issue in the patch readme.

Thanks for any guidance you may offer.

[T G Manikandan]

check for the patch

PHNE_24260

check for the latest one


Thanks

[Stefan Farrelly]

see;

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xe0f8a12d6d27d5118fef0090279cd0f9,00.html

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x10ca3a7b3682d611abdb0090277a778c,00.html

[Tom Danzig]

Thanks for the replies.

TG - I have ping patch PHNE_19566 installed. PHNE_16188 addressed "Ping has a buffer overflow problem.".

Stefan - I searched and read those post. No resolution was evident.

[Tom Danzig]

(Bump)

Still unresolved. Anyone have any further ideas?

[Jeff Schussele]

Hi Tom,

Does netstat -an yield any clues?
Syslog show anything?

I'd bounce the net daemon from the console:

/sbin/init.d/net stop/start

Rgds,
Jeff

[James R. Ferguson]

Hi Tom:

You don't indicate what type of LAN card. I've seen this behavior with 10.20 and 100BT cards after a network "burp". I've found that more stabliity was gained by applying both the latest LAN and ARPA patches. When done, I've had reasonable success resetting the card with 'lanadmin'.

Too, make sure that your switch and local card settings are matched (duplex and speed). I have not found auto-negotation (if this is involved) to be very reliable, although some folks claim good success with it.

Regards!

...JRF...

...JRF...

[Tom Danzig]

The card is a HP-PB 100 Base TX. My main concern was that I was unable to ping 127.0.0.1. My understanding is that this can be run even if NO lan cards are installed as it works at the protocol level and actually doesn't send anything out to the network. The sole purpose of having this is to check the internal TCP/IP stack.

I was planning on installing the latest ARPA patch as I don't have any other possible resolutions. Latest LAN products cumulative Patch is installed.

I tried to "lan reset" via lanadmin without success. The card is hard configured 100FD as is the switch port.

Thanks for the replies.