ioftpd kills itself..

[multiPASS]

I have just download ioFTPD-v7.0.1, but I got a proglem, ioftpd.exe kills itself...

here are my CRASH-Log.

ID: 2924 [03430000-0342f2e8]
# 1: 77F88F13 -> [ntdll + 7F13] ? NtWaitForSingleObject() + 0xB
# 2: 77F87F26 -> [ntdll + 6F26] ? RtlEnterCriticalSection() + 0x46
# 3: 016F5876 -> [nl_msgc + 4876] ? ?CreateNLMsgClient@@YAPAVINLMsgClient@@XZ() + 0x2676
# 4: 7C57B3CF -> [KERNEL32 + A3CF] ? lstrcmpiW() + 0xCA



hope someone there can help me :|

[LordM]

Wed Aug 05 22:44:08 2009 - ioFTPD v7.0.1
Unhandled exception: Access Violation (0xC0000005)
Address: 0x7C809784 [attempting to write data to 0x00000000]
PID=1704, PATH=C:\Programme\ioFTPD\system\ioFTPD.exe
Thread ID: 3428

System information:
Processor #0 Name: AMD Athlon(tm) 64 Processor 3200+
Processor #0 Identifier: x86 Family 15 Model 47 Stepping 2
OS: Windows 5.1 (build 2600)
Registry: Microsoft Windows XP
Decoded: XP - Service Pack 2
Page size: 4096

If any further information is neede, just let me know.

And these infos appear on nearly every start. I get io running from time to time, but only one out of twenty starts is successful.

[ArtX]

I would say update to sp3

[Yil]

multiPASS: I probably should document this in a list of known issues in the release notes but from your stack trace it appears you are using netlimiter. Way back in the v6.2 days I discovered the completely crappy Nvidia Firewall and the useful but still broken netlimiter v1.3 both have problems and make ioFTPD unstable. It's possible the v2+ versions of netlimiter work but I haven't tested them. Try uninstalling netlimiter (not sure disabling wouldn't still load the broken dll).

LordM: if you have a reproducible crash like that during startup PM me the CrashLog file and I can send you details on uploading the tiny/mini dumps from the crashes if it looks like I'll need them to debug it further. There simply isn't enough info from what you posted for me to make any headway.

[Domin]

I got almost the same error, also reportede in the x64 error tread here, im not running netlimiter or any other software like that, here is my error dump header, shouldt i pm you the files Yil ?

Thu Jul 30 11:34:49 2009 - ioFTPD v7.0.1
Unhandled exception: Access Violation (0xC0000005)
Address: 0x7D4D8815 [attempting to write data to 0x00000002]
PID=2864, PATH=C:\ioFTPD\system\ioFTPD.exe
Thread ID: 3252

System information:
Processor #0 Name: AMD Athlon(tm) 64 Processor 3500+
Processor #0 Identifier: AMD64 Family 15 Model 63 Stepping 2
OS: Windows 5.2 (build 3790)
Registry: Microsoft Windows XP
Decoded: Server 2003 - Service Pack 2
Page size: 4096

[Yil]

Domin: Does it crash on startup or only after a bit of light use? Which version of nod32 are you using? v3 (not sure about v4) had an internet protection piece along with the anti-virus. I've seen that cause problems before, try disabling just that piece for a bit to see if it affects the problem. PM me the full crashlog file and I'll take a look and send you the FTP info if I need the dumps.

[Domin]

Thank you so much for the help Yil, disabeling NOD did the trick :)

As soon as i enable it again it kills ioftpd.exe after a few sec of runtime (as soon as it reads the default.vfs and it got other paths than the root path)

Now to get this fixed, is this something you need to change or shouldt i write to the NOD team to get them to fix it ?

Thanks for your greate work :cool:

[Yil]

I think talking to the NOD folk is probably the way to go. Somewhere I found an email of theirs to a client posted on the web with them acknowledging a problem in v3. It's entirely possible that ioFTPD is at fault somehow but given the similar problem with v3 I'm guessing the client dll library might not be that different. They however can just download the v7 source and/or grab the regular release and the .pdb to debug it. I have a closed source dll so that makes it really tough...

[Domin]

Okie, im gonna talk to them and post here what they report back.

However i wouldt like to stat that i have been running io in every version from 5.x.x and until latest build had no problem what so ever with NOD, and im also running V4 not V3, you can see the version and build in my signature ;-)