That's been waiting on networking all week, it looks like a routing issue. It's online, just specific IP addresses and routes at specific times act wonky. So to some people it's online, to some it's offline, and to our panel it's responding sometimes and according to our monitoring it might be working about half the time.
@Mumbly said:
I was about to ask the same. Longer measured in hours or weeks? :P
Click start in panel, things online! I've seen load went from 0.05 to 1.89 so I assumed server was fixed just no VMs started and this seems true - my shit online after clicking start. Now need to figure out how to sync data back
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
@Mumbly said:
I was about to ask the same. Longer measured in hours or weeks? :P
Click start in panel, things online! I've seen load went from 0.05 to 1.89 so I assumed server was fixed just no VMs started and this seems true - my shit online after clicking start. Now need to figure out how to sync data back
Everyone I've seen have it still be offline have an old ISO mounted and either ignored the message on boot up to unmount ISO or not used the reset button.
It would be useful to see some kind of status message about what then plans/ETA are regarding your node when your node is locked, all that can be seen is "The node is currently locked" without rudimentary information like which node it even is (I only remember the datacenter). I have the option to cancel but it's not clear if this provides a refund based on the remaining time paid for since the platform advertises "No complicated hourly billing".
@WhatTheFunction said:
It would be useful to see some kind of status message about what then plans/ETA are regarding your node when your node is locked, all that can be seen is "The node is currently locked" without rudimentary information like which node it even is (I only remember the datacenter). I have the option to cancel but it's not clear if this provides a refund based on the remaining time paid for since the platform advertises "No complicated hourly billing".
If you have a plan that shows as a "Special Offer" in the title then it does not normally qualify for a refund. Specials state at time of purchase "No Refunds". If you do not have a "Special Offer" then let us know the type of plan you have and we can give you more information.
@FrankZ said:
If you have a plan that shows as a "Special Offer" in the title then it does not normally qualify for a refund. Specials state at time of purchase "No Refunds". If you do not have a "Special Offer" then let us know the type of plan you have and we can give you more information.
It's been a while so I don't remember most of the details but I don't think it was a special offer, it's called 'Legacy KVM Plans - SSD512' now. I understand 100% that it's cheap node and definitely didn't go in expecting any technical support if I messed something up or anything like an SLA guarantee, but sending a ticket in just to get some information about what's going on made an AI recite what I already told it back to me and the ticket was closed so I'm a bit in the dark about what to expect. Appreciate the response.
I am not totally sure that the "Legacy KVM Plans" are eligible for partial refunds, so I would not want to steer you wrong and say it is. Regarding the "The node is currently locked" message:
if you see a message "The node is currently locked" it means the node controls are temporarily locked off. This could mean an ongoing maintenance, so please check the network status page for more information.
@FrankZ said:
I am not totally sure that the "Legacy KVM Plans" are eligible for partial refunds, so I would not want to steer you wrong and say it is. Regarding the "The node is currently locked" message:
if you see a message "The node is currently locked" it means the node controls are temporarily locked off. This could mean an ongoing maintenance, so please check the network status page for more information.
Yeah, I can only assume it's one of the down NYC nodes since I can't view anything about the node but remember it was an NYC instance. The instance was extremely low traffic and I rarely touched it nor monitored it beyond an occasional package update, but I have a rough idea for how long it's been down because LetsEncrypt starts sending emails when certs fail to autorenew within 20 days of expiry and there's now 6 days remaining, giving a minimum 2 weeks the node has either been locked or down (I assume locked since I know it's been locked for the last week).
I should probably consider the ~4 months remaining on the instance to be flushed and move on, for the price I understood/expected that service would be a "whatever's left" of available resources but it seems the resources have been zero for a while now. Appreciate your time though!
@WhatTheFunction said:
It would be useful to see some kind of status message about what then plans/ETA are regarding your node when your node is locked, all that can be seen is "The node is currently locked" without rudimentary information like which node it even is (I only remember the datacenter). I have the option to cancel but it's not clear if this provides a refund based on the remaining time paid for since the platform advertises "No complicated hourly billing".
It's just not how the system works, not how we built it or want it in terms of not being able to see your node name. Luckily right now there are not that many outages posted, so you should be able to tell which one applies to you.
One is for Tokyo.
One is for NYCB043 but it's listed as an outage. I agree that I should put more information for this one to let everyone know it's a network routing issue and it's not locked.
One is for NYCB011X --> NYCB035, NYCB020, and NYCB027 bundled in that has had previous updates posted. So if it's for a long long time, then you are on NYCB027. If it's for the past 1-2 weeks, then you were on NYCB011X and migrated to NYCB035 or NYCB020. I'll add in some more information on this one as well and moving forward I'll try to better label which is specifically locked.
can you check my ticket #913893
I waited another 4 months already, just want to grab my missing deposit funds(because I sent the wrong amount of coins) back to my main account
should I buy 60$ extra support on an abandon-ready account to grab my 22.52$ back?
@vgood said: LAX2Z019 nodes. I want to try migration but it can't, the Migrate menu doesn't show any options.
I'm also on that node in Los Angeles. The node is having issues for the last couple of days and there are no control panel options available at the moment. It is also on the Virmach status page, so he is aware.
08/13/2023 12:57 Last Updated 08/13/2023 12:58
We're investigating and attempting to resolve an outage on LAX2Z019.
Don't try to migrate until things are completely fixed or you might break your VM and have further issues.
So when you say, "My San Jose VPS" what you mean is "My Los Angeles VPS"? That's going to cause a bit of confusion. Perhaps rethink that strategy.
sorry I forgot, that's why I didn't explain the node code, the member panel felt very slow to open, and finally when I looked at the purchase email, the purchase at that time was San Jose. maybe I've moved nodes, I forgot too because this is indeed an old VPS. after finally opening the full VPS panel, it turned out that the node code was visible. sorry
I'm having trouble figuring out how to use netboot.xyz ISO and install Debian 12. After mounting the ISO, I change the boot order to 1. CD Rom 2. Hard disk and reboot the VPS.
When I select Debian 12 from the Distributions list then after a couple of seconds (it configures something network related) it takes me back to the main menu to select either to boot from local disk (which gets stuck if I choose it), distributions, tools etc. What step am I missing while doing the install?
@KernelPanic said:
I'm having trouble figuring out how to use netboot.xyz ISO and install Debian 12. After mounting the ISO, I change the boot order to 1. CD Rom 2. Hard disk and reboot the VPS.
When I select Debian 12 from the Distributions list then after a couple of seconds (it configures something network related) it takes me back to the main menu to select either to boot from local disk (which gets stuck if I choose it), distributions, tools etc. What step am I missing while doing the install?
I understand that this is not the answer you are looking for, but mounting the Debian Latest (12.1.0) ISO was faster for me.
When I choose Distributions -> Linux Network Installs -> Debian -> 12 -> Text Based Install, it shows this screen for a few seconds and then takes me back to that first screen with those options. I'm not sure where to look for the disk on these 2 screens.
I understand that this is not the answer you are looking for, but mounting the Debian Latest (12.1.0) ISO was faster for me.
Thanks. Till now I thought it was the Debian 10 ISO (at-least as per the SolusVM which only contains Debian 10 ISO), so I didn't try the "Debian Latest" in the WHMCS. Looks like that will do the trick. Thanks for pointing that out!
EDIT: What's the best way to do a minimal install using this ISO?
@KernelPanic said:
It shows me the following screen on boot
When I choose Distributions -> Linux Network Installs -> Debian -> 12 -> Text Based Install, it shows this screen for a few seconds and then takes me back to that first screen with those options. I'm not sure where to look for the disk on these 2 screens.
this is what i encountered as well. also tried mounting debian 12 iso, but it installs debian 11 instead. did not test any further and went back to deb11 template
@cybertech said:
this is what i encountered as well. also tried mounting debian 12 iso, but it installs debian 11 instead. did not test any further and went back to deb11 template
I just installed using the Debian latest in expert mode and it did install Debian 12. Now just trying to figure out if there is any other minimal installation option available or that's pretty much it.
@KernelPanic said:
I'm having trouble figuring out how to use netboot.xyz ISO and install Debian 12. After mounting the ISO, I change the boot order to 1. CD Rom 2. Hard disk and reboot the VPS.
When I select Debian 12 from the Distributions list then after a couple of seconds (it configures something network related) it takes me back to the main menu to select either to boot from local disk (which gets stuck if I choose it), distributions, tools etc. What step am I missing while doing the install?
There's a bug with one of the newer Netboot versions and QEMU. It's not a Virmach thing specifically.
Comments
That's been waiting on networking all week, it looks like a routing issue. It's online, just specific IP addresses and routes at specific times act wonky. So to some people it's online, to some it's offline, and to our panel it's responding sometimes and according to our monitoring it might be working about half the time.
Same here
FFME04 on fire, please dispatch someone to handle it (-:
Load 1400, memory usage 98% - are we OOM?!
@VirMach
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Not OOM. Patch that went out didn't play well with this particular node, so more of the same old issue on this one. Might take a little longer to fix.
Standardize all nodes: exactly same hardware and software everywhere.
You'll save a lot of troubles down the road.
We accept Karma donations for the last flan. 🍮 affbrr
How much is the fish? Aka how long is little longer than longer than usual longer?
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
It's between 3 and 3000 regular longers long. Any longer and it will be longer then little longer long.
I was about to ask the same. Longer measured in hours or weeks? :P
Click start in panel, things online! I've seen load went from 0.05 to 1.89 so I assumed server was fixed just no VMs started and this seems true - my shit online after clicking start. Now need to figure out how to sync data back
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
It's back indeed. Thanks!
It is lucky I have moved site off NJ node.
I forgot to say thank you @VirMach for quick fix of FFFME!
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
FFME004 is still down.
So everybody else is wrong?
Mine was down, but was able to boot it up
PHXZ002 is down
Everyone I've seen have it still be offline have an old ISO mounted and either ignored the message on boot up to unmount ISO or not used the reset button.
It would be useful to see some kind of status message about what then plans/ETA are regarding your node when your node is locked, all that can be seen is "The node is currently locked" without rudimentary information like which node it even is (I only remember the datacenter). I have the option to cancel but it's not clear if this provides a refund based on the remaining time paid for since the platform advertises "No complicated hourly billing".
If you have a plan that shows as a "Special Offer" in the title then it does not normally qualify for a refund. Specials state at time of purchase "No Refunds". If you do not have a "Special Offer" then let us know the type of plan you have and we can give you more information.
It's been a while so I don't remember most of the details but I don't think it was a special offer, it's called 'Legacy KVM Plans - SSD512' now. I understand 100% that it's cheap node and definitely didn't go in expecting any technical support if I messed something up or anything like an SLA guarantee, but sending a ticket in just to get some information about what's going on made an AI recite what I already told it back to me and the ticket was closed so I'm a bit in the dark about what to expect. Appreciate the response.
I am not totally sure that the "Legacy KVM Plans" are eligible for partial refunds, so I would not want to steer you wrong and say it is. Regarding the "The node is currently locked" message:
Also the status page is here https://statusbot.virm.ac/en/ so if you see anything that looks familiar to you ....
Yeah, I can only assume it's one of the down NYC nodes since I can't view anything about the node but remember it was an NYC instance. The instance was extremely low traffic and I rarely touched it nor monitored it beyond an occasional package update, but I have a rough idea for how long it's been down because LetsEncrypt starts sending emails when certs fail to autorenew within 20 days of expiry and there's now 6 days remaining, giving a minimum 2 weeks the node has either been locked or down (I assume locked since I know it's been locked for the last week).
I should probably consider the ~4 months remaining on the instance to be flushed and move on, for the price I understood/expected that service would be a "whatever's left" of available resources but it seems the resources have been zero for a while now. Appreciate your time though!
It's just not how the system works, not how we built it or want it in terms of not being able to see your node name. Luckily right now there are not that many outages posted, so you should be able to tell which one applies to you.
One is for Tokyo.
One is for NYCB043 but it's listed as an outage. I agree that I should put more information for this one to let everyone know it's a network routing issue and it's not locked.
One is for NYCB011X --> NYCB035, NYCB020, and NYCB027 bundled in that has had previous updates posted. So if it's for a long long time, then you are on NYCB027. If it's for the past 1-2 weeks, then you were on NYCB011X and migrated to NYCB035 or NYCB020. I'll add in some more information on this one as well and moving forward I'll try to better label which is specifically locked.
I have a VPS from VIR JP, and it's currently quite stable. Although I haven't been using it for long, I hope it will remain stable.
Sigh, another fanboy above...
Ya chaps never learn
Ontario Dildo Inspector
can you check my ticket #913893
I waited another 4 months already, just want to grab my missing deposit funds(because I sent the wrong amount of coins) back to my main account
should I buy 60$ extra support on an abandon-ready account to grab my 22.52$ back?
Yes.
We accept Karma donations for the last flan. 🍮 affbrr
@VirMach Just an FYI LAX2Z019 appears to be overloading.
EDIT: Not overloading anymore.
The more you buy, the more you save
-- Jensen Huang
Ontario Dildo Inspector
How about TYOC007, it had been offline dozens of days.
@VirMach consider hiring a priest
FYI the node TYOC007 is not offline. My VM on that node shows only 18 minutes of downtime in the last 45 days.
my san jose vps is still off until now, is there the same?
"Operation Timed Out After 90001 Milliseconds With 0 Bytes Received"
What node are you on in SJC ?
LAX2Z019 nodes. I want to try migration but it can't, the Migrate menu doesn't show any options.
So when you say, "My San Jose VPS" what you mean is "My Los Angeles VPS"? That's going to cause a bit of confusion. Perhaps rethink that strategy.
I'm also on that node in Los Angeles. The node is having issues for the last couple of days and there are no control panel options available at the moment. It is also on the Virmach status page, so he is aware.
Don't try to migrate until things are completely fixed or you might break your VM and have further issues.
sorry I forgot, that's why I didn't explain the node code, the member panel felt very slow to open, and finally when I looked at the purchase email, the purchase at that time was San Jose. maybe I've moved nodes, I forgot too because this is indeed an old VPS. after finally opening the full VPS panel, it turned out that the node code was visible. sorry
okay, thanks for reminding me.
We need Debian 12 :-)
maybe you just need to upgrade from debian 11
I'm having trouble figuring out how to use netboot.xyz ISO and install Debian 12. After mounting the ISO, I change the boot order to 1. CD Rom 2. Hard disk and reboot the VPS.
When I select Debian 12 from the Distributions list then after a couple of seconds (it configures something network related) it takes me back to the main menu to select either to boot from local disk (which gets stuck if I choose it), distributions, tools etc. What step am I missing while doing the install?
Can you find the disk when install?
I understand that this is not the answer you are looking for, but mounting the Debian Latest (12.1.0) ISO was faster for me.
It shows me the following screen on boot
When I choose Distributions -> Linux Network Installs -> Debian -> 12 -> Text Based Install, it shows this screen for a few seconds and then takes me back to that first screen with those options. I'm not sure where to look for the disk on these 2 screens.
Thanks. Till now I thought it was the Debian 10 ISO (at-least as per the SolusVM which only contains Debian 10 ISO), so I didn't try the "Debian Latest" in the WHMCS. Looks like that will do the trick. Thanks for pointing that out!
EDIT: What's the best way to do a minimal install using this ISO?
this is what i encountered as well. also tried mounting debian 12 iso, but it installs debian 11 instead. did not test any further and went back to deb11 template
I bench YABS 24/7/365 unless it's a leap year.
Which node? I'm on
RYZE.CHI-Z027.VMSI just installed using the Debian latest in expert mode and it did install Debian 12. Now just trying to figure out if there is any other minimal installation option available or that's pretty much it.
There's a bug with one of the newer Netboot versions and QEMU. It's not a Virmach thing specifically.