Hey all,

after extracting Heartbeat to sites/all/modules and viewing Admin/Module my Apache (version 2.2.22) seems to crash. I get a Windows (Vista 64bit) error message "Apache HTTP Server has stopped working and was closed" and the modules page never loads. I'm running WAMPServer 2.2 on my PC with PHP version 5.3.13.

When the crash happens Apache's error log looks like this:

[Mon Nov 26 19:09:02 2012] [notice] Child 6404: Child process is running
[Mon Nov 26 19:09:02 2012] [notice] Child 6404: Acquired the start mutex.
[Mon Nov 26 19:09:02 2012] [notice] Child 6404: Starting 64 worker threads.
[Mon Nov 26 19:09:02 2012] [notice] Child 6404: Starting thread to listen on port 80.
[Mon Nov 26 19:09:02 2012] [notice] Child 6404: Starting thread to listen on port 80.
[Mon Nov 26 19:09:10 2012] [notice] Parent: child process exited with status 3221225725 -- Restarting.
[Mon Nov 26 19:09:10 2012] [notice] Apache/2.2.22 (Win64) PHP/5.3.13 configured -- resuming normal operations
[Mon Nov 26 19:09:10 2012] [notice] Server built: May 13 2012 19:41:17
[Mon Nov 26 19:09:10 2012] [notice] Parent: Created child process 5684
[Mon Nov 26 19:09:10 2012] [notice] Child 5684: Child process is running

and the PHP error log seems to be empty.

I do not get similar problems with any other module I have installed. All other pages except for the Admin/Module seem to work as well. If I remove the heartbeat folder from sites/all/modules the Admin/Module page works again. I get similar results by using the /modules folder.

Any advice on this?

Comments

calmeyda’s picture

calmeyda CreditAttribution: calmeyda commented

Hi, have you get fix this?

matcorrao’s picture

matcorrao CreditAttribution: matcorrao commented

Hi guys,

This same issue is now happening for me. No kind of PHP error and apache log looks identical.

Have you ever got to fix this?

Thanks!

seanB’s picture

seanB
Primary language Dutch
Location Netherlands
CreditAttribution: seanB commented

This just happened to me as well with the same setup. Most of the time this is triggered when Drupal tries to read an info file of a module.

When I deleted the heartbeat_plugins and heartbeat_og modules, this doesn't happen anymore. Removing any other combination of modules doesn't work, so I guess the problem is in both of these submodules. Changing the content of the info files didn't work though?

Hope this helps, if I find anything more I will let you guys know..

erick_at’s picture

erick_at CreditAttribution: erick_at commented

Hey seanB,

I did what you posted, and it works fine. My question is do you have an idea if the heartbeat_plugins is something crucial for the functionality of Heartbeat?