Neighboursepisodes.com

[Hawker]

No, it's a long standing issue - I've got a fix for it, but it needs to run overnight.  

Sorry for the outage.

[Hawker]

Fixed now; should be better going forward.   

[ict 3000]

Problem maybe back when trying to access the latest updates I am getting a 503 error meesage

[Tracy C]

Sal is aware of it and we’re waiting for the hosts to do something (technical term! ).

[Hawker]

All fixed now; apologies.

[birdman]

Error 503 message is back again as of the 6th June 2022. 

[Tracy C]

Its working okay for me just now.  And it was okay earlier this morning when I used it.  

[birdman]

43 minutes ago, Tracy C said:

Its working okay for me just now.  And it was okay earlier this morning when I used it.  

It's changed from error 503 to error 500 now: Internal Server Error. 

[Tracy C]

Sorry, I've been off doing the summary.  Its still working fine for me but I'll let Sal know.  

[birdman]

Interesting, it's working on my iPhone but not in Microsoft Edge. Getting a blue background with an error 500 shop style sign. 

[Tracy C]

I heard back from Sal and she did a reboot yesterday but there is some "tinkering" going on behind the scenes which might have meant it didn't work.  

I'm using chrome and its okay on there, so maybe give that a go until the "tinkering" is finished and another reboot can be carried out.  

[birdman]

Summaries are showing as down for me in Microsoft Edge still, unless the tinkering is still going on?

[Hawker]

It'll be ongoing for several days yet.

[Sayaka]

10 hours ago, birdman said:

Summaries are showing as down for me in Microsoft Edge still, unless the tinkering is still going on?

There's really no reason that the browser should affect things as it's a server side thing. Have you tried a hard refresh? (CTRL+F5)? Working fine for me in Edge.

[birdman]

38 minutes ago, Sayaka said:

There's really no reason that the browser should affect things as it's a server side thing. Have you tried a hard refresh? (CTRL+F5)? Working fine for me in Edge.

So what would be causing this error screen?

[Sayaka]

Hmm. Have had a further look and 1992 is a funny one. It's a year where the caps are not complete so the part where the little picture is put next to the episode number is more resource intensive. Probably was fine when the archive was smaller, but the combination of archive growth and a different host, it may be groaning. 

I think there's scope for a re-code that may improve thing - I'll have a look into it (when I'm not at work!)

 

[birdman]

3 hours ago, Sayaka said:

Hmm. Have had a further look and 1992 is a funny one. It's a year where the caps are not complete so the part where the little picture is put next to the episode number is more resource intensive. Probably was fine when the archive was smaller, but the combination of archive growth and a different host, it may be groaning. 

I think there's scope for a re-code that may improve thing - I'll have a look into it (when I'm not at work!)

 

Thanks Sayaka. It’s no major annoyance, as I’m currently re-watching 1992 I'm making a log of what I’ve watched so far and like to refer to the archive for the correct Australian air dates. 

[Sayaka]

Had an hour or so this afternoon, so I've made the code more efficient with fewer database queries on the main site. (I've moved them off to a background area which will only need to run occasionally)

Hopefully that will help things a bit - as long as I haven't killed anything else during the coding process 

[Sayaka]

Still seems to be having problems, so @Hawker is talking to the hosts

[Sayaka]

I have been doing a bit more optimising - I think there are a LOT of hits on ne.com at the moment as a result of the huge interest in Neighbours over the last few days (for reasons we'd rather not have  )