@FrankZ, thanks for update, I'm on same boat with 193.93.xx.xxx, but it does not even ping, unmount stuff,
reconfiguration, etc, still fails to raise network. weird.
@tenpera - 193.93.xx.0/24 should have a default route of 193.93.xx.1
check to make sure it is this way by
ip route show
and checking to see if one of the entries is
default via 193.93.xx.1 dev eth0 proto static metric 100
If you have an network adapted that is not eth0, reconfigure networking will not work and you will need to change the ifcfg setting and default route manually.
I am currently traveling in mostly remote areas until sometime in April 2024. Consequently DM's sent to me will go unanswered during this time.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
TYOC038 - Royally screwed, anyone who makes a ticket for existing outage report, I'm just moving away from Tokyo. Will update network status page in a moment. Data recovery may not be very easy, but trying. May all have to end up being moved away. And no, not enough space to be moved to Tokyo.
I don't want to move away from Tokyo. Can I stay in Tokyo until have space?
LES has got to be better than LET at this point. Seeing members helping one another to bypass bugs in in times of provider migrations... what could be better than that?
I don't know, just a thought that came into my mind even though it might not be fair to do such comparison.
@sh97 - Are you talking about LAX1Z014 ? If so, I can't run a yabs disk test, or yum update, as it just shuts down the VM. So I expect that maybe there is a lot going on right now. There is no LAX1Z014 on https://status.virm.ac/ so maybe it is a new node and does not have all the updates yet. I decided just to wait and see how it is in a couple of days before setting up anything on that VM.
I am currently traveling in mostly remote areas until sometime in April 2024. Consequently DM's sent to me will go unanswered during this time.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
@FrankZ said: @sh97 - Are you talking about LAX1Z014 ? If so, I can't run a yabs disk test, or yum update, as it just shuts down the VM. So I expect that maybe there is a lot going on right now. There is no LAX1Z014 on https://status.virm.ac/ so maybe it is a new node and does not have all the updates yet. I decided just to wait and see how it is in a couple of days before setting up anything on that VM.
Yup, that's the one. Yeah, same here, the first time I tried to run YABS, it just shut down. Tried a second time and worked.
Thanks again, good to know I'm not alone
My Atlanta VM appears to have been migrated to Miami, its even up and running but the IP routes to Atlanta so I cant do anything with it yet, but hey, thats progress!
(Can't post the screen shot - but it seems to roughly a flat-line with CPU at 66% , Memory at 74% and the Disk at 6% - maybe disk failure?)
Service shows powered-off, boot times out (even if the log says, "Complete")
Attempting to open KVM: Failed to connect to server (code: 1011, reason: Failed to connect to downstream server)
Could've just been corrupted backups or issues when they were loaded in. You could try repairing your filesystem would be my blind guess that might be helpful. It's also not overloading, disks are fine, network is fine. Although I will say the disk is a little slow, but that might happen if everyone is facing problems and simultaneously running benchmarks, re-installs and such. Disk wait is 0 so it's able to process everyone's disk requests.
Actually I did find a problem. Fixing it now, this makes sense why there may be shutdowns when trying to do something.
@VirMach said: Actually I did find a problem. Fixing it now, this makes sense why there may be shutdowns when trying to do something.
(edit) Fixed. @FrankZ said: as it just shuts down the VM.
Right after seeing this part of your message I knew what it was.
Thank you. The VM no longer shuts down when doing update or disk test.
I am currently traveling in mostly remote areas until sometime in April 2024. Consequently DM's sent to me will go unanswered during this time.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
@tenpera said: @VirMach, about LAX1Z014, still fixing? It gives ** failed to raise a network. ** on vnc.
When you have an individual issue I expect it would be helpful if you included the node name and your VM ID number. You can find the ID number for your VM by looking at the URL when in the product details page for your VM in WHMCS.
I am currently traveling in mostly remote areas until sometime in April 2024. Consequently DM's sent to me will go unanswered during this time.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
Any info on LAX1Z015 ? i have a VM migrated there, but is down unable to power up even if it say is powered up sucessfully and there is no operation system i tried to boot a live cd like gparted and clonezilla removed all iso and boot to default but still unable to boot i looked on the status page, and other page but found nothing and when i try to get vnc it say Failed to connect to server (code: 1011, reason: Failed to connect to downstream server).
@DeviousDev said:
Any info on LAX1Z015 ? i have a VM migrated there, but is down unable to power up even if it say is powered up sucessfully and there is no operation system i tried to boot a live cd like gparted and clonezilla removed all iso and boot to default but still unable to boot i looked on the status page, and other page but found nothing and when i try to get vnc it say Failed to connect to server (code: 1011, reason: Failed to connect to downstream server).
DeviousDev
If network status page doesn't say it's done and a network status update exists, then it's not done and we shouldn't be contacted about it yet.
MIAZ011
SolusVM is showing a VNC server address in the 47.87.158.0/24 range that is no longer connected.
It should be replaced with a correct address in the routable range.
Also, outgoing mtr is showing 47.87.156.1 as the first hop router.
This should be corrected too.
I know that there has been some discussion here about issues with CDROM mounting, but on LAX2Z020 it is entirely broken. If you try to mount a CDROM and boot from it the VPS becomes unreachable ("Operation Timed Out After 90001 Milliseconds With 0 Bytes Received") for a while although it eventually recovers, but still doesn't work at all. I've tried a few different standard ISOs and they're all the same.
@VirMach is this a known problem or is it just me?
Comments
@FrankZ, thanks for update, I'm on same boat with 193.93.xx.xxx, but it does not even ping, unmount stuff,
reconfiguration, etc, still fails to raise network. weird.
@tenpera - 193.93.xx.0/24 should have a default route of 193.93.xx.1
check to make sure it is this way by
and checking to see if one of the entries is
If you have an network adapted that is not eth0, reconfigure networking will not work and you will need to change the ifcfg setting and default route manually.
I am currently traveling in mostly remote areas until sometime in April 2024. Consequently DM's sent to me will go unanswered during this time.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
The 038 node in Tokyo has been out of service for several times. When will it be repaired?
this is not virmach support
I bench YABS 24/7/365 unless it's a leap year.
I thought it was a question to the Japanese government
I don't want to move away from Tokyo. Can I stay in Tokyo until have space?
https://lowendspirit.com/discussion/comment/151890/#Comment_151890
Brain exploded, they fucking copy-paste the same message :-D
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
LES has got to be better than LET at this point. Seeing members helping one another to bypass bugs in in times of provider migrations... what could be better than that?
I don't know, just a thought that came into my mind even though it might not be fair to do such comparison.
That is not a very ambitious target for us
Is anyone else facing some disk issue at LAX?
Was taking a look just now.
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC
1 IOPS. ONE.
VirMach did it again, set a fucking record!
Kappa NoKappa
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
@sh97 - Are you talking about LAX1Z014 ? If so, I can't run a yabs disk test, or yum update, as it just shuts down the VM. So I expect that maybe there is a lot going on right now. There is no LAX1Z014 on https://status.virm.ac/ so maybe it is a new node and does not have all the updates yet. I decided just to wait and see how it is in a couple of days before setting up anything on that VM.
I am currently traveling in mostly remote areas until sometime in April 2024. Consequently DM's sent to me will go unanswered during this time.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
Yup, that's the one. Yeah, same here, the first time I tried to run YABS, it just shut down. Tried a second time and worked.
Thanks again, good to know I'm not alone
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC
My Atlanta VM appears to have been migrated to Miami, its even up and running but the IP routes to Atlanta so I cant do anything with it yet, but hey, thats progress!
I wonder what happened to the node ..
Node: LAX2Z021 (doesn't show on Network Status, last whine on here was last year)
https://status.virm.ac/?s=62d9fd33778ad15ede24adb4
(Can't post the screen shot - but it seems to roughly a flat-line with CPU at 66% , Memory at 74% and the Disk at 6% - maybe disk failure?)
Service shows powered-off, boot times out (even if the log says, "Complete")
Attempting to open KVM: Failed to connect to server (code: 1011, reason: Failed to connect to downstream server)
LAX1Z014 failed to raise a network. i.p is not pinging, dead. probably takes longer time.
Can't reproduce any issues on LAX1Z014.
Could've just been corrupted backups or issues when they were loaded in. You could try repairing your filesystem would be my blind guess that might be helpful. It's also not overloading, disks are fine, network is fine. Although I will say the disk is a little slow, but that might happen if everyone is facing problems and simultaneously running benchmarks, re-installs and such. Disk wait is 0 so it's able to process everyone's disk requests.
Actually I did find a problem. Fixing it now, this makes sense why there may be shutdowns when trying to do something.
(edit) Fixed.
Right after seeing this part of your message I knew what it was.
IP changes on that node not going well, it's causing it to overload.
Thank you. The VM no longer shuts down when doing update or disk test.
I am currently traveling in mostly remote areas until sometime in April 2024. Consequently DM's sent to me will go unanswered during this time.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
@VirMach, about LAX1Z014, still fixing? It gives ** failed to raise a network. ** on vnc.
When you have an individual issue I expect it would be helpful if you included the node name and your VM ID number. You can find the ID number for your VM by looking at the URL when in the product details page for your VM in WHMCS.
I am currently traveling in mostly remote areas until sometime in April 2024. Consequently DM's sent to me will go unanswered during this time.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
Any info on LAX1Z015 ? i have a VM migrated there, but is down unable to power up even if it say is powered up sucessfully and there is no operation system i tried to boot a live cd like gparted and clonezilla removed all iso and boot to default but still unable to boot i looked on the status page, and other page but found nothing and when i try to get vnc it say Failed to connect to server (code: 1011, reason: Failed to connect to downstream server).
DeviousDev
my vm has unexpected shutdown again
due to possible tyoc026's memory full
https://downloadmoreram.com/
If network status page doesn't say it's done and a network status update exists, then it's not done and we shouldn't be contacted about it yet.
Okay, which one you rat buggers is abusing PHXZ001? STeal's been at ~10-15% for 24h now ...
I abuse 1 core per some VPS but nothing else till virmach get stable
stopped one core abuse steal still there, stats page say 15-20% node use so must be something else then not the CPU
Hello, virmach.
How long will it take for TYOC038 to recover?
MIAZ011
SolusVM is showing a VNC server address in the 47.87.158.0/24 range that is no longer connected.
It should be replaced with a correct address in the routable range.
Also, outgoing mtr is showing 47.87.156.1 as the first hop router.
This should be corrected too.
HostBrr aff best VPS; VirmAche aff worst VPS.
Unable to push-up due to shoulder injury 😣
I know that there has been some discussion here about issues with CDROM mounting, but on LAX2Z020 it is entirely broken. If you try to mount a CDROM and boot from it the VPS becomes unreachable ("Operation Timed Out After 90001 Milliseconds With 0 Bytes Received") for a while although it eventually recovers, but still doesn't work at all. I've tried a few different standard ISOs and they're all the same.
@VirMach is this a known problem or is it just me?
Anyone else having this exact same problem?