Cerberus Crashes & Restarts

Think you've found a bug? Post a description here.

Moderator: Serin

Post Reply
JamesP
Posts: 2
Joined: Thu Apr 24, 2008 9:29 am

Cerberus Crashes & Restarts

Post by JamesP » Thu Apr 24, 2008 9:35 am

I am running Cerberus as a service using FireDaemon. Using Cerberus built in feature did not work for me as I need to start the service using a specific domain account that has rights to some of the directories Cerberus serves.

I selected the 'Use different IP for PASV check box to cure an issue with PASV logins being rejected which worked. Later the Service failed (see event log entry below) and when it restarted the Interface setting had reset.

I need the setting to be persistent so I either need to ensure it retains that setting if it restarts or that it does not restart in the first place.


Event Type: Information
Event Source: Application Error
Event Category: (100)
Event ID: 1004
Date: 4/24/2008
Time: 11:51:57 AM
User: N/A
Computer: UKFTP
Description:
Reporting queued error: faulting application Cerberus.exe, version 2.4.7.0, faulting module comctl32.dll, version 6.0.3790.3959, fault address 0x0001199e.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 43 65 72 ure Cer
0018: 62 65 72 75 73 2e 65 78 berus.ex
0020: 65 20 32 2e 34 2e 37 2e e 2.4.7.
0028: 30 20 69 6e 20 63 6f 6d 0 in com
0030: 63 74 6c 33 32 2e 64 6c ctl32.dl
0038: 6c 20 36 2e 30 2e 33 37 l 6.0.37
0040: 39 30 2e 33 39 35 39 20 90.3959
0048: 61 74 20 6f 66 66 73 65 at offse
0050: 74 20 30 30 30 31 31 39 t 000119
0058: 39 65 9e

JamesP
Posts: 2
Joined: Thu Apr 24, 2008 9:29 am

Post by JamesP » Thu Apr 24, 2008 9:48 am

The error that broke the FTP by causing it to restart occurred at 9.44 and again at 11:59.

I started with a test restarts of the FTP server service; it lost the corrected interface setting on the first test.

I launched Cerberus as a foreground App instead of a Service and enforced the Interface settings again.

Then I shut down and launched as a service again… the setting was retained.

I forced a couple of restarts and the setting remained persistent.

This should mean that even if it fails and restarts it should not break the client access again.

I would still like to know if anyone can tell me why the MS's comctl32.dll is crashing.

Post Reply