0.9.44 beta "Faulting module name: libeay32.dll"

Need help with FileZilla Server? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Message
Author
dwingerson
500 Syntax error
Posts: 12
Joined: 2014-04-22 22:09
First name: David
Last name: Wingerson

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#16 Post by dwingerson » 2014-07-29 16:00

The link is invalid I get

Code: Select all

Not Found

The requested URL /codesquid/temp/FileZilla_Server-TLS_test2.exe was not found on this server.

User avatar
botg
Site Admin
Posts: 31605
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#17 Post by botg » 2014-07-29 16:28

Thanks for reporting. The link is working now.

leave_my_name_out
500 Command not understood
Posts: 5
Joined: 2014-05-20 14:27
First name: thomas
Last name: notimportant

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#18 Post by leave_my_name_out » 2014-08-18 07:22

installed the test2 version ~10 days ago, no service crash since then.
looking good so far!

thx for the help and the fixed exe, appreciated!

User avatar
botg
Site Admin
Posts: 31605
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#19 Post by botg » 2014-08-18 08:01

Note the test version is already outdated. There's FileZilla Server 0.9.46 by now.

leave_my_name_out
500 Command not understood
Posts: 5
Joined: 2014-05-20 14:27
First name: thomas
Last name: notimportant

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#20 Post by leave_my_name_out » 2014-08-18 11:03

didn't notice.... just been checking this thread here for news on the issue
since only a few users seem to have (had) the same problem and nobody left feedback about the test2.exe I couldn't tell if you are working on it at all or just waiting for replys or even chilling somewhere at the beach (holiday season ^^)

would have made sense to add some info here and close the thread if the bug has been fixed ;-)

so that 0.9.46 is safe to install for everybody now? no "faulting module" (for a few of us) any more?
I can't tell if one of those two fixes listed in the version tracker addresses the issue with the libeay32.dll and I don't dare to switch without knowing for sure it's stable now.
Bugfixes and minor changes:

Fix stalling or improperly terminated connections when using FTP over TLS
Fix crash with enabled speed limits
thanks!

User avatar
boco
Contributor
Posts: 24156
Joined: 2006-05-01 03:28
Location: Germany

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#21 Post by boco » 2014-08-18 16:39

According to the other thread (viewtopic.php?f=6&t=33565) the crashes continue for that user. Doesn't need to be the same for you, though.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
All FileZilla products fully support IPv6. http://worldipv6launch.org
### END SIGNATURE BLOCK ###

dwingerson
500 Syntax error
Posts: 12
Joined: 2014-04-22 22:09
First name: David
Last name: Wingerson

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#22 Post by dwingerson » 2014-08-18 16:44

I am still testing this we have cloned our production FTP server and I am attempting to recreate the error. There does not seem to be a pattern associated with fore mentioned issue. I haveNOT yet applied the patch yet until I can verify I can even reproduce the issue on the cloned server. I am however continuing efforts to isolate the problem.

dwingerson
500 Syntax error
Posts: 12
Joined: 2014-04-22 22:09
First name: David
Last name: Wingerson

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#23 Post by dwingerson » 2014-08-18 16:48

This was a suggestion from one of the Developers at OpenSSL. Again I am waiting to reproduce on the clone.

Code: Select all

> This was present only since the new binaries provided to address heart 
> bleed there are others having challenges with this. It seems somehow 
> related to vmware possibly here is the original thread.
>
> https://forum.filezilla-project.org/viewtopic.php?f=6&t=32837&p=124817#p124817


It's not clear (to me at least) what the cause is from that information. As a temporary measure you could try downgrading the version of libeay32.dll ONLY to 1.0.1f to see if that fixes your problem. The critical security fixes are in ssleay32.dll so you'd still get those.

Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org

User avatar
boco
Contributor
Posts: 24156
Joined: 2006-05-01 03:28
Location: Germany

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#24 Post by boco » 2014-08-18 16:48

That's the crux of relying on third-party components. Especially OpenSSL did have bad press in the last months...
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
All FileZilla products fully support IPv6. http://worldipv6launch.org
### END SIGNATURE BLOCK ###

User avatar
boco
Contributor
Posts: 24156
Joined: 2006-05-01 03:28
Location: Germany

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#25 Post by boco » 2014-08-18 16:51

So they want you to use libssleay32.dll 1.0.1f and ssleay32.dll 1.0.1h. You can try that, the security fixes seem to be in the latter while the crashes happen inside the former.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
All FileZilla products fully support IPv6. http://worldipv6launch.org
### END SIGNATURE BLOCK ###

