Internal server error
Author
Discussion

karona

Original Poster:

1,928 posts

215 months

Saturday 2nd January 2016
quotequote all
and lots of 'oopsies'

Did someone forget to feed the hamsters during the holidays?

(Win 10 & Chrome)

750turbo

6,164 posts

253 months

Saturday 2nd January 2016
quotequote all
Getting this as well, maybe the site is mega busy?

JD PH

2,670 posts

146 months

Sunday 3rd January 2016
quotequote all
Hi,

Can you shed any additional light on the specific issues? Is this occurring on one particular page / link / section?

Either it has resolved itself or I can't see the issue to report it to the Dev guys to investigate!

Thanks
JD

karona

Original Poster:

1,928 posts

215 months

Sunday 3rd January 2016
quotequote all
JD PH said:
Hi,

Can you shed any additional light on the specific issues? Is this occurring on one particular page / link / section?

Either it has resolved itself or I can't see the issue to report it to the Dev guys to investigate!

Thanks
JD
Everything fine now. It was random error pages, or 'internal server error' whether selecting the next page in a thread, or clicking back, all in 'what's new'

It seems to have resolved itself now.

JD PH

2,670 posts

146 months

Sunday 3rd January 2016
quotequote all
Ok, just let us know if it crops up again! smile

JD

MitchT

17,114 posts

238 months

Sunday 3rd January 2016
quotequote all
I just had it now. It seems to happen randomly now and then. Usually if I refresh the page it loads.

2 sMoKiN bArReLs

31,988 posts

264 months

Sunday 3rd January 2016
quotequote all
Just had it several times

bitchstewie

67,254 posts

239 months

Sunday 3rd January 2016
quotequote all
Ditto, it's been on and off for ages.

I also find often that when I browse to a new page on the forums it'll spend an age saying "resolving site" and then load at normal speed.

I've had it across various laptops on different ISPs and only ever experience it on PH.

An in one of life's little ironies it's doing it when I hit submit on this.

JD PH

2,670 posts

146 months

Sunday 3rd January 2016
quotequote all
Thanks guys - I'll get the clever tech folks onto it in the morning!

RacingPete

9,195 posts

233 months

Sunday 3rd January 2016
quotequote all
We will look at the logs in the morning to see if there is anything obvious causing this issue that we need to fix immediately...

Though we are moving the hamsters to a new pasture in the next few days, which will give them some nice new grass and more room to run around in - we are hoping that will make them happy, and not throw errors again.

It will be like this



To this...



(yes we may have some Guinea pigs too)

karona

Original Poster:

1,928 posts

215 months

Monday 4th January 2016
quotequote all
clapclapclapclap

robinessex

11,994 posts

210 months

Monday 4th January 2016
quotequote all
Is the PH server running on AA batteries this morning? Slow doesn't begin to describe it.

RacingPete

9,195 posts

233 months

Monday 4th January 2016
quotequote all
robinessex said:
Is the PH server running on AA batteries this morning? Slow doesn't begin to describe it.
We are looking into this at the moment.

All that jazz

7,632 posts

175 months

Wednesday 6th January 2016
quotequote all
RacingPete said:
We are looking into this at the moment.
hehe The default reply then nothing ever happens.

Site has been sporadically throwing 500s all evening on various forum threads.

RacingPete

9,195 posts

233 months

Thursday 7th January 2016
quotequote all
All that jazz said:
RacingPete said:
We are looking into this at the moment.
hehe The default reply then nothing ever happens.

Site has been sporadically throwing 500s all evening on various forum threads.
We have seen an increase in posts across the site at the beginning of January, and the database is struggling with the load. We are currently finishing the testing on the new platform we are moving to that will sort this (and looking very good) - in the meantime, the old database is being nurtured to not throw too many errors (all we can do with the new platform imminent).

We will be doing the work to move the platform on Monday night, so after that these will hopefully go away (well those caused by traffic load).

Sorry it is a bit st at the moment frown

2 sMoKiN bArReLs

31,988 posts

264 months

Thursday 7th January 2016
quotequote all
RacingPete said:
those caused by traffic load).
yikes a motoring website affected by traffic! hehe

bitchstewie

67,254 posts

239 months

Thursday 7th January 2016
quotequote all
RacingPete said:
We have seen an increase in posts across the site at the beginning of January, and the database is struggling with the load. We are currently finishing the testing on the new platform we are moving to that will sort this (and looking very good) - in the meantime, the old database is being nurtured to not throw too many errors (all we can do with the new platform imminent).

We will be doing the work to move the platform on Monday night, so after that these will hopefully go away (well those caused by traffic load).

Sorry it is a bit st at the moment frown
If I could offer some constructive criticism, as a business (it's a business not a hobby) Pistonheads communications sucks.

Most of us would be fine if we simply knew that you knew there was an issue and that it's being looked into.

There was mention some years back of stickies and all sorts but it doesn't seem to happen.

I don't want to be posting "it's slow" threads and wouldn't if I simply say "we know it's slow and we're working on it" somewhere obvious.

Maybe I'll now be pointed to it, but I don't think there are any stickies or announcements or status pages that I've missed and https://twitter.com/pistontechs says it all on the supposed Twitter status feed.

robinessex

11,994 posts

210 months

Friday 8th January 2016
quotequote all
The infamous 500 error popped up again

Koofler

616 posts

195 months

Friday 8th January 2016
quotequote all
robinessex said:
The infamous 500 error popped up again
This.

Twice while trying to post the above response.

All that jazz

7,632 posts

175 months

Friday 8th January 2016
quotequote all
Koofler said:
robinessex said:
The infamous 500 error popped up again
This.

Twice while trying to post the above response.
RacingPete said:
We are looking into this at the moment.
hehe