-
Notifications
You must be signed in to change notification settings - Fork 36
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
server hang after started for a while #7
Comments
I am also experiencing the same issue . Running windows 2016 server |
@raymondiwi are you running a 32 or 64 bit OS? Please provide as much information as you can to allow me to replicate the issue. |
So this is what I did. The server hangs after few hours after it has been started. Sometimes it hangs after a few minutes. Details of the machine: |
Hi, @svenkle I also modified some configuration settings Svenkle.NuGetServer.Service.exe.config server hang seems taking few minutes after been started. |
Same here |
I, too, am having this issue... Server 2016, running in VM, 64-Bit, port changed to 5111. Nothing else changed. v0.0.6535.20611-pre |
More information: Seems to list my repositories just fine for about 1 minute. I can make 5 successful calls to list the repo (1 package only), after which the call will time out. If I end the svenkle service from the console (i.e. press enter or Ctrl-C, then enter again) it ends the nuget provider, and I can immediately rerun it and get a good response from a call that is still awaiting response. If I end the nuget service via task-manager whilst a call is being made, I get an INSTANT and FINAL response from the nuget provider, and cannot start it again - error message from IIS Express It seems like the thread is awaiting input of some kind, rather than hanging. |
I am also having this issue with v0.0.6535.20611-pre and v0.0.6330.3877-pre. |
Not sure, but i see a requirement not met : |
Tried to deploy zip(v0.0.6535.20611-pre) and ran Svenkle.NuGetServer.Service.exe,
When it was just up, functions work, but after a while, server seems to stay in hang state.
Though I deployed on Windows server 2008 R2, it does not meet requirement.
Web server IIS 6.0 and IIS 7.5 exists also.
When started up, IIS express warning always shows.
The text was updated successfully, but these errors were encountered: