This weekend we're moving the main PJRC website to a new server. Hopefully everything will go smoothly and the only disruption will be the shopping cart offline for several hours.
The forum is hosted by a separate server, so if you're seeing this but the main site is having trouble, as least DNS is working well enough for your browser to find the forum's server.
Good morning Paul
So far can see the forum and product pages. Only thing that seems to be offline is the actual shopping cart as you said.
At this point, you're still seeing the old server (96.31.77.63). The real fun starts later today!
Oh boy going to be a fun day.fingers crossed
The server switch-over is at about 95%. Hopefully the site is all working at the new server (162.254.150.250)?
Question... are you getting the forum's notification emails?
Seems to have gotten right here:
Cart seems to be working - up to not sending me free stuff from the CART with no credit card provided.Code:>ping pjrc.com Pinging pjrc.com [162.254.150.250] with 32 bytes of data: Reply from 162.254.150.250: bytes=32 time=83ms TTL=44 Reply from 162.254.150.250: bytes=32 time=83ms TTL=44 Reply from 162.254.150.250: bytes=32 time=83ms TTL=44 Reply from 162.254.150.250: bytes=32 time=83ms TTL=44 Ping statistics for 162.254.150.250: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 83ms, Maximum = 83ms, Average = 83ms
Forum still seems #'s noted in p#3 as old:
Did a flushdnsCode:>ping forum.pjrc.com Pinging forum.pjrc.com [96.31.69.28] with 32 bytes of data: Reply from 96.31.69.28: bytes=32 time=83ms TTL=46 Reply from 96.31.69.28: bytes=32 time=83ms TTL=46
Pretty much did what @defragster did with going to the new server location and trying the cart. So ditto - seems to be working up to that point.
Last forum notification I got was from you at 2:44 am in my inbox. Nothing after that. So will see soon I guess
Is there anything that we should be looking for?
That is, was this a "simple" server change or was there other things that changed as well?
My guess is simple is never simple!
I noticed recently that you rearranged how the 32 bit products are arranged, but again I believe that was before the move.
That is if I have this page:
And click on the 32 bit products on left hand list, I end up at:
You probably don't want to go to the legacy page instead of the T4.x page...
But again don't think this is related to server change
Indeed it's never that simple. The forum also needs to change IP number. Looks like it will become 66.232.106.something.
The hosting company is working on remote console access, which apparently never got set up for this server.
The main site still has several minor things broken, like automated backup and the script that updates the inventory status and date last counted. So far looks like most of the things still needing work will (probably) only affect me and Robin.
Yup, edited the Teensy 3.x pages several days ago. Indeed that product page needs to be edited. But that too is not so simple. It's tied up with the blog theme rather than the scripts that generate the navigation html for the rest of the site.
Oh, looks like we're going to have about 20 minutes down time.... soon, while they do some sort of reconfiguration on the server. Should be just the forum down. Main site should stay up.
Well, we had over an hour with the forum offline this morning. Wish I could say that would be the last, but still another reboot will be needed.
Just got home and missed the down time.Originally Posted by PaulStoffregen
Know this might be a loaded question but with the server change are you planning on making any changes to the forum or the product pages? Know that would be long term though.
Right now, the urgent situation is IP numbers are getting reassigned, so we have to switch to different IP numbers. Both servers need to change IP numbers.
The path of least resistance probably would have been to get DNS hosted elsewhere, then reconfigure the existing servers and edit the DNS zone files.
We've been planning for years to replace both servers with newer machines and update to newer software. For the main site all the software would stay pretty much the same, just newer versions, faster hardware, larger storage, higher bandwidth allocated. Upgrading the forum is a lot more involved, probably a migration from vBulletin4 to XenForo.
So for this IP number issue, I decided to migrate the main server to new hardware, and then we'll just keep the forum server as-is but with different IP number. Doing both at once seemed like far more than I could do in a matter of days. In hindsight, I'm kinda wishing I would have just gone the easy route. But over the last couple days I've fixed a lot of minor things that would have eventually needed updating, like strftime() deprecated in PHP 8.1.
For future plans, we need to eventually get off vBulletin. Probably should have done it many years ago.
The main website could also use a lot of work, but most of that will look like static html, static images and maybe video.
If you're seeing the forum and this message, you're (hopefully) accessing the server at IP 66.232.106.106.
Code:C:\Users\kurte>ping pjrc.com Pinging pjrc.com [162.254.150.250] with 32 bytes of data: Reply from 162.254.150.250: bytes=32 time=506ms TTL=42 ... C:\Users\kurte>ping forum.pjrc.com Pinging forum.pjrc.com [66.232.106.106] with 32 bytes of data: Request timed out. Reply from 66.232.106.106: bytes=32 time=283ms TTL=42 Reply from 66.232.106.106: bytes=32 time=284ms TTL=42 Reply from 66.232.106.106: bytes=32 time=259ms TTL=42 ...
Glad you're seeing the forum at the new IP number.
But wow, such long ping times. I get about 78ms from here. Wonder if it's a problem elsewhere?
Times look the same to the new from here. Did a cache flush - maybe if not done there is a redirect lookup?
Code:C:\T_Drive\Programs\iperf>ipconfig /flushdns Successfully flushed the DNS Resolver Cache. C:\T_Drive\Programs\iperf>ping pjrc.com Pinging pjrc.com [162.254.150.250] with 32 bytes of data: Reply from 162.254.150.250: bytes=32 time=83ms TTL=44 Reply from 162.254.150.250: bytes=32 time=83ms TTL=44 Reply from 162.254.150.250: bytes=32 time=83ms TTL=44 Reply from 162.254.150.250: bytes=32 time=84ms TTL=44 C:\T_Drive\Programs\iperf>ping forum.pjrc.com Pinging forum.pjrc.com [66.232.106.106] with 32 bytes of data: Reply from 66.232.106.106: bytes=32 time=83ms TTL=45 Reply from 66.232.106.106: bytes=32 time=86ms TTL=45 Reply from 66.232.106.106: bytes=32 time=83ms TTL=45 Reply from 66.232.106.106: bytes=32 time=86ms TTL=45 C:\T_Drive\Programs\iperf>ping forum.pjrc.com Pinging forum.pjrc.com [66.232.106.106] with 32 bytes of data: Reply from 66.232.106.106: bytes=32 time=83ms TTL=45 Reply from 66.232.106.106: bytes=32 time=83ms TTL=45 Reply from 66.232.106.106: bytes=32 time=83ms TTL=45 Reply from 66.232.106.106: bytes=32 time=83ms TTL=45
Morning all, saw there was a reboot this morning
Code:C:\Users\Merli>ping forum.pjrc.com Pinging forum.pjrc.com [66.232.106.106] with 32 bytes of data: Reply from 66.232.106.106: bytes=32 time=40ms TTL=54 Reply from 66.232.106.106: bytes=32 time=38ms TTL=54 Reply from 66.232.106.106: bytes=32 time=40ms TTL=54 Reply from 66.232.106.106: bytes=32 time=38ms TTL=54 Ping statistics for 66.232.106.106: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 38ms, Maximum = 40ms, Average = 39ms C:\Users\Merli>ping pjrc.com Pinging pjrc.com [162.254.150.250] with 32 bytes of data: Reply from 162.254.150.250: bytes=32 time=46ms TTL=54 Reply from 162.254.150.250: bytes=32 time=45ms TTL=54 Reply from 162.254.150.250: bytes=32 time=43ms TTL=54 Reply from 162.254.150.250: bytes=32 time=51ms TTL=54 Ping statistics for 162.254.150.250: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 43ms, Maximum = 51ms, Average = 46ms C:\Users\Merli>ping forum.pjrc.com Pinging forum.pjrc.com [66.232.106.106] with 32 bytes of data: Reply from 66.232.106.106: bytes=32 time=39ms TTL=54 Reply from 66.232.106.106: bytes=32 time=37ms TTL=54 Reply from 66.232.106.106: bytes=32 time=45ms TTL=54 Reply from 66.232.106.106: bytes=32 time=40ms TTL=54 Ping statistics for 66.232.106.106: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 37ms, Maximum = 45ms, Average = 40ms C:\Users\Merli>
Note: no incoming mail " ... has just replied to a thread " for the post:
Code:Today, 07:10 AM #15 PaulStoffregen
FYI, from LA area:
Code:MikesAir:~ michael$ ping forum.pjrc.com PING forum.pjrc.com (66.232.106.106): 56 data bytes 64 bytes from 66.232.106.106: icmp_seq=0 ttl=54 time=75.204 ms 64 bytes from 66.232.106.106: icmp_seq=1 ttl=54 time=77.956 ms 64 bytes from 66.232.106.106: icmp_seq=2 ttl=54 time=155.765 ms 64 bytes from 66.232.106.106: icmp_seq=3 ttl=54 time=84.648 ms 64 bytes from 66.232.106.106: icmp_seq=4 ttl=54 time=73.759 ms ^C --- forum.pjrc.com ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 73.759/93.466/155.765/31.373 ms
Probably. It is probably with the DNS that I am using. I think I still have it hard coded at my connection to my provider as something like: 1.1.1.1
Or might have been googles: 8.8.8.8
Was earlier having problems letting it default to the one by the provider as had times where it did not work at all for hours on end...
Getting 36 ms ping here in Texas (Houston area).
- Wes, W5ZZO
The servers are physically located in Tampa, Florida, USA. Just to put the ping times in perspective.
Can anyone outside the US comment with the ping times? Many times I've wondered if we should use a CDN. Or somehow use redundant servers in Europe and Asia.
I'm getting the same. Up the road a piece in Washington state...
Posting Permissions
Reply With Quote