@Jab said:
it's so quiet, I guess migration went pretty well?
@VirMach : Web hosting on lax2z017.virm.ac came back up after being down, but control panel and web mail did not. Then again, the ticket for them (#482793) has been open since 01/29/2025, so 'the good old days are back again'.
@Jab said:
it's so quiet, I guess migration went pretty well?
@VirMach : Web hosting on lax2z017.virm.ac came back up after being down, but control panel and web mail did not. Then again, the ticket for them (#482793) has been open since 01/29/2025, so 'the good old days are back again'.
Let me know if you want me to continue addressing your concerns here or if you want it shifted back over to the ticket. I haven't closed the ticket as I usually would have if we addressed you here instead when you reference the ticket, as I wanted to read through it to make sure I didn't miss anything else.
I did see your feedback relating to communication and I hope you saw that we did better this time around in sending out the maintenance email for shared hosting services.
@Brayvin said: @VirMach : Web hosting on lax2z017.virm.ac came back up after being down, but control panel and web mail did not. Then again, the ticket for them (#482793) has been open since 01/29/2025, so 'the good old days are back again'.
Let me know if you want me to continue addressing your concerns here or if you want it shifted back over to the ticket. I haven't closed the ticket as I usually would have if we addressed you here instead when you reference the ticket, as I wanted to read through it to make sure I didn't miss anything else.
I did see your feedback relating to communication and I hope you saw that we did better this time around in sending out the maintenance email for shared hosting services.
I do prefer the ticket system as long as it gets timely results. I only mentioned the number here because I've happened to have a number of tickets drop into a black hole. I'll wait it out, hoping the migration will make this service viable.
Sure I'll venture a guess.
Virmach has remote hands checking and/or trying to recover a broken drive. I don't think the node is down, only some VMs are down on TYOC027. We were just lucky enough to be on a drive that has issues. If the drive can't be recovered, it will be replaced and restored from backups. This could take a few more days or a week depending on DC hands workload and what needs to be done.
When the Los Angeles migrations are finished, I expect that VirMach may have time to deal with this, but right now it is probably not the top priority as relatively few VMs are affected. I know this probably doesn't make you feel any better about this downtime, but that is my guess. If you are really in a bind, and have your own backups to restore, PM me with what size VM you have and I'll see if there is something I can lend you in the meantime.
Of course maybe you'll get lucky and because I said it could take a week, it will be up in a hour just to show how wrong I am.
TYO-C027 has not been recovered so far, is anyone following up and dealing with it? @VirMach@FrankZ
It still makes me chuckle when people tag me along with VirMach for a service related issue.
You guys should know that I do not, and never have, worked for VirMach.
I am just a long time customer.
@geo said:
Damn. LAXA019 was online for a while then offline.
Looks like I'll be waiting along with you on LAXA019.
Affecting System - LAX
02/24/2025 09:37 Last Updated 02/27/2025 01:26
LATEST UPDATE
The following servers are still waiting for IPv4 to route. Current ETA is 9AM February 27th (delayed, need further maintenance.)
LAXA008 - Needs power cycle
LAXA009 - Needs power cycle
LAXA010 - Needs power cycle
LAXA024 - Needs power cycle
LAXA025 - Needs power cycle
LAXA026 - Needs power cycle
The following servers have further issues after returning back online and will be looked into in the morning. We apologize for the continued network outage.
LAXA019 - Went offline after being brought back (network)
LAXA004 - Having other issues unrelated to network
LAXA014 - Other issues related to networking specifically on the server
LAXA015 - Extreme packet loss
LAXA016 - Extreme packet loss
LAXA006 - Went offline after being brought back (network)
LAX Shared Hosting node - Needs some configuration changes
If you are having any other issues and it is not listed above, we are likely aware of the issue and it will be addressed as part of the maintenance.
Sure I'll venture a guess.
Virmach has remote hands checking and/or trying to recover a broken drive. I don't think the node is down, only some VMs are down on TYOC027. We were just lucky enough to be on a drive that has issues. If the drive can't be recovered, it will be replaced and restored from backups. This could take a few more days or a week depending on DC hands workload and what needs to be done.
When the Los Angeles migrations are finished, I expect that VirMach may have time to deal with this, but right now it is probably not the top priority as relatively few VMs are affected. I know this probably doesn't make you feel any better about this downtime, but that is my guess. If you are really in a bind, and have your own backups to restore, PM me with what size VM you have and I'll see if there is something I can lend you in the meantime.
Of course maybe you'll get lucky and because I said it could take a week, it will be up in a hour just to show how wrong I am.
TYO-C027 has not been recovered so far, is anyone following up and dealing with it? @VirMach@FrankZ
Sure I'll venture a guess.
Virmach has remote hands checking and/or trying to recover a broken drive. I don't think the node is down, only some VMs are down on TYOC027. We were just lucky enough to be on a drive that has issues. If the drive can't be recovered, it will be replaced and restored from backups. This could take a few more days or a week depending on DC hands workload and what needs to be done.
When the Los Angeles migrations are finished, I expect that VirMach may have time to deal with this, but right now it is probably not the top priority as relatively few VMs are affected. I know this probably doesn't make you feel any better about this downtime, but that is my guess. If you are really in a bind, and have your own backups to restore, PM me with what size VM you have and I'll see if there is something I can lend you in the meantime.
Of course maybe you'll get lucky and because I said it could take a week, it will be up in a hour just to show how wrong I am.
TYO-C027 has not been recovered so far, is anyone following up and dealing with it? @VirMach@FrankZ
Just wanted to say thank you! I've got my VM back up that was on LAXA0007.
I know it isn't a priority, and you are busy with many other things; With QPS in the loop will we be possibly getting IPv6?
There’s a bullet point somewhere mentioning IPv6 and Los Angeles.
@FrankZ said:
It still makes me chuckle when people tag me along with VirMach for a service related issue.
You guys should know that I do not, and never have, worked for VirMach.
I am just a long time customer.
@geo said:
Damn. LAXA019 was online for a while then offline.
Looks like I'll be waiting along with you on LAXA019.
This one needed to be physically unplugged and plugged back in, no idea why. Probably related to BMC/IPMI on these boards and particular scenarios where everything randomly breaks.
LAXA006 similar issue but needed BIOS configurations set again (but unrelated to CMOS battery or anything like that, just a feature.) Still not 100% sure.
LAXA014, LAXA015, LAXA016 related to SolusVM bug and abuse (IP stealing, probably unintentional.)
141.11.95.0/24 mentioned earlier related to me being dumb and missing a few blocks on initial announcement request (I copied the same row twice on a spreadsheet, skill/hand-eye coordination issue.)
Hi, I see "LAX1Z013 - Complete" in February 26th's Network Status page, not metioned in February 27th's though. Does it mean the service is back to normal? Mine is not. It went back online at about 05:30 (UTC +8), then turned to unpingable at about 13:57 (UTC +8). It can be accessible via VNC, but can't connect to the internet.
I tried Troubleshooter, it shows :
Main IP pings: false
Node Online: true
Service online: online
Operating System:
Service Status:Active
Registration Date:2021-09-23
Then I tried "Reconfigure Networking", it shows:
An Error Occurred!
Networking could not be reconfigured. Unknown operating system
@dudu said: Hi, I see "LAX1Z013 - Complete" in February 26th's Network Status page, not metioned in February 27th's
May be delayed.
Affecting System - LAXA028,LAX1Z013,LAXA005,LAXA011,LAXA024,LAXA031,LAX1Z019
02/27/2025 01:20 Last Updated 02/27/2025 10:40
LATEST UPDATE — LAXA031 is being worked on
The following servers are going to have thermal paste re-applied as we've noticed higher CPU temperatures. This is unrelated to the current maintenance window but we are going to complete this necessary maintenance to avoid having to schedule another window in the future.
LAXA028 (critical) -- COMPLETE LAX1Z013 -- Delayed
LAXA005 -- Delayed
LAXA011 -- Delayed
LAXA012 -- Complete
LAXA024 -- Planned soon
LAXA031 (also NVMe thermals checked) -- Delayed
LAX1Z019 (not CPU, but NVMe thermals checked) -- Delayed
If listed as "Delayed" we may defer this until a later date.
The following servers may be brought offline to add an additional NVMe SSD, and some customers may be moved to the new NVMe (the second portion will not have any additional downtime)
LAXA022
LAX1Z015
LAXA014
LAX1Z017
P.S. LAXA019 has been online and working fine for @geo and I for the past three hours.
Thank you VirMach.
Comments
3 out of 7 came back.
4 out of 7
What is it?
Virmach Deals
@VirMach : Web hosting on lax2z017.virm.ac came back up after being down, but control panel and web mail did not. Then again, the ticket for them (#482793) has been open since 01/29/2025, so 'the good old days are back again'.
Let me know if you want me to continue addressing your concerns here or if you want it shifted back over to the ticket. I haven't closed the ticket as I usually would have if we addressed you here instead when you reference the ticket, as I wanted to read through it to make sure I didn't miss anything else.
I did see your feedback relating to communication and I hope you saw that we did better this time around in sending out the maintenance email for shared hosting services.
I do prefer the ticket system as long as it gets timely results. I only mentioned the number here because I've happened to have a number of tickets drop into a black hole. I'll wait it out, hoping the migration will make this service viable.
Yes, the email was valued. Thank-you.
mine seems down
I bench YABS 24/7/365 unless it's a leap year.
141.11.95.0/24
This prefix is not visible in the DFZ right now
We are losing millions.
No hostname left!
I'm obviously not Virmach support, but the IP block is announced now.
QuickPacket - Dedicated Servers in Ashburn, Los Angeles, Chicago
Hey @QPS
I love my new provider of my provider.
@VirMach
Just wanted to say thank you! I've got my VM back up that was on LAXA0007.
I know it isn't a priority, and you are busy with many other things; With QPS in the loop will we be possibly getting IPv6?
We're IPv6 ready at all of our locations. Beyond that, it's up to VirMach.
QuickPacket - Dedicated Servers in Ashburn, Los Angeles, Chicago
EXCELLENT
Virmach Deals
RYZE.LAX-A026.VMS is still down for meI will open a ticket
TYO-C027 has not been recovered so far, is anyone following up and dealing with it? @VirMach @FrankZ
@FrankZ @VirMach do you have update for RYZE.TYO-C033.VMS ? Because vps still offline since 20 Feb
Damn. LAXA019 was online for a while then offline.
It still makes me chuckle when people tag me along with VirMach for a service related issue.
You guys should know that I do not, and never have, worked for VirMach.
I am just a long time customer.
Looks like I'll be waiting along with you on LAXA019.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
I dealt with it by cancelling the service.
@FrankZ @VirMach
RYZE.LAX-Z0016.VMS
RYZE.LAX-A006.VMS
off
Well that's sounds good idea!
Good morning.
I'm at the beach today but there is no flan available in the hotel.
Also all my Virmach servers are online.
good day huh?
Virmach Deals
There’s a bullet point somewhere mentioning IPv6 and Los Angeles.
This one needed to be physically unplugged and plugged back in, no idea why. Probably related to BMC/IPMI on these boards and particular scenarios where everything randomly breaks.
LAXA006 similar issue but needed BIOS configurations set again (but unrelated to CMOS battery or anything like that, just a feature.) Still not 100% sure.
LAXA014, LAXA015, LAXA016 related to SolusVM bug and abuse (IP stealing, probably unintentional.)
141.11.95.0/24 mentioned earlier related to me being dumb and missing a few blocks on initial announcement request (I copied the same row twice on a spreadsheet, skill/hand-eye coordination issue.)
Monitor name: box5 VirMach LAX
Root cause: Host Is Unreachable
Incident started at: 2025-02-25 16:58:35
Resolved at: 2025-02-27 16:51:16
Duration: 47 hours and 52 minutes
Waiting SLA credits.
A refund equivalent of 1-month of service cost sounds reasonable.
$0/month
No hostname left!
Hi, I see "LAX1Z013 - Complete" in February 26th's Network Status page, not metioned in February 27th's though. Does it mean the service is back to normal? Mine is not. It went back online at about 05:30 (UTC +8), then turned to unpingable at about 13:57 (UTC +8). It can be accessible via VNC, but can't connect to the internet.
I tried Troubleshooter, it shows :
Then I tried "Reconfigure Networking", it shows:
What should I do now? Do you aware of that?
cc @VirMach
3 out of 6 is online.
May be delayed.
P.S. LAXA019 has been online and working fine for @geo and I for the past three hours.
Thank you VirMach.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
I've warned you before about posting in offer threads.
You need to take a 24 hr timeout.
Go to the movies, or maybe bake a cake.
See you tomorrow.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
The latest regarding these nodes from the status page:
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add