Console in LXC not available

[adminms]

When attempting to access the Console in LXC's, the console option is empty and non-responsive to entries. How do I correct this?

 

[fba]

In the options of the container there are three entries related to the console:
/dev/console set to enabled
TTY count set to 2
Console mode set to tty
If settings are different, reset them to these values.

 

[adminms]

In the options of the container there are three entries related to the console:
/dev/console set to enabled
TTY count set to 2
Console mode set to tty
If settings are different, reset them to these values.

 

[fba]

Is this the only container with this issue?
Can you enter the container via shell with pct enter 108?

 

[adminms]

Is this the only container with this issue?
Can you enter the container via shell with pct enter 108?

This is a new container I'm attempting to deploy but stuck with no Console. The other working containers have functioning Consoles until I access any other option, then the Console becomes inoperable with them as well.

 

[fba]

if you enter the container successfully, you have full access and can run any command.
For testing if just the webconsole has an issue, you can try pct console 108. This opens same console like in webGUI. (Exit via ctrl+a q)

 

[adminms]

if you enter the container successfully, you have full access and can run any command.
For testing if just the webconsole has an issue, you can try pct console 108. This opens same console like in webGUI. (Exit via ctrl+a q)

Any idea why Console itself can’t be reached?

 

[Impact]

I'd try to start the CT with debugging enabled to see what's going on.

pct shutdown 108
lxc-start -n 108 -F -l DEBUG

See here for more.
Please also share the output of pct config 108 --current.

 

[adminms]

I'd try to start the CT with debugging enabled to see what's going on.

pct shutdown 108
lxc-start -n 108-F -l DEBUG

See here for more.
Please also share the output of pct config 108 --current.

results of running these

 

[adminms]

results of running these

 

[Impact]

Sorry, I missed a space. I edited above. Try now. Please don't full quote messages you are directly responding to. Also try to disable DHCPv6.

 

[adminms]

Sorry, I missed a space. I edited above. Try now. Please don't full quote messages you are directly responding to. Also try to disable DHCPv6.

 

[adminms]

Not sure what you mean by “don’t quote…….sorry, new to this

 

[Impact]

You are including my whole message inside yours. It's redundant as my message is directly anove already and inhibits the usefulness of editing my posts to fix mistakes like this. Stupid reply button. Anyways please check my initial message #8. I edited the command to include the space between 108 and-F. Also see the docs I linked there which show the proper syntax.

 

[adminms]

from commands in #8

 

[Impact]

The uninitilized value issue should probably be looked at first. I guess you could try to stop the CT manually via the GUI. I'd also disable HA for now while testing.
The DHCPv6 setting I mentioned earlier can often cause hangs like this in the console. At least initially. Have you tried disabling it like this?

 

[adminms]

IPv6 is disabled. I have stopped, shutdown, rebooted, and restarted the container multiple times.
I have had several LXC's and a couple of VM working for some time and have not had this issue with those. However, now, none of the
Containers have working Consoles. If I reboot, a couple of them will allow me to login but then the console quits.
Just to be transparent, I love this stuff but I'm 77 years old and this is all new stuff to me.
Sorry, what is HA?

 

[Impact]

High Availability. This Requesting HA stop for CT 108 message should only occur if HA is configured for the guest.

 

[adminms]