@VirMach FFME006 giving timeout errors in CP.
History of this server is really poor (All UK times)
Service migrated with data from Amsterdam AMSKVM6 to Frankfurt FFME006 and worked on 29/6/22
30/6/22 FFME006 server went offline with Booting from hard disk - boot failed.
8/7/22 Managed to re-install Ubuntu 20.04 Ryzen
25/7/22 Failed - timeout accessing panel recovered 26/7/22 @ 7:35
27/7/22 Failed @ 10:52 recovered 29/7/22 ~ 01:00
6/8/22 Failed @ 06:24:02 recovered 11:31 (uptime not reset - so likely network problem) up 8 days
11/8/22 Failed @ 07:25:01
@msatt said: @VirMach FFME006 giving timeout errors in CP.
History of this server is really poor (All UK times)
Service migrated with data from Amsterdam AMSKVM6 to Frankfurt FFME006 and worked on 29/6/22
30/6/22 FFME006 server went offline with Booting from hard disk - boot failed.
8/7/22 Managed to re-install Ubuntu 20.04 Ryzen
25/7/22 Failed - timeout accessing panel recovered 26/7/22 @ 7:35
27/7/22 Failed @ 10:52 recovered 29/7/22 ~ 01:00
6/8/22 Failed @ 06:24:02 recovered 11:31 (uptime not reset - so likely network problem) up 8 days
11/8/22 Failed @ 07:25:01
My VPS at FFME006 has been good, last problem in my monitoring (1m periods) is 27/7/22
Current hostnode is timing out in CP but VPS is working fine with uptime of 23days
@atomi said:
My VPS at FFME006 has been good, last problem in my monitoring (1m periods) is 27/7/22
Current hostnode is timing out in CP but VPS is working fine with uptime of 23days
The VM sends a heartbeat (MQTT) message every 2 minutes and after 6 minutes I get a report.
I try to ssh in and get no response so then use CP which gives a timeout error trying to access the VM - so can't check VNC. Other VMs (on different nodes are fine).
So either my VM is being 'chosen' or something else is happening..... (not trying to be rude) :-)
Edit - just had a thought - perhaps this is some dhcp timeout?
@msatt said: Edit - just had a thought - perhaps this is some dhcp timeout?
Could also be someone hijacking your IP. I had similar intermittent connectivity issues with a different provider in the past and found out my IP was doubly assigned.
@Mason said: Could also be someone hijacking your IP. I had similar intermittent connectivity issues with a different provider in the past and found out my IP was doubly assigned.
Good point although pinging does not give a response (at all) - I have seen a 'flipping' ip which switches between one machine and another with same ip.
Also (but may not be related) the CP gives the standard -
Operation Timed Out After 90001 Milliseconds With 0 Bytes Received
Not openeing tickets as I am sure @VirMach will be aware.....
@atomi said:
My VPS at FFME006 has been good, last problem in my monitoring (1m periods) is 27/7/22
Current hostnode is timing out in CP but VPS is working fine with uptime of 23days
The VM sends a heartbeat (MQTT) message every 2 minutes and after 6 minutes I get a report.
I try to ssh in and get no response so then use CP which gives a timeout error trying to access the VM - so can't check VNC. Other VMs (on different nodes are fine).
So either my VM is being 'chosen' or something else is happening..... (not trying to be rude) :-)
Edit - just had a thought - perhaps this is some dhcp timeout?
@reb0rn said:
From 14 VPS one is offline in LA node timeout (control panel) I am not sure on which one it was, rest work, one PHXZ001 is slow net/performance
Ah, welcome my fellow LAX neighbour, welcome to the "it worked great til it exploded" neighbourhood
@msatt said: @VirMach FFME006 giving timeout errors in CP.
History of this server is really poor (All UK times)
Service migrated with data from Amsterdam AMSKVM6 to Frankfurt FFME006 and worked on 29/6/22
30/6/22 FFME006 server went offline with Booting from hard disk - boot failed.
8/7/22 Managed to re-install Ubuntu 20.04 Ryzen
25/7/22 Failed - timeout accessing panel recovered 26/7/22 @ 7:35
27/7/22 Failed @ 10:52 recovered 29/7/22 ~ 01:00
6/8/22 Failed @ 06:24:02 recovered 11:31 (uptime not reset - so likely network problem) up 8 days
11/8/22 Failed @ 07:25:01
Happened to my VPS in FFME006 as well. All the timings are similar too 😂
@kheng86@atomi
FFME006 back online.
Service migrated with data from Amsterdam AMSKVM6 to Frankfurt FFME006 and worked on 29/6/22
30/6/22 FFME006 server went offline with Booting from hard disk - boot failed.
8/7/22 Managed to re-install Ubuntu 20.04 Ryzen
25/7/22 Failed - timeout accessing panel recovered 26/7/22 @ 7:35
27/7/22 Failed @ 10:52 recovered 29/7/22 ~ 01:00
6/8/22 Failed @ 06:24:02 recovered 11:31 (uptime not reset - so likely network problem) up 8 days
11/8/22 Failed @ 07:25:01 timeout accessing panel - recovered 12/8/22 @ 12:02
Looking for guidance on how to report/track outstanding problems that I think likely require some actual support from VirMach. I've had dozens of dozens migrated successfully, but I have at least the following outstanding problems:
A system (on RYZE.ATL-Z005.VMS) was successfully migrated, but is missing two additional IPv4 addresses that were part of the original plan.
A system (on RYZE.NYC-B018.VMS) was migrated, but network layer reachability is very spotty and practically unusable, maybe a duplicate IPv4 address issue?
A BF system (was on LA10GKVM14) has been unavailable since June 23, not even sure if this was migration related.
I have a "[MERGED]" priority ticket (#298500) open that includes a note about a NY dedicated server (per a request I saw in an earlier forum message) and a few "Your service's IP address w.x.y.z has been blacklisted [...]" tickets VirMach initially opened for some migrated systems. Maybe I should add details of the above issues to that ticket?
@jtk said: ..is missing two additional IPv4 addresses..
I have the same situation on a different node (it was auto migrated Buffalo->NYC). The answer(s) from Virmach haven't been encouraging at all and there's a distinct possibility that they won't be reinstated.
[RYZE.ATL-Z007.VMS appears to be as dead as a can o' Spam, for about a week.]
@jtk said: ..is missing two additional IPv4 addresses..
I have the same situation on a different node (it was auto migrated Buffalo->NYC). The answer(s) from Virmach haven't been encouraging at all and there's a distinct possibility that they won't be reinstated.
[RYZE.ATL-Z007.VMS appears to be as dead as a can o' Spam, for about a week.]
Bummer as I had enjoyed servers with additional IPs. Had open ticket on this as well as replacement server from the CC Dedicated server fiasco. was merged into one and closed earlier today only to instruct with open new ticket with "Dedicated Server Migration" in title and my preference for the new server. So lets see when the replacement server would be deployed.
@AlwaysSkint said:
[RYZE.ATL-Z007.VMS appears to be as dead as a can o' Spam, for about a week.]
I'm also affected by this unfortunately.
On the plus side, the freemach dedi was delivered. However, it has centos loaded and their dedi control panel isn't working, so will have to wait until they get that fixed that so I can install proxmox and all that fun stuff.
Dunno if you load from ISO, or as I prefer, boot debian and per-configure partitions etc. Boot debian from CentOS - a piss about but possible?
I usually just use proxmox ISO because I'm a basic bitch. Don't think I'd ever trust proxmox on top of Debian on top of centos or whatever would be involved in that :P
They're tracking the dedicated server control issue in their status announcements. Something broken with the modulesgarden plugin it seems.
Dunno if you load from ISO, or as I prefer, boot debian and per-configure partitions etc. Boot debian from CentOS - a piss about but possible?
I usually just use proxmox ISO because I'm a basic bitch. Don't think I'd ever trust proxmox on top of Debian on top of centos or whatever would be involved in that :P
They're tracking the dedicated server control issue in their status announcements. Something broken with the modulesgarden plugin it seems.
I usually prefer using Debian 11, allocating all space to root, and then installing Proxmox on top. It's much easier than dealing with ZFS (only option via Proxmox ISO for RAID) or the weird partitioning Proxmox does
@AlwaysSkint said: Debian would replace CentOS completely in what I suggested above
Got it! Though, I am a bit hesitant to try anything without some sort of console redirection or power controls at the very least.
@Advin said: I usually prefer using Debian 11, allocating all space to root, and then installing Proxmox on top. It's much easier than dealing with ZFS (only option via Proxmox ISO for RAID) or the weird partitioning Proxmox does
Yeah, I'll probably take that route this time around. Didn't have much experience under my belt when first setting the server up years ago so I kept things simple.
A BF system (was on LA10GKVM14) has been unavailable since June 23, not even sure if this was migration related.
I had VPS also in that node and asked earlier in this thread from @VirMach. Its gone because of PSU failure and they are regenerating servers at some point. I guess all we can do is wait
Comments
Right back at ya!
AMD Ryzen 9 3950X on both nodes.
(some) Frankfurt nodes have 5950x iirc from OGF posts.
@VirMach FFME006 giving timeout errors in CP.
History of this server is really poor (All UK times)
Service migrated with data from Amsterdam AMSKVM6 to Frankfurt FFME006 and worked on 29/6/22
30/6/22 FFME006 server went offline with Booting from hard disk - boot failed.
8/7/22 Managed to re-install Ubuntu 20.04 Ryzen
25/7/22 Failed - timeout accessing panel recovered 26/7/22 @ 7:35
27/7/22 Failed @ 10:52 recovered 29/7/22 ~ 01:00
6/8/22 Failed @ 06:24:02 recovered 11:31 (uptime not reset - so likely network problem) up 8 days
11/8/22 Failed @ 07:25:01
My VPS at FFME006 has been good, last problem in my monitoring (1m periods) is 27/7/22
Current hostnode is timing out in CP but VPS is working fine with uptime of 23days
The VM sends a heartbeat (MQTT) message every 2 minutes and after 6 minutes I get a report.
I try to ssh in and get no response so then use CP which gives a timeout error trying to access the VM - so can't check VNC. Other VMs (on different nodes are fine).
So either my VM is being 'chosen' or something else is happening..... (not trying to be rude) :-)
Edit - just had a thought - perhaps this is some dhcp timeout?
Could also be someone hijacking your IP. I had similar intermittent connectivity issues with a different provider in the past and found out my IP was doubly assigned.
Humble janitor of LES
Proud papa of YABS
Good point although pinging does not give a response (at all) - I have seen a 'flipping' ip which switches between one machine and another with same ip.
Also (but may not be related) the CP gives the standard -
Operation Timed Out After 90001 Milliseconds With 0 Bytes Received
Not openeing tickets as I am sure @VirMach will be aware.....
Now also my VPS went offline
From 14 VPS one is offline in LA node timeout (control panel) I am not sure on which one it was, rest work, one PHXZ001 is slow net/performance
Ah, welcome my fellow LAX neighbour, welcome to the "it worked great til it exploded" neighbourhood
I want it online anywhere in US. I will wait patiently, it's free stuff anyway.
Happened to my VPS in FFME006 as well. All the timings are similar too 😂
GreenCloudVPS: Cheap Asia/EU VPS starting from $20/yr!!! (aff) Webhosting24: Ryzen 9 VPS SG/DE/JP at €1.25/mo (aff)
@kheng86 @atomi
FFME006 back online.
Service migrated with data from Amsterdam AMSKVM6 to Frankfurt FFME006 and worked on 29/6/22
30/6/22 FFME006 server went offline with Booting from hard disk - boot failed.
8/7/22 Managed to re-install Ubuntu 20.04 Ryzen
25/7/22 Failed - timeout accessing panel recovered 26/7/22 @ 7:35
27/7/22 Failed @ 10:52 recovered 29/7/22 ~ 01:00
6/8/22 Failed @ 06:24:02 recovered 11:31 (uptime not reset - so likely network problem) up 8 days
11/8/22 Failed @ 07:25:01 timeout accessing panel - recovered 12/8/22 @ 12:02
I just had to reconfigure network with the new IP.
It took me around an hour. Fucking VNC, keyboard layout and YAML files. Fucking Ubuntu.
Looking for guidance on how to report/track outstanding problems that I think likely require some actual support from VirMach. I've had dozens of dozens migrated successfully, but I have at least the following outstanding problems:
I have a "[MERGED]" priority ticket (#298500) open that includes a note about a NY dedicated server (per a request I saw in an earlier forum message) and a few "Your service's IP address w.x.y.z has been blacklisted [...]" tickets VirMach initially opened for some migrated systems. Maybe I should add details of the above issues to that ticket?
Dataplane.org's current server hosting provider list
I have the same situation on a different node (it was auto migrated Buffalo->NYC). The answer(s) from Virmach haven't been encouraging at all and there's a distinct possibility that they won't be reinstated.
[RYZE.ATL-Z007.VMS appears to be as dead as a can o' Spam, for about a week.]
lowendinfo.com had no interest.
Bummer as I had enjoyed servers with additional IPs. Had open ticket on this as well as replacement server from the CC Dedicated server fiasco. was merged into one and closed earlier today only to instruct with open new ticket with "Dedicated Server Migration" in title and my preference for the new server. So lets see when the replacement server would be deployed.
Interesting; poor Virmach is still working through dedis - that'll be hampering progress elsewhere.
(I do hope that additional IPs will materialise - one can but hope.)
lowendinfo.com had no interest.
I'm also affected by this unfortunately.
On the plus side, the freemach dedi was delivered. However, it has centos loaded and their dedi control panel isn't working, so will have to wait until they get that fixed that so I can install proxmox and all that fun stuff.
Humble janitor of LES
Proud papa of YABS
Dunno if you load from ISO, or as I prefer, boot debian and per-configure partitions etc. Boot debian from CentOS - a piss about but possible?
lowendinfo.com had no interest.
I usually just use proxmox ISO because I'm a basic bitch. Don't think I'd ever trust proxmox on top of Debian on top of centos or whatever would be involved in that :P
They're tracking the dedicated server control issue in their status announcements. Something broken with the modulesgarden plugin it seems.
Humble janitor of LES
Proud papa of YABS
That's what I done the 1st time and regretted it due to the disc layout. Subsequently, I boot debian, then add Proxmox.
(Debian would replace CentOS completely in what I suggested above.)
lowendinfo.com had no interest.
Now some good news, for a change..
My titchy Dallas VPS is alive again! Yay! From the mod that gave us YABS.
Fri 12 Aug 2022 08:28:30 PM EDT
Basic System Information:
Uptime : 0 days, 0 hours, 0 minutes
Processor : AMD Ryzen 9 5900X 12-Core Processor
CPU cores : 1 @ 3693.060 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 231.2 MiB
Swap : 256.0 MiB
Disk : 9.6 GiB
Distro : Debian GNU/Linux 10 (buster)
Kernel : 4.19.0-21-amd64
fio Disk Speed Tests (Mixed R/W 50/50):
iperf3 Network Speed Tests (IPv4):
Provider | Location (Link) | Send Speed | Recv Speed
| | |
Clouvider | London, UK (10G) | 609 Mbits/sec | 192 Mbits/sec
Online.net | Paris, FR (10G) | 637 Mbits/sec | 214 Mbits/sec
Hybula | The Netherlands (40G) | 577 Mbits/sec | 412 Mbits/sec
Uztelecom | Tashkent, UZ (10G) | 357 Mbits/sec | 179 Mbits/sec
Clouvider | NYC, NY, US (10G) | 907 Mbits/sec | 571 Mbits/sec
Clouvider | Dallas, TX, US (10G) | 936 Mbits/sec | busy
Clouvider | Los Angeles, CA, US (10G) | 921 Mbits/sec | 598 Mbits/sec
Thanks @Virmach !
lowendinfo.com had no interest.
I usually prefer using Debian 11, allocating all space to root, and then installing Proxmox on top. It's much easier than dealing with ZFS (only option via Proxmox ISO for RAID) or the weird partitioning Proxmox does
debian 11 ftw
I bench YABS 24/7/365 unless it's a leap year.
Got it!
Though, I am a bit hesitant to try anything without some sort of console redirection or power controls at the very least.
Yeah, I'll probably take that route this time around. Didn't have much experience under my belt when first setting the server up years ago so I kept things simple.
Humble janitor of LES
Proud papa of YABS
I had VPS also in that node and asked earlier in this thread from @VirMach. Its gone because of PSU failure and they are regenerating servers at some point. I guess all we can do is wait
Yeah I think there is a SJC server in the same condition.
Looks like ryzen migrate button is available again on my service. I tried to use it for 2nd time (LAX to JP), but not working.
So i tried to use paid migrate (without data $3) button, and my BF vps finally online on Tokyo, JP
⭐⭐⭐⭐⭐ virmach for this feature
very lucky.
on my side, even paid migration was not automated (#596130 since 26/07/2022).
why it's so hard to move from this problematic node (LAXA014), even LA to LA doesn't work.