dwingerson
500 Syntax error
Posts: 12
Joined: 2014-04-22 22:09
First name: David
Last name: Wingerson

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#26 Post by dwingerson » 2014-08-18 16:52

Correct that's how I read that too.

User avatar
botg
Site Admin
Posts: 31605
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#27 Post by botg » 2014-08-18 18:57

The openssl binaries shipped with FileZilla currently include the attached patch for a nullpointer dereference observed by some users:
nullptr_dereference.diff
(470 Bytes) Downloaded 70 times

somebody08
550 File not found
Posts: 35
Joined: 2014-07-02 03:29
First name: A
Last name: T

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#28 Post by somebody08 » 2014-08-22 16:06

Faulting application name: FileZilla Host.exe, version: 0.9.46.0, time stamp: 0x53de0ab0
Faulting module name: libeay32.dll, version: 1.0.2.0, time stamp: 0x53de0305
Exception code: 0xc0000005
Fault offset: 0x0000478e
Faulting process id: 0x16bc
Faulting application start time: 0x01cfbd01078c005d

I continue to be available to test new versions as needed, as I can replicate the crash with consistency every few days.

dwingerson
500 Syntax error
Posts: 12
Joined: 2014-04-22 22:09
First name: David
Last name: Wingerson

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#29 Post by dwingerson » 2014-08-22 18:26

As of yesterday I am running on 0.9.45 and I have reverted libeay32.dll only to the version provided in 0.9.43. Per the suggestion of one of the Core Developers for OpenSSL as seen below.
libeay32.dll
File Version 1.0.1.5
Product Version 1.0.1e
It seems for me every few days it will happen. Can you confirm that you are using a virtualized server also?
> This was present only since the new binaries provided to address heart
> bleed there are others having challenges with this. It seems somehow
> related to vmware possibly here is the original thread.
>
> viewtopic.php?f=6&t=32837&p=124817#p124817
>

It's not clear (to me at least) what the cause is from that information. As a temporary measure you could try downgrading the version of libeay32.dll ONLY to 1.0.1f to see if that fixes your problem. The critical security fixes are in ssleay32.dll so you'd still get those.

Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
These errors below are from 2014-08-19 with stock version of 0.9.45 the below information is from event viewer there was actually 2 crashes one at 1:12:36 and again at 1:36:16. From analysis I have found that there was activity going on at this time files were being transfered.

Code: Select all

Faulting application name: FileZilla Server.exe, version: 0.9.45.0, time stamp: 0x53931dfc
Faulting module name: libeay32.dll, version: 1.0.1.8, time stamp: 0x539303fb
Exception code: 0xc0000005
Fault offset: 0x00003569
Faulting process id: 0x15e0
Faulting application start time: 0x01cfbb6c574077b3
Faulting application path: C:\Program Files (x86)\FileZilla Server\FileZilla Server.exe
Faulting module path: C:\Program Files (x86)\FileZilla Server\libeay32.dll
Report Id: bc966c73-2762-11e4-b8d9-005056b45797

Code: Select all

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FileZilla Server.exe
P2: 0.9.45.0
P3: 53931dfc
P4: libeay32.dll
P5: 1.0.1.8
P6: 539303fb
P7: c0000005
P8: 00003569
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FileZilla Server_5f62e218eb5cb337599b9828a5b24190fb69_853b85d1

Analysis symbol: 
Rechecking for solution: 0
Report Id: bc966c73-2762-11e4-b8d9-005056b45797
Report Status: 0

Code: Select all

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FileZilla Server.exe
P2: 0.9.45.0
P3: 53931dfc
P4: libeay32.dll
P5: 1.0.1.8
P6: 539303fb
P7: c0000005
P8: 00003569
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FileZilla Server_5f62e218eb5cb337599b9828a5b24190fb69_853b85d1

Analysis symbol: 
Rechecking for solution: 0
Report Id: bc966c73-2762-11e4-b8d9-005056b45797
Report Status: 4
private information was removed

Code: Select all

