You are Here
Stuff

Curiouser and curiouser (21/29)

It looks as though the problem Young Masher has so thoughtfully identified, scales back to a server-side timing.

This evening I shall be rolling up my sleeves and picking the server apart.

See what you’re doing to me, Masher?

See?

This evening is the only free time I had, this week. And now that free time has gone, evaporated like an evaporated thing on a hot day.

*weeps*

8 thoughts on “Curiouser and curiouser (21/29)”

  2. Testing for the timeout problem. Actually not. Testing to see if I managed to fix the timeout problem at 2am. The time is 21.14 on this paragraph.

    The time is now 21.16
    The time is now 21.17
    The time is now 21.18, that’s four minutes.

    1. This looks promising. I was unable to replicate the problem, so I have switched the website’s design back. And I am testing for the timeout problem again.

      The time is now 21.43
      The time is now 21.45
      The time is now 21.46
      The time is now 21.47
      The time is now 21.49

  3. OK, well I’m still wondering whether it’s just me. No-one else seems to have reported the issue.
    Do I take it you have actually seen it yourself? I assume so: people don’t take their server apart for no reason!

    I’m taking a while to write this on purpouse… why can I suddenly not spell!? Probably because I’ve been on a nightshift and haven’t slept yet – just to see if you have truly been successful in your endeavours.

  4. It seems you have. Well done!

    I can stop recording this now (was gonna mail the vid to you just to prove I wasn’t doing summat wrong).

    1. I was up until 2am yesterday, fixing this. I took the website offline, reset the nameservers to a test server I have here in the house, create a new zone file, run timeout tests against the new hosting arrangements (which it passed), reset the namservers back to default, created a new zone file on the old server and then (and this is the critical bit) I went to sleep.

      When I ran tests the next evening I was unable to create the problem. So resetting the nameservers and creating a new zone file did the job. I didn’t have to unpick the database. Yay!

      But thanks for spotting the problem.

Comments are closed.