Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HAProxy: [ALERT] sendmsg logger #2 failed: Resource temporarily unavailable (errno=11) #488

Open
ayashjorden opened this issue Aug 17, 2017 · 3 comments

Comments

@ayashjorden
Copy link

ayashjorden commented Aug 17, 2017

Hi,
Opening here as the error message is coming from the bundled HAProxy component in MLB container.

Context:

When running MLB without enabling the /devlog device for HAProxy, I'm getting blasted with:
[ALERT] 228/081350 (412) : sendmsg logger #2 failed: No such file or directory (errno=2)

After enabling the /dev/log device:

  1. I've started seeing HAProxy log messages
  2. I'm getting blasted with:
    [ALERT] 228/081044 (10579) : sendmsg logger #2 failed: Resource temporarily unavailable (errno=11)

I've searched online for similar solutions but all I found is not MLB related.
Tried restarting the rsyslog daemon, didn't help.

UPDATE: Found this issue which is related.

Questions

Can someone shed some light here?
Why mounting the /dev/log device into the MLB container didn't help?
Can someone elaborate on how to configure rSyslog on the host machine to support HAProxy logging to /dev/log ?

Running on CentOS7.3.1611

Thank you,
Yarden

@petr-k
Copy link

petr-k commented Oct 23, 2017

We're also facing the same issues.. would be cool if somebody could explain what the correct configuration should look like. Thanks! ;)

@sureshcvh
Copy link

sureshcvh commented Feb 2, 2018

  1. Increased the Max datagram queue length (/proc/sys/net/unix/max_dgram_qlen via sysctl --> sysctl -w net.unix.max_dgram_qlen=100) from 10 to 100.

and

2.restarted the syslog (sudo service rsyslog restart).

Alerts stopped showing.

@treborbg
Copy link

In my case syslog service was faulty, I restart it and I was able to move on.
service syslog restart

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants