Well with your log I can surely find it out I bet, since it contains the address where it failed.
I wonder what it is since I see no reason for a sudden crash.
Hmm I dont seem to have enough info to be able to trace this back. The address 0x3213b looks like a strange address. I would need drwatson logs to see what is really going on. Is there any way you can reproduce this??
It should be known that sitekill actually sends a kill message to ioftpd. If ioftpd decides to not listen to it then there is nothing that sitekill can do. For example if someone is running a script and you want to kick the connection then io wont normally let you. Eevn tho io properly recognizes the message. This behaviour is proper tho, you wouldnt want your files to be messed up due to a user being prematurely kicked would you?
If you can get a situation in which it occurs please open a command box and do this command:
..\scripts\SiteKill.exe debug user!=sitebot "idletime>120" service=FTP_Service
And give me the info it gives...
|