OFFICIAL "SERVER PROBLEMS" THREAD

[James Heinrich]

Originally Posted by snme2pm1

Me wonders as to the definition of "night"

Presumably that would be set to the typical period of least average load on the server, which may or may not conform to any particular user's (or even the of the server's) geographic location's definition of "night".

[snme2pm1]

Originally Posted by James Heinrich

I reworked that page several months ago

I noticed that there is much more comprehensive result information now visible, at odds with assertions from some quarters in the past that there is no record of partial (or not) range TF factored result.
I can see a tell-tale asterisk.
Hopefully that indicator is well agreed among the various agents.
... F 729540971773795344071;[TF:69:70*:mfakto 0.14-Win cl_barrett15_71_gs_2]

[NBtarheel_33]

Originally Posted by snme2pm1

Me wonders as to the definition of "night", and impact on mersenne.org response to people's enquiries and submissions, prime95 and misfit.

I bet that anything in the "wee hours" (e.g. 0300) in any of the continental US time zones would work fairly well. Might not be perfect, but should work well.

[kladner]

These results included a Factor Found. I don't remember seeing the error below before:

Processing result: nHTTP/1.1 502 Gateway Error Server: Microsoft-IIS/5.0

[Mark Rose]

Originally Posted by snme2pm1

I noticed that there is much more comprehensive result information now visible, at odds with assertions from some quarters in the past that there is no record of partial (or not) range TF factored result.
I can see a tell-tale asterisk.
Hopefully that indicator is well agreed among the various agents.
... F 729540971773795344071;[TF:69:70*:mfakto 0.14-Win cl_barrett15_71_gs_2]

Nope. I just factored M68743163 with StopAfterFactor=2 in mfaktc, and this is all it produced: F-PM1 2463386658202793009209. No indication of the agent or that factoring was only partial for the bit depth.

[sdbardwick]

Originally Posted by Mark Rose

Nope. I just factored M68743163 with StopAfterFactor=2 in mfaktc, and this is all it produced: F-PM1 2463386658202793009209. No indication of the agent or that factoring was only partial for the bit depth.

Not sure if that result is representative. It looks like a TF that was interpreted by PrimeNet as P-1; did you report a no-factor found before the TF result to get around the P-1 bug?

[Madpoo]

Originally Posted by snme2pm1

Me wonders as to the definition of "night", and impact on mersenne.org response to people's enquiries and submissions, prime95 and misfit.

Fortunately doing an index reorganization is an online task. Performance can be hit a bit since it's doing some disk I/O (well, a lot of disk I/O on large indices).

An index rebuild is an offline task except in the enterprise editions of SQL, which this definitely won't be (that's a lot of extra $$$), so that probably wouldn't happen except in some extreme circumstance. There are some clustered indices in use so during any rebuild there would probably be some features that wouldn't work that specifically use an indexed view, but I don't know for sure. Other queries could run okay but take longer without an index to help them along.

The best times of day to run any maintenance task whether it's SQL, doing a disk defrag, or anything else that impacts some subsystem, is best determined by looking at traffic levels over the course of a few weeks and finding those dips in activity.

I see that the web page is instrumented with Google Analytics which would help see how the web traffic does.

On the API side of things, check in and check out activity is timestamped so it should be fairly easy to gather in some stats for the last XX days or weeks and see if there's any type of pattern. Those are probably more evenly spread because clients don't care what time of day it is, they just check in/out as needed. But maybe there's something surprising in the data... maybe I can do a little analysis on the copy of the DB and see if anything pops out in that regard. Could be interesting, although I suspect it's fairly even.

[Mark Rose]

Originally Posted by sdbardwick

Not sure if that result is representative. It looks like a TF that was interpreted by PrimeNet as P-1; did you report a no-factor found before the TF result to get around the P-1 bug?

Ahh, nevermind. I was just going by what I could see on the web. The actual results submitted should look like:

M68743163 has a factor: 2463386658202793009209 [TF:71:72*:mfaktc 0.20 barrett76_mul32_gs]
found 1 factor for M68743163 from 2^71 to 2^72 (partially tested) [mfaktc 0.20 barrett76_mul32_gs]

[Madpoo]

Originally Posted by kladner

These results included a Factor Found. I don't remember seeing the error below before:

Processing result: nHTTP/1.1 502 Gateway Error Server: Microsoft-IIS/5.0

Weird... 502 error is a gateway related error, like a proxy server in the path had an issue. There's no proxy directly in front of the current website... traffic goes directly to IIS from the outside world, not through a load balancer/caching proxy/whatever.

Any proxy seems like it'd be on the client's side, but the IIS/5.0 is kind of a giveaway that it did manage to hit the server in some way... might have been a request going through a proxy that timed out or something...that's my guess.

[kladner]

Last response from the server, 1754 UTC:

Warning: odbc_pconnect() [function.odbc-pconnect]: SQL error: [Microsoft][ODBC SQL Server Driver]Timeout expired, SQL state S1T00 in SQLConnect in C:\v5\www\2013\v5server\0.96_database.inc.php on line 21
pnErrorResult=3 pnErrorDetail=Database unavailable ==END==

In reference to my previous post, NF results were accepted. I still haven't gotten the Factor Found result to go through.

EDIT: I got in to submit results, but the response is the same. The NF results have already been accepted.

Processing result: no factor for M68762963 from 2^73 to 2^74 [mfaktc 0.20 barrett76_mul32_gs]
Error code: 40,
error HTTP/1.1 502 Gateway Error
Server: Microsoft-IIS/5.0
Date: Thu, 14 Aug 2014 18:00:04 GMT
Connection: close
Content-Length: 186
Content-Type: text/html
CGI Timeout

The specified CGI application exceeded the allowed time for processing. The server has deleted the process.

[James Heinrich]

Originally Posted by Mark Rose

No indication of the agent or that factoring was only partial for the bit depth.

How was the result submitted? Manually? with misfit?