in reply to Re: PM currently very slow, caused empty post? (updated)
in thread PM currently very slow, caused empty post? (updated)

Perlmonks uses three machines and two of them are currently getting hammered by machines claiming to be search engines. I've blocked these in some way, but there seem to be other problems as my webhoster can't make a TCP connection to Pair.com.

This is completely unrelated to the timezone settings. I'll post a notice once I've restored the timezone settings.

  • Comment on Re^2: PM currently very slow, caused empty post? (updated)

Replies are listed 'Best First'.
Re^3: PM currently very slow, caused empty post? (thanks)
by Discipulus (Canon) on Nov 05, 2016 at 21:35 UTC
    nasty noisy breakers prefere weekends for ddos et similia when good 'ol hacker like you and others want just relaxing bringing the camel on the field

    thanks Corion for yor work!

    L*

    There are no rules, there are no thumbs..
    Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
Re^3: PM currently very slow, caused empty post? (updated)
by kcott (Archbishop) on Nov 05, 2016 at 22:04 UTC

    Thanks for the feedback.

    I tried pair.com from my browser. It resolved to https://www.pair.com/ and took about five minutes or so to load; however, the layout appeared to have issues and images were missing.

    I reloaded several times with varying degrees of success. Each attempt took many minutes (except for one which seemed to have no CSS at all). I finally got what appeared to be a reasonable layout with just one image, https://www.pair.com/img/render-shared.png, missing (although, I was able to download this separately).

    I also tried pinging it. This seemed to be fine and I got similar values to those I reported for PM above.

    — Ken

Re^3: PM currently very slow, caused empty post? (updated)
by kcott (Archbishop) on Nov 10, 2016 at 00:21 UTC

    I've just seen the update in Tidings (posted a few hours ago). Timestamps now appear correctly and "Timezone Settings" are back to normal. Thanks for all your work on this.

    — Ken