Server Error Reports

[gnif]

Just FYI, since the last 10 hours or so, I can not access eevblog.com from Bucharest/Romania/EU.

However, the "is it down" type of websites show eevblog up all around the world but when I try to traceroute I get this:

Code: [Select]

traceroute eevblog.com
traceroute to eevblog.com (192.154.109.3), 30 hops max, 60 byte packets
 1  _gateway (192.168.100.1)  0.381 ms  0.576 ms  0.750 ms
 2  StamAcasa.rdsnet.ro (10.0.0.1)  5.356 ms  5.435 ms  5.498 ms
 3  10-30-0-65.rdsnet.ro (10.30.0.65)  5.553 ms  5.620 ms  5.701 ms
 4  10.220.153.179 (10.220.153.179)  5.685 ms 10.220.148.208 (10.220.148.208)  16.294 ms static-10-220-131-97.rdsnet.ro (10.220.131.97)  16.373 ms
 5  * * *
 6  * * *
 7  * * *
...
30  * * *
Host eevblog.com returns

Code: [Select]

host eevblog.com
eevblog.com has address 192.154.109.3
eevblog.com has address 192.154.111.219
eevblog.com mail is handled by 0 mail.eevblog.com.
Posted this using Tor browser, so it's using some other route to reach eevblog.  It seems like it's a routing problem on my side, though I've noticed the number of logged users right now (173) is lower than usual.  I suspect a wider area is affected, not just my ISP.  Changing the OS or restarting the router for a new IP doesn't help.

Today is also Friday The 13th   
 

No issues our side, as you have noted this is a routing issue and there is nothing here we can do about it.

[RoGeorge]

Starting this afternoon, I'm seeing 5-10 seconds delay to load a page, from EEVblog only, the very few other forums I use to visit doesn't seem affected.  Before, EEVblog forum pages used to load almost instantly (less than a second or so, never measured), but now I can count to 10-20 and the page still not shown.

Browsing from EU/Bucharest/Romania.

Anybody else seeing 5-10 seconds delay to load the "Show unread posts since last visit." or "Show new replies to your posts." pages, please?


Later edit:
Submitting this post also took 10-20 seconds to upload + display back the posted message. 

[RoGeorge]

False alarm, sorry.  Went out for groceries, and now it's all OK, as normal again. 

[MK14]

False alarm, sorry.  Went out for groceries, and now it's all OK, as normal again. 

Maybe not a false alarm.

I experienced exactly the same, in the last few days or maybe longer.  At the time, other webpages, worked just fine for me.

I didn't report it, in case the issue, was my side.  E.g. A EU wide internet issue.

But it seemed to eventually sort itself out, so I didn't report it.

[RoGeorge]

For me it was only today, for an hour or two, previous days were OK.  Now it's about normal again, not sure what happened.

[Ranayna]

Some line seems to have been clogged somewhere
I can confirm intermittent long loading times today and yesterday from germany as well.

[rsjsouza]

[off-topic]
From time to time I still feel amazement at how we nowadays almost take for granted that data traveling for thousands of kilometers has to reach its destination only seconds after it was commanded to be sent.

In Internet's early days, I recall giving a leg up to my data traffic by trace routing the destination IP to help either keep the route alive or eventually capture a slightly more efficient route - back when I browsed with no images and only enabled them when I had reached the page I wanted. This is something unthinkable these days, not only due to the sheer bandwidth available but also to the heavily scripted/crapified web pages with loads of graphical menus and options.
[/off-topic]

[gnif]

Nothing server side that shows any kind of issue and no latency issues from AU to US. Seems to be an issue with international routing to the server, as such there is nothing we can do about this but wait for it to be resolved.

@rsjsouza please don't post anything off-topic here, this thread is special in that it triggers a monitoring alarm if it sees activity.

[PlainName]

Just had the above reported symptoms. Viewing messages OK and then nothing for a minute, then OK again and a couple minutes later nothing. Once it had frozen and I got my act together (not easy at this time) I grabbed a tracert. This one seems to be down to the UK backbone, but if other countries are getting the same symptoms maybe there's a more global issue that's triggering local problems.

[MK14]

3:40 PM UK time (and UTC time is the same at the moment), 6/11/22.

Lots of delay, and lots of error messages (seems to happen on all forum pages):

502 Bad Gateway
nginx

On all pages, maybe (perhaps) 50% of the time.  I even got one (502), while I tried to get to this posting screen.

Had the problem for around the last twenty minutes.

But had delays, in recent day(s), as well.

[RoGeorge]

Same from here, very slow loading of 5...10+ seconds per forum webpage, sometimes ending not loading the forum page at all, and showing the "bad gateway nginx" webpage instead.

Later edit:
--------------
Now it's back to normal:  fast pages and no nginx errors 

[MK14]

Again I'm getting these intermittent delays (NOW!, UTC almost 5:00 PM).  From around 10 to 50 seconds and sometimes with:

502 Bad Gateway
nginx

It can be alright for a while (e.g. hours), then starts getting delays again and sometimes these 502's.

