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

Network monitoring knocks out AMQP connections #52

Open
jonkafton opened this issue Sep 24, 2015 · 3 comments
Open

Network monitoring knocks out AMQP connections #52

jonkafton opened this issue Sep 24, 2015 · 3 comments

Comments

@jonkafton
Copy link

If network monitoring is turned on (pmx.init() with network: true), RabbitMQ server will abruptly close attempts to establish connection (amqplib on client).

@wespen
Copy link

wespen commented Sep 15, 2016

+1
Just found out I cant use both at the same time.

@schornio
Copy link

+1

Node.js Timeout:
Error: Socket closed abruptly during opening handshake

RabbitMQ Log Entry:
=ERROR REPORT==== 26-Sep-2016::16:45:07 === closing AMQP connection <0.5604.0> (127.0.0.1:54533 -> 127.0.0.1:5672): {handshake_timeout,frame_header}

@vmarchaud
Copy link
Contributor

I will advice you to disable monitoring network in pmx for now, we are wrapping the socket constructor to get those metrics in pure javascript (AMQP client must do the same)
What you could do is use pm2-server-monit to monitor these datas since it use linux binary to get them, it should work well.

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