@Ahui said:
It seems that you have become accustomed to being humble and kneeling, so keep kneeling and continue using this provider that easily imposes the death penalty
I don't think you understand the difference between a VPS and a VDS. If you want to use 100% of the resources assigned all the time you need to buy a VDS. A VPS has shared resources and can only be used at high rates for a limited time.
Your question is very good. Let me ask you a few questions
1.VPS will first directly restrict IO usage, for example, each VPS will only have 2000IOPS
2.When VPS uses 1000IOPS, the provider will directly sentence you to death and permanently ban VPS
3.Have you experienced the issue of IO abuse being sentenced to death by other providers?
Let me help you out here. I have a few VMs that I am not going to use from other providers in the EU that ether have hard limits on I/O or do not have hard limits but let people run wild. Let me see which one will let me transfer one to you. I'll give it to you for free for almost a year. It's Christmas after all. They are all much bigger than your 768MB VPS, lets see if that works for you.
Thank you for your help. I want to say thank you to you. I have many VPS, 50-60 , and I also have 15 on @ VirMach. I just find it unbelievable
Peace on earth will come to stay, when we all live as LESbians every day.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
@imok said:
From the kind of answers he gives, I've come to a conclusion, but no one cares so I keep it to myself.
You are all great, it's just that this provider is too bullying users when dealing with things
I had a several suspensions a few years ago on a @Virmach VPS I still have. I was perplexed and stated so in a ticket. @Virmach gave me advice how to potentially fix/avoid suspension. I've not had trouble since. My experience was that @Virmach worked with me rather than giving me the ax immediately. At the time, the VPS was running a spigot (minecraft) server for a handful of users. One user was apparently going crazy flying over massive amounts of unexplored terrain. I put a limiter on the server to deal with it.
I think its really harsh to say @Virmach is bullying. Frankly, I think you're being rude. It's hard to want to help rude people. I'm surprised at @FrankZ 's offer... also impressed. Take a deep breath, calm down. It feels like the flood of stacatto messages and answers really do not have meat (detailed facts). I doubt that will help the situation.
I finally had my VirMach only regional failover system fail completely after 1456 days [3.98 years] of continuous website uptime.
Was it VirMach's fault ?
Not this time. it was my fault for not updating a certificate chain.
I had 15 minutes of downtime while I corrected it.
So I'm now down to 99.9992846% uptime with VirMach on this production website.
Peace on earth will come to stay, when we all live as LESbians every day.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
I finally had my VirMach only regional failover system fail completely after 1456 days [3.98 years] of continuous website uptime.
Was it VirMach's fault ?
Not this time. it was my fault for not updating a certificate chain.
I had 15 minutes of downtime while I corrected it.
So I'm now down to 99.9992846% uptime with VirMach on this production website.
@FAT32 said:
Any tips on installing for 128MB RAM on VirMach servers? I tried a few ways via ISO/Netboot directly but all of them crashed/killed with OOM (Debian 9+, AlmaLinux 8+)
You can run debian 10 on a VPS with 128M RAM by using the official debian cloud image.
Since the rescue mode version is quite old, you may also need to update some software like wget or xz or something like that.
Good luck!
Well I given up at this point and just installed CentOS 6 and call it a day, the Debian 10 image is still showing out of memory and kernel panic Tried to Geekbench but to no avail as it requires newer glibc, so ya that's that for now
@VirMach can you bring back the $0.95/yr package that I forgot to pay 6 years ago? I would have never expected 128MB RAM to be that painful nowadays, most installer crashed even Debian 8/9 ISO
@FAT32 said:
Any tips on installing for 128MB RAM on VirMach servers? I tried a few ways via ISO/Netboot directly but all of them crashed/killed with OOM (Debian 9+, AlmaLinux 8+)
You can run debian 10 on a VPS with 128M RAM by using the official debian cloud image.
Since the rescue mode version is quite old, you may also need to update some software like wget or xz or something like that.
Good luck!
Well I given up at this point and just installed CentOS 6 and call it a day, the Debian 10 image is still showing out of memory and kernel panic Tried to Geekbench but to no avail as it requires newer glibc, so ya that's that for now
@VirMach can you bring back the $0.95/yr package that I forgot to pay 6 years ago? I would have never expected 128MB RAM to be that painful nowadays, most installer crashed even Debian 8/9 ISO
Blame me for not describing it well.
Yes, you will get kernel panic after the installation is done, at that point you need to POWER OFF the VPS and reboot it and you will be able to log in via VNC using the root password.
@core said: @VirMach
I submitted a suspension appeal in Ticket #619341
I paid the relevant fees as required, but because I did not receive the email notification, my server was suspended again (only 5 hours later)
I am not sure what happened to the server that caused the abnormal traffic. I cannot operate it immediately after the server is restored to normal, so please reinstall the system and restore it
If you're in a rush to receive a response, I can provide a rushed response. You won't like the response though. Any time a suspension appeal is taking a long time it means I really know I have to deny the appeal but waiting to see if I can convince myself otherwise.
A #619341 #791068
"This ticket is regarding a matter that was previously communicated. Please refer to previous communication by us."
I responded to the ticket, and you just closed it without responding to me
In fact, my server was suspended for some reason, I paid the fine, I waited for 2 hours, and didn't see the server back to normal, so I went to work
After 4 hours, I received a reminder that my server was suspended again
In this case, I didn't know when my server was back to normal, and I didn't receive any reminder of recovery. I think I was treated unfairly.
I don't know why you're mentioning paying anything. That did occur, but you're leaving out the part where I specifically refunded you the fee. Not that we're required to refund the fee. So $40 suspension fee was reduced to $5 as a courtesy. This is for the suspension and not the appeal. The appeal was rejected, and I also refunded the fee as I mentioned.
You also received this communication, Which did not include anything about it being unsuspended and resuspended, the appeal was just rejected. So the response you received is correct, as it was previously communicated. Refer to previous communication:
This cannot be unsuspended due to the severity. Heavy traffic even after suspension with packets being sent to it. I've refunded the appeal fee.
Reminder, your suspension reason as well:
Reason: Mass file sharing/torrent/high connection + high I/O
Let me know how it's unfair. You basically simultaneously broke at least four portions of our AUP in a really bad way, to an extreme level. You contributed to the entire node crashing. When I say you contributed I mean I believe you caused the node to crash but there's obviously a possibility that one other abuser at the same time may have exasperated the situation, and you would have instead only heavily overloaded the server. Your service also almost immediately crashed the server again after it came back online. You most definitely can rest assured that even if we billed you our $40 standard suspension fee, you would be receiving a big discount compared to our bill rate as this took would have cost in the $80 to $120 range if we were to bill you for the actual time it took to address, not including responding to you here or your tickets.
Your service is less than a 1/100th chunk of all the disk, yet your service by itself was 40% average or as high as 60% utilization rate, as in the proportion of total disk processing capacity being used by your service alone, with peak of around 5MB/s reads and 4MB/s writes at around 4kB to 8kB average request size. Other people use the server too, so this likely led to saturation, overloading, and a crash.
This also is not the first time this has happened and you should have honestly been suspended sooner (that's my fault for missing it.) Your usage for this server looks like it shifted some time around August 2024 in some way, with larger incoming network spikes about once every 1 to 3 months, with the accompanied heavy I/O spikes. When you were suspended, over 500 individual IP addresses were connecting to your service.
Although you'd still be breaking our terms of service, we can't provide a service to you, nor would we want to continue doing business with you in any other way, my recommendation for your use case, with another provider, would at the very least be an SSD service. That won't solve everything but it would get rid of the problem where your service is trying to do (according to SolusVM) 60MB/s to 200MB/s in reads to serve whatever content or whatever you're doing (and they're at 4kB to 8kB average request size.)
My math and analysis above may not be perfect and I've been awake for a very long time, if any of the above bothers you, refer to the most important portion of the message again, the only part that matters:
This cannot be unsuspended due to the severity.
Welcome to judgement day bro @core
Make ticket will make you naked here.
@core said: @VirMach
I submitted a suspension appeal in Ticket #619341
I paid the relevant fees as required, but because I did not receive the email notification, my server was suspended again (only 5 hours later)
I am not sure what happened to the server that caused the abnormal traffic. I cannot operate it immediately after the server is restored to normal, so please reinstall the system and restore it
If you're in a rush to receive a response, I can provide a rushed response. You won't like the response though. Any time a suspension appeal is taking a long time it means I really know I have to deny the appeal but waiting to see if I can convince myself otherwise.
A #619341 #791068
"This ticket is regarding a matter that was previously communicated. Please refer to previous communication by us."
I responded to the ticket, and you just closed it without responding to me
In fact, my server was suspended for some reason, I paid the fine, I waited for 2 hours, and didn't see the server back to normal, so I went to work
After 4 hours, I received a reminder that my server was suspended again
In this case, I didn't know when my server was back to normal, and I didn't receive any reminder of recovery. I think I was treated unfairly.
I don't know why you're mentioning paying anything. That did occur, but you're leaving out the part where I specifically refunded you the fee. Not that we're required to refund the fee. So $40 suspension fee was reduced to $5 as a courtesy. This is for the suspension and not the appeal. The appeal was rejected, and I also refunded the fee as I mentioned.
You also received this communication, Which did not include anything about it being unsuspended and resuspended, the appeal was just rejected. So the response you received is correct, as it was previously communicated. Refer to previous communication:
This cannot be unsuspended due to the severity. Heavy traffic even after suspension with packets being sent to it. I've refunded the appeal fee.
Reminder, your suspension reason as well:
Reason: Mass file sharing/torrent/high connection + high I/O
Let me know how it's unfair. You basically simultaneously broke at least four portions of our AUP in a really bad way, to an extreme level. You contributed to the entire node crashing. When I say you contributed I mean I believe you caused the node to crash but there's obviously a possibility that one other abuser at the same time may have exasperated the situation, and you would have instead only heavily overloaded the server. Your service also almost immediately crashed the server again after it came back online. You most definitely can rest assured that even if we billed you our $40 standard suspension fee, you would be receiving a big discount compared to our bill rate as this took would have cost in the $80 to $120 range if we were to bill you for the actual time it took to address, not including responding to you here or your tickets.
Your service is less than a 1/100th chunk of all the disk, yet your service by itself was 40% average or as high as 60% utilization rate, as in the proportion of total disk processing capacity being used by your service alone, with peak of around 5MB/s reads and 4MB/s writes at around 4kB to 8kB average request size. Other people use the server too, so this likely led to saturation, overloading, and a crash.
This also is not the first time this has happened and you should have honestly been suspended sooner (that's my fault for missing it.) Your usage for this server looks like it shifted some time around August 2024 in some way, with larger incoming network spikes about once every 1 to 3 months, with the accompanied heavy I/O spikes. When you were suspended, over 500 individual IP addresses were connecting to your service.
Although you'd still be breaking our terms of service, we can't provide a service to you, nor would we want to continue doing business with you in any other way, my recommendation for your use case, with another provider, would at the very least be an SSD service. That won't solve everything but it would get rid of the problem where your service is trying to do (according to SolusVM) 60MB/s to 200MB/s in reads to serve whatever content or whatever you're doing (and they're at 4kB to 8kB average request size.)
My math and analysis above may not be perfect and I've been awake for a very long time, if any of the above bothers you, refer to the most important portion of the message again, the only part that matters:
This cannot be unsuspended due to the severity.
Welcome to judgement day bro @core
Make ticket will make you naked here.
Yes, virmarch was smart and suspended my server 6 months after PayPal payment. According to him, the abnormality appeared in August, but my server was suspended around December.
Yes, according to him, he should have suspended me earlier, but he was very considerate and waited until the PayPal payment exceeded 6 months before suspending it
In addition, I don't know why a 2-core 3G memory VPS can cause the entire node to crash. If virmarch's technology is so good that it can allow people to use a low-configuration VPS to cause the entire node to crash, it is really worth learning for other merchants
So, I doubt the authenticity of what he said. Is it true?
He still didn’t answer my most important question. My VPS returned to normal for a short time, and I didn’t receive any notification
Yes, you will get kernel panic after the installation is done, at that point you need to POWER OFF the VPS and reboot it and you will be able to log in via VNC using the root password.
Nope the kernel panic happened after the reboot, it seems like 128MB just didn't cut it for some reason. Tried twice using different image (one with cloud-init and one without) but to no avail
@Ahui said:
As a user of @ VirMach for 3 years, I purchased 15 VPS with annual billing. Recently, I received a notice stating that a VPS has been suspended and accused of abuse IO@VirMach Please tell me that lifting the suspension requires a payment of $40. This is the first time I have encountered a problem in three years, and that's how he solved it. This is so interesting, it made me see @ VirMach clearly. No wonder so many people are boycotting @ VirMach. I finally understand
Hi guys,
If your server has some abnormal servers that are running continuously, you need to deal with it as soon as possible after payment. If you are late by 3 hours, your server will be suspended again and the fee will be refunded.
Also please note that there is no email reminder when the server is restored to normal. Please refresh the page 24 hours after payment until the server is restored.
Yes, you will get kernel panic after the installation is done, at that point you need to POWER OFF the VPS and reboot it and you will be able to log in via VNC using the root password.
Nope the kernel panic happened after the reboot, it seems like 128MB just didn't cut it for some reason. Tried twice using different image (one with cloud-init and one without) but to no avail
That's right, the kernel panic does happen after the first reboot, the key is that after the kernel panic happens, the normal reboot doesn't work, You need to go to “Full VPS Control Panel” and click “Power Off” instead of other buttons, then reboot again. At this point you should see the login screen.
PS: Make sure you use a cloud image, virmach's default debian 10 image won't run on a VPS with only 128M RAM.
I took this approach to install debian 10.13 on my mystery box.
@core said: Yes, according to him, he should have suspended me earlier, but he was very considerate and waited until the PayPal payment exceeded 6 months before suspending it
What are you saying here?
@core said: He still didn’t answer my most important question. My VPS returned to normal for a short time, and I didn’t receive any notification
That's not a question it's a statement.
@core said: Also please note that there is no email reminder when the server is restored to normal. Please refresh the page 24 hours after payment until the server is restored.
Surely your monitoring saw it return to service. A relatively minor thing which most will never notice as they will never get suspended.
Yes, you will get kernel panic after the installation is done, at that point you need to POWER OFF the VPS and reboot it and you will be able to log in via VNC using the root password.
Nope the kernel panic happened after the reboot, it seems like 128MB just didn't cut it for some reason. Tried twice using different image (one with cloud-init and one without) but to no avail
That's right, the kernel panic does happen after the first reboot, the key is that after the kernel panic happens, the normal reboot doesn't work, You need to go to “Full VPS Control Panel” and click “Power Off” instead of other buttons, then reboot again. At this point you should see the login screen.
PS: Make sure you use a cloud image, virmach's default debian 10 image won't run on a VPS with only 128M RAM.
I took this approach to install debian 10.13 on my mystery box.
If you take the proper steps, you can do it too.
It is a cloud image, I might just try Debian 9 instead and I did poweroff before reboot...
Yes, you will get kernel panic after the installation is done, at that point you need to POWER OFF the VPS and reboot it and you will be able to log in via VNC using the root password.
Nope the kernel panic happened after the reboot, it seems like 128MB just didn't cut it for some reason. Tried twice using different image (one with cloud-init and one without) but to no avail
That's right, the kernel panic does happen after the first reboot, the key is that after the kernel panic happens, the normal reboot doesn't work, You need to go to “Full VPS Control Panel” and click “Power Off” instead of other buttons, then reboot again. At this point you should see the login screen.
PS: Make sure you use a cloud image, virmach's default debian 10 image won't run on a VPS with only 128M RAM.
I took this approach to install debian 10.13 on my mystery box.
If you take the proper steps, you can do it too.
It is a cloud image, I might just try Debian 9 instead and I did poweroff before reboot...
I'll describe them in order:
enter rescue mode and install the cloud image with DD
exit rescue mode and the system should automatically reboot and go into a kernel panic state
Use the POWER OFF button in the Full VPS Control Panel
@core said: Yes, according to him, he should have suspended me earlier, but he was very considerate and waited until the PayPal payment exceeded 6 months before suspending it
What are you saying here?
@core said: He still didn’t answer my most important question. My VPS returned to normal for a short time, and I didn’t receive any notification
That's not a question it's a statement.
@core said: Also please note that there is no email reminder when the server is restored to normal. Please refresh the page 24 hours after payment until the server is restored.
Surely your monitoring saw it return to service. A relatively minor thing which most will never notice as they will never get suspended.
@core said: Yes, according to him, he should have suspended me earlier, but he was very considerate and waited until the PayPal payment exceeded 6 months before suspending it
What are you saying here?
@core said: He still didn’t answer my most important question. My VPS returned to normal for a short time, and I didn’t receive any notification
That's not a question it's a statement.
@core said: Also please note that there is no email reminder when the server is restored to normal. Please refresh the page 24 hours after payment until the server is restored.
Surely your monitoring saw it return to service. A relatively minor thing which most will never notice as they will never get suspended.
I installed the Windows system through the backend. Where can I monitor whether my VPS has returned to normal? Please tell me the URL
In fact, I visited the virmach website within 2 hours after payment. I don’t know how I can know that my VPS has returned to normal in the first time except this method. At least virmach official does not provide it (if there is no email reminder)
Yes, you will get kernel panic after the installation is done, at that point you need to POWER OFF the VPS and reboot it and you will be able to log in via VNC using the root password.
Nope the kernel panic happened after the reboot, it seems like 128MB just didn't cut it for some reason. Tried twice using different image (one with cloud-init and one without) but to no avail
That's right, the kernel panic does happen after the first reboot, the key is that after the kernel panic happens, the normal reboot doesn't work, You need to go to “Full VPS Control Panel” and click “Power Off” instead of other buttons, then reboot again. At this point you should see the login screen.
PS: Make sure you use a cloud image, virmach's default debian 10 image won't run on a VPS with only 128M RAM.
I took this approach to install debian 10.13 on my mystery box.
If you take the proper steps, you can do it too.
It is a cloud image, I might just try Debian 9 instead and I did poweroff before reboot...
I'll describe them in order:
enter rescue mode and install the cloud image with DD
exit rescue mode and the system should automatically reboot and go into a kernel panic state
Use the POWER OFF button in the Full VPS Control Panel
BOOT
5.login (you need to use VNC)
debian 9 cloud image also works perfectly.
Yup thats exactly what I did, unfortunately I dont think I want to spend more time on this but thanks for the suggestions!
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
Comments
Thank you for your help. I want to say thank you to you. I have many VPS, 50-60 , and I also have 15 on @ VirMach. I just find it unbelievable
From the kind of answers he gives, I've come to a conclusion, but no one cares so I keep it to myself.
BTW I've run out of flan.
It's arroz con leche time... maybe.
Peace on earth will come to stay, when we all live as LESbians every day.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
You are all great, it's just that this provider is too bullying users when dealing with things
I had a several suspensions a few years ago on a @Virmach VPS I still have. I was perplexed and stated so in a ticket. @Virmach gave me advice how to potentially fix/avoid suspension. I've not had trouble since. My experience was that @Virmach worked with me rather than giving me the ax immediately. At the time, the VPS was running a spigot (minecraft) server for a handful of users. One user was apparently going crazy flying over massive amounts of unexplored terrain. I put a limiter on the server to deal with it.
I think its really harsh to say @Virmach is bullying. Frankly, I think you're being rude. It's hard to want to help rude people. I'm surprised at @FrankZ 's offer... also impressed. Take a deep breath, calm down. It feels like the flood of stacatto messages and answers really do not have meat (detailed facts). I doubt that will help the situation.
what do these people do with this much vps? vpn? jumpbox to clean the tracks?
>
That suggests you are using a low-end provider in some type of production (that is to say "serious use") environment. This may not be a good idea.
In other news ....
I finally had my VirMach only regional failover system fail completely after 1456 days [3.98 years] of continuous website uptime.
Was it VirMach's fault ?
Not this time. it was my fault for not updating a certificate chain.
I had 15 minutes of downtime while I corrected it.
So I'm now down to 99.9992846% uptime with VirMach on this production website.
Peace on earth will come to stay, when we all live as LESbians every day.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
Outrageous!
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
tutorial?
Jeez, is this the first sensible comment, ever?
Just saying.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
@FrankZ i wouldnt mind some help too lol
I bench YABS 24/7/365 unless it's a leap year.
Well I given up at this point and just installed CentOS 6 and call it a day, the Debian 10 image is still showing out of memory and kernel panic
Tried to Geekbench but to no avail as it requires newer glibc, so ya that's that for now 
@VirMach can you bring back the $0.95/yr package that I forgot to pay 6 years ago?
I would have never expected 128MB RAM to be that painful nowadays, most installer crashed even Debian 8/9 ISO
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
Blame me for not describing it well.
Yes, you will get kernel panic after the installation is done, at that point you need to POWER OFF the VPS and reboot it and you will be able to log in via VNC using the root password.
Have the honor of being the crybaby who pays $20 for a 128MB VPS at VirMach in 2023.
Yes, virmarch was smart and suspended my server 6 months after PayPal payment. According to him, the abnormality appeared in August, but my server was suspended around December.
Yes, according to him, he should have suspended me earlier, but he was very considerate and waited until the PayPal payment exceeded 6 months before suspending it
In addition, I don't know why a 2-core 3G memory VPS can cause the entire node to crash. If virmarch's technology is so good that it can allow people to use a low-configuration VPS to cause the entire node to crash, it is really worth learning for other merchants
So, I doubt the authenticity of what he said. Is it true?
He still didn’t answer my most important question. My VPS returned to normal for a short time, and I didn’t receive any notification
Nope the kernel panic happened after the reboot, it seems like 128MB just didn't cut it for some reason. Tried twice using different image (one with cloud-init and one without) but to no avail
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
Hi guys,
If your server has some abnormal servers that are running continuously, you need to deal with it as soon as possible after payment. If you are late by 3 hours, your server will be suspended again and the fee will be refunded.
Also please note that there is no email reminder when the server is restored to normal. Please refresh the page 24 hours after payment until the server is restored.
The above is my experience
That's right, the kernel panic does happen after the first reboot, the key is that after the kernel panic happens, the normal reboot doesn't work, You need to go to “Full VPS Control Panel” and click “Power Off” instead of other buttons, then reboot again. At this point you should see the login screen.
PS: Make sure you use a cloud image, virmach's default debian 10 image won't run on a VPS with only 128M RAM.
I took this approach to install debian 10.13 on my mystery box.
If you take the proper steps, you can do it too.
Have the honor of being the crybaby who pays $20 for a 128MB VPS at VirMach in 2023.
What are you saying here?
That's not a question it's a statement.
Surely your monitoring saw it return to service. A relatively minor thing which most will never notice as they will never get suspended.
It is a cloud image, I might just try Debian 9 instead and I did poweroff before reboot...
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
I'll describe them in order:
5.login (you need to use VNC)
debian 9 cloud image also works perfectly.
Have the honor of being the crybaby who pays $20 for a 128MB VPS at VirMach in 2023.
I installed the Windows system through the backend. Where can I monitor whether my VPS has returned to normal? Please tell me the URL
In fact, I visited the virmach website within 2 hours after payment. I don’t know how I can know that my VPS has returned to normal in the first time except this method. At least virmach official does not provide it (if there is no email reminder)
Yup thats exactly what I did, unfortunately I dont think I want to spend more time on this but thanks for the suggestions!
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
Maybe because he ran out of flan
blog | exploring visually |
I dont understand