I host my site with Go Daddy - and according to them I violate their terms as the finnd the next problems : 1796 "GET yatzit.com/groups/all?handler=groups&page=all HTTP/1.0" and
HTTP/1.1"
1068 "GET yatzit.com/blog/all?handler=blog&page=all HTTP/1.0"
959 "GET yatzit.com/blog/all?handler=blog&page=all&offset=50 HTTP/1.0"
I use Elgg 1.8.3 and dont have a clue what the problem may be.
Thanks in advance
Piet
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Cash@costelloc
Cash - 0 likes
- Piet Muller@MullerPiet
Piet Muller - 0 likes
Discussion Notes Support Staff Response
The yatzit.com hosting account has been determined to be in violation of Section 3 "Your Obligations" of the Go Daddy's “Web Hosting and Virtual Dedicated Hosting Service Agreement.”
The relevant passage of this agreement has been provided below:
Go Daddy's "Web Hosting and Virtual Dedicated Hosting Service Agreement" is located at the following URL: https://www.godaddy.com/agreements/ShowDoc.aspx?pageid=HOSTING_SA
The administrators of Go Daddy’s Hosting Operations Center discovered that your hosting account caused an overload of shared resources for the server that it resides on. This overload threatened the health of the server and, in turn, threatened the connectivity of other web sites housed on this server. This is, of course, unacceptable. Go Daddy had no choice but to take immediate action to protect our network and to prevent the possibility of a service interruption for other customers. Your site was migrated to a specialized server environment to both protect the other customers on the affected server and to allow you to correct the root cause of this problem.
*PLEASE NOTE* The “specialized” server environment that your site has been moved to may not be perfectly attuned to meet the needs of your site and may impact its general performance or even cause some services to cease functioning. It is also extremely possible that your site will not be impacted at all and may continue to perform as expected. Regardless, further action on your part is required; allowing your site to remain at this new location is not a permanent option, merely a temporary alleviation of the problem affecting our network.
After detecting this problem Go Daddy's hosting administrators requested that Go Daddy's Advanced Hosting Support team notify you of this action and request that you resolve the underlying issue. Unfortunately, we are unable to troubleshoot custom scripting, and therefore, unable to provide a specific solution to you. However the following files were the most frequently accessed files on your site, and should be the starting point for further troubleshooting on your end.
1796 "GET yatzit.com/groups/all?handler=groups&page=all HTTP/1.0"
Keep in mind, the above files may not be the root cause of this issue, as the owner of this site it is incumbent upon you to determine what is wrong and how to best resolve this situation.
*IMPORTANT* a response from you regarding this situation is required. Your site has been scheduled for suspension on July 22, 2012. As explained above, the migration of your site is a temporary solution; the underlying issue MUST be resolved. Your site cannot remain in this new location and must be moved back to its original hosting environment. If you fail to address this matter your services may be suspended.
After you have resolved this issue, this matter can be closed by responding to this notice with the following:
-
A statement that you have reviewed and agree to abide by the terms of the "Web Hosting and Virtual Dedicated Hosting Service Agreement," and
-
A detailed description of the steps you have taken to resolve and/or correct this issue, and
-
A statement that you agree to configure your site in such a way as to ensure that there is not a re-occurrence of this issue in the future.
After we receive your reply with these statements we will contact Go Daddy’s hosting administrators, provide them with your solution, and request that they re-investigate the issue. If they approve your proposed solution, your site will be returned to its original hosting environment. (We reserve the right to migrate the site again should its return to its original environment result in a repeat occurrence of the problem.)
- iionly@iionly
iionly - 0 likes
- Piet Muller@MullerPiet
Piet Muller - 0 likes
- Matt Beckett@Beck24
Matt Beckett - 0 likes
- Burgs@burgs
Burgs - 0 likes
- Piet Muller@MullerPiet
Piet Muller - 0 likes
- Piet Muller@MullerPiet
Piet Muller - 0 likes
- Arsalan Shah@arsalanlee
Arsalan Shah - 0 likes
You must log in to post replies.I do not understand what you are asking.
Dear Sir/Madam,
Regarding your hosting account yatzit.com:
1498 "GET yatzit.com/groups/all?handler=groups&page=all HTTP/1.1"
1068 "GET yatzit.com/blog/all?handler=blog&page=all HTTP/1.0"
959 "GET yatzit.com/blog/all?handler=blog&page=all&offset=50 HTTP/1.0"
932 "POST yatzit.com/action/login?action=login HTTP/1.0"
878 "GET yatzit.com/blog/all?handler=blog&page=all&offset=100 HTTP/1.0"
835 "GET yatzit.com/blog/all?handler=blog&page=all&offset=150 HTTP/1.0"
817 "POST yatzit.com/action/login?action=login HTTP/1.1"
792 "GET yatzit.com/blog/all?handler=blog&page=all&offset=200 HTTP/1.0"
769 "GET yatzit.com/pages/all?handler=pages&page=all HTTP/1.0"
767 "GET yatzit.com/blog/all?handler=blog&page=all&offset=250 HTTP/1.0"
753 "GET yatzit.com/blog/all?handler=blog&page=all HTTP/1.1"
731 "GET yatzit.com/blog/all?handler=blog&page=all&offset=300 HTTP/1.0"
702 "GET yatzit.com/blog/all?handler=blog&page=all&offset=350 HTTP/1.0"
681 "GET yatzit.com/blog/all?handler=blog&page=all&offset=400 HTTP/1.0"
663 "GET yatzit.com/blog/all?handler=blog&page=all&offset=50 HTTP/1.1"
663 "GET yatzit.com/blog/all?handler=blog&page=all&offset=450 HTTP/1.0"
646 "GET yatzit.com/blog/all?handler=blog&page=all&offset=500 HTTP/1.0"
624 "GET yatzit.com/blog/all?handler=blog&page=all&offset=550 HTTP/1.0"
603 "GET yatzit.com/blog/all?handler=blog&page=all&offset=100 HTTP/1.1"
551 "GET yatzit.com/blog/all?handler=blog&page=all&offset=150 HTTP/1.1"
530 "GET yatzit.com/blog/all?handler=blog&page=all&offset=200 HTTP/1.1"
502 "GET yatzit.com/blog/all?handler=blog&page=all&offset=250 HTTP/1.1"
483 "GET yatzit.com/pages/all?handler=pages&page=all HTTP/1.1"
476 "GET yatzit.com/blog/all?handler=blog&page=all&offset=300 HTTP/1.1"
461 "GET yatzit.com/blog/all?handler=blog&page=all&offset=350 HTTP/1.1"
441 "GET yatzit.com/blog/all?handler=blog&page=all&offset=400 HTTP/1.1"
430 "GET yatzit.com/blog/all?handler=blog&page=all&offset=450 HTTP/1.1"
416 "GET yatzit.com/blog/all?handler=blog&page=all&offset=500 HTTP/1.1"
399 "GET yatzit.com/blog/all?handler=blog&page=all&offset=550 HTTP/1.1"
If you have questions about this matter, you may contact us by replying to this email or by calling 480-505-8871.
We appreciate your cooperation in this matter.
Hosting Support Team
Hi Cash - Thanks for responding so quik - This was the whole message they sent me - A fews monts back I lost 1300 members and my whole database - also becuase something queried the database to much - Now again I have almost regained the same numeber of members (1800) an now again I am in trouble - I dont even now what to try and do
Thanks
I think the violation of their terms might be a too excessive use of CPU resources. Are you on a shared server at GoDaddy? Most shared server hoster have limitations of CPU use in their terms of usage. Elgg's pagehandler process shows a high CPU usage as a lot of page requests etc. are done via the "pagehandler" process. From the hoster side point of view they only see this "pagehandler" process that creates seemingly long-lasting high CPU load.
I think you can't do anything to solve the problem apart from either changing to a other hosting plan (VPS) or moving to another hoster.
iionly - Yes I am on shared hosting - and then you are correct - I thought this might be the problem but dont have a lot of knowledge round server.
Thanks a lot to you and Cash
Have a great evening
If you don't have much server knowledge you can just tell godaddy that you need to move to a vps (or dedicated, whatever the case maybe) they mostl likely have services to migrate it for you.
I have had 17 years on shared hosting and it's normal for them to nudge you onto a VPS when a site starts becoming successful and the CPU usage is the stick they nudge you with. Lets hope you are making enough wonga from your visitors to pay for the hosting. Many VPS and Dedicated packages are un-managed so be careful.
Thanks Matt and Burgs - I am not happy with Go Daddy at all - On this shared hosting account they offer Elgg as a "free" aplication without a warning telling their clients to - if they want to use Elgg they rather need dedicated or VPS hosting - They - the first time just disabled my account and database - I could not get access to backup the database and lost 1300 members - this time they migrate my websites to a server without notice, this put all my websites of the air for about 20 hours, I realy dont think this is the way to run hosting, and ask money for that service. But yes, One only makes a mistake once, and luckely one learn by this the hard way, I will most definite shift my websites to another host in future. I have deleted the whole website as its a free site, and I cant pay more for hosting at this stage.
I want to thank all the friendly people of the Elgg comunity for helping out, always lending a hand, and thanks to the developers for the great work.
Thank you all
A lot of money and long hours of hard work into the drain - AGAIN
@Piet Muller change your server thats the solution... (*_*)