Opened 7 years ago

Closed 16 months ago

#8596 closed Bug report (invalid)

Crashes Occasionally

Reported by: gheissenberger Owned by:
Priority: normal Component: FileZilla Server
Keywords: Application Error Cc:
Component version: Operating system type: Windows
Operating system version: Server 2003 R2

Description

We host a filezilla 0.9.41 server on a Windows Server 2003 R2 box. We are aiming for 100% uptime, however the service infrequently crashes. For example so far this year it crashed Jan 19 and April 10. It was up without restarts in between that time.
We discover the problem when a user reports they are unable to connect. (Windows service monitoring based alerts were not triggered, interestingly.) The server interface shows unable to connect to server. The event viewer application logs at this point show no problems. Attempt to launch filezilla server.exe and service comes back up. Error then appears in application log:

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 4/10/2013
Time: 8:44:09 PM
User: N/A
Computer: EDI-NODE0
Description:
Faulting application , version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

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 20 30 2e ure 0.
0018: 30 2e 30 2e 30 20 69 6e 0.0.0 in
0020: 20 75 6e 6b 6e 6f 77 6e unknown
0028: 20 30 2e 30 2e 30 2e 30 0.0.0.0
0030: 20 61 74 20 6f 66 66 73 at offs
0038: 65 74 20 30 30 30 30 30 et 00000
0040: 30 30 30 000

This seems to have been reported here: https://forum.filezilla-project.org/viewtopic.php?f=6&p=97108 but I don't see a bug report so I thought I'd put one in.

Change History (2)

comment:1 Changed 6 years ago by Tim Kosse

Status: newmoreinfo

Are you still experiencing this in FileZilla Server 0.9.42 or newer?

comment:2 Changed 16 months ago by Kurt McKee

Resolution: invalid
Status: moreinfoclosed

Closing because requested information has not been provided.

Note: See TracTickets for help on using tickets.