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.
Comments
@Cam
What's this:
https://i.imgur.com/ZfsYcLs.png
That is the serial console information provided by solus vm.
I assume it is not useable for NAT VPS? No creds allow me to login here: solusvm.gullo.me
For some reason my OS takes 50MB after load even though it should be ~30Mb with this minimal setup. It is not enough memory for shadowsocks + v2ray, the latter is the offender. It would be nice to have an external console and be able to shutdown SSHD when not needed to free memory.
You can use it. Grab the credentials from soulsvn directly. The plug-in in the client area doesn’t show the IP for some reason.
Yeah okay, I'm RAM limited it seems.
Is there any way to increase RAM on current setup or best course of action is to refund and get another VPS plan/config?
You can upgrade in the client area
Thanks.
Follow-up question - is there any way to configure scale limit for the graphs on stats page? Rendered image size relatively small so it is kind hard to see at a glance the peaks.
No
@Cam
What's this:
https://i.imgur.com/ctJnLWA.png
It happens fairly often (the graph does not show all the cases) and VPS becomes completely unreachable for a few minutes, both SSH and from any of the control panels (https://hosting.gullo.me also dies)
My container on CA-VZ3 has similar gaps in SolusVM, but I didn't notice it becoming unreachable.
I have long-standing SSH sessions into this container, and they keep connected for weeks or months.
For you this is something different, then. I started noticing these prolong "blackouts" immediately after VPS was set up and these gaps line up in time when the monitoring software happens to take snapshot during this issue. At first I thought it was due to Go-based application, when GC is too busy and it "stops the world" to clean up memory, but I quickly wrote it off as ridiculous because we are talking about just 50-60 MB here and it would take a few milliseconds at best (besides other factors like whole VPS dies).
The moment when blackout hits I no longer can access the VPS by any means. In fact, it does not even respond to TCP SYN.
https://hosting.gullo.me/client/services/manage/ becomes inaccessible too.
https://solusvm.gullo.me/ loads but it shows irrelevant data.
Since I'm still on 128MB vps it is a bit hard to setup diagnostics/monitoring tools to collect data, but if it will be necessary to solve the issue I can do it.
I’m not too sure how those graphs are configured. They’re from SolusVM. Your better off setting up your own monitor or logs.
Well, yeah, figures.
I've checked the system logs - VPS uptime is 2+ days. My service also never was killed or restarted.
Another blackout happened just a hour/two back and during that I've tested network connectivity:
1. I can ICMP-ping the public IP of the node
2. I can send TCP SYN on 22 port on public IP of the mode and receive response
3. However, trying to tcp-ping the opened (and used by my service) port dedicated to my VPS results in failure by timeout. Attempt to open
https://hosting.gullo.me/client/services/manage/****/tabClientStats/also dies by timeout.Hypervisor issues maybe?
I haven’t seen any issues recently. I get notifications any time a hypervisor disconnects from the master. What node is it? I’ll check the load.
20510 (NAT IPv4 128MB PL)
Loads are normal.
This is odd. Just had one right now, ~1:30,
https://hosting.gullo.me/client/services/manage/wasnt responding but sending TCP SYN to hosting.gullo.me:443 worked just fine.I dont think it is my ISP either, never seen such behaviour, usually it just outright blocks resources without any second chance. Will try to get trace next time.
@Cam Checked NAT 128M VPS config page, hard-disk size is not the same.
For example: Chicago shows 3G. In fact, it's 2G.
Checked other location, some shows 2G, some shows 3G....Please confirm whether it's consistent.
They have been lowered to 2GB now that they are SSD. This is an old post.
Got it. Thx.
The same problem occurred in the French node. At present, vps is offline and cannot be used.
Will lvz instance upgraded to ssd ?
Your server is as powered down for abuse. I responded to your ticket. Totally separate from this.
Not likely with the upcoming OVH costs.
@Cam
Are Debian 10/11 not actually supported despite being in the list of possible OS choices? It is named as
OpenVZ EZso I have assumed it is cut down to run on 128/2GB machines but no matter what I do it just wont install any of them.Same node: 20510 (NAT IPv4 128MB PL)
EZ is just the new template format for OpenVZ. They should work with no issues.
@Cam
Well they dont, all my logs says it was reinstalled but it wasnt, I still have my old OS running. Can you do it from your side?
Yeah I can try from my end. I may have to re-create your server. Open a ticket for me.
@cam done
German's has been out of stock all the time