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.
Takes minutes to login to HostCram
It takes anywhere from 1-10 minutes to login to my HostCram node. Does anyone else have this issue or have any idea how to fix it?
This happens with a fresh image and it happens both through SSH and VNC. When connecting via SSH, the delay occurs at this point in the process:
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Requesting [email protected]
debug1: Entering interactive session.
debug1: pledge: filesystem full
~~~~~~~~~~~~~~~~~
30-180 second delay
~~~~~~~~~~~~~~~~~
debug1: client_input_global_request: rtype [email protected] want_reply 0
I tried checking the usual suspects like bash_history and bashrc, but these files are fine. The delay happens both for root and my user. It hangs with password auth as well as with keys.
When I first login after a while, it always takes 10 minutes. If I exit and then login again, it usually takes less, but always at least a minute.
Comments
LXC? I just mask the systemd-logind
@Shakib
Me too, I also get "Uh oh! We can't reach your node. " from Dash Board.
Yes, it's LXC. Is this normal for LXC?
Thanks! I'll give this a try.
Looking into that.
I now have this as well and cannot connect at all. I thought I was just waiting the 10 minutes, but it timed out fully this time.
No idea since I only have 1 active VPS with LXC today. But it worked for Hazi.ro's LXC.
systemctl mask systemd-logindPlease do a recheck.
If there is still any issues i will try my best to help you out.
Panel is fixed!
This did the trick. Login is fast now!
Did you ever raise a ticket?
Any idea what this command does and does it have any impact?
Yes, but was told to figure it out for myself. This is one of those $7/yr BF deals. So, it's already losing money without support.
Sorry. My bad. Had too much work at that time.
My deal LXC-4G has some troubles yesterday, after I contacted @Shakib , everything seems sorted.
Fair play, shit happens. Taking accountability is to be respected.
It's ok. Hopefully, now if someone else has this same issue, they can find the solution here instead of having to make a ticket. It's annoying to have to deal with tickets from each "half the cost of an IP" service.
To prevent systemd-logind being started?
There is some issues mentioned on this page
I haven't checked those, but so far no issue for me.
It seems that this is necessary if nesting is disabled on the host.
Provider now needs to teach clients system administration with the VPS/dedi package? Nice.
My LXC-4G feels like going down hill now.
The performance is not as usual. Maybe there are a lot of abuser now.
Everyone YABs'ing like motherfuckers.
Oh my, I'm adding the load on the server too. Haha..
This issue is on one node only. The one we put $4/three months clients in.
We are not limiting anything from our end. I know it's getting abused a bit, some people using very high network I/O and causing I/O delay for the hostnode.
Many of those VPS will expire soon therefore suspending them now will cause more trouble than it's worth.
The leftover Disk and Network for this node is sufficient for any real world use, CPU performance shouldn't be an issue as well.
You can submit an ticket to migrate on another node so you can get the full disk speed.
Edit: Automated backups are running on this node now.