again suspended!

[jose.ph8923]

can you provide to us the exact thing what causes our site to be suspended? i've already made some changes on wordpress plus i am only receiving generic suspension notification and i believe it would be useless if you cannot provide the exact location on where the high system usage is occurring ..

---------- Post added at 07:05 AM ---------- Previous post was at 06:58 AM ----------

i really don't understand i just requested for unsuspension and then it goes to suspended again... what's wrong? its this a glitch or something else?/?

---------- Post added at 07:07 AM ---------- Previous post was at 07:05 AM ----------

im trying to backup my database if you don't allow me to backup my database, can you make a backup and i'll download later??? anyone would like to say something from the support staff?

---------- Post added at 07:08 AM ---------- Previous post was at 07:07 AM ----------

im trying to backup my database if you don't allow me to backup my database, can you make a backup and i'll download later??? anyone would like to say something from the support staff?

[Livewire]

It's in your crons. That's a major problem considering they'll execute every time you do an unsuspend.

At last hit, they were using 114% of the cpu, which is very bad, as that's actually more than 1 full CPU being dedicated to processing wp-cron.php and the streamlogic cron.


What I can tell you is it is quite likely the streamlogic cron, as the wp-cron goes away after a few seconds. The streamlogic cron doesn't.


I'm running an unsuspension from here, but my guess is it will suspend you again shortly because of it being on a cron.

[jose.ph8923]

wait i'll disable the wp cron on stmlogic

---------- Post added at 07:25 AM ---------- Previous post was at 07:17 AM ----------

thanks for a quick overview, now I've disabled the wp-cron.php from running on streamlogic, can you tell me now if there is already a process, and if there is a process still can you kill it for me? thank you.

It's in your crons. That's a major problem considering they'll execute every time you do an unsuspend.

At last hit, they were using 114% of the cpu, which is very bad, as that's actually more than 1 full CPU being dedicated to processing wp-cron.php and the streamlogic cron.


What I can tell you is it is quite likely the streamlogic cron, as the wp-cron goes away after a few seconds. The streamlogic cron doesn't.


I'm running an unsuspension from here, but my guess is it will suspend you again shortly because of it being on a cron.