I am still having problems with working via cell phone.
~ Peggy M 1949 Chevrolet 3804 "Charlie" - The Stovebolt Flagship In the Gallery || In the Gallery Forum "I didn't see this one coming. I don't see much of anything coming. :-O"
Was slow loading pages yesterday, fast early this morning and slow again now. I thought it was just me until I realized other web sites were operating at expected speeds.
'57 GMC 102, Original 347 V8, HydraMatic, 3.08 rear gear, added A/C, disk front brakes, HEI, AFB carb, '98 Honda Black Currant paint. T-boned and totaled 10/12 '52 GMC 152 Stake Bed, Original 228, SM420, added A/C, HEI, disk front brakes, '67 Chev 3.55 rear gear. Gets used as a real truck.
Bill, me too and worse than my *normal* slow speed ... and like you, only on Stovebolt. I just sent an email to Paul to see if he can find an explanation.
~ Peggy M 1949 Chevrolet 3804 "Charlie" - The Stovebolt Flagship In the Gallery || In the Gallery Forum "I didn't see this one coming. I don't see much of anything coming. :-O"
Kevin 1951 Chevy 3100 work truck Follow this saga in Project Journal Photos 1929 Ford pickup restored from the ground up. | 1929 Ford Special Coupe (First car) Busting rust since the mid-60's If you're smart enough to take it apart, you darn well better be smart enough to put it back together.
aaauggggggggggghhhhhhhhhhh. Even a click to Active Threads I have to wait. And here I wondered if it was the "corners news."
more like
~ Peggy M 1949 Chevrolet 3804 "Charlie" - The Stovebolt Flagship In the Gallery || In the Gallery Forum "I didn't see this one coming. I don't see much of anything coming. :-O"
Yes, we're having page-loading problems, and yes, it's been reported to the hosting company. It appears to be routing issues with the intermeidary hosts, but we'll let the hosting company figure it out.
I don't know if this will help any, but I sometimes get this after a few minutes of waiting:
Last edited by Bill Hanlon; 10/16/20248:04 PM.
'57 GMC 102, Original 347 V8, HydraMatic, 3.08 rear gear, added A/C, disk front brakes, HEI, AFB carb, '98 Honda Black Currant paint. T-boned and totaled 10/12 '52 GMC 152 Stake Bed, Original 228, SM420, added A/C, HEI, disk front brakes, '67 Chev 3.55 rear gear. Gets used as a real truck.
~ Peggy M 1949 Chevrolet 3804 "Charlie" - The Stovebolt Flagship In the Gallery || In the Gallery Forum "I didn't see this one coming. I don't see much of anything coming. :-O"
It was working pretty good and now it's slow again.
~ Peggy M 1949 Chevrolet 3804 "Charlie" - The Stovebolt Flagship In the Gallery || In the Gallery Forum "I didn't see this one coming. I don't see much of anything coming. :-O"
~ Peggy M 1949 Chevrolet 3804 "Charlie" - The Stovebolt Flagship In the Gallery || In the Gallery Forum "I didn't see this one coming. I don't see much of anything coming. :-O"
REALLY SLOW! I'm drinking too much coffee between mouse clicks.
Kevin 1951 Chevy 3100 work truck Follow this saga in Project Journal Photos 1929 Ford pickup restored from the ground up. | 1929 Ford Special Coupe (First car) Busting rust since the mid-60's If you're smart enough to take it apart, you darn well better be smart enough to put it back together.
When I first came on tonight it wouldn't go from the home page to "forums". So I left and came back later. Then the forums opened right up, but it took forever to log in. Once that finally happened, it worked normally.
Still issues logging in this morning. Once in though, it’s fine.
Phil Moderator, The Engine Shop, Interiors and Project Journals
1952 Chevrolet 3100, Three on the Tree, 4:11 torque tube Updated to: ‘59 235 w/hydraulic lifters, 12v w/alternator, HEI, PCV and Power front Disc Brakes Project Journals Stovebolt Gallery Forum
I'm not having any problems with initial main forum page display time (before signing in), or when moving from page to page/post to post when just reading. Any action, like posting a reply or editing a post of my own etc. still has about a 10 second delay time for the action to take place. Had that delay when signing in, replying to a post, editing a post, or any other action (including moderator functions). Not receiving any error message so far, just a time lag in action completion.
~ Dan 1951 Chevy 3 window 3100 Follow this story in the DITY Gallery "My Grandpa Carl's Truck and How it Became Mine" 1966 Chevelle (Wife's Hot Rod) | 2013 Chevy Silverado (Current daily driver) US Army MSG Retired (1977-1998) | Com Fac Maint Lead Tech Retired (1998-2021)
Dear me dear me. It's been slow but every once in awhile, it's normal. But that's been rare. Just a while ago I got another "Gateway timed out" message. When I refreshed, it took a very long time to finally get to this page.
What in the world could be going on? We have had the lowest number of Members on-line this day. Lots of Guests ... but I wonder if they try and just leave.
~ Peggy M 1949 Chevrolet 3804 "Charlie" - The Stovebolt Flagship In the Gallery || In the Gallery Forum "I didn't see this one coming. I don't see much of anything coming. :-O"
.... Whatever was done was done by zayo.com, because they are where the problem was.
What did THEY do? The pop-up on their website makes it sound like they want to take us to the "next level." Is what they did gave us an occasional boost; and who got that going?
When I posted this, I got the fatal error message again. But I checked in another tab and this post was there.
Last edited by Peggy M; 10/17/20248:37 PM.
~ Peggy M 1949 Chevrolet 3804 "Charlie" - The Stovebolt Flagship In the Gallery || In the Gallery Forum "I didn't see this one coming. I don't see much of anything coming. :-O"
What in the world could be going on? We have had the lowest number of Members on-line this day. Lots of Guests ... but I wonder if they try and just leave.
I'm going to respond with some traceroutes.
Here's how the internet works. Your computer makes a request on the stovebolt website (please show me this page). That request is passed through your internet provider (A), who passes the request to his internet provider (B). That provider then asks his provider (C) do you know where this site is? C then says, yes, and I will deliver it. C delivers the request to D who then delivers it to E who then delivers it to F etc., etc., etc. until the request ends up at www.stovebolt.com.
Stovebolt.com then responds (Here's the page you asked for). That response then goes through etc.,etc., etc., to F, to E, to D, to C, to B, to A, who provides it to you.
All of this is done by machines called routers. And, each router asks "what's the best route to this host?" The router that responds, "I am!" gets the request. If a router is down, some other, less optimal route to stovebolt will end up being used. And the return route may not be the same as the sending route.
Think of it like short haul trucks picking up a package at your house, delivering to their local terminal where it get sorted and then routed to its destination. There may be two trucks involved in delivering it. There may be ten. Depends on the delivery methods and practices of the various trucking companies involved, where bridges are closed, or routes are closed, etc. and how far away the destination is. Obviously, the best route is interstate highways but sometimes secondary or even tertiary routes must be used..
One thing all methods have in common is that, no matter where the request begins, they always end up at the same place (www.stovebolt.com), and they likely share several stops along the way (usually the ones closest to stovebolt.) You should notice that you see 38.140.105.74 in a lot (but not all) of these traces.
The default timeout for traceroutes is 4 seconds. If it takes longer than that to get a response, the trace moves to the next router. Timeouts are represented by the empty lines in the trace.
Now, this is a traceroute from Frankfurt, Germany.
Quote
Host Packet Loss Average Best Worst 1. 79.127.216.76 unn-79-127-216-76.datapacket.com 0% 0.1 ms 0.1 ms 0.1 ms 2. 169.150.194.48 vl215.fra-itx7-core-1.cdn77.com 0% 0.5 ms 0.4 ms 0.5 ms 3. - 4. 154.54.77.82 be2889.ccr41.fra05.atlas.cogentco.com 0% 1.3 ms 1.1 ms 1.6 ms 5. 154.54.63.74 be5535.ccr42.par01.atlas.cogentco.com 0% 10.3 ms 10.2 ms 10.3 ms 6. 154.54.89.225 be3111.ccr42.dca01.atlas.cogentco.com 0% 95.2 ms 95.1 ms 95.3 ms 7. 154.54.24.222 be2113.ccr42.atl01.atlas.cogentco.com 0% 103.2 ms 103 ms 103.3 ms 8. 154.54.163.54 be5027.ccr32.dfw01.atlas.cogentco.com 0% 117.3 ms 117.1 ms 117.4 ms 9. 154.54.47.214 be2764.ccr41.dfw03.atlas.cogentco.com 0% 118 ms 117.7 ms 118.3 ms 10. 38.140.105.74 0% 117.1 ms 117.1 ms 117.1 ms 11. 108.174.193.28 stovebolt.com 0% 117 ms 117 ms 117 ms
And this is a traceroute from Bangkok, Thailand.
Quote
Host Packet Loss Average Best Worst 1. - 2. 107.155.27.144 0% 11.6 ms 11.4 ms 11.8 ms 3. 107.155.27.138 0% 5.4 ms 5.4 ms 5.4 ms 4. 107.155.27.70 0% 0.9 ms 0.8 ms 0.9 ms 5. 128.1.108.106 0% 0.8 ms 0.8 ms 0.8 ms 6. 98.98.230.196 0% 23.2 ms 23.2 ms 23.2 ms 7. 98.98.230.188 0% 23.1 ms 23.1 ms 23.1 ms 8. 23.91.111.233 0% 23.1 ms 23.1 ms 23.2 ms 9. 116.51.27.101 ae-3.a03.sngpsi07.sg.bb.gin.ntt.net 0% 23.4 ms 23.3 ms 23.4 ms 10. - 11. - 12. - 13. 129.250.7.68 ae-3.r22.dllstx14.us.bb.gin.ntt.net 0% 224.4 ms 224.4 ms 224.4 ms 14. 129.250.3.47 ae-29.a00.dllstx14.us.bb.gin.ntt.net 0% 229.4 ms 229.4 ms 229.5 ms 15. 128.241.1.226 xe-5-5-1-1.a00.dllstx14.us.ce.gin.ntt.net 0% 235.8 ms 235.8 ms 235.8 ms 16. 108.174.193.28 stovebolt.com 0% 228 ms 228 ms 228 ms
And this is a traceroute from New York City.
Quote
Host Packet Loss Average Best Worst 1. 138.199.40.60 unn-138-199-40-60.datapacket.com 0% 0.4 ms 0.1 ms 0.5 ms 2. 169.150.194.92 vl212.nyc-tlx3-core-2.cdn77.com 0% 0.9 ms 0.6 ms 1 ms 3. - 4. 154.54.3.125 be3363.ccr42.jfk02.atlas.cogentco.com 0% 1.4 ms 1.1 ms 1.5 ms 5. 154.54.30.121 port-channel4188.ccr92.dca04.atlas.cogentco.com 0% 5 ms 4.9 ms 5.2 ms 6. 154.54.162.222 be5042.ccr41.dca01.atlas.cogentco.com 0% 5.7 ms 5.4 ms 5.8 ms 7. 154.54.7.158 be2112.ccr41.atl01.atlas.cogentco.com 0% 22.3 ms 21.9 ms 22.5 ms 8. 154.54.163.42 be5024.ccr31.dfw01.atlas.cogentco.com 0% 36.7 ms 36.5 ms 36.9 ms 9. 154.54.28.74 be2763.ccr41.dfw03.atlas.cogentco.com 0% 36.7 ms 36.4 ms 36.8 ms 10. 38.140.105.74 0% 36.8 ms 36.6 ms 36.9 ms 11. 108.174.193.28 stovebolt.com 0% 36.5 ms 36.3 ms 36.6 ms
And here's one from my laptop.
Quote
traceroute www.stovebolt.com traceroute to www.stovebolt.com (108.174.193.28), 64 hops max, 40 byte packets 1 192.168.1.254 (192.168.1.254) 3.613 ms 3.460 ms 1.780 ms 2 99-48-0-1.lightspeed.dllstx.sbcglobal.net (99.48.0.1) 3.024 ms 3.081 ms 3.155 ms 3 71.155.70.201 (71.155.70.201) 3.706 ms 4.140 ms 3.830 ms 4 * * * 5 * * * 6 * * * 7 38.140.105.74 (38.140.105.74) 10.456 ms 38.140.105.66 (38.140.105.66) 6.684 ms 38.140.105.74 (38.140.105.74) 7.647 ms 8 stovebolt.com (108.174.193.28) 19.105 ms 21.775 ms 20.014 ms
If you look at my traceroute, you will notice something strange.
Quote
7 38.140.105.74 (38.140.105.74) 10.456 ms 38.140.105.66 (38.140.105.66) 6.684 ms 38.140.105.74 (38.140.105.74) 7.647 ms
38.140.105.74 hands the request off to 38.140.105.66 (another router on the same network) which then hands it BACK to 38.140.105.74. That's strange. That may indicate a problem at that network.That is PSINet, Inc. But, I can guarantee that they won't talk to me, because I am not their customer. (I've tried this numerous times in the past.)
The stovebolt server is working fine. The routes to the server are not. In other words, there's not a single thing we can do to fix this problem. We just have to suffer through it.
30-45 seconds per page load, and I usually have to hit "refresh" to get a post to appear. If I log out and back in, the speed is normal for 2-3 page changes, then back to the stovebolt glacier again!
"It is better to be silent and be thought a fool than to speak and eliminate all doubt!" - Abraham Lincoln Cringe and wail in fear, Eloi- - - - -we Morlocks are on the hunt! There is nothing noble in being superior to your fellow man; true nobility is being superior to your former self. - Ernest Hemingway Love your enemies and drive 'em nuts!
Our hosting company has asked us to provide mtrs. You can download mtr for Windows here: https://sourceforge.net/projects/winmtr/ Once it's installed, run it and type www.stovebolt.com in the window at tht top. Let it run for about 15 minutes. Then copy and paste the results into a reply to this thread.
Hopefully, these will help our hosting company understand and pinpoint the problem.
Here is 15 minutes of running WinMTR as you requested. Time was 07:15 to 07:30 CDT. I was accessing Stovebolt while the trace was running. The site was NOT exhibiting the long delays during the trace capture. I live in the boondocks. The internet connection from my house to the rest of the world is a 4G/LTE phone. Download speed (Speedtest by Ookla) right now is 43 Mbits/sec. Upload is 0.92 Mbits/sec.
'57 GMC 102, Original 347 V8, HydraMatic, 3.08 rear gear, added A/C, disk front brakes, HEI, AFB carb, '98 Honda Black Currant paint. T-boned and totaled 10/12 '52 GMC 152 Stake Bed, Original 228, SM420, added A/C, HEI, disk front brakes, '67 Chev 3.55 rear gear. Gets used as a real truck.
Here's a couple sessions. the first when browsing the site, and having pretty good response. I copied the results, then went back to browsing and noticed it was really slow, so started it running again and got a second set of results. I ran for about 10 minutes each time. The only significant difference I can see is the packet size changed. [on edit] that's not packet size, it just accumulates. Hope that helps them figure out what's up.
Here's the numerical IP addresses for my Traceroute (I'm currently in SoCAL) Internet speed from here is 300+ down and 250+ up. So should be pretty snappy. 192.168.4.1 192.168.254.254 47.155.26.1 74.42.113.25 74.40.3.229 45.52.201.143 No response from host 154.54.0.165 154.54.44.85 154.54.166.57 154.54.165.25 154.54.28.74 38.140.105.74 108.174.193.28
Last edited by klhansen; 10/18/20244:13 PM. Reason: added more info
Kevin 1951 Chevy 3100 work truck Follow this saga in Project Journal Photos 1929 Ford pickup restored from the ground up. | 1929 Ford Special Coupe (First car) Busting rust since the mid-60's If you're smart enough to take it apart, you darn well better be smart enough to put it back together.
'57 GMC 102, Original 347 V8, HydraMatic, 3.08 rear gear, added A/C, disk front brakes, HEI, AFB carb, '98 Honda Black Currant paint. T-boned and totaled 10/12 '52 GMC 152 Stake Bed, Original 228, SM420, added A/C, HEI, disk front brakes, '67 Chev 3.55 rear gear. Gets used as a real truck.
For the last few minutes, my speed and ability to go from one spot to another is like the old normal.
~ Peggy M 1949 Chevrolet 3804 "Charlie" - The Stovebolt Flagship In the Gallery || In the Gallery Forum "I didn't see this one coming. I don't see much of anything coming. :-O"
Thank you Bill, KL, and Gord. I've posted a link to this thread in the ticket I opened with the hosting company. If you would provide these every time the site is slow, that would be very helpful.
Mine faster again. Easy to go to threads. Takes a little more time when I post, tho.
~ Peggy M 1949 Chevrolet 3804 "Charlie" - The Stovebolt Flagship In the Gallery || In the Gallery Forum "I didn't see this one coming. I don't see much of anything coming. :-O"
As I coninue to work through this problem, I've come to the conclusion that the forum is the problem. Every other page on the website loads instantly. When I run top, it shows extremely high cpu usage for the database server (which is the forum.)
Code
top
top - 15:40:50 up 37 days, 21:50, 2 users, load average: 7.19, 15.83, 27.35
Tasks: 274 total, 3 running, 271 sleeping, 0 stopped, 0 zombie
%Cpu(s): 39.6 us, 39.2 sy, 0.0 ni, 20.9 id, 0.1 wa, 0.1 hi, 0.1 si, 0.0 st
MiB Mem : 15718.4 total, 1303.4 free, 1961.1 used, 12454.0 buff/cache
MiB Swap: 4000.0 total, 3809.3 free, 190.7 used. 13370.9 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3071685 mysql 20 0 4974296 506424 38448 S 516.3 3.1 71:46.41 mysqld
3071874 apache 20 0 765364 56580 19292 R 20.3 0.4 0:15.25 php-fpm
3071973 apache 20 0 743916 37640 19740 S 19.9 0.2 0:10.23 php-fpm
3071958 apache 20 0 739824 33888 20060 S 18.3 0.2 0:11.03 php-fpm
3072413 apache 20 0 764840 56512 20248 R 17.3 0.4 0:10.91 php-fpm
3071965 apache 20 0 745968 39764 19804 S 12.6 0.2 0:13.08 php-fpm
3072414 apache 20 0 739820 33020 19228 S 8.0 0.2 0:09.17 php-fpm
3071127 apache 20 0 741872 36664 20764 S 5.3 0.2 0:37.67 php-fpm
3072405 apache 20 0 739820 33488 19676 S 4.3 0.2 0:09.56 php-fpm
3071875 apache 20 0 733676 27668 20000 S 1.3 0.2 0:14.09 php-fpm
3072408 apache 20 0 737780 31176 19420 S 1.3 0.2 0:09.37 php-fpm
3069386 apache 20 0 2505452 24460 9000 S 0.3 0.2 0:02.43 httpd
3069599 apache 20 0 2505452 25624 9080 S 0.3 0.2 0:02.79 httpd
3069666 apache 20 0 2505452 28176 9144 S 0.3 0.2 0:03.54 httpd
3069873 apache 20 0 2505452 25528 9272 S 0.3 0.2 0:03.07 httpd
3070009 apache 20 0 2505452 23932 9336 S 0.3 0.1 0:02.90 httpd
3070651 root 20 0 264640 5048 3720 S 0.3 0.0 0:07.27 top
Mysql (the database) is using 516.3% of CPU???
That is clearly abnormal. So, I did some testing. I closed the forum, stopped and restarted mysql, reopened the forum, and ran top again. Same problem.
Then I closed the forum and ran top. Mysql was using 0.7% of cpu.
So, something is causing mysql to consume tons of CPU. And that drives response times into the stratosphere.
I"ve noticed recently that our pageview counts have been dramatically higher than normal. (4000 to 6000+) I'm now wondering if we're under some sort of denial of service attack. It's either that, or the forum software is the problem. I have a ticket open with the hosting company actively working this problem, and I have a thread started at UBB to discuss it.
~ Peggy M 1949 Chevrolet 3804 "Charlie" - The Stovebolt Flagship In the Gallery || In the Gallery Forum "I didn't see this one coming. I don't see much of anything coming. :-O"
The site is running fine now. I'll repost numbers the next time I notice it running slow. I just got home from the gym, so I need a shower (and maybe a little nap) right now.
'57 GMC 102, Original 347 V8, HydraMatic, 3.08 rear gear, added A/C, disk front brakes, HEI, AFB carb, '98 Honda Black Currant paint. T-boned and totaled 10/12 '52 GMC 152 Stake Bed, Original 228, SM420, added A/C, HEI, disk front brakes, '67 Chev 3.55 rear gear. Gets used as a real truck.
Correction. I got the "fatal error" when I hit send. But the post still showed up in Active Thread.
Last edited by Peggy M; 10/18/202411:58 PM.
~ Peggy M 1949 Chevrolet 3804 "Charlie" - The Stovebolt Flagship In the Gallery || In the Gallery Forum "I didn't see this one coming. I don't see much of anything coming. :-O"
Isn't Alibaba the Chinese version of Amazon? What would they be doing in a conversation between my computer and Stovebolt?
'57 GMC 102, Original 347 V8, HydraMatic, 3.08 rear gear, added A/C, disk front brakes, HEI, AFB carb, '98 Honda Black Currant paint. T-boned and totaled 10/12 '52 GMC 152 Stake Bed, Original 228, SM420, added A/C, HEI, disk front brakes, '67 Chev 3.55 rear gear. Gets used as a real truck.
Isn't Alibaba the Chinese version of Amazon? What would they be doing in a conversation between my computer and Stovebolt?
Yes, Alibaba is the Chinese version of Amazon. What they were doing was hammering the server with hundreds of requests per minute. They weren't getting between you and Stovebolt. They were forcing Stovebolt to handle so many requests that it slowed down the response time. Over 700,000 requests in 24 hours. That's almost 30,000 requests per hour, or 486 requests per minute or 8 requests each second. In other words, they tripled our traffic. If we ever got to that level of legitimate traffic, we would need multiple servers configured in a load balancing configuration to handle the requests. If that ever happens, I'll be resigning immediately.
Paul - That's nuts!!! On a slightly different tack I found multiple instances (around 10) last night and this morning with almost all of them originating from ISP's in France of "Guests" shown as "Logging In"???
Screen shots of the partial guest lists and IP address check results below show the IP's and ISP involved. Is this something related to what is slowing things down, or should this be reported in another way?
Just my thought process that multiple IP's from the same server, all showing what appears to be efforts to Log In, might be bad actors trying to gain unauthorized member level access?
The primary IP involved last night and this morning (with 9-10 listed Guests as Logging In) is 217.113.194.XX. ISP = Hostname:c078.babbar.eu / ASN:210743 / L'ile aux surfers s.a.r.l. / Services:Datacenter
There is also another single Guest Logging In at IP = 154.54.249.200 / ISP = Hostname:crawl-prodd4-8.babbar.eu / ASN:210743 / ISP:Babbar / Services:None detected, located in a different part of France that shows both last night and this morning.
Please let me know if I need to move this report elsewhere or if no further action is needed.
Thanks!
NOTE: A recheck after almost 2 hours since this posted and the same "Guests" are still listed as "Loggin In" (added 1 more screenshot)
Last edited by Gdads51; 10/19/20243:19 PM. Reason: added note and another screenshot of WOL
~ Dan 1951 Chevy 3 window 3100 Follow this story in the DITY Gallery "My Grandpa Carl's Truck and How it Became Mine" 1966 Chevelle (Wife's Hot Rod) | 2013 Chevy Silverado (Current daily driver) US Army MSG Retired (1977-1998) | Com Fac Maint Lead Tech Retired (1998-2021)
more like 
