Running Raven as a Service - No response from http://localhost:8080/

[legion]

I'm running Raven as a Service on a win28k r2 64bit server.

Every X hours/minutes (i haven't figured out the frequency yet), i have to restart the service. The server is chugging along fine with no spike in memory or CPU.

The reason why I have to restart the service is when I browse to: http://localhost:8080/ or http://myserver:8080 it just sits there for several minutes before the browser stops trying to connect.

Once i restart the service, everything is fine. And i can get the studio to load. Then after X hours/minutes, i try to open the studio again and the browser just sits there 

What do I need to provide you gentleman to assist me and figure out what is going on?

 

[Oren Eini (Ayende Rahien)]

Can you enable debug logging?

Check the Raven.Server.exe.config, is the port set to be 8080?

[legion]

2012-08-11 12:06:46.9162,Raven.Database.Indexing.WorkContext,Debug,"No work was found, workerWorkCounter: 0, for: ReducingExecuter, will wait for additional work",

2012-08-11 12:06:46.9630,Raven.Database.Indexing.WorkContext,Debug,"No work was found, workerWorkCounter: 0, for: IndexingExecuter, will wait for additional work",

2012-08-11 13:06:46.9975,Raven.Database.Indexing.WorkContext,Debug,"No work was found, workerWorkCounter: 0, for: ReducingExecuter, will wait for additional work",

2012-08-11 13:06:47.0287,Raven.Database.Indexing.WorkContext,Debug,"No work was found, workerWorkCounter: 0, for: IndexingExecuter, will wait for additional work",

2012-08-11 14:06:47.0631,Raven.Database.Indexing.WorkContext,Debug,"No work was found, workerWorkCounter: 0, for: ReducingExecuter, will wait for additional work",

2012-08-11 14:06:47.0943,Raven.Database.Indexing.WorkContext,Debug,"No work was found, workerWorkCounter: 0, for: IndexingExecuter, will wait for additional work",

that is the last log entry. Its now 3 PM and when i tried to hit the studio, no response from the server.

Port isn't set to 8080, it is set to "*".

Thoughts?

[Itamar Syn-Hershko]

You probably have another app listening on 8080, so raven selected another port. If you are running the console, it writes which port there

[legion]

Its a brand new server with nothing on except raven. I verified that IIS is not even installed.

Here is port scanner:

TCP port 8080 (unknown service): LISTENING

portqry.exe -n ravenServer -e 8080 -p TCP exits with return code 0x00000000

IF it was another app, then it doesn't explain why it works after I restart the service and continues to for a period of time. 

[Oren Eini (Ayende Rahien)]

It is possible that you started RavenDB twice?

[Hassan Mirza]

I installed it as a service. and I thought the same so i poked around to make sure there were no other instances.

[legion]

Any other ideas guys?

[legion]

FYI,

I tried telneting into the server on 8080 and set it basic commands. No response. I tried the same on test server with Raven running under IIS, and the server responded with expected http response results.

[Oren Eini (Ayende Rahien)]

That seems really strange.

The only thing that pops to mind is some firewall or something like that which is causing the issue

[Chris Marisic]

Antivirus / Antimalware also, some of those products seem to be heavily interested in trying to intercept local http traffic