[11.25 Current] apache restarting every hour

[Reado]

I didn't have a problem downgrading to RELEASE however I used the --force option just to be sure.

[Cristi4n]

yes, maybe I'm an idiot, anyway I completely forget about RELEASE. Thanks.

[cpanelkenneth]

We are testing a testing a redesign of the log processing mechanism that will significantly reduce the number of restarts. This will be in place before publishing cPanel 11.25 RELEASE.

For servers that are experiencing hundreds of graceful restarts during log processing we recommend downgrading to cPanel 11.24 ( change to RELEASE or STABLE ).

[konrath]

Hello

9 servers updated, 9 server with same problem.

I do not understand why I can upgrade to 11.25 if this version has a critical bug.

Should be locked to upgrade to version 11.25

I downgraded and now everything is ok. I look forward solution to this problem.

I need to reactivate the roubcube

Thank you
Konrath

[hostmedic]

What is the status of this now?
is it safe to be on 11.25?

[factor]

same question, it is safe to upgrade to 11.25 now?

regards,

[Reado]

Out of interest why do you want to upgrade? It's not really any different to 11.24 that I can see. It's still missing MySQL 5.1 and phpMyAdmin 3.1.

Can cPanel shed any light as to how 11.25 is different to 11.24 please?

[Infopro]

You might like to read the release note for 11.25 located here:
ReleaseNotes < AllDocumentation < TWiki

[Reado]

Thanks. Do you know when the MySQL 5.1 and phpMyAdmin 3.1 upgrades will be featured?

[Infopro]

No I don't unfortunately, what I do know is this, the cPanel team seem to work 24/7/365 on many fronts, so it will be ASAP, I'm sure of it.

[hostmedic]

I did a test today - and the multiple restarts are still there... so I would venture to say its not ready yet...

BTW - 11.25 does look nice - has some extra little things (like in the migration / transfers)

I am pleased w/ where cPanel is going w/ this - but ... its not ready for a prime time system with lots of sites sadly

Awesome work - now if I can just be patient enough to sit back and wait :-)

[mike25]

upgraded a box today to 11.25 current to get around the roundcube php load issue. now the box restarts apache near constantly while running cpanellogd. load goes through the roof, not a good idea. will probably just downgrade and disable roundcube and deal with the complaints.

[cPanelDon]

upgraded a box today to 11.25 current to get around the roundcube php load issue. now the box restarts apache near constantly while running cpanellogd. load goes through the roof, not a good idea. will probably just downgrade and disable roundcube and deal with the complaints.

In the latest EDGE builds the described restarts during log processing (e.g., running cpanellogd) are reduced to no more than 3 as per the change log entry for EDGE build number 40716, dated "2009-10-27 16:40:35"; when ready the more recent fixes in EDGE will make their way into the next CURRENT build.

For a more verbose listing of detailed fixes and enhancements please reference our official change log as available via the following link:
http://changelog.cpanel.net/

[mike25]

In the latest EDGE builds the described restarts during log processing (e.g., running cpanellogd) are reduced to no more than 3 as per the change log entry for EDGE build number 40716, dated "2009-10-27 16:40:35"; when ready the more recent fixes in EDGE will make their way into the next CURRENT build.

For a more verbose listing of detailed fixes and enhancements please reference our official change log as available via the following link:
cPanel - The Leading Control Panel - Change Log

I am glad a fix is on the way, but I should not have to update to an edge build to solve a bug. In the event that a bug makes it down to the release branch, shouldnt the fix then also be applied to that next release version? I suspect I will just introduce more issues by going with an edge build.

[ChrisRHS]

I was having this issue on a couple of servers when we upgraded. To fix the problem, run EasyApache and rebuild, you can use the exact same settings as the last build. Once I did that, the problems went away.

Worked for me, give it a shot.