LinkBack URL
About LinkBacks...please....say something vía email so we can make something quickly.
Its only a suggestion. Thanks for reading.
Marc.
New Bee
before banning an account for "cpu abuse"....
...please....say something vía email so we can make something quickly.
Its only a suggestion. Thanks for reading.
Marc.
I don't necessarily agree with that. Why put off the convenience of everyone else on that server just for one person? While we wait for a response to your email, or for you to fix the problem, everybody else on the same server has to suffer. That's not exactly fair to everyone else.
New Bee
I suggest make a good Suspended page or if you can make it possible to every one to create his own Suspended page .
With Cpanel there is no control to any shared account (as there is in VPS), so if one of them abuse all go down, if they don't suspend it will probably do again. It's no good, ugly, and I don't like it, but... that's the way of action.Originally Posted by reboam
New Bee
So you can put a estatistic like data transfer,but in this case of cpu use of every account of shared servers,so we everyone can see if is using a lot of cpu or not.
There is a Server Status link in cPanel for the shared hosting users. It's on the left side, on the bottom, under General Server Information.
New Bee
But this is global, not by account.
How can you possibly divide the CPU usage by accounts? It's for the core of the server.
If you see a heavy load on the CPU, submit a ticket so tech support can investigate it. It's as simple as that.
Member
Perhaps now with MailFoundry taking spam load a lot of people may not be hit with high CPU usage? Is that the theory?
I am still seeing a lot of sites where images are not optimised. For instance, a 100K image being fully downloaded only to be used as a thumbnail!
Also, Cpanel allows file protection. That means people cannot use your bandwidth to download your picture onto their site.
Mark
WeeHBie
Most of the problems are caused by PHP or Perl scripts with tons of queries per second and poorly written code. 99% of the times, these are what will get suspended -- our hosting service isn't a sandbox to test them though, so if you test them locally then upload, it'd be better all round.
Member
But mostly, those scripts are from fantasico..
There are hundreds of settings that can be used to limit all the accounts. From memory use to the number of connections to the threads being used. You don't have to kill a site, just reduce the memory available, since obviously INFINITY is too high for a virtual server.
There is also a catch 22...
Virtual servers require twice as much cpu use, since each "Page" is a "Virtual Page" located in a "Virtual Path"...
If they used proper virtual server setups, they could reduce their own overhead by 25%-50%. Double that with the realistic limitations of all processing, since the master PHP.ini and APACHE.ini rules in a virtual environment. We can tell it to use 128mb for RAM, but if we are limited to 32mb in the master file... then we only get 32mb. Unless we say 12mb, then we get 12mb.
Yes, there are many settings that are DEFAULT that are highly hoggy... They are there for show... they are not there, to be all on. (They, WHB, should place a link to, or include TIPS for each of these tools, suggesting realistic settings. We are not all network admins, and those that are not, expect that WHB has already setup a nice default setting. Which apparently, they have not. Step up to the plate, make the proper default settings before you install these tools. Check to see if there are MAJOR security issues, or if these tools have expired beyond support. Warn your customers, whom you provide these tools to, about the RISKS you have just provided them with. Let them know that the tool they are using MAY get them banned if they have changed the settings, beyond the default settings.)
Yes, and there is a setting for that... it is called data limits and loop-count limits. Some settings can also be controlled inside the tools from fantastico installations. (Some)
http://www.sitepoint.com/article/mod...-endless-loops
http://www.net2ftp.org/forums/viewtopic.php?id=1306
http://www.ilovejackdaniels.com/php-...source-limits/
http://devzone.zend.com/manual/ini.core.html
Here is a novel idea... Create a USER SANDBOX ACCOUNT... Offer people the ability to test code there. (Just not MAIL or SMTP/POP3 or FSOCK commands.)
Direct them to another free server to experiment, tell them they can play all the want over there. If you want code to go bad... might as well have it go bad on another server. (Though they are hardly competition.)
Last edited by JasonD; 08-27-2007 at 11:35 AM.
WeeHBie
I agree with what you are saying on tips, etc. This is what we're putting in the Wiki we are creating.
Oh, your making a wiki... I want to help... I like to research!
WeeHBie
I've made you a 'WHB Helper', so you can see the forum that details how we plan to set all of this up.
Looking fore-ward to participation in this creation.
Another thing, as to the banning. Does that disable FTP access also, or just port:80 access? (HTTP SERVING/PROCESSING)
I would like to suggest that, possible suspect accounts, have an altered config arrangement made for that virtual server. (One with harsh limits, so the account still functions, just poorly.)
Suspect accounts would then be notified in the c-panel, and e-mail, that the account has been temporarily placed into this "Limited Access Mode", which may impede the operation of the site. They must contact, "Insert Link Here", for resolution instructions.
Persistent control could be extended to degradation of out-going CGI and PHP mailers, disabled MODREWRITE, disabled MySQL access, disabled PHP, disabled CGI, disabled Other Scripts... Eventually they will reply, to seek resolution.
Offer them a quick step-by-step checking, to see if the problem can be centralized. (If available, force full monitoring of that site, while in this super-restricted mode, to see if you can single-out any one thing that may be causing the issue.)
I imagine the WiKi would greatly help, once all common occurrences have been found and recorded. (Off hand, I know of a few things that can go unseen, and are hard to test for, but when they are found... OMG they can cripple a server, almost instantly! Hackers are not all evil!)
It is in our best interest, as customers, to see that WHB offers our neighbors as much assistance as possible, where not overextending into the point of losses. (Having 200 accounts crippled, is a loss. If you loose one customer, you loose two... The banned person, and the one who left.)
Would be nice to see this WiKi become a permanent fixture in the WHB support site and forum area. It would also be nice to see the forum become more open and common, for non-panic mode postings. Place the link as the first thing you see in the c-panel. Invite people here. Get them familiar, so they feel guilty about posting irrational remarks.
Build your community, and the word-of-mouth you gain will help you more than any search-scheme will ever help you.
P.S. That new logo needs to be modified... It is slightly unclear. Looks like it says "U I t B". In my artistic opinion.
P.P.S. How much do I have to contribute to WiKi, to get a dedicated server with SSL? I don't even care if I have to share it with others, as long as the SSL is 100% mine, and I am not on there with 200 other people. LOL. I don't need bandwidth, or storage, just up-time and security.
Posting Permissions
Reply With Quote