-
Notifications
You must be signed in to change notification settings - Fork 27
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
Stop to work after some time #47
Comments
I see, that it's probably connected with vesse/node-ldapauth-fork#67 |
I have the same issue. The ldap authentication stop works after few hours. The connection to ldap is not lost. and list all users in my ldap server. The verdaccio is running on screen behand nginx proxy. I am attach to this screen and I don't see any errors. |
The same also for me. |
Same here. Log:
|
The last ldapauth-fork seems to fix the issue. Could you try the latest release ? |
First, thanks @Alexandre-io for the update.! |
Hi! I start using verdaccio-activedirectory project, which is enought for my needs and which works fine - so i can't reproduce it anymore. |
Hello @lneveu . Verdaccio and verdaccio-ldap are updated. I will keep you updated. [root@verdaccio-testlink ~]# sudo npm update -g verdaccio
|
I had upgraded verdaccio-ldap to 3.1.0, but nothing changed. The problem is still there after node-ldapauth-fork was upgraded to 4.2.0. BTW: My Verdaccio version is 3.8.6. Update: I have tested under node@8.14.0/node@10.15.0, and verdaccio@3.8.6/verdaccio@3.10.1, all with the same issue. |
Today the verdaccio ldap authentication was crashed again and not works. :( |
I'm using |
Hello. Last week, verdaccio ldap authentication stops works multiple times. Can you tell me how can I run it in debug mode ? After next crash I will sent the log here. Thanks a lot. |
@iovcho you can set trace log level in config file
|
Also I have the same problem. |
It seems to be related with LDAP bind requests and concurrency. I can reproduce the bug when multiple authentications are made "simultaneously" (try to disable cache to reproduce the issue more easily). |
Done. I will sent you report on next crash. |
Hello @nemca . Here is the tracelog, before crash. I change my personal data in log (emails, username, passwords etc). Here is the output: {"name":"verdaccio","hostname":"verdaccio.hostname","pid":7284,"sub":"in","level":35,"request":{"method":"GET","url":"/-/verdaccio/packages"},"user":null,"remoteIP":"192.168.101.3 via 127.0.0.1","status":304,"bytes":{"in":0,"out":0},"msg":"304, user: null(192.168.101.3 via 127.0.0.1), req: 'GET /-/verdaccio/packages', bytes: 0/0","time":"2019-03-14T13:50:15.051Z","v":0} |
I has merge #46 PR on my env and verdaccio don't stopping work more. But I see too many ESABLISHED connections to LDAP server (>2000), which verdaccio not close and not use. |
It seems like connections are never unbind ( |
@lneveu I can add |
@nemca You can add it like that: (after the catch handler)
(note that |
This output after I'm added you code. |
Finally! |
Can't this problem be solved? |
is this problem solved? |
Hi, No, the problem still exist. I have cronjob who restart Verdaccio each 20 minutes, but this is really ugly workaround. :) Best wishes. |
Ha ha ,me too |
@Alexandre-io Can we have this in a bugfix release? We're seeing this behavior in production too. |
@martin31821 I just release the version 4.0.0. Could you try it and provide us a feedback please ? |
Works fine, thank you! |
@Alexandre-io the problem just reappeared on our production instance, is there anything I can do to help tracking down the real issue? |
4.0.1 problem still exists, connection lost after a while
|
I've configured verdaccio-ldap agains ldap from AD. It works fine few minutes after start, with configuration like
Unfortunately, after few login/logout it stop works, and i have in logs:
Any suggestions how to solve it?
The text was updated successfully, but these errors were encountered: