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

Burst of "Unable to send to wakeup socket!" #1837

Closed
fcracker79 opened this issue Jun 5, 2019 · 3 comments
Closed

Burst of "Unable to send to wakeup socket!" #1837

fcracker79 opened this issue Jun 5, 2019 · 3 comments

Comments

@fcracker79
Copy link

After upgrading from 1.4.4 to 1.4.6, we receive a burst of logs of "Unable to send to wakeup socket!".
Based on our metrics, clients are not consuming messages any more.
We solved the issue by restarting our clients.

@fcracker79
Copy link
Author

At first I would suggest replacing

            except socket.error:
                log.warning('Unable to send to wakeup socket!')

with

            except socket.error:
                log.warning('Unable to send to wakeup socket!', exc_info=True)

just to dig into the issue.

@ghost
Copy link

ghost commented Jun 13, 2019

Hi, i have the same problem...#1842
Screenshot from 2019-06-10 17-01-51

But after i replace

            except socket.error:
                log.warning('Unable to send to wakeup socket!')

with

            except socket.error:
                log.warning('Unable to send to wakeup socket!', exc_info=True)

i still get the same error

@dpkp
Copy link
Owner

dpkp commented Oct 1, 2019

I believe this is fixed in latest release, 1.4.7. Please reopen if issue persists.

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

2 participants