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

server hang after started for a while #7

Open
raymondiwi opened this issue Nov 28, 2017 · 9 comments
Open

server hang after started for a while #7

raymondiwi opened this issue Nov 28, 2017 · 9 comments

Comments

@raymondiwi
Copy link

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.
image

@gowthamrang
Copy link

I am also experiencing the same issue . Running windows 2016 server

@svenkle
Copy link
Owner

svenkle commented Nov 29, 2017

@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.

@gowthamrang
Copy link

So this is what I did.
applicationhost.config file was modified
<!-- <binding protocol="http" bindingInformation=":8080:localhost" /> --> <binding protocol="http" bindingInformation="*:8080:" />
window authentication was enabled.

The server hangs after few hours after it has been started. Sometimes it hangs after a few minutes.
It seems to me that the problem does not occur if bindingInformation=":8080:localhost" is not modified, but i am not too sure of it.

Details of the machine:
Windows Server 2016, 64 bit OS (x64 processor)

@raymondiwi
Copy link
Author

raymondiwi commented Nov 30, 2017

Hi, @svenkle
Windows server 2008 R2, 64bit, 1 CPU 4 cores, 8GB RAM run on VmWare ESXi 6.0.0
.net framework 4.6.2

I also modified some configuration settings
applicationhost.config
<binding protocol="http" bindingInformation=":8080:HostName" />
web.config
<add key="requireApiKey" value="false" />

Svenkle.NuGetServer.Service.exe.config
I leave it as default setting
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6" />

server hang seems taking few minutes after been started.

@KimSchneider
Copy link

Same here

@adrian-andersson
Copy link

adrian-andersson commented Mar 26, 2018

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

@adrian-andersson
Copy link

adrian-andersson commented Mar 26, 2018

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've attached a zipped-up MP4 video to illustrate exactly what is happening

brokenNuget.zip

@svenkle

@Filipsi
Copy link

Filipsi commented Sep 17, 2018

I am also having this issue with v0.0.6535.20611-pre and v0.0.6330.3877-pre.

@tunisiano187
Copy link

Hi, @svenkle Windows server 2008 R2, 64bit, 1 CPU 4 cores, 8GB RAM run on VmWare ESXi 6.0.0 .net framework 4.6.2

I also modified some configuration settings applicationhost.config <binding protocol="http" bindingInformation=":8080:HostName" /> web.config <add key="requireApiKey" value="false" />

Svenkle.NuGetServer.Service.exe.config I leave it as default setting <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6" />

server hang seems taking few minutes after been started.

Not sure, but i see a requirement not met :
*** Requirements
.NET 4.8 or higher

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

7 participants