Lish console won't bring up login prompt (Ubuntu 14.04)
Hi there, I'm having trouble with the Lish console: it opens normally in a new window and there's a bit of normal-looking output from the server, but then it stalls out before bringing up the prompt.
The last line of output is "* Stopping System V runlevel compatibility", and then the cursor just sits and blinks on the next line.
Here's a screenshot: https://i.imgur.com/u2bWNvn.png
Any suggestions? I've searched a good bit, and haven't found anything exactly relevant to our situation. We don't have any trouble SSH'ing in to the server using our keys, it's just a matter of Lish not bringing up a prompt.
Couple of additional notes:
- We are in the process of upgrading/migrating to a new server - clearly it's not good to be still on 14.04 - but we need to do a couple things that involve the network interface config as part of our migration, and I would prefer to perform that work over Lish.
- Also, I've tried using the Lish SSH gateway (https://www.linode.com/blog/linode/lish-ssh-gateway/) and the behavior is exactly the same.
Thank you very much in advance!
3 Replies
rgerke
Linode Staff
Hey there -
As I do not have access to your Linode's internal configurations, I can't see what might be causing this issue - but I'm going to give you some suggestions based on past experiences with this error.
One thing you may want to try is booting your Linode into Rescue Mode and running a file system check. This will scan your system for any errors or corruption and attempt to fix any that it does find.
I've also found a post on Stack Exchange that addresses this on Ubuntu 14.04:
Stopping System V runlevel compatibility (Ubuntu 14.04 LTS
I can't see what kernel you're running, but we have a guide on updating your Linode's kernel if you decide you need to do so. If you're running our latest kernel, you might want to try an earlier one.
In an effort to cover all of our bases here, you might also want to check out your /etc/fstab file to make sure that the proper disks are mounted, and nothing is set in there that shouldn't be. For example, if you have a disk listed in your fstab that no longer exists, the system could hang while waiting for it to boot.
caker
Linode Staff
Hello,
It sounds like you need a getty listening on ttyS0. Usually this is done via /etc/inittab, you may need to uncomment a line like this one:
T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100
and then run: init q and a login prompt should appear on the console.
You may also need to add ttyS0 to /etc/securetty to allow the root user to log in from that console.
HTH,
-Chris
Thank you both! Very much appreciate those suggestions - just kinda needed some ideas for starting points/potential avenues to explore, so big thanks. I'll post back when I figure it out, but again just wanted to say thanks & hope you have a great afternoon there!