account suspended twice when installing Drupal openpublish

[azamkandy]

account suspended twice when installing Drupal openpublish for the reason of

" You have been suspended for high system resource usage. Accounts are suspended for usage when they are detected to have consistently high cpu usage, memory usage, or process amounts. This is an automatic suspension, you're able to unsuspend yourself immediately. Warning 2 of 3"

Any solutions please!!!

your suspension reason code is SPND_RUSAGE2
your account's queue id code is: FTQQE8K2QKOQ

[Anna]

Yes, does seem as the install procedure use up a lot cpu. Not sure if we can do anything about that though, as that would probably be a question for the developers of Drupal openpublish.

Thu 12 Nov 2009 00:43:22 / 1258008202:
cpu: 123.000
mem: 0.200
ctm: 00:00:01
commands: (1 total)

cpu: 123.000 means that you're using 100% of one cpu and 23% of a second one.


If it had only been one or two peak occurrences you would probably not have been suspended, but it stays high long enough to be flagged. Is there any way you can "pause" during installation? Meaning wait a little before clicking "next" button, assuming there is more then one step. I'm not entirely sure that would help as it's hard to tell which part of installation causes it.

[azamkandy]

No actually i wasn't started the installation i just open the page install.php and account suspended ..
How to reactivate the acount first and after that how to install openpublish??



Ticket ID: NQI-746591

[azamkandy]

Drupal says "

Sorry for your troubles. It is well documented that OpenPublish does, indeed, consume a lot of resources at the time of installation. In the next couple of weeks a new version is coming out that has an overhauled installation procedure that rectifies this situation - which is considerably a bigger problem on shared hosts, obviously. One thing people have had success with is to install OpenPublish locally, then move the files and DB over to your shared host.

Thanks,

[Jarryd]

Hello, the best way to go about it then would be either wait for the new release, or install it on a local webserver such as wamp and then copy the files from your machine to your hosting account via FTP.