@imok said:
I started working with my phoenix ryzen vps again. Installed Debian 11 and upgraded and it stopped working.
Reinstallling Debian 11... I suppose I should not upgrade the OS.
Hmm, I do see a history of things like this happening with Debian. Update, then bug reported of a similar issue, "fixed" and then repeat. Seems like it could be caused by any particular package. Gets even more fun when you add in virtualization, Ryzen, and specific motherboards.
It sure is going to be fun to see where we're at with everything in 10, 20, 30 years.
So minimal ISO is confirmed working? It must be missing whatever's causing this. If someone can confirm exact setup with ISO that works the best I should be able to just make a template.
@imok said:
I started working with my phoenix ryzen vps again. Installed Debian 11 and upgraded and it stopped working.
Reinstallling Debian 11... I suppose I should not upgrade the OS.
Hmm, I do see a history of things like this happening with Debian. Update, then bug reported of a similar issue, "fixed" and then repeat. Seems like it could be caused by any particular package. Gets even more fun when you add in virtualization, Ryzen, and specific motherboards.
It sure is going to be fun to see where we're at with everything in 10, 20, 30 years.
So minimal ISO is confirmed working? It must be missing whatever's causing this. If someone can confirm exact setup with ISO that works the best I should be able to just make a template.
i think so yes. it wasn't working for a while then now it is.
@mbk said: @VirMach Four of my servers were moved to NYC, two from Dallas and two from Atlanta. Network status page said that nodes in ATLZ010 were not moving?
I don't want all those servers in NYC. Is it possible to get these servers migrated away from NYC?
Very long answer but some variation of this will occur, yes.
@Dompetri said: @VirMach stopped giving refunds for downtime periods?
Had a VPS down for months, requested a refund and the ticket was closed.
If you mean SLA credit for the down time, you might get a better response from VirMach if you say that in your ticket, as saying "refund" had a predictable response. I have never known of VirMach, or any other provider, to give refunds for downtime on a no refunds product.
Also, congratulations on your first LES comment.
@Dompetri said: @VirMach stopped giving refunds for downtime periods?
Had a VPS down for months, requested a refund and the ticket was closed.
If you mean SLA credit for the down time, you might get a better response from VirMach if you say that in your ticket, as saying "refund" had a predictable response. I have never known of VirMach, or any other provider, to give refunds for downtime on a no refunds product.
Also, congratulations on your first LES comment.
Yeah in my post I did mean credits for downtime, thanks for the correction.
In the ticket I asked clearly that I wanted the credits due to downtime period and it was closed.
I wouldn't even open a ticket if the VPS was down for some weeks, but 5 months down and no response about the credits is disappointing.
@Dompetri said: @VirMach stopped giving refunds for downtime periods?
Had a VPS down for months, requested a refund and the ticket was closed.
If you mean SLA credit for the down time, you might get a better response from VirMach if you say that in your ticket, as saying "refund" had a predictable response. I have never known of VirMach, or any other provider, to give refunds for downtime on a no refunds product.
Also, congratulations on your first LES comment.
Yeah in my post I did mean credits for downtime, thanks for the correction.
In the ticket I asked clearly that I wanted the credits due to downtime period and it was closed.
I wouldn't even open a ticket if the VPS was down for some weeks, but 5 months down and no response about the credits is disappointing.
If you don't mind my asking, which node are you on that's been down five months? I haven't paid that close of attention.
@cybertech said: this is just about what the strawberry generation can do really.
So after looking up "strawberry generation" I am really glad I posted the above. Your comment gave me a whole new insight into understanding some of the folks who visit this thread.
Strawberry generation (Chinese: 草莓族; pinyin: Cǎoméi zú; or 草莓世代; cǎoméi shìdài)[1] is a Chinese-language neologism used for people born from 1990s onwards who "bruise easily" like strawberries – meaning they cannot withstand social pressure or work hard like their parents' generation; the term refers to people who are perceived as insubordinate,[2] spoiled, selfish, arrogant, and sluggish in work.[3]
The term arises from the perception that members of this generation have grown up being overprotected by their parents and in an environment of stability, in a similar manner to how strawberries are grown in protected greenhouses and command a higher price compared to other fruits. The term gained prominence in the press, as it could be a way to designate a rising demographic or psychographic in terms of consumer behavior.
@cybertech said: this is just about what the strawberry generation can do really.
So after looking up "strawberry generation" I am really glad I posted the above. Your comment gave me a whole new insight into understanding some of the folks who visit this thread.
Strawberry generation (Chinese: 草莓族; pinyin: Cǎoméi zú; or 草莓世代; cǎoméi shìdài)[1] is a Chinese-language neologism used for people born from 1990s onwards who "bruise easily" like strawberries – meaning they cannot withstand social pressure or work hard like their parents' generation; the term refers to people who are perceived as insubordinate,[2] spoiled, selfish, arrogant, and sluggish in work.[3]
The term arises from the perception that members of this generation have grown up being overprotected by their parents and in an environment of stability, in a similar manner to how strawberries are grown in protected greenhouses and command a higher price compared to other fruits. The term gained prominence in the press, as it could be a way to designate a rising demographic or psychographic in terms of consumer behavior.
It's interesting the different meanings that a literal translation of a word can have. Here is Mexico if I called someone a strawberry (Fresa) it would mean that they were a junior of a rich dad. If I called them a snowflake it would be probably be taken as calling them gay. In Mexico I would call an easily bruised person "Crystal"
@Dompetri said: @VirMach stopped giving refunds for downtime periods?
Had a VPS down for months, requested a refund and the ticket was closed.
It'd be helpful to have a ticket ID in this case. It shouldn't be closed with no credit or extension, unless you're leaving out any details, such as the outage is still ongoing and not yet ended and so on. Probably post the full ticket here.
I'll of course make a correction and provide explanation on what happened if there was a mistake.
(edit) I checked all tickets recently made mentioning NYCB027 and NYCB035 and there's one close match, created one day ago. Ticket marked as completed and closed, due date for service was extended to 09/26/2024.
It'd be helpful to have a ticket ID in this case. It shouldn't be closed with no credit or extension, unless you're leaving out any details, such as the outage is still ongoing and not yet ended and so on. Probably post the full ticket here.
Ticket marked as completed and closed, due date for service was extended to 09/26/2024.
Are Flashsales VPS eligible for extension and were on SEA nodes ? I have a SEA VPS up and running now but due date isn't extended
It'd be helpful to have a ticket ID in this case. It shouldn't be closed with no credit or extension, unless you're leaving out any details, such as the outage is still ongoing and not yet ended and so on. Probably post the full ticket here.
Ticket marked as completed and closed, due date for service was extended to 09/26/2024.
Are Flashsales VPS eligible for extension and were on SEA nodes ? I have a SEA VPS up and running now but due date isn't extended
With everything flying around, we haven't done any auto credits, especially since we also have been manually crediting people. So you'd need to make a ticket to request credits. If we bring back auto credits it will be under a new better system but it's not ready yet and these wouldn't be logged in it.
I will make a small note here however, that this would be considered not qualifying as SLA credits under our terms of service:
downtime caused by issues in third party services
causes beyond the control of VirMach or that are not reasonably foreseeable
But in this case I did sort of foresee this, but it could have just been a coincidence. Anyway, we're not disputing any credits/extensions requested, we're just not doing it automatically.
But yeah just so we're clear, in the future any datacenters burning down, flooding, servers being stolen, companies we use going out of business without appropriate notice for us to act all fall under not eligible for credits. I know there's no reason to make this comment in this way other than maybe 17 years from now something happens and someone says "but you said here that you did cover it when blah blah happened."
Oh another note, DDoS attacks aren't protected either unless your location is advertised as protected and then that's only protected up until the advertised level. Maintenance windows aren't covered although in the past we tend to be courteous and just approve them. Re-installing/breaking your service doesn't qualify.
What is reasonably foreseeable and covered?
DDoS up until advertised level if advertised
A business says they're going out of business and not renewing contract and giving us reasonable notice
Our hardware has general issues like bad memory, disk
Our network goes down because VirMach screws it up or switch dies
The PDU dies and we lose power
We accidentally turn off your service when we shouldn't have done so (it's happened, we credit people immediately usually.)
Abuse system makes a mistake and powers you down (extremely rare, doesn't really happen anymore.)
Are Flashsales VPS eligible for extension and were on SEA nodes ? I have a SEA VPS up and running now but due date isn't extended
With everything flying around, we haven't done any auto credits, especially since we also have been manually crediting people. So you'd need to make a ticket to request credits. If we bring back auto credits it will be under a new better system but it's not ready yet and these wouldn't be logged in it.
Thank you, I just wanted to get clarity about credits and whether or not to expect them. It is a small VPS so I don't need it in this case.
I might request for the one in DAL one once it is back.
@VirMach said: causes beyond the control of VirMach or that are not reasonably foreseeable
This include every possible outage except scheduled/maintenance outages - and those most likely aren't covered with SLA so basically everything
Isn't then better to write something short and clear like: "we don't offer SLA for our service"?
Edit.
ah, overlooked this part (still early morning here)
@VirMach said: What is reasonably foreseeable and covered?
DDoS up until advertised level if advertised
A business says they're going out of business and not renewing contract and giving us reasonable notice
Our hardware has general issues like bad memory, disk
Our network goes down because VirMach screws it up or switch dies
The PDU dies and we lose power
We accidentally turn off your service when we shouldn't have done so (it's happened, we credit people immediately usually.)
Abuse system makes a mistake and powers you down (extremely rare, doesn't really happen anymore.)
@Mumbly said: This include every possible outage except scheduled/maintenance outages - and those most likely aren't covered with SLA so basically everything
Isn't then better to write something short and clear like: "we don't offer SLA for our service"?
Yeah, it could definitely be interpreted in a ridiculous way on both sides, but I'd like to think actions speak louder than words when it comes to this and why we tend to be very lenient on qualifications. But hey, as with almost everything else I guess it depends most on whether you trust the company you are doing business with and perhaps that could also be argued either way. What I do know is in I suppose in a very biased way, we've never had bad intentions.
I just thought it'd be a good time to remind people we do have a terms of service and at some point in the future we may decide to draw the line somewhere if things continue getting crazy in a way that's completely out of our control and not within the realm of what's normally calculated into the SLA. Because who knows, we've been so unlucky that maybe there being a hole in the ceiling and our cabinet getting struck by lightening is within the realm of possibility and we're not prepared to provide SLA credits in that case.
I honestly do not expect SLA on my black friday, limited support services. they are already below retail prices so if it works 99% of the time, it is profit, unless someone is hosting a million dollar website on it...
I also don't bother with SLA, never did. Imho that's for people who pay for service $40+ monthly and not us peasants, who pay $10 - $40 yearly.
Extension of a service date after longer outage is a nice gesture, but to specifically request and bother host for few pennies is just silly waste of time for both parties.
fully agree with @dgc1980 and @Mumbly
If you get 99% uptime for 50% of the price of 99,9% uptime its still a win.
but you have to understand what 99% uptime means and accept it.
@FrankZ@VirMach
After the machine migrated, I don't know about the situation of other nodes, the situation with lax1z014 is very bad.it has been experiencing frequent disconnections, ranging from 1 to 10 minutes each time, occurring several tens to hundreds of times per day. Essentially, the machine is no longer usable due to these disconnections. While we can understand that the performance and speed may be compromised as it is a discounted machine, the frequent disconnections are a quality issue. Are there any plans to fix this?
@sparkssss said: @FrankZ@VirMach
After the machine migrated, I don't know about the situation of other nodes, the situation with lax1z014 is very bad.it has been experiencing frequent disconnections, ranging from 1 to 10 minutes each time, occurring several tens to hundreds of times per day. Essentially, the machine is no longer usable due to these disconnections. While we can understand that the performance and speed may be compromised as it is a discounted machine, the frequent disconnections are a quality issue. Are there any plans to fix this?
Run MTR from your VPS to another location that we have like Amsterdam, Tokyo, NYC for a day and submit that in a ticket. Do it to one of our test IPs if possible so we can check it the other way around if there's any major issues and provide credentials in the ticket to your VPS for fastest resolution. Make sure to pick connection issue when making the ticket.
@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 ?
@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
Comments
i think its best to use ISO for latest now
I bench YABS 24/7/365 unless it's a leap year.
Hmm, I do see a history of things like this happening with Debian. Update, then bug reported of a similar issue, "fixed" and then repeat. Seems like it could be caused by any particular package. Gets even more fun when you add in virtualization, Ryzen, and specific motherboards.
It sure is going to be fun to see where we're at with everything in 10, 20, 30 years.
So minimal ISO is confirmed working? It must be missing whatever's causing this. If someone can confirm exact setup with ISO that works the best I should be able to just make a template.
i think so yes. it wasn't working for a while then now it is.
I bench YABS 24/7/365 unless it's a leap year.
@VirMach Four of my servers were moved to NYC, two from Dallas and two from Atlanta. Network status page said that nodes in ATLZ010 were not moving?
I don't want all those servers in NYC. Is it possible to get these servers migrated away from NYC?
"If you put your mind to it, anything is possible." -- Kimberly Guilefoyle
Very long answer but some variation of this will occur, yes.
Alright, thanks for the reply. I guess I'll wait on renewing these for now but I hope that something good occurs before BF/CM.
My node was migrated from NYCB027 to NYCB035, and there is still no network connectivity.
How about if we had a bunch of servers migrated to NY and we actually like it that way, can they stay?
TYOC038 what time can online ?
It's offline is more than 1 month.
did xtom jp got ddos'd again?
Fuck this 24/7 internet spew of trivia and celebrity bullshit.
@VirMach stopped giving refunds for downtime periods?
Had a VPS down for months, requested a refund and the ticket was closed.
If you mean SLA credit for the down time, you might get a better response from VirMach if you say that in your ticket, as saying "refund" had a predictable response. I have never known of VirMach, or any other provider, to give refunds for downtime on a no refunds product.
Also, congratulations on your first LES comment.
Yeah in my post I did mean credits for downtime, thanks for the correction.
In the ticket I asked clearly that I wanted the credits due to downtime period and it was closed.
I wouldn't even open a ticket if the VPS was down for some weeks, but 5 months down and no response about the credits is disappointing.
If you don't mind my asking, which node are you on that's been down five months? I haven't paid that close of attention.
Originally NYCB027 and moved to NYCB035 after Dedipath closure, VPS went alive two weeks ago since May or June.
Wow, exactly the same as you. and in 3 months, the VPS will expire.
I found this on a forum that shall remain nameless. It was so humorous, and cute, that I just had to share it with you.
this is just about what the strawberry generation can do really.
still, dogs are much cuter than cunts
since i'm educated and civilized i shall not post a picture of gathering of cunts
as Confucious teaching goes, we should be gentleman.
I bench YABS 24/7/365 unless it's a leap year.
So after looking up "strawberry generation" I am really glad I posted the above. Your comment gave me a whole new insight into understanding some of the folks who visit this thread.
aka snowflakes
I bench YABS 24/7/365 unless it's a leap year.
There's also another word for it... "glass-hearted"
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
It's interesting the different meanings that a literal translation of a word can have. Here is Mexico if I called someone a strawberry (Fresa) it would mean that they were a junior of a rich dad. If I called them a snowflake it would be probably be taken as calling them gay. In Mexico I would call an easily bruised person "Crystal"
Such a cute CyberTech, no aggression.
such docile MJJ, no complaints
I bench YABS 24/7/365 unless it's a leap year.
It'd be helpful to have a ticket ID in this case. It shouldn't be closed with no credit or extension, unless you're leaving out any details, such as the outage is still ongoing and not yet ended and so on. Probably post the full ticket here.
I'll of course make a correction and provide explanation on what happened if there was a mistake.
(edit) I checked all tickets recently made mentioning NYCB027 and NYCB035 and there's one close match, created one day ago. Ticket marked as completed and closed, due date for service was extended to 09/26/2024.
Who ever posted this: fuck you, I am not on FrankZ leash, he too weak in his spaghetti (only on VirMach leash, kthxbye).
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Just wondering who the other three are, like wow we only have 3 people they could identify as not being negative about us there?
nonononononono, it's called 'acceptance stage' rather than 'not being negative'
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Wow, I'm jealous. I want fan-art too!
Website: thomassen.sh
I want to be the cute one to the left, with the orange!
If there's only 3 why not Ceberus?
I only want to be in the meme if I am a cat!
Are Flashsales VPS eligible for extension and were on SEA nodes ? I have a SEA VPS up and running now but due date isn't extended
With everything flying around, we haven't done any auto credits, especially since we also have been manually crediting people. So you'd need to make a ticket to request credits. If we bring back auto credits it will be under a new better system but it's not ready yet and these wouldn't be logged in it.
I will make a small note here however, that this would be considered not qualifying as SLA credits under our terms of service:
But in this case I did sort of foresee this, but it could have just been a coincidence. Anyway, we're not disputing any credits/extensions requested, we're just not doing it automatically.
But yeah just so we're clear, in the future any datacenters burning down, flooding, servers being stolen, companies we use going out of business without appropriate notice for us to act all fall under not eligible for credits. I know there's no reason to make this comment in this way other than maybe 17 years from now something happens and someone says "but you said here that you did cover it when blah blah happened."
Oh another note, DDoS attacks aren't protected either unless your location is advertised as protected and then that's only protected up until the advertised level. Maintenance windows aren't covered although in the past we tend to be courteous and just approve them. Re-installing/breaking your service doesn't qualify.
What is reasonably foreseeable and covered?
Thank you, I just wanted to get clarity about credits and whether or not to expect them. It is a small VPS so I don't need it in this case.
I might request for the one in DAL one once it is back.
This include every possible outage except scheduled/maintenance outages - and those most likely aren't covered with SLA so basically everything
Isn't then better to write something short and clear like: "we don't offer SLA for our service"?
Edit.
ah, overlooked this part (still early morning here)
Isn't then better to write something short and clear like: "we don't offer SLA for our service"?
Yeah, it could definitely be interpreted in a ridiculous way on both sides, but I'd like to think actions speak louder than words when it comes to this and why we tend to be very lenient on qualifications. But hey, as with almost everything else I guess it depends most on whether you trust the company you are doing business with and perhaps that could also be argued either way. What I do know is in I suppose in a very biased way, we've never had bad intentions.
I just thought it'd be a good time to remind people we do have a terms of service and at some point in the future we may decide to draw the line somewhere if things continue getting crazy in a way that's completely out of our control and not within the realm of what's normally calculated into the SLA. Because who knows, we've been so unlucky that maybe there being a hole in the ceiling and our cabinet getting struck by lightening is within the realm of possibility and we're not prepared to provide SLA credits in that case.
I honestly do not expect SLA on my black friday, limited support services. they are already below retail prices so if it works 99% of the time, it is profit, unless someone is hosting a million dollar website on it...
^ This +1.
I also don't bother with SLA, never did. Imho that's for people who pay for service $40+ monthly and not us peasants, who pay $10 - $40 yearly.
Extension of a service date after longer outage is a nice gesture, but to specifically request and bother host for few pennies is just silly waste of time for both parties.
SLA is just marketing gimmick. and so is 24/7/365 support
I bench YABS 24/7/365 unless it's a leap year.
fully agree with @dgc1980 and @Mumbly
If you get 99% uptime for 50% of the price of 99,9% uptime its still a win.
but you have to understand what 99% uptime means and accept it.
@FrankZ @VirMach
After the machine migrated, I don't know about the situation of other nodes, the situation with lax1z014 is very bad.it has been experiencing frequent disconnections, ranging from 1 to 10 minutes each time, occurring several tens to hundreds of times per day. Essentially, the machine is no longer usable due to these disconnections. While we can understand that the performance and speed may be compromised as it is a discounted machine, the frequent disconnections are a quality issue. Are there any plans to fix this?
Yea, @FrankZ, fix it! Now!
Run MTR from your VPS to another location that we have like Amsterdam, Tokyo, NYC for a day and submit that in a ticket. Do it to one of our test IPs if possible so we can check it the other way around if there's any major issues and provide credentials in the ticket to your VPS for fastest resolution. Make sure to pick connection issue when making the ticket.
Once that's provided, I'll have FrankZ fix it.
That sounds like effort, a lot of effort.
Can't FrankZ intern handle it himself if user provide login/pass!?
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
@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 ?
@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