(000749) 8/19/2014 1:12:39 AM - USERACCOUNT (###.###.###.###)> PASV
(000749) 8/19/2014 1:12:39 AM - USERACCOUNT (###.###.###.###)> 227 Entering Passive Mode (206,41,51,43,196,174)
(000749) 8/19/2014 1:12:39 AM - USERACCOUNT (###.###.###.###)> STOR Filename.xls
(000749) 8/19/2014 1:12:39 AM - USERACCOUNT (###.###.###.###)> 150 Opening data channel for file upload to server of "/folder1/folder2/folder3/Folder4/Filename.xls"
(000749) 8/19/2014 1:12:41 AM - USERACCOUNT (###.###.###.###)> SSL connection for data connection established
FileZilla Server version 0.9.45 beta started
Initializing Server.
Creating listen socket on port 21...
Creating listen socket on port 990...
Server online.

Code: Select all

Faulting application name: FileZilla Server.exe, version: 0.9.45.0, time stamp: 0x53931dfc
Faulting module name: libeay32.dll, version: 1.0.1.8, time stamp: 0x539303fb
Exception code: 0xc0000005
Fault offset: 0x00003569
Faulting process id: 0x15e0
Faulting application start time: 0x01cfbb6c574077b3
Faulting application path: C:\Program Files (x86)\FileZilla Server\FileZilla Server.exe
Faulting module path: C:\Program Files (x86)\FileZilla Server\libeay32.dll
Report Id: bc966c73-2762-11e4-b8d9-005056b45797

Code: Select all

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FileZilla Server.exe
P2: 0.9.45.0
P3: 53931dfc
P4: libeay32.dll
P5: 1.0.1.8
P6: 539303fb
P7: c0000005
P8: 0000355f
P9: 
P10: 

Attached files:
C:\Windows\Temp\WERE0AC.tmp.appcompat.txt
C:\Windows\Temp\WERE57E.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WERE58E.tmp.hdmp
C:\Windows\Temp\WERECEF.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FileZilla Server_56b243dbe648a9297451d5394c7d7a4f5cbaf2_cab_8511ed4a

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6e7c8e53-275f-11e4-b8d9-005056b45797
Report Status: 0

Code: Select all

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FileZilla Server.exe
P2: 0.9.45.0
P3: 53931dfc
P4: libeay32.dll
P5: 1.0.1.8
P6: 539303fb
P7: c0000005
P8: 0000355f
P9: 
P10: 

Attached files:
C:\Windows\Temp\WERE0AC.tmp.appcompat.txt
C:\Windows\Temp\WERE57E.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WERE58E.tmp.hdmp
C:\Windows\Temp\WERECEF.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FileZilla Server_56b243dbe648a9297451d5394c7d7a4f5cbaf2_cab_8511ed4a

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6e7c8e53-275f-11e4-b8d9-005056b45797
Report Status: 4
private information was removed

Code: Select all

(000012) 8/19/2014 1:36:16 AM - USERACCOUNT (###.###.###.###)> PASV
(000012) 8/19/2014 1:36:16 AM - USERACCOUNT (###.###.###.###)> 227 Entering Passive Mode (206,41,51,43,196,226)
(000012) 8/19/2014 1:36:16 AM - USERACCOUNT (###.###.###.###)> STOR Folder4
(000012) 8/19/2014 1:36:16 AM - USERACCOUNT (###.###.###.###)> 150 Opening data channel for file upload to server of "/Folder1/Folder2/Folder3/008/Folder4"
(000012) 8/19/2014 1:36:16 AM - USERACCOUNT (###.###.###.###)> SSL connection for data connection established
(000012) 8/19/2014 1:36:16 AM - USERACCOUNT (###.###.###.###)> 226 Successfully transferred "/Folder1/Folder2/Folder3/008/Folder4"
FileZilla Server version 0.9.45 beta started
Initializing Server.
Creating listen socket on port 21...
Creating listen socket on port 990...
Server online.

somebody08
550 File not found
Posts: 35
Joined: 2014-07-02 03:29
First name: A
Last name: T

Re: 0.9.44 beta "Faulting module name: libeay32.dll"

#30 Post by somebody08 » 2014-08-23 02:12

I am not using a virtualized server.
I have a Windows task that monitors for when FileZilla crashes and relaunches it /start immediately. (Workaround I am using to keep the server up)

Code: Select all

------------------
System Information
------------------
Time of this report: 8/22/2014, 19:10:08
       Machine name: FTP
   Operating System: Windows Server 2012 Standard 64-bit (6.2, Build 9200) (9200.win8_gdr.140502-1507)
           Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
       System Model: PowerEdge R520
               BIOS: Phoenix ROM BIOS PLUS Version 1.10 1.6.7
          Processor: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz (12 CPUs), ~1.9GHz
             Memory: 65536MB RAM
Available OS Memory: 65490MB RAM
          Page File: 19255MB used, 46235MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.02.9200.16384 64bit Unicode
Attachments
Clipboard01.jpg
Clipboard01.jpg (45.17 KiB) Viewed 2316 times

Post Reply