@newlan said: @VirMach
After I manually restarted, the service on TYOC029 is offline, and VNC cannot be connected. Please take the time to help me solve it, thank you boss
The node TYOC029 is not offline. It would be helpful for you to add more information.
TYOC029 node is indeed online, only mine is offline
VPS Control Panel does not see Disk Usage
The cause is that I restarted the VPS on the panel, maybe my mouse problem caused multiple clicks? i don't know the exact reason
I tried to start, shut down, restart, network repair, reinstall the system and still can't go online
@newlan - I've had this happen before, although I am not sure why it happens. I had reinstalled the VM and shut it down. Then went back to set up the new install a couple of days later and it would not start. I tried to start it each day from the control panel and on the 11th day it started. It did not start up itself. I have no advise to offer on how to get it started quicker.
@FrankZ said: @newlan - I've had this happen before, although I am not sure why it happens. I had reinstalled the VM and shut it down. Then went back to set up the new install a couple of days later and it would not start. I tried to start it each day from the control panel and on the 11th day it started. It did not start up itself. I have no advise to offer on how to get it started quicker.
Thank you for your reply. I can only wait until @VirMach sees my request before processing it.
@localhost you now have company @tonyapac which is probably good news as I expect that VirMach will notice this issue quicker if there are more than one of you with the same problem.
@tonyapac - Read what I said here. for some tidbits of information regarding this issue.
@FrankZ said: @localhost you now have company @tonyapac which is probably good news as I expect that VirMach will notice this issue quicker if there are more than one of you with the same problem.
@FrankZ said: @localhost you now have company @tonyapac which is probably good news as I expect that VirMach will notice this issue quicker if there are more than one of you with the same problem.
@tonyapac - Read what I said here. for some tidbits of information regarding this issue.
I'm not sure if my issue was fixed by Virmach or it was fixed by itself just like the issue that happens out of nowhere. Virmach didn't reply to my ticket even after the issue was fixed, so I closed it manually.
I run my code server external authentication proxy there. As it is offline today, my friends and I login code without any authentication. This incident helps me learning more about nginx config; my bad
@CyberneticTitan said:
LAXA031 also seems to be taking a dump right now
Thank you for the update, looks like it has been unavailable for about six hours. That is actually good news for me as I have a VM on LAXA031 that developed the "No boot device available" yesterday. Hoping a reboot will fix it without having to wait as long as normal. Fingers crossed.
@VirMach VM on SEAZ005 have been not reachable for over 3 months. Ip4 47.87.135.xxx . Unsuccessfully tried every troubleshooting steps in the book reconfigure network, re-install various os images, reboot, VNC and verified all networks files, disabled firewall resolver but still not connected to internet and can't ssh from outside. Ticket open for over a month and also created priority ticket $ but no help. Please @VirMach help!
@xyz said: @VirMach VM on SEAZ005 have been not reachable for over 3 months. Ip4 47.87.135.xxx . Unsuccessfully tried every troubleshooting steps in the book reconfigure network, re-install various os images, reboot, VNC and verified all networks files, disabled firewall resolver but still not connected to internet and can't ssh from outside. Ticket open for over a month and also created priority ticket $ but no help. Please @VirMach help!
I have a VM on SEAZ005 and the IP I have is in a completely different subnet (72.5.34.xxx). If I try to traceroute what should be your gateway IP ( 47.87.135.1) from my VM on SEAZ005 it shows as 35 ms away at quadranet.com (LAX ?). If you would like to PM me your actual IP and default gateway IP I will double check this for you.
Anybody else recently started having IPv6 issues in Tokyo ?
I can ping6 the IPv6 gateway, but nothing past that and nothing in to the VM via IPv6.
@xyz said: @VirMach VM on SEAZ005 have been not reachable for over 3 months. Ip4 47.87.135.xxx . Unsuccessfully tried every troubleshooting steps in the book reconfigure network, re-install various os images, reboot, VNC and verified all networks files, disabled firewall resolver but still not connected to internet and can't ssh from outside. Ticket open for over a month and also created priority ticket $ but no help. Please @VirMach help!
I have a VM on SEAZ005 and the IP I have is in a completely different subnet (72.5.34.xxx). If I try to traceroute what should be your gateway IP ( 47.87.135.1) from my VM on SEAZ005 it shows as 35 ms away at quadranet.com (LAX ?). If you would like to PM me your actual IP and default gateway IP I will double check this for you.
@xyz said: @VirMach VM on SEAZ005 have been not reachable for over 3 months. Ip4 47.87.135.xxx . Unsuccessfully tried every troubleshooting steps in the book reconfigure network, re-install various os images, reboot, VNC and verified all networks files, disabled firewall resolver but still not connected to internet and can't ssh from outside. Ticket open for over a month and also created priority ticket $ but no help. Please @VirMach help!
I have a VM on SEAZ005 and the IP I have is in a completely different subnet (72.5.34.xxx). If I try to traceroute what should be your gateway IP ( 47.87.135.1) from my VM on SEAZ005 it shows as 35 ms away at quadranet.com (LAX ?). If you would like to PM me your actual IP and default gateway IP I will double check this for you.
My VM on SEAZ005 has an IP same net as @FrankZ and works fine.
@xyz, Curious, what IP does your panel show in the the Main IP's field.
@xyz said: @VirMach VM on SEAZ005 have been not reachable for over 3 months. Ip4 47.87.135.xxx . Unsuccessfully tried every troubleshooting steps in the book reconfigure network, re-install various os images, reboot, VNC and verified all networks files, disabled firewall resolver but still not connected to internet and can't ssh from outside. Ticket open for over a month and also created priority ticket $ but no help. Please @VirMach help!
I have a VM on SEAZ005 and the IP I have is in a completely different subnet (72.5.34.xxx). If I try to traceroute what should be your gateway IP ( 47.87.135.1) from my VM on SEAZ005 it shows as 35 ms away at quadranet.com (LAX ?). If you would like to PM me your actual IP and default gateway IP I will double check this for you.
My VM on SEAZ005 has an IP same net as @FrankZ and works fine.
@xyz, Curious, what IP does your panel show in the the Main IP's field.
Panel main IP is same as 47.87.135.xxx inside the gateway 47.87.135.1 but @FrankZ mentioned that is from LAX subnet not sure how I got that in SEA. I did go through a migration from LAX so could be messed up migration
@xyz - If you received a email from the migration, check if the IPs that show in the email match what you show in the panel. I expect that they do, but if they don't and are from the 72.5.34.xxx subnet you should be able to fix this without VirMach.
@FrankZ said: @xyz - If you received a email from the migration, check if the IPs that show in the email match what you show in the panel. I expect that they do, but if they don't and are from the 72.5.34.xxx subnet you should be able to fix this without VirMach.
same Ip in the email. This is one of those super cheap VM during 2019 BF, I assume @VirMach want me to get frustrated and cancel myself without resolution. Should I request new Ip? That is like $3 and may be they have automation to assign from the right subnet?
@FrankZ said: @xyz - If you received a email from the migration, check if the IPs that show in the email match what you show in the panel. I expect that they do, but if they don't and are from the 72.5.34.xxx subnet you should be able to fix this without VirMach.
same Ip in the email. This is one of those super cheap VM during 2019 BF, I assume @VirMach want me to get frustrated and cancel myself without resolution. Should I request new Ip? That is like $3 and may be they have automation to assign from the right subnet?
As a person with several of those, I'm going to say he isn't putting that kind of effort into getting rid of us.
I don't expect it should cost you anything since your current one won't work on the location you're at. Will it take a while? Probably. But now at least you can update your existing ticket with useful information. Maybe it'll go faster since all he has to do is assign you one relevant to your server location. Who can say?
Since you have waited three months already, I would let it ride as is for a little while longer. Maybe @VirMach will see your post here on LES and have someone assign your VM some correct IPv4 for the node you are on instead of the ones from the Los Angeles node you migrated from. I expect there is only one VM trying to use IPv4 from the 47.87.135.xx subnet on node SEAZ005 so it should not be that hard to find.
@JoeMerit said:
What is the next location for a full outage?
Although there is not a full location outage anywhere at the moment, Atlanta comes pretty close, as I only see one node still responding there. (fixed) Personally I am keeping my eye on SEAZ001 which has a load average of 833 1,138 currently. I can't help but wonder if it will catch on fire, or get rebooted before doing so.
I have a shared hosting service with Virmach.com, and unfortunately, the service has been down since April. However, I recently received a bill for the next year's subscription, which is due on 06/30/2023. I am concerned about making the payment while the service is still not restored. Is there a way to pause or postpone the payment until the service is fully operational again?
Thanks @dgc1980 !!
It looks like the network issue involving ATLZ005, ATLZ007B, ATLZ009, and ATLZ010 has been resolved.
My VM on ATLZ007B is back as well, no restart.
From the status page:
06/09/2023 19:04
LAXA031 is being rebooted for an emergency patch, related to disk.
After reaching a load average 1,620, and a reboot, the problem on SEAZ001 seems to have been resolved. My VM is now responding normally.
@FrankZ said:
Thank you for the update, looks like it has been unavailable for about six hours. That is actually good news for me as I have a VM on LAXA031 that developed the "No boot device available" yesterday. Hoping a reboot will fix it without having to wait as long as normal. Fingers crossed.
Has your LAXA031 VM been able to be brought back online after the node reboot? I don't seem to be able to boot my VM, mount a recovery disk, or even access VNC at the moment.
@CyberneticTitan said: Has your LAXA031 VM been able to be brought back online after the node reboot? I don't seem to be able to boot my VM, mount a recovery disk, or even access VNC at the moment.
Not yet, my VM just shows "offline" in the billing panel. If I attempt to boot it, it continues to show "offline". I expect that this means that customers are not allowed to start VMs on LAXA031 as of yet. VirMach has probably identified a further issue with this node, and until it is corrected, we have to wait.
Anyone using the ryzen flash deals for serious production use? (where you would be losing money or reputation if they were offline.) Just trying to decide if i'm thinking about my $100+ worth of flash deals the right way.
i.e. if its a fun toy/hobby thing, where you get tons of performance and cheap resources and can do things like run Windows, where youd never be able to do that on $2 per month (or less, lol!) VPS elsewhere, but the tradeoff is that it can have lengthy downtimes. OR if its something that really should be okay for production use?
@JoeMerit said:
Anyone using the ryzen flash deals for serious production use? (where you would be losing money or reputation if they were offline.) Just trying to decide if i'm thinking about my $100+ worth of flash deals the right way.
i.e. if its a fun toy/hobby thing, where you get tons of performance and cheap resources and can do things like run Windows, where youd never be able to do that on $2 per month (or less, lol!) VPS elsewhere, but the tradeoff is that it can have lengthy downtimes. OR if its something that really should be okay for production use?
You say, "where you would be losing money or reputation if they were offline," but for serious production use you shouldn't be in that situation anyway. Would it be perfectly appropriate for serious production use as a single-node web server for clients with hard SLA's? Prob'ly not. Would it be okay for serious production as part of a redundant group of application servers where if a single node goes temporarily AWOL the other locations pick up the slack? I'd say definitely. I believe there are several people on here using them for purposes like that currently.
@JoeMerit said:
Anyone using the ryzen flash deals for serious production use? (where you would be losing money or reputation if they were offline.) Just trying to decide if i'm thinking about my $100+ worth of flash deals the right way.
i.e. if its a fun toy/hobby thing, where you get tons of performance and cheap resources and can do things like run Windows, where youd never be able to do that on $2 per month (or less, lol!) VPS elsewhere, but the tradeoff is that it can have lengthy downtimes. OR if its something that really should be okay for production use?
You say, "where you would be losing money or reputation if they were offline," but for serious production use you shouldn't be in that situation anyway. Would it be perfectly appropriate for serious production use as a single-node web server for clients with hard SLA's? Prob'ly not. Would it be okay for serious production as part of a redundant group of application servers where if a single node goes temporarily AWOL the other locations pick up the slack? I'd say definitely. I believe there are several people on here using them for purposes like that currently.
I think there are some places where you could host on a single node and expect that you will be okay. Since the flash sale we've experienced multiple full location outages, IP addresses for multiple locations being dropped off the internet by the IP owner, week/month long node outages etc... On the other hand, name a provider where you will get 4 cores, 4-6gb of ram and tons of storage/bandwidth (including 2 or more IPv4) for under $2 month. I guess i'm to the point where i'm willing to accept the outages, knowing that when its up, its not going to be beaten for the price by any other provider. (just maybe not $100+/yr worth, might just keep 1 or 2 of the best deals.)
@JoeMerit said:
Anyone using the ryzen flash deals for serious production use? (where you would be losing money or reputation if they were offline.) Just trying to decide if i'm thinking about my $100+ worth of flash deals the right way.
i.e. if its a fun toy/hobby thing, where you get tons of performance and cheap resources and can do things like run Windows, where youd never be able to do that on $2 per month (or less, lol!) VPS elsewhere, but the tradeoff is that it can have lengthy downtimes. OR if its something that really should be okay for production use?
You say, "where you would be losing money or reputation if they were offline," but for serious production use you shouldn't be in that situation anyway. Would it be perfectly appropriate for serious production use as a single-node web server for clients with hard SLA's? Prob'ly not. Would it be okay for serious production as part of a redundant group of application servers where if a single node goes temporarily AWOL the other locations pick up the slack? I'd say definitely. I believe there are several people on here using them for purposes like that currently.
I think there are some places where you could host on a single node and expect that you will be okay.
Your risk tolerance is higher than mine. There's always network upgrades, provider maintenance, etc... that happen. Over the last few years even Amazon has had multiple regional outages of half a day or more. If my reputation is on the line I'm running redundant locations.
It depends. Imho. GCV brings better value for a dollar (considering every aspect of a service). Especially their anniversary and blackfriday deals. (things like their super reliable 7777MB RAM, 4 cores, 47GB SSD, IPv6, quick support response ... for $47.00 USD / biennially - and that's not even my favourite deal with them).
I have resources wise one really terrific deal from VirMach (2GB memory, 4 cores, 100GB NVMe disk, 2 IPs .. for barely $19.99 /yr) and there are people with most likely even better deals, but because of known reasons I mostly let it idle. It's simply more comfortable for me to use super reliable 4GB memory, 2 cores, etc... stuff for $25 /y or something from GCV, Kuro, HH, etc...
btw. my XenVZ uk vps has like 2 or 3 short outages in the last 10 years. Pretty much the same with little securedragon. Sadly both boxes are highly outdated and won't be renewed ...
I haven't thought about that as my stuff isn't CPU intensive. More like unspecific long term outages without knowing when stuff will come back, IPs renumbering again and again, etc.
Nothing what can't be migitated with other VPSes, but it takes time, and sometimes with recurring issues and unspecific long outages it simply isn't worth it as there are more reliable hosting companies with (still) budget pricing who even in the case of short term outage work actively on the issue instread of let it in the queve for unspecific time of the year.
I can easily use Virmach for eggdrops, vpn, webssh, etc... (mostly idle stuff used on a case-by-case basis) but I would never use it for lets say thelounge with hundred or more people connected through to my local irc community and crashed down every so often.
Comments
wget --limit-rate=50k https://whatever.com
kill -STOP < pid >
wait a while
kill -CONT < pid >
Repeat as necessary to achieve the necessary average speed.
TYOC029 node is indeed online, only mine is offline
VPS Control Panel does not see Disk Usage
The cause is that I restarted the VPS on the panel, maybe my mouse problem caused multiple clicks? i don't know the exact reason
I tried to start, shut down, restart, network repair, reinstall the system and still can't go online
@newlan - I've had this happen before, although I am not sure why it happens. I had reinstalled the VM and shut it down. Then went back to set up the new install a couple of days later and it would not start. I tried to start it each day from the control panel and on the 11th day it started. It did not start up itself. I have no advise to offer on how to get it started quicker.
@VirMach
What happened? The HD was deleted? Node Name：TPAZ003
https://imgur.com/NRksBHd
Thank you for your reply. I can only wait until @VirMach sees my request before processing it.
@localhost you now have company @tonyapac which is probably good news as I expect that VirMach will notice this issue quicker if there are more than one of you with the same problem.
@tonyapac - Read what I said here. for some tidbits of information regarding this issue.
Fingers crossed 🤞
@FrankZ
Thanks for the information.
@localhost
Let's see and wait together.
Yup... hopefully we will start to get noticed... by @VirMach
SEAZ001 IP 47.87.187.xxx
Operation Timed Out After 90001 Milliseconds With 0 Bytes Received
I'm not sure if my issue was fixed by Virmach or it was fixed by itself just like the issue that happens out of nowhere. Virmach didn't reply to my ticket even after the issue was fixed, so I closed it manually.
I am having the same issue with my VM on SEAZ001.
Node SEAZ001 is overloading. Current load average is a bit over 700.
The Yeti has left the building.
The Yeti has left the building.
I run my code server external authentication proxy there. As it is offline today, my friends and I login code without any authentication. This incident helps me learning more about nginx config; my bad
Virmach Deals
LAXA031 also seems to be taking a dump right now
Thank you for the update, looks like it has been unavailable for about six hours. That is actually good news for me as I have a VM on LAXA031 that developed the "No boot device available" yesterday. Hoping a reboot will fix it without having to wait as long as normal. Fingers crossed.
@VirMach VM on SEAZ005 have been not reachable for over 3 months. Ip4 47.87.135.xxx . Unsuccessfully tried every troubleshooting steps in the book reconfigure network, re-install various os images, reboot, VNC and verified all networks files, disabled firewall resolver but still not connected to internet and can't ssh from outside. Ticket open for over a month and also created priority ticket $ but no help. Please @VirMach help!
I have a VM on SEAZ005 and the IP I have is in a completely different subnet (72.5.34.xxx). If I try to traceroute what should be your gateway IP ( 47.87.135.1) from my VM on SEAZ005 it shows as 35 ms away at quadranet.com (LAX ?). If you would like to PM me your actual IP and default gateway IP I will double check this for you.
Anybody else recently started having IPv6 issues in Tokyo ?
I can ping6 the IPv6 gateway, but nothing past that and nothing in to the VM via IPv6.
Appreciate checking for me, messaged you.
My VM on SEAZ005 has an IP same net as @FrankZ and works fine.
@xyz, Curious, what IP does your panel show in the the Main IP's field.
Panel main IP is same as 47.87.135.xxx inside the gateway 47.87.135.1 but @FrankZ mentioned that is from LAX subnet not sure how I got that in SEA. I did go through a migration from LAX so could be messed up migration
@xyz - If you received a email from the migration, check if the IPs that show in the email match what you show in the panel. I expect that they do, but if they don't and are from the 72.5.34.xxx subnet you should be able to fix this without VirMach.
@FrankZ what don't you visit virvir and help him. He need your fingers to focus.... do you remember my dream
Yes, I remember your dream, but I don't think that VirMach wants my help.
same Ip in the email. This is one of those super cheap VM during 2019 BF, I assume @VirMach want me to get frustrated and cancel myself without resolution. Should I request new Ip? That is like $3 and may be they have automation to assign from the right subnet?
As a person with several of those, I'm going to say he isn't putting that kind of effort into getting rid of us.
I don't expect it should cost you anything since your current one won't work on the location you're at. Will it take a while? Probably. But now at least you can update your existing ticket with useful information. Maybe it'll go faster since all he has to do is assign you one relevant to your server location. Who can say?
Since you have waited three months already, I would let it ride as is for a little while longer. Maybe @VirMach will see your post here on LES and have someone assign your VM some correct IPv4 for the node you are on instead of the ones from the Los Angeles node you migrated from. I expect there is only one VM trying to use IPv4 from the 47.87.135.xx subnet on node SEAZ005 so it should not be that hard to find.
What is the next location for a full outage?
Although there is not a full location outage anywhere at the moment, Atlanta comes pretty close, as I only see one node still responding there. (fixed) Personally I am keeping my eye on SEAZ001 which has a load average of 833 1,138 currently. I can't help but wonder if it will catch on fire, or get rebooted before doing so.
I have a shared hosting service with Virmach.com, and unfortunately, the service has been down since April. However, I recently received a bill for the next year's subscription, which is due on 06/30/2023. I am concerned about making the payment while the service is still not restored. Is there a way to pause or postpone the payment until the service is fully operational again?
considering to let go these BF deals soon:
both have been stable. any interest?
I bench YABS 24/7/365 unless it's a leap year.
What are the renewal prices on those bad boys?
ATLZ009 is back
Thanks @dgc1980 !!
It looks like the network issue involving ATLZ005, ATLZ007B, ATLZ009, and ATLZ010 has been resolved.
My VM on ATLZ007B is back as well, no restart.
From the status page:
After reaching a load average 1,620, and a reboot, the problem on SEAZ001 seems to have been resolved. My VM is now responding normally.
IPv6 in Tokyo is indeed dead, since yesterday.
Has your LAXA031 VM been able to be brought back online after the node reboot? I don't seem to be able to boot my VM, mount a recovery disk, or even access VNC at the moment.
Not yet, my VM just shows "offline" in the billing panel. If I attempt to boot it, it continues to show "offline". I expect that this means that customers are not allowed to start VMs on LAXA031 as of yet. VirMach has probably identified a further issue with this node, and until it is corrected, we have to wait.
This time again to enjoy OUTAGE PARTY
Virmach Deals
I bench YABS 24/7/365 unless it's a leap year.
Nice plan cybertech, I have a 3c/5g/60G with 30$ renewal price.
Anyone using the ryzen flash deals for serious production use? (where you would be losing money or reputation if they were offline.) Just trying to decide if i'm thinking about my $100+ worth of flash deals the right way.
i.e. if its a fun toy/hobby thing, where you get tons of performance and cheap resources and can do things like run Windows, where youd never be able to do that on $2 per month (or less, lol!) VPS elsewhere, but the tradeoff is that it can have lengthy downtimes. OR if its something that really should be okay for production use?
You say, "where you would be losing money or reputation if they were offline," but for serious production use you shouldn't be in that situation anyway. Would it be perfectly appropriate for serious production use as a single-node web server for clients with hard SLA's? Prob'ly not. Would it be okay for serious production as part of a redundant group of application servers where if a single node goes temporarily AWOL the other locations pick up the slack? I'd say definitely. I believe there are several people on here using them for purposes like that currently.
I think there are some places where you could host on a single node and expect that you will be okay. Since the flash sale we've experienced multiple full location outages, IP addresses for multiple locations being dropped off the internet by the IP owner, week/month long node outages etc... On the other hand, name a provider where you will get 4 cores, 4-6gb of ram and tons of storage/bandwidth (including 2 or more IPv4) for under $2 month. I guess i'm to the point where i'm willing to accept the outages, knowing that when its up, its not going to be beaten for the price by any other provider. (just maybe not $100+/yr worth, might just keep 1 or 2 of the best deals.)
Your risk tolerance is higher than mine. There's always network upgrades, provider maintenance, etc... that happen. Over the last few years even Amazon has had multiple regional outages of half a day or more. If my reputation is on the line I'm running redundant locations.
It depends. Imho. GCV brings better value for a dollar (considering every aspect of a service). Especially their anniversary and blackfriday deals. (things like their super reliable 7777MB RAM, 4 cores, 47GB SSD, IPv6, quick support response ... for $47.00 USD / biennially - and that's not even my favourite deal with them).
I have resources wise one really terrific deal from VirMach (2GB memory, 4 cores, 100GB NVMe disk, 2 IPs .. for barely $19.99 /yr) and there are people with most likely even better deals, but because of known reasons I mostly let it idle. It's simply more comfortable for me to use super reliable 4GB memory, 2 cores, etc... stuff for $25 /y or something from GCV, Kuro, HH, etc...
btw. my XenVZ uk vps has like 2 or 3 short outages in the last 10 years. Pretty much the same with little securedragon. Sadly both boxes are highly outdated and won't be renewed ...
@Mumbly are the 'known reasons' the concern that there is low tolerance for putting the CPU under load and leading to termination?
I haven't thought about that as my stuff isn't CPU intensive. More like unspecific long term outages without knowing when stuff will come back, IPs renumbering again and again, etc.
Nothing what can't be migitated with other VPSes, but it takes time, and sometimes with recurring issues and unspecific long outages it simply isn't worth it as there are more reliable hosting companies with (still) budget pricing who even in the case of short term outage work actively on the issue instread of let it in the queve for unspecific time of the year.
I can easily use Virmach for eggdrops, vpn, webssh, etc... (mostly idle stuff used on a case-by-case basis) but I would never use it for lets say thelounge with hundred or more people connected through to my local irc community and crashed down every so often.