[MK14]

I'm currently getting massive delays, on most/all features.  So, most/all things take perhaps 10 seconds, maybe longer, to load.
My internet seems fine, but my adblocker, just updated, raising a tiny/small chance it is JUST ME.

It is so bad, I'm having to leave the forum, until it speeds up.

SPECULATION: There seem to have been lots of changes to the forum (software?), recently.  Which might have caused the issue(s).

[PA0PBZ]

I don't think that the recent changes have anything to do with it, but it is equally slow for me. Opening a thread should not take 15 seconds... Ping times to eevblog.com are a steady 130ms, not sure if that is normal or not, there is however a jump from 10 to 115 ms going from Amsterdam to Cogentco.

Edit: It's now more like 30 seconds 

[gnif]

Server performance metrics show all green, access times all green from the AU to the server, no abnormal latency noted.

Edit: testing an update

[McBryce]

The time needed to update a forum page here (in Germany) at the moment can be measured on a sundial!

McBryce.

[gnif]

The time needed to update a forum page here (in Germany) at the moment can be measured on a sundial!

McBryce.

Sorry mate, not a server issue our side, must be a connectivity issue on your end.

[PA0PBZ]

Sorry mate, not a server issue our side, must be a connectivity issue on your end.

Ping times to the server are a stable 130ms from several EU countries (FR, NL, UK) and 160ms from Sidney. It doesn't look like a connectivity issue. However, if you don't seen anything strange on the server there's not much we (you) can do.

[Bud]

No issues browsing in Toronto Canada.

[gnif]

Sorry mate, not a server issue our side, must be a connectivity issue on your end.

Ping times to the server are a stable 130ms from several EU countries (FR, NL, UK) and 160ms from Sidney. It doesn't look like a connectivity issue. However, if you don't seen anything strange on the server there's not much we (you) can do.

Ping times are not a good indicator for packet loss, or fragmentation. If you want something somewhat more reliable, use `mtr`

[PA0PBZ]

Yes. I agree but I used an online tool to check from several locations. MTR shows that there are indeed problems on the last hop before gorilla (38.104.174.42):

|-------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                    |
|                       Host              -   %   | Sent | Recv | Best | Avrg | Wrst | Last |
|-------------------------------------------------|------|------|------|------|------|------|
|                               fritz.box  -    0 |   70 |   70 |    0 |    0 |    0 |    0 |
|                 j139001.upc-j.chello.nl  -    0 |   70 |   70 |    7 |   10 |   23 |    8 |
|                          212.142.51.205  -    0 |   70 |   70 |    7 |   11 |   23 |   11 |
|asd-tr0021-cr101-be112-2.core.as33915.net -    0 |   70 |   70 |    8 |   11 |   23 |    9 |
|    nl-ams14a-ri1-ae51-0.core.as9143.net  -    0 |   70 |   70 |    8 |   12 |   40 |   10 |
|                   No response from host  -  100 |   15 |    0 |    0 |    0 |    0 |    0 |
|  be12265.ccr41.par01.atlas.cogentco.com  -    0 |   70 |   70 |  120 |  123 |  144 |  122 |
|   be3095.ccr41.dca01.atlas.cogentco.com  -    0 |   70 |   70 |  120 |  123 |  140 |  121 |
|   be2891.ccr21.cle04.atlas.cogentco.com  -    0 |   70 |   70 |  120 |  123 |  132 |  122 |
|   be2717.ccr41.ord01.atlas.cogentco.com  -    0 |   70 |   70 |  121 |  132 |  279 |  122 |
|   be2831.ccr21.mci01.atlas.cogentco.com  -    0 |   70 |   70 |  132 |  136 |  154 |  134 |
|   be3035.ccr21.den01.atlas.cogentco.com  -    0 |   70 |   70 |  143 |  147 |  159 |  145 |
|   be3037.ccr21.slc01.atlas.cogentco.com  -    0 |   70 |   70 |  163 |  168 |  189 |  168 |
|                           38.104.174.42  -   34 |   30 |   20 |  174 |  177 |  189 |  175 |
|104-250-157-167.static.gorillaservers.com -    0 |   70 |   70 |  136 |  138 |  147 |  137 |
|192-154-111-219.static.gorillaservers.com -    0 |   70 |   70 |  135 |  139 |  159 |  138 |
|_________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Oh well, we have to 'sit it out' I guess.

[MK14]

Sorry mate, not a server issue our side, must be a connectivity issue on your end.

Ping times to the server are a stable 130ms from several EU countries (FR, NL, UK) and 160ms from Sidney. It doesn't look like a connectivity issue. However, if you don't seen anything strange on the server there's not much we (you) can do.

Ping times are not a good indicator for packet loss, or fragmentation. If you want something somewhat more reliable, use `mtr`

I've tried mtr on linux, and seem to be getting HUGE packet losses.  The output, is as follows:

                                      My traceroute  [v0.94]
*************** -> www.eevblog.com                                      2022-12-06T15:14:24+0000
Keys:  Help  Display mode  Restart statistics  Order of fields  quit
                                                          Packets              Pings
