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?
On Fri, Aug 10, 2012 at 3:48 PM, legion <hassanfmi...@gmail.com> wrote:
> 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?
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.
You probably have another app listening on 8080, so raven selected another
port. If you are running the console, it writes which port there
On Aug 11, 2012 11:05 PM, "legion" <hassanfmi...@gmail.com> wrote:
> 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.
On Mon, Aug 13, 2012 at 7:56 PM, legion <hassanfmi...@gmail.com> wrote:
> Its a brand new server with nothing on except raven. I verified that IIS
> is not even installed.
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.
On Tue, Aug 14, 2012 at 5:58 PM, legion <hassanfmi...@gmail.com> wrote:
> 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.
On Wednesday, August 15, 2012 7:50:36 AM UTC-4, Oren Eini wrote:
> That seems really strange. > The only thing that pops to mind is some firewall or something like that > which is causing the issue
> On Tue, Aug 14, 2012 at 5:58 PM, legion <hassan...@gmail.com <javascript:> > > wrote:
>> 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.