[Case 74677] EACCELERATOR can't restore parent class

[rasa]

sorry for mix every thing
but what are these error that they appeared from no where after a simple update ?


[Tue Sep 10 17:16:02 2013] [warn] mod_fcgid: process 39593 graceful kill fail, sending SIGKILL
[Tue Sep 10 17:16:02 2013] [warn] mod_fcgid: process 40150 graceful kill fail, sending SIGKILL
[Tue Sep 10 17:16:02 2013] [warn] mod_fcgid: process 40097 graceful kill fail, sending SIGKILL
[Tue Sep 10 17:16:02 2013] [warn] mod_fcgid: process 39595 graceful kill fail, sending SIGKILL

 

[ScottTh]

sorry for mix every thing
but what are these error that they appeared from no where after a simple update ?


[Tue Sep 10 17:16:02 2013] [warn] mod_fcgid: process 39593 graceful kill fail, sending SIGKILL
[Tue Sep 10 17:16:02 2013] [warn] mod_fcgid: process 40150 graceful kill fail, sending SIGKILL
[Tue Sep 10 17:16:02 2013] [warn] mod_fcgid: process 40097 graceful kill fail, sending SIGKILL
[Tue Sep 10 17:16:02 2013] [warn] mod_fcgid: process 39595 graceful kill fail, sending SIGKILL

Hi rasa,

I'm sorry to see that you are still experiencing issues. I'm concerned that some of these problems might not be caused solely by eAccelerator. In order to get you the quickest service please open a support ticket. Our techs will be able to help diagnosis what is going on: Submit a Ticket

 

[kdean]

Can posters other than rasa state whether they're eaccelerator is working again with the latest EasyApache? I'm using the last working version before people started having problems and it doesn't seem clear here whether it's working for most people or not again. I'm using apache 2.2 / FCGID and mostly an eaccelerator /dev/shm file cache to share amongst processes in memory.

I don't want to upgrade and break everything, so whatever yes or no responses out there would be helpful. Thanks.

 

[kdean]

Well, I went ahead and ran Easy Apache and while my websites appear to be working fine and Eaccelerator cache files are being created, I get the error message as mentioned at the beginning (and supposedly fixed) of this thread repeatedly in the Apache error_log.

eAccelerator: Unable to change cache directory /dev/shm/eaccelerator permissions

Note that I have the cache folder different than the default. Are prior fixes specific to the default location?

Anyone have any thoughts on how to get rid of this error?

 

[kdean]

It seems that I only got those error messages the first hour and a half after starting up, maybe the time it took to create cache sub-folders for all or most of my accounts. If that's all I can probably live with it. Still a little odd though.

 

[jecro77]

Tried this week the latest eaccelerator with mod_ruid2 and PHP 5.3.27. Doesn't work with Typo3 and other CMS. In the error_log are some" Invalid opcode" messages.

Now I'm trying xcache... Works till now like a charm.

 

[ScottTh]

Tried this week the latest eaccelerator with mod_ruid2 and PHP 5.3.27. Doesn't work with Typo3 and other CMS. In the error_log are some" Invalid opcode" messages.

Now I'm trying xcache... Works till now like a charm.

Hi jecro77,

Thanks for passing on that information to us. I'm glad that XCache is working well for you!