New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More
This discussion has been closed.
Comments
Invoice 1396995,Tokyo, can I set it today?
No. Next batch on Tuesday if everything goes good with shipping.
I have some similar issue:
Debian 11
Node:TYOC039
I have been using the vps around one week. Everything is going smooth recently, but everyday the system will shutdown automatically at a random time, I have to boot it again manually through the panel, and everything back to happy again.
Not sure if the system is still in test version, or only me. Anyway looks like we are 2 now.
TYOC039 + Ryzen Special 384 + Almalinux Template
(edit) Some of the errors may be due to less RAM and may not result on machines with more RAM.
I install debian10 by mount iso boot.xyz and connect through VNC.
Node39 - Installed Alma8 Template, then installed from Centos7 Server ISO with default disk setup. Changing disk from LVM to regular partitions caused crashes during install or kernel panic after install. Disk and network look good.
Me too......
After the server was activated, I tested it, and the problems I found are as follows:
1. Irregular automatic shutdown. The VPS found several (at least four) automatic shutdowns, most of which occurred without any action, and once suddenly interrupted while executing the “apt upgrade” command.
After this problem occurred, I checked the “/var/log/messages.1” file and used the “cat messages.1 | grep error” command to check the error message, the prompt is as follows:
root@jp:/var/log# cat messages.1 | grep error
Dec 28 22:52:07 debiantemplate kernel: [ 2.926642] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
Apr 2 01:23:23 jp kernel: [ 1.177559] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
Apr 2 01:28:58 jp kernel: [ 1.438291] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
Apr 2 01:37:06 jp kernel: [ 1.191632] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
Apr 2 02:00:08 jp kernel: [ 1.323795] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
Apr 2 15:49:19 jp kernel: [ 0.950615] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
Apr 2 21:41:05 jp kernel: [ 1.069917] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
2. The server cannot be restarted using the "reboot" command. I tested it twice and each time it failed to reboot, only rebooted in the control panel.
3. The network connection is unstable. The normal ping response time is about 60ms, and it often happens that the ping response time suddenly jumps to more than 200ms and there is packet loss. Since I'm from China, this might be due to GFW.
Due to poor English, the above text is translated by google translate. The problems found above are for reference.
would someone give a download link so we can check the speed?
Templates updated, let me know if it's better or worse.
I'm on the node TYO-C040. I could install Debian 10 ISO and upgrade to 11 just fine. Network speed outside of Japan isn't looking great currently though.
This is not important, but...
Linux Almalinux 8 X86 64 Gen2 V1
hello
I bought two machines at virmach. #1397158 was supposed to be in Tokyo, but it actually started in San Jose. I applied for #1405380STORAGE-500G to move to Tokyo eight days ago, but no one has responded so far. So, #1405380 apply for a refund. thanks
People are basically doing a constant 400Mbps to 1Gbps in network tests it seems at any given moment (and I/O.)
beta tester
Looks the disk is gone again and VPS offline (try to reinstall from templates listed did not help)
VPS ID: 652588
Invoice #1397292 (In case the above ID not helped ) . thanks
Disk is fine on our end. Try powerdown, wait a little bit, and install.
thanks,
tried shutdown. power on, reinstall but the VPS continuously showing Offline status.
Edit: update here, not sure if anything was done but when i remove the ubuntu iso ( routed before) and mount with netboot.xyz and reboot , it did help to boot up the VPS and i see the last reinstall from template (debian 10) works , will see if everything is going well.
非常蛋疼,一下跳到100到800的ping,我终端cpu表示反应不过来,速度看480p应该没有问题😄
Invoice #1398549,Tokyo,can I set it Tuesday?
@VirMach
@VirMach Just confirming, are all the new Ryzen nodes on 1GBPS uplinks in all locations? The 10G burst might be the only thing I'll miss from the CC nodes.
Invoice #503758,Tokyo,can I set it Tuesday?
@VirMach
Hello,May i join the test? My Invoice is 1400458. Thank you!
我这里河北联通,出口走上海联通,正常的情况下非常好,ping值在60ms左右,但经常性跳到200多ms且有丢包,等一会可能就好了,而且不能怪virmach,很可能是GFW的原因。但无任何规律的自动关机太折腾了……
ps.如果你有hostloc的账号的话,邀请我一下……没人邀请不能注册……
Have you tried to re-install Debian 11? I'm going to quote what the boss said "Disk is fine on our end. Try powerdown, wait a little bit, and install." you can try it.
I've been able to install Debian 11 from netboot.xyz ISO multiple times without issue on Node39.
First I installed the Alma8 template from billing panel, then installed Debian 11 from the netboot.xyz ISO in SolusVM panel.
For those of you mentioning packet loss and high ping times from China, this may be because you are in China and there may not be anything VirMach can do about this. Below is a graph of the dns request times every two minutes for the last 10 hours from Sydney AU, San Jose CA, Seacaucus NJ (NYC), and Sofia BG to my VPS on Node39. As you can see the response times are very consistent and without any failures.
Larger image: https://i.postimg.cc/W1mx00Fx/Screenshot-2022-04-03-at-10-15-14.png
until when is the beta testing?
The I/O and network speed in the Node39 are better than Node40.
Well said! The vm on Node40 is still drowning in the sea of panicking. Let me see what else I could do with it.
Looks like this is not normal, or maybe Everyone's benchmarking
Please test Node40. Why the same configuration Node40 is much worse than Node39!For example, I/O and network speed.Thanks
It's the same uplink and transfer providers for Node 39 as Node 40, so as soon as everybody settles down the network should be more or less the same.
Regarding I/O everybody is thrashing the disks on Node 40 right now and it is a beta test so if the I/O is bad after things settle down I am sure VirMach will make adjustment/improvments.
Node 39 is better because 50 people have been on it for days already, and Node 40 had everyone put on it less then 24 hours ago.
Just give things a little time.