Fedora 15 x86_64, rsyslogd: imuxsock: recvfrom UNIX: Resource temporarily unavailable

corp769 · 11-23-2011, 09:18 AM

Hello all,

The following messages are just part of many of them, filling up my /var/log/messages file. After really intensive searching around, I haven't been able to come up with a firm answer about this. My system works as advertised for the time being, and is more of a nuisance than anything. Anyone else ever experience this issue?

Code:

Nov 23 09:51:41 ltp01 rsyslogd: imuxsock: recvfrom UNIX: Resource temporarily unavailable
Nov 23 09:55:18 ltp01 rsyslogd: imuxsock: recvfrom UNIX: Resource temporarily unavailable
Nov 23 09:55:34 ltp01 rsyslogd: imuxsock: recvfrom UNIX: Resource temporarily unavailable
Nov 23 09:58:40 ltp01 rsyslogd: imuxsock: recvfrom UNIX: Resource temporarily unavailable

Cheers,

Josh

kbp · 11-24-2011, 05:00 AM

Have you tried restarting rsyslog ? .. it should tell us if the problem is permanent

corp769 · 11-24-2011, 05:25 AM

Quote:

Originally Posted by kbp

Have you tried restarting rsyslog ? .. it should tell us if the problem is permanent

Yes I have. Have you seen this pop up on your machine at all?

kbp · 11-28-2011, 04:49 PM

No .. you might need to go down the strace road to get more visibility. Could also be worth checking that there's nothing leaking sockets - try lsof.

corp769 · 11-28-2011, 06:19 PM

Yeah I was starting to think that. I'm at work, so I will report back once I get home.

corp769 · 12-07-2011, 10:12 AM

Still nothing..... This is weird.

kbp · 12-07-2011, 03:55 PM

I did a little digging, it could be that your unix socket receive queue is too small and is getting overrun - check what setting you have for /proc/sys/net/unix/max_dgram_qlen and maybe increase it.

corp769 · 12-07-2011, 04:01 PM

Yeah, it's at 10. What's yours set at?

kbp · 12-07-2011, 04:35 PM

My default is 10 ... I gather it should be increased for a busy server. Unfortunately I'm not guru enough to give you instructions on how to monitor/tune this .. maybe a system tap script using socket.* probes if you want to find the underlying cause, otherwise just pump it up until the messages stop

corp769 · 12-07-2011, 05:59 PM

Well I certainly know enough about it... But the thing is, this is not a server, or a high-usage computer. This is my laptop. On the other hand, I do run a lot of things on it, being an alienware, and I am a very active programmer, so maybe the overall load could be doing this as well. I brought it in with me into work, so I will probably just up it by 10 or so, and give it a shot.

kbp · 12-07-2011, 06:56 PM

There seems to be a lot of options you can use to tune the behaviour of imuxsock in terms of flow control etc, have a read here .. it may be better than fiddling with sysctl.

corp769 · 12-07-2011, 07:01 PM

Hmmm... Thanks for that. I might mess around with the rate limiting option, that may have to do something with it.