New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Two client reports confirmed the issues I was seeing. Netplan reverted. Chisinau node rebooted.
Great news! Chisinau node came back up without needing a power bump! Also, I can ssh into the node and into my test VPS via IPv4 and via IPv6.
Hopefully we are back to where we left off before the netplan adjustment!
I need to sleep now. Anybody still having problems please post, and I will try to fix.
Thanks to Alexhost!
Best wishes!
@Not_Oles Just to say Thank You.
My Aunt died and I promised her daughter I would produce a memorial video. When I tried to do it on my Chromebook (I know I was optimistic) it was pathetically slow. So I had the idea to migrate everything to your kindly provided London server. I built a kvm on the London server and installed the app and all assets. I am now able to work (using SPICE to pass audio) on the video and although it takes about 30 minutes to do final rendering the results are excellent.
So Thank you and to @dan_onlyservers (for the donation) once again, you will have made a large family generation very happy.
Just want to give my condolences here
I am very sorry but it seems my VM is not reachable via the network. I.e., it does not respond to echo requests neither on IPv6 nor IPv4, both HetrixTools and RIPE Atlas consider the respective probes down, and both the NTP server and NTP monitor agent are unreachable/don't report.
Anything I can help troubleshoot this on the host side, let me know.
Thanks!
I don't see any issues on my VM. In fact, things appear slightly better than before. Performance had been slowly getting worse little by little but after this most recent update things are back to normal. Great job!
@msatt Best wishes to you and to your family! Your memorial video seems like an excellently positive response to a challenging event. Congrats! I am delighted that you were successful in making the memorial video on your VPS. I also thank OnlyServers for their kind server node donation.
Looking at the ARP table on the host, and guessing the IP addresses of the VMs, it seems more of them are unreachable than reachable.
Does your VM's IPv4 address by any chance end in 49 or 59?
Hi @Starnberg!
Sorry about the issues.
I just sent you a PM.
What might cause an issue where some VPSes are reachable while others are not?
No, I'm not 49 or 59 but then again like I said above mine is reachable and I don't see any current issues.
@FrankCastle Thanks for your report! Glad everything is working for your VPS!
Not entirely sure off the top of my head. I unfortunately don't recall how the networking was configured inside the VM, whether that could break something.
I need to think about this a bit, maybe I get some ideas.
And maybe my interpretation of what I saw also just is some false negative, given that @FrankCastle's VM seems to be reachable.
Coming to think about it now, I faintly recall there being some potential issues when communicating between a host, and guests, when the host is running the virtual bridge all of them are connected to. Need to think about it a bit more, maybe I remember what it was exactly, and whether/how it could be relevant here.
The ones ending in 49, 59, 79 are the ones that are definitely responding to pings, that is why I inferred yours must be one of those (and since I think you got your VM early on, I assumed you wouldn't have the one ending in 79 as that seems from a later batch of addresses). But if it is not, then maybe I am seeing the wrong things, or interpreting it wrong.
Maybe 81 then?
Yup, 81 is me!
Unfortunately I have to be away for an hour or two. More soon!
@Starnberg
Although I could get in via the console on my test VPS, when I tried with your VPS, the console froze and did not even ask for the login username.
Although your VPS seems broken, some of the other VPSes seem to be working fine. There are several positive reports. And my test VPS seems to be working fine. However, the overall picture doesn't look the best. Just now, top showed about nine VPSes as running 100%CPU.
Hello!
Here is this morning's view from inside the Chisinau server:
Hi @Not_Oles glad to see you much improving, sending you lots of kisses and perhaps a pantone color palette
Update on the Chisinau Node issues
At least two VPSes seem to be working fine! These are mine and @FrankCastle's.
Does anyone else have a working VPS?
What is the difference between the group of VPSes which have high CPU% and do not have network connectivity and the two VPSes which seem to be fine?
Is it just a networking issue? Are there multiple issues?
For awhile, the server hasn't rebooted without needing a power bump, although the most recent reboot went fine.
A while back, after an update, new Debian VMs seemed not to work any more. New Ubuntu VMs still worked.
Later, new Ubuntu VMs made with newly assigned, additional IPs did not work.
Alexhost Support and I adjusted the netplan configuration, hoping to make the new IP addresses work. Thanks to Alexhost Support for their help!
The new netplan configuration seemed to cause multiple issues with multiple VMs becoming unreachable from the WAN and from the node console. Multiple VMs are running high %CPU.
The new netplan configuration was reverted and the node rebooted. Nevertheless, network access and high CPU remain on multiple VMs, but at least two VMs continue to work fine.
Looking around yesterday didn't suggest the cause of the issues or how to resolve them.
LA keeps online
The plan for today includes:
London okay as well!
At least for mine, I would ask to hold off on that until examination of the VM image points to it being irreparably broken.
Also, I am still hoping for more explicit indications from more of the other VPS users on the Chișinău node as to whether their VPSs are working, or not working either (so far, my understanding is two VPSs are working, and one is not - what about all the others?). If it turns out mine is the only one not working, then the issue is likely with it. If others aren't working properly either, it might be more likely the issue is not primarily with those VPSs.
This is easily my favorite tv show recently!
Except for the reboots mine has worked flawlessly
modern day bingo for the elderly
Mystery partially solved!
I missed one space in a yaml configuration file when testing the first of the Chisinau node's newly assigned IP addresses!
Looks like the newly assigned IP addresses do work just fine with the previous and now again reverted netplan when the yaml configuration is correct.
Now I have to figure out why some (but definitely not all!) of the previously made VPSes stopped WAN network access and picked up high %CPU after the netplan change and reversion, which turned out not to have been necessary.
My fault!
Sorry! 
Thanks again to Alexhost Support for trying to help! Thanks again to Alexhost for your kind donation!
Yes, of course. I just wanted to figure out whether I could make another brand new VPS successfully. It looks like it worked!
I won't touch your VPS until after we agree about what to do and what not to do.
Agreed. It may be, however, that others don't want to look like they might be complaining. Nevertheless, it is, as you say, valuable information to know when issues are occuring and when everything is okay. . . .
Thanks for your comments and support!
@zejjnt
Thank for your helpful report!
I will take a look!
Well, we should probably put an asterisk on mine. My original VM was having the same issue with spiking to 100% cpu after that one update (before that update everything was fine). When it was brought to my attention that this was happening, I didn't want to be a noisey neighbor and cause issues for the other tenants so I wiped mine and went with a different OS which appears to have resolved those issues. Had I left things as they were I'd probably still be in the same boat as everyone else it seems like.
Personally, I would suggest reinstalling the hypervisor after everyone has the opporunity to get their data off if they want it. Start over fresh!