Error Messages

[Nico]

I've just gotten this error:

Error 502 - Bad Gateway
Monday, March 30th, 2015: Server software upgrade and database replication change.
I generally try to put updates to https://twitter.com/Vekseid

Refreshing the page solved the issue, but I just wanted to say something, incase it happens to others as well.

[BAMF]

I got one of these just now too. A refresh worked.

[Geraint]

I've been getting these for three or four days, even at times when not many people are on.  They go away with a refresh true enough, but the are also capable of eating a post for one on a browser that doesn't support Lazarus (like my IE11)

[Blythe]

Has been happening consistently for me since the 8th; when I asked about it then, Veks mentioned about E being out of RAM. Not sure if that's still the case, but that was what it was on the 8th.

[Vekseid]

What happened on the 8th was persistent...

We're slowly getting back to that point of unusability, but this is a bit different. Someone should Skype/text me the next time they get this.

[Vekseid]

I found one potential culprit.

Please let me know if this continues.

[Blythe]

If it happens again, I'll poke you on Skype and try to get you the time it occured

[Vekseid]

Got the error from Mithlomwen's report.

I'll try resetting things tonight and see if that functions appropriately.

[Vekseid]

Reset done, will see how the system handles things.

[Jag]

I just got it twice in the last half hour. Just thought I would let someone know.

[RampantDesires]

I get these in the shoutbox a lot.  They have time stamps if that helps at all?

(12:22:52) SweetSerenade: words
(12:23:13) Elliquiy: Error: Connection status: 502
(12:23:15) wander: words

[Vekseid]

At least when it's in the shoutbox no one loses much. : /

[SweetSerenade]

At least when it's in the shoutbox no one loses much. : /

I've been getting the error about five times a day for the last three days?  I've gotten it once on mobile. 

[Vekseid]

Ugh.

Know what I need to do. It'll require a slight bit of downtime so I won't be able to address it until tonight.

[Flower]

Thank you for working to fix it. ^_^

[AmberStarfire]

FYI, I just got the Bad Gateway error when I clicked on the Things That Cheer You Up thread.

[Inkidu]

I got a bad gateway clicking on  the forum button.

[Geraint]

I got one at about 9:20 this morning EST, that cost me all the forum formatting on a RP post written offline and lasted several minutes.

[Flower]

I just received a different message.

Connection Problems

Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later.

That's what it displayed. Not sure if it was related but I thought to share it.

[Vekseid]

This is a lot more serious than I thought. A security patch has apparently busted things.

This could take awhile. : /

[AmberStarfire]

I hope it isn't too bad.

If you need someone to bounce ideas off, just let me know.

[Vekseid]

Well fuck.

This has actually been a problem for six years now. The recent security patch just made it worse.

There is another patch incoming and that may hopefully help fix it, if not I can try another repo. It's not looking like this will properly be fixed in 5.6, so this may entail moving to 7.1... which E can't currently run.

I have also enabled an autorestart for masses of SIGBUS errors, so when we get a lot it should correct itself a bit. This will only help some. : /

[AmberStarfire]

The site's made it this far well.

Is it possible to unpatch it and manually create some kind of security fix that won't cause the same problems? If so, would that interfere with future patches?

It may not solve the problem completely but it was happening less regularly before.

[Lustful Bride]

Maybe a call should be put out for anyone and everyone here on E with some technical knowledge. It might not get any help but more minds working on the problem cant hurt.

[Vekseid]

Maybe a call should be put out for anyone and everyone here on E with some technical knowledge. It might not get any help but more minds working on the problem cant hurt.

We already know why it is happening. In theory, I could just patch out mmap from the lexical parser myself. The problem is whatever else that ends up breaking. The site functions 99.9% of the time right now.