You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using your sample config, modified only to work with my LDAP server.
I then start it with node index.js and it says 'Listening on port: 12983' for two minutes. Then it crashes with
Listening on port: 12983
events.js:160
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at exports._errnoException (util.js:1020:11)
at TCP.onread (net.js:568:26)
This happens even if I don't query the API for authentication.
I've done a bunch of searching on Google but it all appears to be connected to timeouts with specific connections. This issue crashes the app even without me making any connections to the app API.
So if this is connection related, it must have to do with the LDAP connection. If so, what can I do with that connection to make it stay alive, or at least not crash the app?
The text was updated successfully, but these errors were encountered:
In my case I was able to catch the errors by modifying index.js and inserting the following code just after var auth = new LDapAuth(settings.ldap) call (near line 21).
// Catch errors so app does not crash
auth._adminClient.on('error', err => {
console.warn('_adminClient: LDAP connection dropped, reconnecting.');
});
auth._userClient.on('error', err => {
console.warn('_userClient: LDAP connection dropped, reconnecting.');
});
I'm not sure why the ldapauth-fork library doesn't already have a plan in place to catch errors.
Using your sample config, modified only to work with my LDAP server.
I then start it with
node index.js
and it says 'Listening on port: 12983' for two minutes. Then it crashes withThis happens even if I don't query the API for authentication.
I've done a bunch of searching on Google but it all appears to be connected to timeouts with specific connections. This issue crashes the app even without me making any connections to the app API.
So if this is connection related, it must have to do with the LDAP connection. If so, what can I do with that connection to make it stay alive, or at least not crash the app?
The text was updated successfully, but these errors were encountered: