cancel
Showing results for 
Search instead for 
Did you mean: 
redbeardrc
Level 9

After upgrading to 4.6.6 from 4.6.4 the apache service won't start

Jump to solution

After upgrading, the apache service won't start and reported the following error: disabled use of acceptex() winsock2 api

Any suggestions?

The ePO console shows it to still be at 4.6.4 and therefore not compatible.

below is the apache error log:

[Thu Mar 28 08:08:40 2013] [notice] Parent: Received shutdown signal -- Shutting down the server.

[Thu Mar 28 08:08:40 2013] [notice] Child 2720: Exit event signaled. Child process is ending.

[Thu Mar 28 08:08:41 2013] [notice] Child 2720: Released the start mutex

[Thu Mar 28 08:08:42 2013] [notice] Child 2720: All worker threads have exited.

[Thu Mar 28 08:08:42 2013] [notice] Child 2720: Child process is exiting

[Thu Mar 28 08:08:42 2013] [notice] Parent: Child process exited successfully.

[Thu Mar 28 08:10:54 2013] [notice] Apache/2.2.22 (Win32) mod_ssl/2.2.22 OpenSSL/1.0.1e configured -- resuming normal operations

[Thu Mar 28 08:10:54 2013] [notice] Server built: Mar 15 2013 14:10:51

[Thu Mar 28 08:10:54 2013] [notice] Parent: Created child process 2212

[Thu Mar 28 08:10:54 2013] [notice] Disabled use of AcceptEx() WinSock2 API

[Thu Mar 28 08:10:55 2013] [notice] Child 2212: Child process is running

[Thu Mar 28 08:10:57 2013] [crit] (OS 6)The handle is invalid.  : master_main: create child process failed. Exiting.

[Thu Mar 28 08:17:50 2013] [notice] Apache/2.2.22 (Win32) mod_ssl/2.2.22 OpenSSL/1.0.1e configured -- resuming normal operations

[Thu Mar 28 08:17:50 2013] [notice] Server built: Mar 15 2013 14:10:51

[Thu Mar 28 08:17:50 2013] [notice] Parent: Created child process 2708

[Thu Mar 28 08:17:50 2013] [notice] Disabled use of AcceptEx() WinSock2 API

[Thu Mar 28 08:17:51 2013] [notice] Child 2708: Child process is running

[Thu Mar 28 08:18:09 2013] [crit] (OS 6)The handle is invalid.  : master_main: create child process failed. Exiting.

[Thu Mar 28 08:21:51 2013] [notice] Apache/2.2.22 (Win32) mod_ssl/2.2.22 OpenSSL/1.0.1e configured -- resuming normal operations

[Thu Mar 28 08:21:51 2013] [notice] Server built: Mar 15 2013 14:10:51

[Thu Mar 28 08:21:51 2013] [notice] Parent: Created child process 3780

[Thu Mar 28 08:21:51 2013] [notice] Disabled use of AcceptEx() WinSock2 API

[Thu Mar 28 08:21:52 2013] [notice] Child 3780: Child process is running

[Thu Mar 28 08:21:52 2013] [crit] (OS 6)The handle is invalid.  : master_main: create child process failed. Exiting.

[Thu Mar 28 08:30:02 2013] [notice] Apache/2.2.22 (Win32) mod_ssl/2.2.22 OpenSSL/1.0.1e configured -- resuming normal operations

[Thu Mar 28 08:30:02 2013] [notice] Server built: Mar 15 2013 14:10:51

[Thu Mar 28 08:30:02 2013] [notice] Parent: Created child process 3100

[Thu Mar 28 08:30:02 2013] [notice] Disabled use of AcceptEx() WinSock2 API

[Thu Mar 28 08:30:03 2013] [notice] Child 3100: Child process is running

[Thu Mar 28 08:30:04 2013] [crit] (OS 6)The handle is invalid.  : master_main: create child process failed. Exiting.

Message was edited by: redbeardrc on 3/28/13 9:02:57 AM CDT
0 Kudos
1 Solution

Accepted Solutions
redbeardrc
Level 9

