[cpx] FW: [IDS-9843139] apache restart

["Brian Haines" <providertalk@xxxxxxxxxxxxxxxx>]

Happy Holidays!

Is the resolution that Sam and the level II tech are referring to currently
in the works for some future upgrade to the CPX Control Panel? 

If this is really a problem with CPX then why does it only effect VPSv3
accounts? No issues with any VPSv2.

If CPX is going to be the Control Panel for the VPS then this kind of issue
needs to be resolved immediately and not rolled out with the next set of
updates. 

...- .--. ... / .... . .-.. .-..
Brian Haines 954-434-1968
 


-----Original Message-----
From: Samuel D [mailto:support@xxxxxxxxxxxx] 
Sent: Wednesday, December 26, 2007 10:00 AM
To: brian@xxxxxxxxxxxxxxxx
Subject: Re: [IDS-9843139] apache restart

Brian,

Thank you for contacting Technical Support regarding your issue. Your case
reference number is IDS-9843139. Please make note of the case number for
future reference. To update an existing case, reply to this email keeping
the same subject line.

After working with a tech II for a while and looking a several different
things we decided we wonted to try a couple of things to see if we can get
this problem resolved.

First thing that we found was that there were several graceful restarts
within the crontab, it looks like this was changed once before but
additional websites may have been added sense the time these were first
changed.  We changed all the graceful restarts to read just restart in hopes
this may help with the problem.

The second thing that we noticed was that you have a large amount of
restarts occurring at the same time, sixteen apache restarts occurring  at
ruffly the same time every night.  After speaking with a tech II he
suggested that you could try creating a script on the server that would run
these sixteen commands without running the apache restart.

To do this you would create a script on your server that would contain the
data for your current save log rotation removing all but one of the apache
restart commands, you would than remove these entries from the crontab and
replace them with a single entry to run the script file you have created.
If you choose to do this I would suggest creating a backup of the current
crontab folder so that it can be reverted back to if things don't runs the
way that you originally planned.

We do not support custom scripting but if you send in a request there may be
someone here who could help guide you threw the setup process for this
script.

We apologize for any inconvenience this has caused you and ask you to pleas
contact us again if you have any further questions for us.

Best regards,

S. Davis
(888)224-9346
Technical Support
support@xxxxxxxxxxxx


======================================================================
This is <cpx@xxxxxxxxxxxxx>      <http://www.groupmail.org/lists/cpx/>
Before posting a question, please search the archives (see above URL).