Host                                                    Loss%  Snt  Last  Avg  Best  Wrst StDev
1. _gateway                                              0.0%    85    3.8  4.0  3.7  6.5  0.5
2. host-***************.net                        0.0%    85  32.5  32.0  31.3  33.7  0.5
3. ae******************.net                          0.0%    85  32.4  32.4  31.5  39.5  1.1
4. ae******************.net                          0.0%    85  32.7  34.8  32.0  69.3  6.2
5. ae******************.net                          0.0%    84  32.8  34.5  32.5  49.3  3.1
6. e0-30.core3.lon1.he.net                              0.0%    84  33.6  33.9  33.0  35.6  0.5
7. 100ge0-75.core3.lon2.he.net                          88.0%    84  72.4  59.7  33.7 146.6  37.4
8. port-channel2.core2.nyc5.he.net                      75.0%    84  102.1 101.1 100.0 104.5  1.1
9. e0-79.core3.nyc4.he.net                              89.2%    84  102.9 101.2 100.2 102.9  1.1
10. port-channel6.core2.mci3.he.net                      85.7%    84  132.6 130.8 126.6 154.1  7.8
11. port-channel2.core3.mci3.he.net                      76.2%    84  128.1 128.4 126.6 142.5  3.8
12. port-channel8.core2.den1.he.net                      88.0%    84  137.0 136.9 136.2 137.8  0.5
13. port-channel10.core2.slc1.he.net                    50.6%    84  147.4 148.5 147.4 153.6  1.2
14. webnx-inc.100gigabitethernet0-25.switch2.slc1.he.net 52.4%    84  185.4 186.4 185.2 188.9  0.8
15. 104-250-156-167.static.gorillaservers.com            42.2%    84  185.9 186.3 185.2 190.4  0.8
16. 192-154-109-3.static.gorillaservers.com              38.1%    84  185.5 185.6 184.5 187.1  0.6

[gnif]

Sorry mate, not a server issue our side, must be a connectivity issue on your end.

Ping times to the server are a stable 130ms from several EU countries (FR, NL, UK) and 160ms from Sidney. It doesn't look like a connectivity issue. However, if you don't seen anything strange on the server there's not much we (you) can do.

Ping times are not a good indicator for packet loss, or fragmentation. If you want something somewhat more reliable, use `mtr`

I've tried mtr on linux, and seem to be getting HUGE packet losses.  The output, is as follows:

                                      My traceroute  [v0.94]
mx (192.168.0.29) -> www.eevblog.com                                      2022-12-06T15:14:24+0000
Keys:  Help  Display mode  Restart statistics  Order of fields  quit
                                                          Packets              Pings
Host                                                    Loss%  Snt  Last  Avg  Best  Wrst StDev
1. _gateway                                              0.0%    85    3.8  4.0  3.7  6.5  0.5
2. host-62-24-254-204.as13285.net                        0.0%    85  32.5  32.0  31.3  33.7  0.5
3. ae53-ner002.bre.as13285.net                          0.0%    85  32.4  32.4  31.5  39.5  1.1
4. ae53-scr101.loh.as13285.net                          0.0%    85  32.7  34.8  32.0  69.3  6.2
5. ae61-scr101.thw.as13285.net                          0.0%    84  32.8  34.5  32.5  49.3  3.1
6. e0-30.core3.lon1.he.net                              0.0%    84  33.6  33.9  33.0  35.6  0.5
7. 100ge0-75.core3.lon2.he.net                          88.0%    84  72.4  59.7  33.7 146.6  37.4
8. port-channel2.core2.nyc5.he.net                      75.0%    84  102.1 101.1 100.0 104.5  1.1
9. e0-79.core3.nyc4.he.net                              89.2%    84  102.9 101.2 100.2 102.9  1.1
10. port-channel6.core2.mci3.he.net                      85.7%    84  132.6 130.8 126.6 154.1  7.8
11. port-channel2.core3.mci3.he.net                      76.2%    84  128.1 128.4 126.6 142.5  3.8
12. port-channel8.core2.den1.he.net                      88.0%    84  137.0 136.9 136.2 137.8  0.5
13. port-channel10.core2.slc1.he.net                    50.6%    84  147.4 148.5 147.4 153.6  1.2
14. webnx-inc.100gigabitethernet0-25.switch2.slc1.he.net 52.4%    84  185.4 186.4 185.2 188.9  0.8
15. 104-250-156-167.static.gorillaservers.com            42.2%    84  185.9 186.3 185.2 190.4  0.8
16. 192-154-109-3.static.gorillaservers.com              38.1%    84  185.5 185.6 184.5 187.1  0.6

Packet loss starts at hop 7, continues right up to the server. Not an eevblog server issue, please stop posting here now that this has been confirmed. This thread is special and triggers alerts to wake me for issues when it's posted to.

[IanB]

Suddenly seeing this a lot:

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

[sokoloff]

Same here. 2022-12-22 19:44-19:45 UTC