Nginx 500 errors affecting post submissions

  • Thread starter Thread starter Fredrik
  • Start date Start date
Join the discussion
Registration is free. Ask a follow-up in this thread, or start your own.
Sign up Log in
76 replies · 9K views
I got it too. Nothing showing up in the logs. Very strange. I'm going to update nginx to the latest version shortly.
 
Physics news on Phys.org
tiny-tim said:
got a 500 ngingx 2 minutes ago, previewing a post

(oh, and another one just now, previewing this post! :rolleyes:)

(ok on 2nd preview)

(and on 3rd)
When it happens to me, I always get the error again if refresh immediately. So I need to wait a minute or a few before I refresh again.
 
Could not post anything for 5 minutes due to 500 nginx errors. What is the cause of them?
 
Greg Bernhardt said:
How long ago. I was making lots of adjustments about an hour ago

Just before I posted the report: about 1940 UK time.
 
Got several 500s less than 10 minutes ago, while trying to post in the photography thread.
 
CAF123 said:
Just before I posted the report: about 1940 UK time.

C'mon, there wasn't even an internet back then!
 
lisab said:
C'mon, there wasn't even an internet back then!

:-p
 
The lesson seems to be that it would help when maintenance is announced.
 
Andre said:
The lesson seems to be that it would help when maintenance is announced.

The problem is there is no good way to make sure everyone sees it. The recent maintenance was emergency. What is the point of announcing it and then shutting down and then people end up reading about the announcement after I'm finished.
 
lisab said:
C'mon, there wasn't even an internet back then!

That doesn't make sense. 1940 UK Time means like 12.01pm NZST.

1940 UK Date/Year would make your statement humourous.
 
StevieTNZ said:
1940 UK Date/Year would make your statement humourous.

That's the way that I interpreted it, and I found it quite amusing.

And yes, as a former pilot I'm familiar with military time.
 
Danger said:
That's the way that I interpreted it, and I found it quite amusing.

And yes, as a former pilot I'm familiar with military time.

Indeed, it was a joke :biggrin:.
 
lisab said:
Indeed, it was a joke :biggrin:.

I am surprised it could be read in any other way.
 
I got 500 nginx errors around 8am CST this morning and lost a longish post which I didn't bother to retype because I didn't want it to get lost again.
 
Time is time. e.g. 12am - 11.59pm
Date includes year.
 
jedishrfu said:
I got 500 nginx errors around 8am CST this morning and lost a longish post which I didn't bother to retype because I didn't want it to get lost again.
You shouldn't lose anything. Just wait a few minutes and then reload the page.
 
I got it repeatedly when trying to edit my posts yesterday (about 0815 GMT on 18th April). I didn't succeed until the error resolved itself.
 
Borek said:
I am surprised it could be read in any other way.

And I'm surprised that you can read at all, with all that hair in your eyes.
 
Danger said:
I didn't smell anything, but I'll take your word for it...
lisab said:
C'mon, there wasn't even an internet back then!
Borek said:
I am surprised it could be read in any other way.
Danger said:
And I'm surprised that you can read at all, with all that hair in your eyes.
Lol...



No errors here.



OCR
 
Just got one now at 9:10pm CST. Was trying to post.
 
Me too.
 
Just got another one (straight 500) at 8:49 MST while responding in GD. It cleared within less than a minute.
 
Just now. Trying to give a warning.
 
So, really... what do those messages mean, other than "something screwed up"?
 
Danger said:
So, really... what do those messages mean, other than "something screwed up"?

That's the problem - nobody knows the exact meaning. Which is why it is so difficult to get rid of them.
 
Well that's no way to run an airline...
 
Danger said:
Well that's no way to run an airline...

I have a good news for you - we don't run an airline :wink:

Airline approach would be to ground the forums till the problem is resolved. Difference is, forum crash means just some posts lost. And even those lost posts are limited to just a last few hours in the worst case.

It doesn't mean Greg is not trying to find out what is happening, but it is often extremely difficult, especially when there is no sure way to reproduce the problem. 500 can mean some stupid error in the system configuration (rather unlikely, as the system was running OK for the last few months), but it can also mean some piece of hardware is failing and misbehaves at random moments. If it is the latter, chances are situation will not become clear before it breaks definitely.

GRRRR%^&! :smile: I got another 500 when trying to submit THIS particular post.