ioFTPD SiteKill for ioFTPD 5.x

[FTPServerTools]

How do you run it? It shouldnt crash of course (I did test it namely).

[nicolay]

All I did was replace the .exe, and now it crashes when i do any site cmd. SITE KILL "idletime>120" / SITE KILL override "idletime>120". I get that windows crash dialog that SiteKill had a problem and had to be closed...

I didnt change any system ini settings from last exe.

[Scheduler]
KillIdlers = 0,5,10,15,20,25,30,35,40,45,50,55 * * * EXEC ..\scripts\ioSiteKill\SiteKill.exe silent "idletime>120" service=FTP_Service

[FTP_Custom_Commands]
KILL = EXEC ..\scripts\ioSiteKill\Sitekill.exe

I dont get any error in error.log from scheduler anymore though, but dont know if it even does anything :P

[R] site kill "idletime>120"
(LAGG)
[R] 550 Command failed.

[FTPServerTools]

It is fixed again. Silly stupid error from my side.

[nicolay]

I'm probably just doing something wrong here, but it keeps crashing occationally.

I think it's the scheduler crashing, i get in error.log
09-25-2004 18:36:12 Scheduler event 'KillIdlers' returned error.

KillIdlers = 0,5,10,15,20,25,30,35,40,45,50,55 * * * EXEC ..\scripts\ioSiteKill\SiteKill.exe silent "idletime>120" service=FTP_Service

[Jog]

if i try this command from command line:

SiteKill.exe debug "idletime>120" > log.txt

but the connections wasn't kiked

ioFTPD 5.8.5r
ioShareDB
ioA , pSio, newdir, dZSbot all last version
SiteKill 2.0.11

i attach the log file!

[FTPServerTools]

SiteKill uses ioFTPD's internal killing method. This means that if you cant kill the connection using ioFTPD itself that I cant do it either. This can occur when the user is logged in and he has a script running (or hanging). Can you please check all the subprocesses of ioFTPD (use ProcessExplorer). And thanks for the log.txt this makes it easier for me to see what is going on. according to the log the kill is sent properly...

[Jog]

i retry now to launch this command:

SiteKill.exe debug "idletime>120" > log.txt

i attach the log.txt and the ProcessExplorer log for ioFTPD.exe

I use ioTrayIcon to launch ioFTPD ... if this information is useful ..

[FTPServerTools]

this log didnt help, all it does is tell me that there were attempts to kill the connection for a user which failed due to the point that your script is hanging or whatever reason. ioftpd doesnt allow the kick to happen ergo sitekill cant make it happen. If this kind of behaviour occurs a lot you should use ioProcess to see which scripts are hanging in io. WIth ioProcess yiu can also kill those processes.

Example of use:
On connection 1 I have a small program that is hanging. It apparently is taking quite some seconds.
This program is args.exe which I called from an event in ioFTPD.
So I type via connection 2:
site proc (so I execute ioProcess.exe under ioFTPD).

And as reply it gives me:
200- pid: process started at kernel user
200- exefile yyyy-mm-dd hh:mm:ss mm:ss mm:ss
200- 3992: args.exe 2004-04-21 21:12:23 00:03 00:52
200- 4060: ioProcess.exe 2004-04-21 22:24:04 00:00 00:00
200 Command successful.

The 1st column is the process id.
The 2nd column is the exe that is called.
The 3rd and 4th column are the date/time when the process was started, this is a criteria
for determining a hanging process. In this example process 3992 has been hanging for more then
a full hour.
The 5th column is the time used in the kernel-mode, here 3 seconds (for pid=3992)
The 6th column is the time used in the user-mode, here 52 seconds (for pid=3992)
If one of these columns is quite high then apparently the process is hanging or very busy.

Since 3992 seems to be hanging I type:

site proc kill 3992

with result:

200-args.exe terminated
200 Command successful.


Dont forget to check the date/time to see which of the processes is hanging.

[FTPServerTools]

to nicolay:
I need a drwtsn32.exe log because whatever you are doing I dont get it to crash. Also can you find a way to get it to crash consistently? It treied with users on, no users, and with your commandline but it failed to crash here.

Do check that you are running version 2.0.11 and that you are running the sitekill 5.x version for ioftpd 5.x ..

[dink-puller]

I haven't been able to do anything with this tool without it crashing. (version 2.0.11) Also, trying to run it without EXEC in ioFTPD.ini produces a failed command, with no other results.

/site version
200-Running ioFTPD version 5-8-5r
::If there is a user connected whose last action was PWD
/site SITEKILL action=PWD produces:
550 Command failed. (SiteKill.exe crashes, see below for offsets)
::If there isn't a user connected whose last action was PWD
200-Totally 0 connections kicked, due to:action=PWD
200 Command successful.

ioFTPD.ini
[Scripts]
SITEKILL = EXEC ..\scripts\SiteKill\SiteKill.exe
[FTP_SITE_Permissions]
SITEKILL = M

/site proc
200- pid: process started at kernel user
200- exefile yyyy-mm-dd hh:mm:ss mm:ss mm:ss
200- 1520: ioProcess.exe 2004-10-31 09:46:03 00:00 00:00
200 Command successful.

no hanging processes.

[FTPServerTools]

Thanks for your mail, with some luck I can recreate the crash and thus solve it quickly.

[dink-puller]

Just wondering if this has something to do with msvcrt.dll and XP sp2? btw, program quits at that exact same place, when executing SiteKill with any parameters, not just the ones I posted above. Hope that helps, can't wait to see this finished.

[FTPServerTools]

Can you make a drwtsn32 report for it? (just run drwtsn32 and let it crash) I can use the log.... You dont have to make a huge memory dump. Apparently sp2 doesnt give any decent error comment as sp2 used to give. msvcrt.dll is the dll that contains many standard routines so it may go wrong in a printf or a stringcompare or whatever. THe log should give a little bit more info (I hope).

[dink-puller]

Crap, I can't make it crash now, everything works great. Wait a second, that's a good thing!! If it happens again, I'll send a crash report.
Thanks, and take care.