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

/api/pings resource not available: socket hang up #363

Open
vijayk2019 opened this issue Dec 14, 2017 · 0 comments
Open

/api/pings resource not available: socket hang up #363

vijayk2019 opened this issue Dec 14, 2017 · 0 comments

Comments

@vijayk2019
Copy link

Most apis failing intermittently. For eg. "/api/checks/needingPoll", "/api/pings" and "/api/checks".

We are getting errors similar to for all apis:

/api/pings resource not available: socket hang up
at ClientRequest. (/root/Uptime/lib/monitor.js:202:14)
at emitOne (events.js:96:13)
at ClientRequest.emit (events.js:188:7)
at Socket.socketOnEnd (_http_client.js:345:9)
at emitNone (events.js:91:20)
at Socket.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)

Even trying to curl locally doesn't help. Has anyone had this problem?

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

1 participant