Linode itself is running slowly? (ongoing issue)
I really like Linode, it's the only VPS I have used, but I have only been into web development for about two years now. But anyway, when I visit Linode.com, or cloud.linode.com, it seems that the site, itself, takes quite a while to load. I get the green "L" across the screen and the three dots below it, and even that takes a minute to show up. And then it takes me to my Dashboard, and the blue loading circle spins for at least 20 seconds as my avi slowly loads in the upper-right on my account.
It used to not do this. For nearly 1 1/2 years everything was fast as one would expect. It's just been the past 2-3 months that this loading issue has been occurring on the site. Everything else works great! Everything I do within the service on Dashboard, Domains, etc. seems to be ok, but just logging IN to the service, seems like the log-in screens struggle a bit.
Could it be the browser I am using (somehow?) (latest version of Firefox)? Could it be MY computer (10th gen Intel MacBook Air)? I don't experience any type of loading issues anywhere else online, so I was curious is others are experiencing this? If it is being addressed?
Thanks :)
6 Replies
It could be many things, though it's hard to know for sure just yet.
Have you tried it in a different browser or a private session? These could help to narrow down if it's browser related. You could also check Firefox's browser console to see if there are any errors.
When the L loading screen is displayed, the only console output I can see attempts to connect to Gravatar. This is expected - we use this tool for profile pictures on your account. If you're seeing something else that is either a warning or an error, those would be very helpful to pass along to us in a Support ticket.
The other possibility that I can think of is a networking issue between your local connection and the servers hosting our site. You can use a tool like MTR (MyTraceRoute) to see what's happening at each hop along the way between the two locations. From your Mac, once you've installed it, a helpful command to run this would be:
mtr -rwzbc100 cloud.linode.com
or just
mtr -rwzbc100 linode.com
If there is packet loss that carries through to the last hop, then there's likely a router in between that's causing a problem. If the packet loss starts in our network, then we can take action on it. If not, there's likely nothing we can do. In those cases, I recommend reporting it to the ISP in charge of the bad hop.
Hello, and thank you for the quick answer!
I may be a little less tech savvy to fool with the Firefox browser console (seemed like an all-encompassing tool), but I went ahead and tried to go the mtr
route, but unfortunately my MacBook Air is having some issues recognizing mtr has been installed at all (installing it with Homebrew works, and it SAYS mtr is installed, but when I run any command with mtr, it always outputs "command not found: mtr".
Not sure where that leaves me, I'll look at the mtr
issue some more when I have time, and see if I can get it working, because it seems like a handy tool to use sometimes. I'll update here if/when I get it working. Thank you for your help :)
my MacBook Air is having some issues recognizing mtr has been installed at all (installing it with Homebrew works, and it SAYS mtr is installed, but when I run any command with mtr, it always outputs "command not found: mtr".
Try putting /usr/local/bin and /usr/local/sbin in your PATH ahead of /usr/bin, /bin, /usr/sbin & /sbin…or run mtr as
/usr/local/sbin/mtr ...
-- sw
I tried the second method you suggested, @steviewi, the /user/local/sbin/mtr
and got:
mtr-packet: Failure to open IPv4 sockets
mtr-packet: Failure to open IPv6 sockets
I re-looked at your recommended command, and ran usr/local/sbin/mtr ...
, and got the same message I was getting originally; command not found: mtr
.
I am not terribly familiar with the first suggestion, as I am relatively new to certain things like this. I am just now memorizing common CLI commands (cd
, ls
, mkdir
, etc.)
Right now I am on a mobile hotspot, so that could possibly be what is going on with the speed of linode.com and cloud.linode.com, but I remember it doing this on other connections, as well (though I may have been using a VPN at those times).
This issue can probably be closed because I do not think I am going to get to the bottom of this.
I tried the second method you suggested, @stevewi, the
/user/local/sbin/mtr
and got:
mtr-packet: Failure to open IPv4 sockets mtr-packet: Failure to open IPv6 sockets
This is my bad… the command should be sudo /usr/local/sbin/mtr ...
The ...
is not literal…it represents whatever arguments you need to give mtr. Also, mtr lives in /usr/local/sbin…not /user/local/sbin (first component of the path is /usr…not /user).
You may have to set up sudo on your MacBook Air. See:
https://apple.stackexchange.com/questions/76088/how-do-i-give-a-user-sudo-permissions
I re-looked at your recommended command, and ran usr/local/sbin/mtr …, and got the same message I was getting originally; command not found: mtr.
The reason this command failed is that the path was incorrect…lacking the leading /.
Right now I am on a mobile hotspot, so that could possibly be what is going on with the speed of linode.com and cloud.linode.com
Mobile hotspots are notoriously slow… Good in a pinch (like getting your boarding pass in the middle of a wedding reception) but not terribly good all the time. My cell provider limits "hotspot data" (how this is different than "regular data" is beyond me).
-- sw
So, some interesting things have come about (not bad things, just different things):
So of course I realized with your last response @steviewi, as well as an e-mail from a friend that I had to be running sudo
before the command, which I was not doing, because I am a noobcakes. Then I had to figure out what my sudo
pw was for this MacBook Air, which is the MBA pw. Ok, cool.
So, some searching around and I see what could be going wrong because even after I ran both
sudo mtr -rwzbc100 cloud.linode.com
AND
sudo /usr/local/sbin/mtr cloud.linode.com
I got the same error both times, command not found: mtr
Then, this site popped up at the top of the search results when searching for "mtr not working on mac" (or something like that). When I ran his suggestion (replacing /mtr/0.92
with /mtr/0.95
, as that is my current version), I was able to get things moving along. But only to the extent that I get this result:
Start: 2022-07-15T19:12:19-0500
So, the laid out "list" of results are not there as shown in the "Reading an MTR - Example Output" shown here, as linked from @watrick at the beginning of this forum thread.
So, I have to figure out what the "Start: 2022 etc, etc" thing is all about, and how/what I can do to get the standard output of MTR.
Suggestions are welcome! :)