Re: After upgrading to 4.6.6 from 4.6.4 the apache service won't start

Jump to solution

After working with support the issue was traced to a problem where apache had an "unknown" issue with C:\Windows\SysWOW64\KernelBase.dll

The resolution was to backup the newly updated 4.6.6 directories and database, re-install 4.6.6 clean and restore.

We were unable to determine the root cause. But I suspect, and this is just a guess on my part, is was caused by the OS being possibly unstable during the install.

P.S. IIS is / was not installed on this server.

Application Log entry of error:

Faulting application name: Apache.exe, version: 2.2.22.0, time stamp: 0x51438d63

Faulting module name: KERNELBASE.dll, version: 6.1.7600.17206, time stamp: 0x50e6605e

Exception code: 0xc06d007e

Fault offset: 0x0000c41f

Faulting process id: 0xe7c

Faulting application start time: 0x01ce2bcd2bae8a5a

Faulting application path: C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Apache2\bin\Apache.exe

Faulting module path: C:\Windows\syswow64\KERNELBASE.dll

4 Replies
waningmcafan
Level 7

Re: After upgrading to 4.6.6 from 4.6.4 the apache service won't start

Jump to solution

I am experiencing the very same problem:

[Thu Mar 28 07:37:05 2013] [notice] Apache/2.2.22 (Win32) mod_ssl/2.2.22 OpenSSL/1.0.1e configured -- resuming normal operations

[Thu Mar 28 07:37:05 2013] [notice] Server built: Mar 15 2013 14:10:51

[Thu Mar 28 07:37:05 2013] [notice] Parent: Created child process 8052

[Thu Mar 28 07:37:06 2013] [notice] Disabled use of AcceptEx() WinSock2 API

[Thu Mar 28 07:37:07 2013] [notice] Child 8052: Child process is running

[Thu Mar 28 07:37:19 2013] [crit] (OS 6)The handle is invalid.  : master_main: create child process failed. Exiting.

Starting to look at different vendor for my security needs.  It seems McAfee never fails to let me down.

0 Kudos
jeffreychirino
Level 10

Re: After upgrading to 4.6.6 from 4.6.4 the apache service won't start

Jump to solution

Do you have IIS active on the server? If so, please stop the service, start apache and restart IIS.

0 Kudos
apoling
Level 14

Re: After upgrading to 4.6.6 from 4.6.4 the apache service won't start

Jump to solution

Hi,

for the "Disabled use of AcceptEx() WinSock2 API" please see - older - KB article: https://kc.mcafee.com/corporate/index?page=content&id=KB51321&actp=search&viewlocale=en_US&searchid=...

This is not an error as per this article.

There is a way to set Apache log to debug mode, if you are willing, you can troubleshoot this issue that way. Here is the Log file guide:

https://kc.mcafee.com/resources/sites/MCAFEE/content/live/PRODUCT_DOCUMENTATION/23000/PD23209/en_US/...

In addition, it may be worth taking a look at the upgrade logs as well.

Hope this helps.

Attila

0 Kudos
redbeardrc
Level 9

Re: After upgrading to 4.6.6 from 4.6.4 the apache service won't start

Jump to solution

After working with support the issue was traced to a problem where apache had an "unknown" issue with C:\Windows\SysWOW64\KernelBase.dll

The resolution was to backup the newly updated 4.6.6 directories and database, re-install 4.6.6 clean and restore.

We were unable to determine the root cause. But I suspect, and this is just a guess on my part, is was caused by the OS being possibly unstable during the install.

P.S. IIS is / was not installed on this server.

Application Log entry of error:

Faulting application name: Apache.exe, version: 2.2.22.0, time stamp: 0x51438d63

Faulting module name: KERNELBASE.dll, version: 6.1.7600.17206, time stamp: 0x50e6605e

Exception code: 0xc06d007e

Fault offset: 0x0000c41f

Faulting process id: 0xe7c

Faulting application start time: 0x01ce2bcd2bae8a5a

Faulting application path: C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Apache2\bin\Apache.exe

Faulting module path: C:\Windows\syswow64\KERNELBASE.dll