yes, I have failure report on. I was trying to get more info
included in it. yes, it has filename/path & reqs, but at
least the default isn't showing the status code with each
file.
The status report shows a summary of how many files have
each status code...
but neither does both detailed filename AND the status code,
which wouldn't seem to be a FAQ 128 situation since that
info is definitely in the same line of the logs, not something
you'd have to cross-reference.
I'll try the STATUSINCLUDE, though it's probably back to
looking at the raw logfiles for most of any real insight into this
[EMAIL PROTECTED] ASP problem... oh well.
BTW, Glenn Keffer had written:
I am guessing that those files never make it to the processing time
report, since the ASP hangs, it probably never finishes the HTML
return to the client, hence status 500 errors. > Brings back (fond?)
memories of searching logs for 500 errors to help find bad ASP code.
:-)
Exactly. I have code that worked great for several years until our
webhost migrated us to the newer win and IIS last year. Since then
I've had this problem, sometimes a lot, and very little that can
point us to an actual cause. HTML still gets served, but ASP files
aren't executed. You have to do a full IIS reset to get it going
again.
FYI, I do get log entries on scripts during the hangs. Here's an
example. Note the last field (time-taken)
#Fields: date time c-ip cs-username s-ip cs-method cs-uri-stem
cs-uri-query sc-status sc-win32-status sc-bytes cs-bytes time-taken
2006-08-01 23:56:26 64.187.48.55 - 216.13.158.101 GET
/peren/perenindex.asp |-|ASP_0147|500_Server_Error 302 0 0 515 10956703
2006-08-01 23:56:26 64.187.48.55 - 216.13.158.101 GET /peren/peren.asp
|-|ASP_0147|500_Server_Error 302 0 0 514 10263640
2006-08-01 23:56:26 69.157.150.101 - 216.13.158.101 GET
/roses/roseindex.asp |-|ASP_0147|500_Server_Error 302 0 0 487 10099703
2006-08-01 23:56:26 69.157.150.101 - 216.13.158.101 GET
/roses/roseindex.asp |-|ASP_0147|500_Server_Error 302 0 0 487 10096500
2006-08-01 23:56:26 69.157.150.101 - 216.13.158.101 GET
/roses/roseindex.asp |-|ASP_0147|500_Server_Error 302 0 0 487 10076875
2006-08-01 23:56:26 69.157.150.101 - 216.13.158.101 GET
/roses/sections.asp |-|ASP_0147|500_Server_Error 302 0 0 486 10074718
2006-08-01 23:56:26 69.157.150.101 - 216.13.158.101 GET
/roses/rosesearch.asp |-|ASP_0147|500_Server_Error 302 0 0 488 10070828
Unfortunately, since it's on a webhosting account, I don't have
direct admin access to much past the logfiles, so I have to pass
requests for anything more direct like events logs through support.
Fun all around. sigh.
later,
jeff
Aengus wrote:
On Tuesday, August 08, 2006 4:47 PM [EDT],
Glenn Keffer <[EMAIL PROTECTED]> wrote:
Apologies if this is too obvious, but do you have the Failure
Report on? I believe it will show you which files failed, but I
don't remember if correlates it to a status code.
It does. The Failure Report will show the filenames that were
requested that returned a "failure" status code (usually a 404 or a
401, but requests that return a 500 are also listed in the Failure
Report).
But all failed requests are reported in the Failure Report. To see
only the 500's, use
STATUSINCLUDE 500-
But you would also need FAILURE ON, because the Failure report is not
on by default, and if you're only including requests with a 500
status code the default reports, that only report on Successful
requests, would all be empty.
Aengus
--
Jeff Wilkinson
[EMAIL PROTECTED]
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------
