I got an email from a user in the wee hours this morning (~2AM, 6/01/2004) complaining that our FoxWeb pages were all unavailable. I verified the error, as shown:
I restarted the FoxWeb service, and all was well. I couldn't find any evidence in the error log, fwstart, etc...so I shrugged it off as a fluke.
Well, I got another email from the same user at 19:41, Tuesday, 6/01. I poked around a bit more before restarting the service this time, at 21:52. The FWStart.log file since 5/25 looks like this :
I tried to run chanstat prior to the restart, but it returned the same error as all the other FoxWeb page. (BTW - I miss v1.29's channel tab on the control panel...very handy when you can't get a web page from the server, for whatever reason. Does such a program exist in v2.x? I would *really* like to have that ability again.)
So now I'm looking at the error log in the FW control panel. I don't see any entries anywhere near the time of the lock-ups.
I did see a few of these errors, but with hours of successful web site use after the error and the lock-up. I don't see much correlation between these errors and the lock-ups.
Sure enough, I was not opening the yearbook database. (wonder how long that's been broken! *blush*). By banging on this page, I could manage to get the channels to hang up with this error:
However, this condition consistently heals itself within a few seconds...unlike the "Broker Timed Out" error which required a restart.
I have fixed the error in my program (file does not exist) and published to our live server, and am hoping for the best. However, I'm not convinced that this error is related to the lock-ups.
Any suggestions? Are there other places I should be looking for evidence? Are there tools I can use to figure out what's going on? What does "FoxWeb Broker Timed Out" mean, compared to "No Channels Active?"
Hopefully, the problem will just "go away" with the change I described above. If it appears again, I will set up a cron job to restart the FoxWeb service once or twice a day. I very much want to avoid that. I hope you have some insight to offer me.
ps. We're running FoxWeb v2.6, VFP v6.0, Microsoft Windows 2000 [Version 5.00.2195], and Netscape-Enterprise/6.0, with 4 FW channels.