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

Error: connection timed out at Socket #11

Open
J-Wilkening opened this issue Nov 4, 2021 · 1 comment
Open

Error: connection timed out at Socket #11

J-Wilkening opened this issue Nov 4, 2021 · 1 comment

Comments

@J-Wilkening
Copy link

Hi. I am running multiple eventhub2Syslog instance in one azure function app. I am getting multiple error messages like:

2021-11-04T11:30:42.015 [Error] Executed 'Functions.XXX' (Failed, Id=XXX, Duration=20ms) node exited with code 1 LanguageWorkerConsoleLog[error] Worker XXX uncaught exception (learn more: https://go.microsoft.com/fwlink/?linkid=2097909 ): Error: connection timed out at Socket.<anonymous> (D:\home\site\wwwroot\node_modules\syslog-client\index.js:276:14) at Object.onceWrapper (events.js:421:28) at Socket.emit (events.js:315:20) at Socket._onTimeout (net.js:483:8) at listOnTimeout (internal/timers.js:554:17) at processTimers (internal/timers.js:497:7)

Can anyone figure out where this is coming from? Thanks for assistance

@devtrf
Copy link

devtrf commented Nov 17, 2022

@J-Wilkening were you able to deploy this solution presently, and was there a lot of deviation from the initial config as described on the README?

This is still the only setup Microsoft documentation points to, but I've been fairly unsuccessful at getting this to work.

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