[projectaon] Re: Fwd: [jonblake 81157683] Followup regarding your site projectaon.org
- From: Jack Van Zyl <jack.vanzyl@xxxxxxxxxxxxxxxxxx>
- To: "projectaon@xxxxxxxxxxxxx" <projectaon@xxxxxxxxxxxxx>
- Date: Tue, 12 Nov 2013 00:05:38 +0000
Hi all,
Holy crap. I’ve gone through the nginx error log on OpenShift for the Lone
Wolf Adventures web app, and found the following. I hope it's because of
the DreamHost server move, or some other reason, but FYI here's the
details.According to Google Analytics (and that's if I've tagged the
web app
correctly) the web app averages 0 to 1 visitors per day (more like 0), and
the site's only had 95 visits by 48 unique visitors. But looking at the
server logs, something went on on 30/31 October (point 6 below):
1. On 13 August, between 22.45 and 22.49, there were suddenly 247 errors
of the following 2 types: “failed (11: Resource temporarily unavailable)
while connecting to upstream” (120 errors), “upstream timed out (110:
Connection timed out) while reading response header from upstream” (127
errors)
2. And then from 12:43 on 16 September to 11:13 on 17 September there
were 106 of the following: “upstream timed out (110: Connection timed
out) while reading response header from upstream”
3. And then from 11.13 on 17 September to 6.06 on 19 September there
were 175 of the following: “failed (11: Resource temporarily
unavailable) while connecting to upstream”
4. And then from 19:50 on 15 October to 19:50 on 15 October there were
70 of the following: “upstream timed out (110: Connection timed out)
while reading response header from upstream”
5. And then from 21:39 on 29 October to 14:13 on 30 October there were
77 of the following: “upstream timed out (110: Connection timed out)
while reading response header from upstream”
6. And then the big one: From 14:15 on 30 October to 10:35 on 31 October
there were 3257 of the following: “failed (11: Resource temporarily
unavailable) while connecting to upstream”
7. And then from 10:35 to 10:36 of 31 October there were 89 of the
following: “upstream timed out (110: Connection timed out) while reading
response header from upstream”
8. And then from 10:40 to 10:40 on 31 October there were 95 of the
following: “failed (11: Resource temporarily unavailable) while
connecting to upstream”
9. And then from 10:41 to 10:42 on 31 October there were 74 of the
following: “upstream timed out (110: Connection timed out) while reading
response header from upstream’
10. And then from 11:33 until 11:33 on 3 November there were 296 of the
following: “failed (11: Resource temporarily unavailable) while
connecting to upstream”
11. And then from 11:34 until 11:35 on 3 November there were 71 of the
following: “upstream timed out (110: Connection timed out) while reading
response header from upstream”
12. And then from 16:13 on 7 November until 5:43 on 11 November there
were 189 of the following: “upstream timed out (110: Connection timed
out) while reading response header from upstream”
(The latest entry recorded on 2013/11/11 at 05:43:23)
Point 6 makes me think there's some bot or something hitting
lonewolfadventures.projectaon.org, and this app of course downloads the
data and images from the main site. I really hope there's some other cause,
but I'd be happy to switch the app off if that would be a good idea.
Best regards
Jack
On Thu, Nov 7, 2013 at 10:01 PM, Fred <freds_cats@xxxxxxxxxxx> wrote:
> I know I recently had one of my e-mails that’s attached to my website
> cause mayhem. Apparently it was trying to access something like 3600 times
> a hour. Interestingly the only places the account is utilised was my
> iPhone and my PC.
>
>
>
> Fred
>
>
>
> *From:* projectaon-bounce@xxxxxxxxxxxxx [mailto:
> projectaon-bounce@xxxxxxxxxxxxx] *On Behalf Of *James Durrant
> *Sent:* 07 November 2013 16:31
> *To:* projectaon@xxxxxxxxxxxxx
>
> *Subject:* [projectaon] Re: Fwd: [jonblake 81157683] Followup regarding
> your site projectaon.org
>
>
>
> Isn't is somewhat co-incidental that they move our server on Wednesday,
> then on Thursday it is suddenly overloaded?
>
>
> > Date: Thu, 7 Nov 2013 08:01:33 -0800
> > Subject: [projectaon] Re: Fwd: [jonblake 81157683] Followup regarding
> your site projectaon.org
> > From: jonathan@xxxxxxxxxxxxx
> > To: projectaon@xxxxxxxxxxxxx
> >
> > Thanks for the suggestions. I've asked them to look into it,
> > especially since we have no way to investigate with the website down.
> > I can't even access usage logs through their administrative website.
> > We'll see what they say.
> >
> > One possible solution is to move to a virtual private server but that
> > wouldn't solve the underlying issue. It would just isolate the problem
> > to us. :-/
> >
> > Jon
> >
> >
> > On Thu, Nov 7, 2013 at 7:08 AM, Nicholas Jankowski <jankowskin@xxxxxxxx>
> wrote:
> > > agree with David's suggestion. My guess is you could ask them for the
> usage
> > > profile over the past few months, and try to identify whether it was a
> > > sudden traffic increase and when that started.
> > >
> > >
> > > On Thu, Nov 7, 2013 at 9:20 AM, David Davis <feline1@xxxxxxxxxxxxx>
> wrote:
> > >>
> > >> oo-er!
> > >>
> > >> It wasn't me :/
> > >>
> > >> Usually in these kind of situations, it turns out the site has been
> hacked
> > >> in some way, and is being used as a relay for spambot traffic or
> something
> > >> similar.
> > >> Can you not get the hoster to check their logs and tell you where all
> the
> > >> bandwith is being guzzled to?
> > >> David
> > >> On 7 November 2013 13:51, Jonathan Blake <jonathan@xxxxxxxxxxxxx>
> wrote:
> > >>>
> > >>> The website has been disabled. Does anyone know of a reason that the
> > >>> bandwidth to the website would have increased dramatically in the
> last
> > >>> while?
> > >>>
> > >>> Jon
> > >>>
> > >>> ---------- Forwarded message ----------
> > >>> From: DreamHost Customer Support Team <support@xxxxxxxxxxxxx>
> > >>> Date: Thu, Nov 7, 2013 at 2:28 AM
> > >>> Subject: [jonblake 81157683] Followup regarding your site
> projectaon.org
> > >>> To: jonathan@xxxxxxxxxxxxx
> > >>>
> > >>> Hello Jonathan,
> > >>>
> > >>> Unfortunately, due to the amount of traffic still trying to access
> your
> > >>> site after we disabled the web directory, we were forced to disable
> it on
> > >>> our end to prevent it from causing further issues on your shared
> server.
> > >>>
> > >>> In order for us to re-enable your site, please reply back with any
> plans
> > >>> you have to lower the amount of usage your site is currently
> receiving,
> > >>> or you may want to consider upgrading to a VPS. I'm afraid with the
> usage
> > >>> being what it is currently, we're not able to keep it active in its
> > >>> current state as it is causing severely high loads on your shared
> server
> > >>> which is affecting other customers.
> > >>>
> > >>> Thanks!
> > >>> Chalise
> > >>>
> > >>> --
> > >>> DreamHost Support Team + support@xxxxxxxxxxxxx
> > >>> Earn over $97 for each referral:
> http://www.dreamhost.com/affiliates/
> > >>> To continue this support case, just reply to this email.
> > >>> Open a new case at: https://panel.dreamhost.com/?tab=support
> > >>>
> > >>> ~~~~~~
> > >>> Manage your subscription at http://www.freelists.org/list/projectaon
> > >>>
> > >>>
> > >>
> > >
> >
> > ~~~~~~
> > Manage your subscription at http://www.freelists.org/list/projectaon
> >
> >
> ------------------------------
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4158 / Virus Database: 3629/6817 - Release Date: 11/07/13
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4158 / Virus Database: 3629/6814 - Release Date: 11/06/13
>
Other related posts: