Author Topic: Return of 502- Bad gateway Error (Read 57909 times)

WastelandTek · « **Reply #100 on:** July 19, 2017, 01:34:01 pm »

hey, at least the message comes from cloudflare now

Muttley Snickers · « **Reply #101 on:** July 19, 2017, 01:37:01 pm »

I suspect that the popcorn emoticon is sucking all the juice.

EEVblog · « **Reply #102 on:** July 19, 2017, 01:38:08 pm »

gnif informs me this is normal. We are using all the RAM for a database buffer for increased performance. The 9.6GB will slowly grow back to 32GB again.
gnif will investigate tomorrow.

LIV2 · « **Reply #103 on:** July 19, 2017, 01:44:08 pm »

Besides DB buffers linux will use the memory for cache/buffers for other stuff too.
Explanation: http://www.linuxatemyram.com/

Dave do you have any stats graphing configured on your server? Something like munin or influx+telegraf & grafana would give you historical stats for the memory usage etc and make it a lot easier to pinpoint the problem. maybe difficult to get going depending on your linux sysadmin skill level but well worth the effort.

alm · « **Reply #104 on:** July 19, 2017, 01:51:14 pm »

Linux considers free memory useless, so will try to fill it with cache or buffers. You should only worry if memory is almost full with little cache or buffers.

linux-works · « **Reply #105 on:** July 20, 2017, 03:01:06 am »

I have not checked all the threads; but I'm curious; WHAT HAS CHANGED since these errors started showing up?

did the content mgmt system get upgraded? anything upgraded? anything changed?

if nothing on the server side changed, it would have to be cloudflare.

and if its cloudflare, maybe its time to dump them.

but I suspect something at the code side has changed. do you guys have version controls so you can go back and find what happened when things broke (timeframe)?

Naguissa · « **Reply #106 on:** July 20, 2017, 06:02:09 am »

Quote from: EEVblog on July 19, 2017, 01:15:28 pm

Houston, we have a problem:

Noooooo!

Add 15Gb of buffers' 3rd col to free memory! You had half memory available!

What I don't know is why it was using 1.2Gb of swap with so much free ram.

Probably you have a (cron?) process that uses a lot of memory runing from time to time (backup process?).

Enviado desde mi Jolla mediante Tapatalk

alm · « **Reply #107 on:** July 20, 2017, 06:43:49 am »

Quote from: Naguissa on July 20, 2017, 06:02:09 am

What I don't know is why it was using 1.2Gb of swap with so much free ram.

Probably some data that has not been accessed for a long time. Might as well swap it out so you can use more memory as buffer if nobody is going to use that data anyhow. I find a few GB of swap usage quote normal for systems that have been running for a couple of days, even those with barely any memory pressure.

StillTrying · « **Reply #108 on:** July 20, 2017, 07:47:39 pm »

Site seem slow, the 502s will be along in a minute.

PA0PBZ · « **Reply #109 on:** July 20, 2017, 07:56:58 pm »

Quote from: StillTrying on July 20, 2017, 07:47:39 pm

Site seem slow, the 502s will be along in a minute.

Yep, just encountered the first one for today

floobydust · « **Reply #110 on:** July 20, 2017, 08:01:36 pm »

I got quite a few 502 errors today.
I have 32GB in my home PC, server needs more

pknoe3lh · « **Reply #111 on:** July 20, 2017, 08:06:50 pm »

Me too

M4trix · « **Reply #112 on:** July 20, 2017, 08:10:44 pm »

Maybe Aurora Australis is active these days !

PA0PBZ · « **Reply #113 on:** July 20, 2017, 08:14:45 pm »

It looks like it's back alive now. It is always the same pattern, the site gets slower and slower until it takes 15-20 seconds to load when you click a topic. Soon after that it will give you the famous 502 page which you can overcome by refreshing the page (Ctrl-F5) but it will still be slow. Then for some unknown reason it is back to normal like now.

StillTrying · « **Reply #114 on:** July 20, 2017, 08:17:18 pm »

Quote from: PA0PBZ on July 20, 2017, 07:56:58 pm

Yep, just encountered the first one for today

I haven't seen one yet, but I recognize the slowdown just before they appear.

StillTrying · « **Reply #115 on:** July 20, 2017, 08:21:44 pm »

Yep, it has recovered to full speed now, I managed to not see any 502s.

richnormand · « **Reply #116 on:** July 21, 2017, 02:30:45 pm »

Got the same error yesterday or the day before. It was doing it despite rebooting the computer.

I then went to my laptop (via WiFi but on the same router as my main computer) and the link was working just fine.
I then went back the main computer and I got the gateway error again.

Using CCleaner I cleaned up all the cookies and caches on the machine and ran a registry scan. All is OK now.

Looks like a cookie or cache from the Chrome browser, acquired when there was a real bad gateway issue with the forum, was doing this even though the forum was OK now.

I'll see if that is repeatable next time there is an issue.

tautech · « **Reply #117 on:** July 22, 2017, 04:55:37 am »

The forum is seriously sick, 502's one after another.
Pot luck if you can get access to any board or thread and if you want to make a post, good luck with that too.

Copy all info typed and pray when you go to post that it gets accepted.
The Preview when it works at least puts your efforts on the server and then you can play the Post>Back>Post>Back>Post game.

When you send a command (press link) if it doesn't get bounced back immediately with a 502, the server seems to take an age to respond (20s) before the browser indicates it's loading.

My poor F5 has never had such a hiding.

Calling gnif, come in gnif.

Edit to add.
When accessing the last post in a thread you briefly get to see it and when page then finishes loading your looking at the top of the page.

Somethings seriously sick.

KE5FX · « **Reply #118 on:** July 22, 2017, 06:15:56 am »

Muttley Snickers · « **Reply #119 on:** July 22, 2017, 06:24:12 am »

What a nightmare, probably not related at all but I even had trouble trying to get on to the #eevblog IRC channel for some news or other peoples connection status, if the main forum page does load then you should look at the last post times to verify that the page is live and not a historical cached version.

ebastler · « **Reply #120 on:** July 22, 2017, 06:29:42 am »

Quote from: richnormand on July 21, 2017, 02:30:45 pm

Got the same error yesterday or the day before. It was doing it despite rebooting the computer.

I then went to my laptop (via WiFi but on the same router as my main computer) and the link was working just fine.
I then went back the main computer and I got the gateway error again.

Using CCleaner I cleaned up all the cookies and caches on the machine and ran a registry scan. All is OK now.
Looks like a cookie or cache from the Chrome browser, acquired when there was a real bad gateway issue with the forum, was doing this even though the forum was OK now.

I'll see if that is repeatable next time there is an issue.

Mate, this error has nothing to do with your computer. It's the server which has problems. No need for you to reboot or fiddle around otherwise.

RoGeorge · « **Reply #121 on:** July 22, 2017, 06:40:42 am »

Starting a few hours, the 502 err started again for me. Since then it was VERY consistent. Always 502 err bad gateway. I was using Win10/Mozilla.

Trying to debug a little, when tested with Tor under a Debian 8 VMware machine, EEVblog was consistently working just fine.

Under Mozilla/Win10 I use to access EEVblog by clicking a bookmark saved long time ago. My Mozilla/Win10 bookmark was pointing to "https://www.eevblog.com/forum/". If I edit the link in the address bar to use https, "https://www.eevblog.com/forum/" then it's working OK.

To sum up:
VMware/Linux/Tor/http - always working
VMware/Linux/Tor/https - always working

Win10/Mozilla/http - 502 bad gateway
Win10/Mozilla/https - always working

In conclusion, using https instead of http helped me to get rid of the 502 error on Win10/Mozila.

1Ghz · « **Reply #122 on:** July 22, 2017, 06:43:04 am »

Quote from: ebastler on July 22, 2017, 06:29:42 am

Mate, this error has nothing to do with your computer. It's the server which has problems. No need for you to reboot or fiddle around otherwise.

You are right.
HTTP error codes 5xx are server side errors. Not client side.

Electro Detective · « **Reply #123 on:** July 22, 2017, 08:20:24 am »

Welcome Back to 502 City a few hours ago

All good again, like nothing happened

Are there any ad thingies interfering with the works perhaps?

Anyway guys, don't break Dave's balls about it,

he's supplying the forum for FREE after all

and it will get sorted out when it does

Meanwhile, back at the WWW superhighway...

not1xor1 · « **Reply #124 on:** July 22, 2017, 08:56:40 am »

here:
linux (kubuntu 14.04):
firefox 54.0 = bad gateway Error

chromium 59.0.3071.109 = no problem


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: Return of 502- Bad gateway Error (Read 57909 times)

Share me