@hemake said: @VirMach #162520
After I reinstalled the system, the status was: shut down.
After I clicked to power on, it was still in the off state.
VNC access failed.
To me, logic says if the server is in an off state, then VNC will not work.
It sounds very much like the re-install failed a reboot.
You don't say what you installed - so try a virmach template such as debian 12 (I think that works - others can confirm). If that boots then it shows your original re-install was likely the problem.
@hemake said: @VirMach #162520
After I reinstalled the system, the status was: shut down.
After I clicked to power on, it was still in the off state.
VNC access failed.
To me, logic says if the server is in an off state, then VNC will not work.
It sounds very much like the re-install failed a reboot.
You don't say what you installed - so try a virmach template such as debian 12 (I think that works - others can confirm). If that boots then it shows your original re-install was likely the problem.
Similarly, no matter what program is installed, it is in an offline state.
@hemake said: @VirMach #162520
After I reinstalled the system, the status was: shut down.
After I clicked to power on, it was still in the off state.
VNC access failed.
To me, logic says if the server is in an off state, then VNC will not work.
It sounds very much like the re-install failed a reboot.
You don't say what you installed - so try a virmach template such as debian 12 (I think that works - others can confirm). If that boots then it shows your original re-install was likely the problem.
Similarly, no matter what program is installed, it is in an offline state.
Ok not an expert but it sounds more like a disk problem - Hopefully your ticket will be answered but don't expect a fast response.
@VirMach seems like "automatic" ticket creation from Troubleshooter is ignoring URL params like &subject= so nothing is auto-set anymore (-:
also please fix javascript, the Troubleshooter is not showing anything as checked (https://i.imgur.com/Pr4ST4V.png) as you fat-fingered s into javascript
However maybe ignored params are related, probably the same script?
too lazy to click it again, sorry.
Sorry @VirMach but in the interests of non bias I have to say your ticketing system is not fit for purpose.
VM id=722446 fails.
VNC shows system had gone in to read only.
Reboot and fsck is needed but fails as it can't write to the file system. Managed to raise a ticket and AI says re-install. After about 12 hours I did attempt a re-install which just put the server offline and it remained offline (as well as control panel). Went to update the ticket which said best to close the ticket and open a new one. Which I did and now the system wont let me open a new ticket and tells me to refer to network status page which shows no issues.
I know you don't want tickets but following YOUR rules the system is broken even more.
OKC beta tester reporting network/routing issues. Not a complaint, just informational.
193.58.147.xxx in OKC can not ping 31.59.129.xx in Amsterdam
193.58.147.xxx in OKC can not ping 66.23.198.xx in Valley Forge, PA.
193.58.147.xxx in OKC can not ping 69.197.140.xxx in Kansas City, MO.
193.58.147.xxx in OKC can not ping 173.249.199.xxx in San Jose, CA.
I'll try to reply to everyone later tonight, with some updates. A lot of what's mentioned is actively being worked on, some of it I've already been addressing before your comments which makes me feel good, and others, at this moment in time with everything going on, I've missed, so the comments are definitely helpful.
As you can see from all the comments though there's a lot going on, so let's hope we have a good day today!
@VirMach said:
I'll try to reply to everyone later tonight, with some updates. A lot of what's mentioned is actively being worked on, some of it I've already been addressing before your comments which makes me feel good, and others, at this moment in time with everything going on, I've missed, so the comments are definitely helpful.
As you can see from all the comments though there's a lot going on, so let's hope we have a good day today!
LAX1Z020is down~ ticket #989759 (but it seems tickets are useless anyway).
The AI's reply is giving me my own IP: The virtual server associated with the IP address $MY_IP_HERE_NOT_THE_SERVER is currently down. I suggest we first check for any known outages or maintenance on the server node [redacted by request]. If none are present, we can attempt a server reboot as a potential solution. If the issue persists after the reboot, it may require human intervention to further investigate any underlying problems. Please confirm if we should proceed with the reboot.
Comments
To me, logic says if the server is in an off state, then VNC will not work.
It sounds very much like the re-install failed a reboot.
You don't say what you installed - so try a virmach template such as debian 12 (I think that works - others can confirm). If that boots then it shows your original re-install was likely the problem.
Similarly, no matter what program is installed, it is in an offline state.
Ok not an expert but it sounds more like a disk problem - Hopefully your ticket will be answered but don't expect a fast response.
I should watch scary movie. But it's not available anywhere
Not sure why you are posting here (rest removed)
Never make the same mistake twice. There are so many new ones to make.
It’s OK if you disagree with me. I can’t force you to be right.
Because my Virmach server is not fully usable right now.
Waiting for the IPs
Virmaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaach
Virtfuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuusion
I bench YABS 24/7/365 unless it's a leap year.
@VirMach
Hello respected boss:
My three VPS have been successfully renewed, but the suspension has not been lifted yet
Invoice #1682926
Maybe today is the day
Today is always the day
So any flan @imok lately?
Today is going to be flan day.
No puede ser, me olvidé de preparar el flan.
Edit: Sorry, wrong language. I forgot to make the flan.
@VirMach seems like "automatic" ticket creation from Troubleshooter is ignoring URL params like
&subject=so nothing is auto-set anymore (-:also please fix javascript, the Troubleshooter is not showing anything as checked (https://i.imgur.com/Pr4ST4V.png) as you fat-fingered
sinto javascriptHowever maybe ignored params are related, probably the same script?
too lazy to click it again, sorry.
https://billing.virmach.com/modules/addons/customTicketsAddon/js/scripts.js
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
Wow jquery
is AMSD025 down? seems nothing on status page but solusvm shows 'The host is currently unavailable' @VirMach
Sorry @VirMach but in the interests of non bias I have to say your ticketing system is not fit for purpose.
VM id=722446 fails.
VNC shows system had gone in to read only.
Reboot and fsck is needed but fails as it can't write to the file system. Managed to raise a ticket and AI says re-install. After about 12 hours I did attempt a re-install which just put the server offline and it remained offline (as well as control panel). Went to update the ticket which said best to close the ticket and open a new one. Which I did and now the system wont let me open a new ticket and tells me to refer to network status page which shows no issues.
I know you don't want tickets but following YOUR rules the system is broken even more.
@Virmach outbound from MIAZ015 (now Oklahoma allegedly?) on 193.58.147.0/24, VM id=721708 is broken.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Is Virmach IP Day today?
@imok FO!
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Looks like lots of CPU Steal occurring on AMSD018.
Additionally, it looks like some data corruptions.
@VirMach any info about LAXA017 ? Its been away for too long
ServerStatus , slackvpn
Recommended Providers: AlphaVPS(aff) | HostBRR(aff) | HostDare(aff) | KuroIT(aff)
Hi again.
ATLZ034 has routing problems.
OKC beta tester reporting network/routing issues. Not a complaint, just informational.
193.58.147.xxx in OKC can not ping 31.59.129.xx in Amsterdam
193.58.147.xxx in OKC can not ping 66.23.198.xx in Valley Forge, PA.
193.58.147.xxx in OKC can not ping 69.197.140.xxx in Kansas City, MO.
193.58.147.xxx in OKC can not ping 173.249.199.xxx in San Jose, CA.
Full stop to the VM + Start worked.
I'll try to reply to everyone later tonight, with some updates. A lot of what's mentioned is actively being worked on, some of it I've already been addressing before your comments which makes me feel good, and others, at this moment in time with everything going on, I've missed, so the comments are definitely helpful.
As you can see from all the comments though there's a lot going on, so let's hope we have a good day today!
Crazy amount of inbound port scanning going on at OKC. :-s
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Is today a good day?
LAX1Z020is down~ ticket #989759 (but it seems tickets are useless anyway).The AI's reply is giving me my own IP:
The virtual server associated with the IP address $MY_IP_HERE_NOT_THE_SERVER is currently down. I suggest we first check for any known outages or maintenance on the server node [redacted by request]. If none are present, we can attempt a server reboot as a potential solution. If the issue persists after the reboot, it may require human intervention to further investigate any underlying problems. Please confirm if we should proceed with the reboot.The server isn't even listed there: https://status.virm.ac/