logoon  windows
Apache Lounge
Webmasters

 


About

Forum Index Downloads Search Forum Register Log in  RSS Apache Lounge


Keep Server Online

If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.

or

Bitcoin

A donation makes a contribution towards the costs, the time and effort that's going in this site and building.

Thank You! Steffen

Apache Lounge is not sponsored by anyone.

Your donations will help to keep this site alive and well, and continuing the building of the binaries.




Apache server Crashes at libeay32.dll

 
Post new topic   Reply to topic    Apache Forum Index -> Apache



View previous topic :: View next topic  
Author Message
AdarshJain



Joined: 09 Mar 2009
Posts: 4
Location: bangalore

PostPosted: Mon 09 Mar '09 23:46    Post subject: Apache server Crashes at libeay32.dll Reply with quote

Hi All,

We have customized Apache server for our needs. For FIPS certification of the product we have enabled the FIPS mode for the Apache server by building FIPS compatible openSSL library. To accomplish this we built the FIPS compatible openSSL source code and used the resultant libraries such as libeay32.lib and ssleay32.dll in the Apache server.

When we install and run the FIPS enabled Apache server, server crashes.
Only in installed version it crashes. When i run the the source code it works fine.

The error log i get is given below

Faulting application Apache.exe, version 1.0.0.1, faulting module libeay32.dll, version 0.9.8.10, fault address 0x0002d3e4.

Please anybody help us to solve this issue.

Thanks in advance.
Adarsh.
Back to top
glsmith
Moderator


Joined: 16 Oct 2007
Posts: 1642
Location: Sun Diego, CA, USofA

PostPosted: Tue 10 Mar '09 2:18    Post subject: Reply with quote

Check Windows/System32 and anything in your PATH for other copies of libeay32.dll and ssleay32.dll

If you got an older version and Apache for some reason is loading it, or Windows has loaded it for something else, this crash can happen.

OR

I the Apache was compiled with a different version then same thing will happen.

Since you do not specifically state you actually built Apache from source, I'm kind of assuming you didn't. Yes you state running from source, which has me a little bewildered as well, how do you run from source?
Back to top
AdarshJain



Joined: 09 Mar 2009
Posts: 4
Location: bangalore

PostPosted: Wed 11 Mar '09 7:45    Post subject: Reply with quote

Dear Smith,

Thanks for your quick reply and here are some more details about the problem.

We did check in the Windows/System32 folder and did not find any other copies of libeay32.dll and ssleay32.dll

To clear off the confusions, here are some details.

1. Apache source code is a part of our application. But it has some plugin, written by us. Apache and the plugin together form our server.

2. We were using Openssl-0.9.7e for security. But now upgraded to Openssl-0.9.8j and Openssl-fips-1.2, to enable the server to work in FIPS mode. The server is set to work only in FIPS mode.

3. For upgradation, we have built Openssl-0.9.8j and Openssl-fips-1.2 from their source and used the resultant dlls (ssleay32 & libeay32) and libs (ssleay32 & libeay32) in our application. All older versions of these dlls are replaced.

4. When we run our application in the debug environment, the server runs fine.

5. The server runs fine even when we build our application for the release environment.

6. But the problem is only when we install our application in one of our systems and try to start the service through services.msc, that it fails to start. This system runs the server with older libeay32 and ssleay32 dlls without any glitch even now.

We suspect that we are missing some configuration on the system, which would support a FIPS-compliant application on it. Could you think of any such possibilities?

Regards,
Adarsh
Back to top
AdarshJain



Joined: 09 Mar 2009
Posts: 4
Location: bangalore

PostPosted: Wed 11 Mar '09 7:46    Post subject: Reply with quote

Dear Smith,

Thanks for your quick reply and here are some more details about the problem.

We did check in the Windows/System32 folder and did not find any other copies of libeay32.dll and ssleay32.dll

To clear off the confusions, here are some details.

1. Apache source code is a part of our application. But it has some plugin, written by us. Apache and the plugin together form our server.

2. We were using Openssl-0.9.7e for security. But now upgraded to Openssl-0.9.8j and Openssl-fips-1.2, to enable the server to work in FIPS mode. The server is set to work only in FIPS mode.

3. For upgradation, we have built Openssl-0.9.8j and Openssl-fips-1.2 from their source and used the resultant dlls (ssleay32 & libeay32) and libs (ssleay32 & libeay32) in our application. All older versions of these dlls are replaced.

4. When we run our application in the debug environment, the server runs fine.

5. The server runs fine even when we build our application for the release environment.

6. But the problem is only when we install our application in one of our systems and try to start the service through services.msc, that it fails to start. This system runs the server with older libeay32 and ssleay32 dlls without any glitch even now.

We suspect that we are missing some configuration on the system, which would support a FIPS-compliant application on it. Could you think of any such possibilities?

Regards,
Adarsh
Back to top
AdarshJain



Joined: 09 Mar 2009
Posts: 4
Location: bangalore

PostPosted: Wed 11 Mar '09 8:14    Post subject: Reply with quote

Dear Smith,

Thanks for your quick reply and here are some more details about the problem.

We did check in the Windows/System32 folder and did not find any other copies of libeay32.dll and ssleay32.dll

To clear off the confusions, here are some details.

1. Apache source code is a part of our application. But it has some plugin, written by us. Apache and the plugin together form our server.

2. We were using Openssl-0.9.7e for security. But now upgraded to Openssl-0.9.8j and Openssl-fips-1.2, to enable the server to work in FIPS mode. The server is set to work only in FIPS mode.

3. For upgradation, we have built Openssl-0.9.8j and Openssl-fips-1.2 from their source and used the resultant dlls (ssleay32 & libeay32) and libs (ssleay32 & libeay32) in our application. All older versions of these dlls are replaced.

4. When we run our application in the debug environment, the server runs fine.

5. The server runs fine even when we build our application for the release environment.

6. But the problem is only when we install our application in one of our systems and try to start the service through services.msc, that it fails to start. This system runs the server with older libeay32 and ssleay32 dlls without any glitch even now.

We suspect that we are missing some configuration on the system, which would support a FIPS-compliant application on it. Could you think of any such possibilities?

Regards,
Adarsh
Back to top


Post new topic   Reply to topic    Apache Forum Index -> Apache
Page 1 of 1