@FrankZ said: @sparkssss - It just so happens I have a VM with a DNS server on node LAX1Z014.
This is what my monitoring shows for the response time from my VM on LAX1Z014 for the day of October 26th.
Taking a longer view of October 19th to 26th, packet loss and ping times look like this.
So from the looks of the above graphs compared to the screenshot you posted here on October 10th we are having different experiences on node LAX1Z014. The conclusion that I come to from this is that it is not a node wide issue and is most likely an issue with your VM.
If you would DM me some information about the operating system, what you are running on your VM, the firewall setup, and if you want me to have a quick look around and see if I can ID your problem, some credentials for your VM.
I would like to once again make it clear that I do not work for Virmach, but am willing to attempt to work with you to resolve your problem.
EDIT: Since you mentioned that the problem started on or about October 1st, I can't help but think this may have something to do with the IP change that happened around that time. Could it be possable that your VM is not setup quite correctly regarding that change ?
thanks for reply.
I just conducted a simple test and found that the possible reason is that the IP address may be assigned to multiple machines, causing frequent disconnections.I hope that these disconnections are not a widespread issue.
@sparkssss said: thanks for reply.
I just conducted a simple test and found that the possible reason is that the IP address may be assigned to multiple machines, causing frequent disconnections.I hope that these disconnections are not a widespread issue.
Probably not wide spread, since this is the complaint thread. If you feel that you have ID'd the issue then may I suggest posting your VM ID so VirMach can identify the IP in question.
@VirMach - Just a FYI, LAX1Z012 seem to be having issues. Gateway IP is up, but my VM shutdown and will not restart. Pinging a dozen IPs around mine, receives no response.
@sparkssss said: @VirMach thanks for replay.
When my machine is inaccessible, I can still ping the IP and I scanned the open ports of the IP and found that port 3389 is open. However, my machine is running CentOS and I haven't opened port 3389. The possible reason could be that the IP has been assigned to multiple machines.There is another machine competing for the same IP address as mine.could u plz check?
When experiencing disconnections,
Starting Nmap 6.40 ( http://nmap.org ) at 2023-10-27 19:59 CST
Nmap scan report for 193.93.xx.xx
Host is up (0.18s latency).
Not shown: 999 filtered ports
PORT STATE SERVICE
3389/tcp open ms-wbt-server
while the normal status,it aligns with my situation.
Starting Nmap 6.40 ( http://nmap.org ) at 2023-10-27 20:05 CST
Nmap scan report for 193.93.xx.xx
Host is up (0.17s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
80/tcp open http
443/tcp open https
You are using the old dedipath IP.
Dedipath was down for one month.
Submit ticket for a new IP.
@FrankZ said: Probably not wide spread, since this is the complaint thread. If you feel that you have ID'd the issue then may I suggest posting your VM ID so VirMach can identify the IP in question.
Seems like sometimes it's easier to just look at arp/mac addresses than try to communicate back and forth. You're definitely a better front-facing support agent than I am.
Anyway, it should be fixed. Maybe. At least one of the two or more people have to play musical chairs though within their VM depending on whether they decided to go with what was assigned to them or whatever they felt like doing, it was a SolusVM feature also known as ebtables randomly breaking. It could also be the other SolusVM feature where the database shows one IP and assigns another but that one's more rare recently and I didn't see any signs of that, at least not in the amount of time I could allocate.
@sparkssss said: thanks for reply.
I just conducted a simple test and found that the possible reason is that the IP address may be assigned to multiple machines, causing frequent disconnections.I hope that these disconnections are not a widespread issue.
Probably not wide spread, since this is the complaint thread. If you feel that you have ID'd the issue then may I suggest posting your VM ID so VirMach can identify the IP in question.
so,where i can find my vm id?
as nightcat said,how to describe my situation in the ticket?
@FrankZ said: @VirMach - Just a FYI, LAX1Z012 seem to be having issues. Gateway IP is up, but my VM shutdown and will not restart. Pinging a dozen IPs around mine, receives no response.
DALZ007: Node has been down since the dedipath problem I think
Operation Timed Out After 90000 Milliseconds With 0 Bytes Received
Affecting System - DALZ004, DALZ007
Update 10/20/23 -- we believe the servers have finally arrived from Dallas to Atlanta today. Since it's the weekend, we'll likely have them racked early next week.
too bad that the least server I care about out of them, there is nothing there. but yeah, I missed reading that part from the status page, thanks to my sucks english
Main IP pings: false
Node Online: true
Service online: online
Operating System: linux-ubuntu-20.04-x86_64-minimal-latest-v2
Service Status:Active
Registration Date:2022-12-29
@wudali said:
My server is in LAXA012 and cannot connect anymor
LAX1Z012 was down for about 6 hours, 15 hours ago, but has been fine since.
What is the specific issue you are having ?
More specifically.
Does it turn on or no ?
Have you tried to turn it off and back on again by clicking the reset button ?
If it turns on, have you checked for error msg in VNC ?
If so, what error messages were there ?
@wudali said:
My server is in LAXA012 and cannot connect anymor
LAX1Z012 was down for about 6 hours, 15 hours ago, but has been fine since.
What is the specific issue you are having ?
Main IP pings: false
Node Online: true
Service online: online
Operating System: linux-ubuntu-20.04-x86_64-minimal-latest-v2
Service Status:Active
Registration Date:2022-12-29
@wudali said:
My server is in LAXA012 and cannot connect anymor
LAX1Z012 was down for about 6 hours, 15 hours ago, but has been fine since.
What is the specific issue you are having ?
More specifically.
Does it turn on or no ?
Have you tried to turn it off and back on again by clicking the reset button ?
If it turns on, have you checked for error msg in VNC ?
If so, what error messages were there ?
The server is online, I have reset the network, but I haven't seen VCN because I'm not professional and my English is translated. I'm not sure if you can understand it
@wudali said:
My server is in LAXA012 and cannot connect anymor
LAX1Z012 was down for about 6 hours, 15 hours ago, but has been fine since.
What is the specific issue you are having ?
More specifically.
Does it turn on or no ?
Have you tried to turn it off and back on again by clicking the reset button ?
If it turns on, have you checked for error msg in VNC ?
If so, what error messages were there ?
@wudali - Lets' take it one guess at a time.
If your IP changed, and you reset your network by going to the SolusVM panel and clicking "Reconfigure Networking". There may be additional steps needed if your network interface is not "eth0".
What operating system are you using ?
@FrankZ said: @wudali - Lets' take it one guess at a time.
If your IP changed, and you reset your network by going to the SolusVM panel and clicking "Reconfigure Networking". There may be additional steps needed if your network interface is not "eth0".
What operating system are you using ?
Ok, if you installed Ubuntu 20.04 from template your network interface should be "eth0".
Go to the billing panel and click on your VPS to get to the product details page for your VPS, then click "VNC/Desktop". A small black screen should pop up, tell me if there is a login prompt, or an error message on that black screen.
If there is a login prompt, login to your VPS, and then enter "ping 1.1.1.1" and post the result.
Also post the output from "ip addr show" and "ip route show".
Ok, if you installed Ubuntu 20.04 from template your network interface should be "eth0".
Go to the billing panel and click on your VPS to get to the product details page for your VPS, then click "VNC/Desktop". A small black screen should pop up, tell me if there is a login prompt, or an error message on that black screen.
If there is a login prompt, login to your VPS, and then enter "ping 1.1.1.1" and post the result.
Also post the output from "ip addr show" and "ip route show".
Ok, we have errors. First we are going to try the easiest thing.
In the product details page for your VPS, click the "Off" button, wait 2 minutes, and then click the "On" button, wait a minute or so, then click the VNC button again to bring up the little black screen.
Do you have the same error message as above, or different error message, or a login prompt.
Did you recently upgrade the system or kernel ?
How much memory does your VPS have ?
Ok, we have errors. First we are going to try the easiest thing.
In the product details page for your VPS, click the "Off" button, wait 2 minutes, and then click the "On" button, wait a minute or so, then click the VNC button again to bring up the little black screen.
Do you have the same error message as above, or different error message, or a login prompt.
Did you recently upgrade the system or kernel ?
How much memory does your VPS have ?
The situation is still the same. I have not upgraded the system or kernel, and my memory is only 384m. I have no choice but to reinstall the system. Thank you for your answer
@wudali said: The situation is still the same. I have not upgraded the system or kernel, and my memory is only 384m. I have no choice but to reinstall the system. Thank you for your answer
I strongly suggest that if you are going to reinstall anyway, that once you get the system going again, do this to help make this less likely to happen again.
sed -i 's/MODULES=most/MODULES=dep/g' /etc/initramfs-tools/initramfs.conf
Then run
update-initramfs -u
Then reboot.
This procedure will shrink the "initrd.img-5.4.0-105-generic" file that your system is using to boot by about half. This will help so that you do not run out of RAM when booting, and get the above error.
I recommend doing this for all low RAM Ubuntu installs on VMs.
Just a note for more advanced users. The above procedure can be done from the recovery system to correct the above "System is deadlocked on memory" error without the need to reinstall.
Ok, we have errors. First we are going to try the easiest thing.
In the product details page for your VPS, click the "Off" button, wait 2 minutes, and then click the "On" button, wait a minute or so, then click the VNC button again to bring up the little black screen.
Do you have the same error message as above, or different error message, or a login prompt.
Did you recently upgrade the system or kernel ?
How much memory does your VPS have ?
The situation is still the same. I have not upgraded the system or kernel, and my memory is only 384m. I have no choice but to reinstall the system. Thank you for your answer
if you dont have any special needs, you could try AlpineLinux which runs smoothly in a very low mem server and its available through ISO install at many hostnodes
Ok, we have errors. First we are going to try the easiest thing.
In the product details page for your VPS, click the "Off" button, wait 2 minutes, and then click the "On" button, wait a minute or so, then click the VNC button again to bring up the little black screen.
Do you have the same error message as above, or different error message, or a login prompt.
Did you recently upgrade the system or kernel ?
How much memory does your VPS have ?
The situation is still the same. I have not upgraded the system or kernel, and my memory is only 384m. I have no choice but to reinstall the system. Thank you for your answer
if you dont have any special needs, you could try AlpineLinux which runs smoothly in a very low mem server and its available through ISO install at many hostnodes
Comments
thanks for reply.
I just conducted a simple test and found that the possible reason is that the IP address may be assigned to multiple machines, causing frequent disconnections.I hope that these disconnections are not a widespread issue.
Probably not wide spread, since this is the complaint thread. If you feel that you have ID'd the issue then may I suggest posting your VM ID so VirMach can identify the IP in question.
@VirMach - Just a FYI, LAX1Z012 seem to be having issues. Gateway IP is up, but my VM shutdown and will not restart. Pinging a dozen IPs around mine, receives no response.
You are using the old dedipath IP.
Dedipath was down for one month.
Submit ticket for a new IP.
Seems like sometimes it's easier to just look at arp/mac addresses than try to communicate back and forth. You're definitely a better front-facing support agent than I am.
Anyway, it should be fixed. Maybe. At least one of the two or more people have to play musical chairs though within their VM depending on whether they decided to go with what was assigned to them or whatever they felt like doing, it was a SolusVM feature also known as ebtables randomly breaking. It could also be the other SolusVM feature where the database shows one IP and assigns another but that one's more rare recently and I didn't see any signs of that, at least not in the amount of time I could allocate.
so,where i can find my vm id?
as nightcat said,how to describe my situation in the ticket?
Virmach said above that your VM is already fixed.
(but of course everybody knows that I really fixed it)
For future reference, you can find your VM ID by signing in to the billing panel, clicking through to the product details of the VM in question, and then looking at the URL
IE: https://billing.virmach.com/clientarea.php?action=productdetails&;id=690069
In the example "690069" would be the VM ID.
Wasn't fixed, now it is. Was also the second issue as well. Have I mentioned how much I love SolusVM?
VirMach
SolusVM
Oh god
@VirMach @FrankZ
I see that the IP has been changed. I will continue to monitor the situation and provide feedback if any issues arise. Thanks.
VirMach fixed IPs manually.
LAX1Z012 is broken.
Coincidence?
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
OK where I am I? Not cool man not cool!!!
edit: Best SLA ever "It will be up 100% of the time it is up."
The Yeti has left the building.
My servers situation, is anyone on the same nodes and the server is live?
LAX1Z016 (2 servers) & NYCB028 (1 server)
Main IP pings: false
Node Online: true
Service online: online
Tried the Reconfigure button, result: Operation Timed Out After 90000 Milliseconds With 0 Bytes Received
DALZ007: Node has been down since the dedipath problem I think
Operation Timed Out After 90000 Milliseconds With 0 Bytes Received
PS: I'm a super noob in Linux and my English sucks.
Affecting System - DALZ004, DALZ007
Update 10/20/23 -- we believe the servers have finally arrived from Dallas to Atlanta today. Since it's the weekend, we'll likely have them racked early next week.
too bad that the least server I care about out of them, there is nothing there. but yeah, I missed reading that part from the status page, thanks to my sucks english
I have 2 VMs on LAXA016, one of them fails to start and fails to connect via VNC.
Such captive doggy, no barking!
such tame strawberry, no whining!
I bench YABS 24/7/365 unless it's a leap year.
Such fragile snowflake, no crying!
im beginning to like you for agreeing with me
I bench YABS 24/7/365 unless it's a leap year.
I couldn't agree more that you are a snowflake.
@FrankZ is there a minimum age for creating a LES account?
We shouldn't judge people by age.
Anyone who has a head should be able to create an account.
We accept Karma donations for the last flan. 🍮 affbrr
Yes, 13.
@VirMach
The VM (id=562557) fails to start after the migration.
Please take a look, thanks!
I have a VM on NYCB028, it is working fine, and has had no issues.
I do not have a VM on LAX1Z016 so I can't tell you anything about that one.
I have one on LAX1Z016 which is working normally.
My server is in LAXA012 and cannot connect anymor
@VirMach Hello sir,
This guy used your loophole to escape deportation and stole $4 from you.
He also called you a douchebag in the TG group.
https://hostloc.com/thread-1221806-1-1.html
My server is in LAXA012 and cannot connect anymor
Main IP pings: false
Node Online: true
Service online: online
Operating System: linux-ubuntu-20.04-x86_64-minimal-latest-v2
Service Status:Active
Registration Date:2022-12-29
LAX1Z012 was down for about 6 hours, 15 hours ago, but has been fine since.
What is the specific issue you are having ?
More specifically.
Does it turn on or no ?
Have you tried to turn it off and back on again by clicking the reset button ?
If it turns on, have you checked for error msg in VNC ?
If so, what error messages were there ?
Main IP pings: false
Node Online: true
Service online: online
Operating System: linux-ubuntu-20.04-x86_64-minimal-latest-v2
Service Status:Active
Registration Date:2022-12-29
The server is online, I have reset the network, but I haven't seen VCN because I'm not professional and my English is translated. I'm not sure if you can understand it
kvm399022，Is this the host number
@wudali - Lets' take it one guess at a time.
If your IP changed, and you reset your network by going to the SolusVM panel and clicking "Reconfigure Networking". There may be additional steps needed if your network interface is not "eth0".
What operating system are you using ?
Ubuntu 20.04
Ok, if you installed Ubuntu 20.04 from template your network interface should be "eth0".
Go to the billing panel and click on your VPS to get to the product details page for your VPS, then click "VNC/Desktop". A small black screen should pop up, tell me if there is a login prompt, or an error message on that black screen.
If there is a login prompt, login to your VPS, and then enter "ping 1.1.1.1" and post the result.
Also post the output from "ip addr show" and "ip route show".
Ok, we have errors. First we are going to try the easiest thing.
In the product details page for your VPS, click the "Off" button, wait 2 minutes, and then click the "On" button, wait a minute or so, then click the VNC button again to bring up the little black screen.
Do you have the same error message as above, or different error message, or a login prompt.
Did you recently upgrade the system or kernel ?
How much memory does your VPS have ?
The situation is still the same. I have not upgraded the system or kernel, and my memory is only 384m. I have no choice but to reinstall the system. Thank you for your answer
I strongly suggest that if you are going to reinstall anyway, that once you get the system going again, do this to help make this less likely to happen again.
Then run
Then reboot.
This procedure will shrink the "initrd.img-5.4.0-105-generic" file that your system is using to boot by about half. This will help so that you do not run out of RAM when booting, and get the above error.
I recommend doing this for all low RAM Ubuntu installs on VMs.
Just a note for more advanced users. The above procedure can be done from the recovery system to correct the above "System is deadlocked on memory" error without the need to reinstall.
if you dont have any special needs, you could try AlpineLinux which runs smoothly in a very low mem server and its available through ISO install at many hostnodes
I just installed Debian 11, thank you
This procedure also works to reduce the required memory when booting Debian 11.
Then run
Then reboot.
Thank you.
@FrankZ is such a nice and helpful guy support agent.
Congratulations South Africa - Rugby World Cup Champions
@VirMach Boss, should the users from Tokyo 038 wait for the node to be fixed? Or do you want to relocate the users to another node in Tokyo?