Resource temporarily unavailable

[Andre Ford]

Hi all,

I've noticed a lot of entires in the syslog file (/var/adm/syslog/syslog.log) and was wondering if someone could shed some light on this:

chpt520 tftpdir[3097]: recvfrom: Resource temporarily unavailable

I have always received great support here so I'm sure someone has seen this. Oh, we're running version 10.20. Thanks.

Andre

[Massimo Bianchi]

Hi,
are you using TFTP ?

It looks so from the message: "tftpdir"... maybe the tftp is tryng to write to a nfs-mounts ?

Just a guess.
HTH,
Massimo

[Steven E. Protter]

I have a broad itrc search for you.

http://us-support.external.hp.com/emse/bin/doc.pl/sid=9a8fcae405edb65d0a?todo=search&searchtext=tftpdir+Resource+temporarily+unavailable+&x=32&y=15&searchcriteria=allwords&searchtype=SEARCH_TECH_DOCS&searchtype=SEARCH_MANUAL&searchtype=SEARCH_TRAINER&searchtype=SEARCH_FORUMS&searchtype=SEARCH_BSD&searchcategory=ALL&rn=25&presort=rank

I've read through some of it and have the following advice:

1)Search for tftp patches, because this has often been resolved for other daemon's with patches.

2)dmesg ioscan... look for some kind of intermittant hardware problem that might cause the tftp home directorhy to be offline. If you have x, try xstm and test out the disks.

3) Check for other errors with regards to networking or heavy load. If the machine is stressed, it might be unable to meet certain requests.

4) Use the scripts I'm attaching to look for possible performance bottlenecks.

SEP

[T G Manikandan]

check the errors from the /var/adm/syslog/syslog.log file.

There are lot of reasons for getting "resource not available" messages.

Revert

[Steven Gillard_2]

I'm assuming you're running a non-standard TFTP server here?

The "Resource temporarily unavailable" message is errno 11, or EAGAIN. The recvfrom() system call will return this error in normal conditions when a socket is in non-blocking mode and there is no data to receive. An application that puts a socket in non-blocking mode should be coded to handle this return code from recvfrom() and should definitely not be making noise about it.

So if your application is working ok you can either ignore this error, or you can ask the vendor to fix the code so it doesn't get logged.

Regards,
Steve