as an aside.. even where there is a script name, without the script query parameters it can be impossible to duplicate the call and reproduce the error.
I have created a log for the main script with an entry and exit stat field. The log stores the query. I am trying to then track which entries never get their exit flag. This should tell me the exact query that is causing the problem.
Sent by Steve Moore on 03/18/2014 06:58:29 AM:
I have checked the troubleshooting section. Again the problem here is that there is no known program/condition to execute. The environment handles 100,000+ requests a day so leaving all the channels open out of service mode just looking for a needle in a haystack is problematic. I need to know WHAT script is causing the hang.
Sent by Steve Moore on 03/18/2014 06:55:26 AM:
fwstart sometiems shows the executing program and sometimes doesn't. When a program name is present there is also an error in the error log. However, there are instances where there is neither a program name or an error entery, just the message restarting channel x.
Sent by FoxWeb Support on 03/17/2014 01:00:13 PM:
Did you check fwstart.log? It should contain a list of instances, when a channel was restarted, along with the script that was executing at the time.
The "Hanging channels, or channels that get restarted often" section in the Troubleshooting > Common Problems
page of the documentation contains additional information on how to isolate the cause of such issues.
FoxWeb Support Team
Sent by Steve Moore on 03/15/2014 02:30:48 PM:
Can anyone give me some ideas on troubleshooting killed channels when there is no information in the error log. Without an error log entry I am not able to determine what program is causing the problem.
I know that one possibility is the error handler itself... but I have not been able to find any problems there. If there is an error in the error handler routine is there a way to know this? other than a hung channel?
Also, is there a graceful way to return an alternate page for timeouts?