Debian 9 Container, sometimes no prompt after logging out.

[David Payne]

Hi,

I'm testing the Debian 9 container:

debian-9.0-standard_9.7-1_amd64.tar.gz

I'm having an issue with the console in the Proxmox UI. Sometimes, after logging out of the console, I am unable to log back in again. Here is the first screenshot where I logged out:


If I close the window and open the console again, I get an empty console with just the cursor:



If I have ssh configured I don't have any problem accessing the container via ssh.

Does anyone know how to solve this problem?

Thanks,

David

 

[LnxBil]

Does anyone know how to solve this problem?

Normally the console returns if you press enter. Have you tried this?

 

[David Payne]

Normally the console returns if you press enter. Have you tried this?

Yes, I have tried this. If I press, enter, or any other keys the input shows up in the console, but it does not prompt me for the username or password.

 

[guletz]

Yes, I have tried this. If I press, enter, or any other keys the input shows up in the console, but it does not prompt me for the username or password.

I can also confirm this behavior as David said!

 

[Chris]

Do you have some ~/.bash_logout scripts? Any error in the syslog?

 

[guletz]

Hi @Chris

Do you have some ~/.bash_logout scripts?

No. When I will see first time this error, I will post the error if will be something relevant in the logs!(I have try now with 6 CT, and this error was not happend)

Thx.

 

[LnxBil]

Is there still the getty process claiming the virtual terminals present? You can list them via

$ ps auxf | grep 1000 -A10

To show container 1000 and its processes but limited to 10 processes

 

[David Payne]

Do you have some ~/.bash_logout scripts? Any error in the syslog?

I didn't add anything to the ~/.bash_logout script that didn't come with the container. I'm only testing. For this container I started it up, logged in and out a few times from the console without doing anything (this worked fine). I then logged in, done an apt-get update/apt-get upgrade. When the upgrade was complete, I tried to log out and the issue occurred.

I was able to reproduce this multiple times. It doesn't happen on every logout, but eventually it does.

 

[dihedral]

I get the following errors in auth.log after logging out with the same symptoms:

agetty[17334]: /dev/pts/1: cannot get controlling tty: Operation not permitted
agetty[17334]: /dev/pts/1: cannot get controlling tty: Operation not permitted
agetty[17334]: /dev/pts/1: cannot set process group: Inappropriate ioctl for device

I can reach the container with lxc-attach, but cannot use xterm,js or any of the other offers in the gui.
It takes a restart of the container to get rid of the issue - until the next logout.
However in some cases this issue does not occur.

 

[Richard Peters]

I have the same issue. The only solution so far is to restart the container.

 

[rolandmade]

Had the same issue on some of our containers.
Found a possible workaround in debian bug archive https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1723520.html
inside the container touch /dev/tty0 and then restart getty service systemctl restart getty@tty1.service
Seems to work for my containers.