Proxmox 7 - LXC SSH Root login not working

lps90

Member
May 21, 2020
168
6
23
Hello

I installed Proxmox 7 and created a LXC container with Debian 10.7.
I edited the sshd_config so i can connect with root user and restarted ssh service.
SSH is working and i can connect as root.
If i restart the container i can not connect with root user anymore.
I need to use "service ssh restart" command everytime i restart my lxc container so i can login with root.

Why is this happening with Proxmox 7?
(in my Proxmox 6.4 with the same configuration it is working like a charm, no problems at all... but Proxmox 7 seems to be full of problems, including this one...)

If someone can help me, i'll be grateful.
thanks
 

lps90

Member
May 21, 2020
168
6
23
Anyone can help?
I already reinstalled Proxmox 7 but this seems to be a general problem and it is still happening the same.
 

gouthamravee

Member
May 16, 2019
20
5
8
How did you create a LXC with Debian 10? Afaik LXC uses the underlying OS, so that should be Debian 11.
The create container dialog doesn't even give you an OS option like the create VM option.

When you create a LXC it gives you the option at the beginning to upload a ssh public key file.
 

leesteken

Famous Member
May 31, 2020
1,519
297
88
I believe Debian disables root ssh login by default. Yuu can use pct enter $VMID from the Proxmox host console to enter the LXC as root and change the /etc/ssh/sshd_config to allow root login.
 

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
5,005
631
118
If i restart the container i can not connect with root user anymore.
I need to use "service ssh restart" command everytime i restart my lxc container so i can login with root.
can you try to enable ssh service on the container: systemctl enable ssh
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
7,476
1,393
164
you can check with pct enter XXX whether the ssh service is running after you start the container. possibly it is not enabled, and thus not started at boot? a restart will also start a not-yet-running service.
 

lps90

Member
May 21, 2020
168
6
23
How did you create a LXC with Debian 10? Afaik LXC uses the underlying OS, so that should be Debian 11.
The create container dialog doesn't even give you an OS option like the create VM option.

When you create a LXC it gives you the option at the beginning to upload a ssh public key file.

what?
I downloaded Debian 10.7 lxc image from proxmox templates and installed (like in proxmox 6).
In proxmox 6 you just need to install it, edit the ssh to allow root login and restart ssh service...
SSH root connections will always work with no problems even after restarting the container xD
 

lps90

Member
May 21, 2020
168
6
23
I believe Debian disables root ssh login by default. Yuu can use pct enter $VMID from the Proxmox host console to enter the LXC as root and change the /etc/ssh/sshd_config to allow root login.
I think you didnt read what i described with attention.
you're telling me to do what i already had done :rolleyes:
 

lps90

Member
May 21, 2020
168
6
23
can you try to enable ssh service on the container: systemctl enable ssh
It is already enabled by default.
This is only happening with proxmox 7 (proxmox 6 works with no problems exactly with the same configuration / steps).
 

lps90

Member
May 21, 2020
168
6
23
you can check with pct enter XXX whether the ssh service is running after you start the container. possibly it is not enabled, and thus not started at boot? a restart will also start a not-yet-running service.
It is enabled by default but i can not connect with root.
i alway need to access with proxmox panel console and run "service ssh restart" command so i can login with root (really stupid) :(
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
7,476
1,393
164
then check the logs inside the container - there must be something in there that indicates why you have to do those steps..
 

lps90

Member
May 21, 2020
168
6
23
I've a friend with a soyoustart dedicated machine and proxmox 7 that is facing exactly the same problem,
so seems to be a general issue.
Can you tell me the correct command to check it?
 
Last edited:

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
7,476
1,393
164
journalctl -b inside the container would be a start.
 

lps90

Member
May 21, 2020
168
6
23
Code:
root@test:~# journalctl -b
-- Logs begin at Mon 2021-08-02 14:44:55 UTC, end at Mon 2021-08-02 14:45:09 UTC. --
Aug 02 14:44:55 test systemd-journald[49]: Journal started
Aug 02 14:44:55 test systemd-journald[49]: Runtime journal (/run/log/journal/bb320c4497504bf4ad044e02a1a
Aug 02 14:44:55 test systemd[1]: Starting Flush Journal to Persistent Storage...
Aug 02 14:44:55 test mount[56]: mount: /sys/kernel/config: permission denied.
Aug 02 14:44:55 test systemd[1]: sys-kernel-config.mount: Mount process exited, code=exited, status=32/n
Aug 02 14:44:55 test systemd[1]: sys-kernel-config.mount: Failed with result 'exit-code'.
Aug 02 14:44:55 test systemd[1]: Failed to mount Kernel Configuration File System.
Aug 02 14:44:55 test systemd[1]: sys-kernel-config.mount: Consumed 1ms CPU time.
Aug 02 14:44:55 test systemd-sysctl[57]: Couldn't write '1' to 'fs/protected_hardlinks', ignoring: Permi
Aug 02 14:44:55 test systemd-sysctl[57]: Couldn't write '1' to 'fs/protected_symlinks', ignoring: Permis
Aug 02 14:44:55 test systemd[1]: Started Apply Kernel Variables.
Aug 02 14:44:55 test systemd-journald[49]: Runtime journal (/run/log/journal/bb320c4497504bf4ad044e02a1a
Aug 02 14:44:55 test systemd[1]: Started Create System Users.
Aug 02 14:44:55 test systemd[1]: Starting Create Static Device Nodes in /dev...
Aug 02 14:44:55 test systemd[1]: Started Helper to synchronize boot up for ifupdown.
Aug 02 14:44:55 test systemd-journald[49]: Forwarding to syslog missed 1 messages.
Aug 02 14:44:55 test systemd[1]: Started Flush Journal to Persistent Storage.
Aug 02 14:44:55 test systemd[1]: Started Create Static Device Nodes in /dev.
Aug 02 14:44:55 test systemd[1]: Reached target Local File Systems (Pre).
Aug 02 14:44:55 test systemd[1]: Reached target Local File Systems.
Aug 02 14:44:55 test systemd[1]: Starting Create Volatile Files and Directories...
Aug 02 14:44:55 test systemd[1]: Condition check resulted in Commit a transient machine-id on disk being
Aug 02 14:44:55 test systemd[1]: Starting Raise network interfaces...
Aug 02 14:44:55 test systemd[1]: Condition check resulted in udev Kernel Device Manager being skipped.
Aug 02 14:44:55 test systemd[1]: Starting Network Service...
Aug 02 14:44:55 test systemd[1]: Started Create Volatile Files and Directories.
Aug 02 14:44:55 test systemd[1]: Condition check resulted in Network Time Synchronization being skipped.
Aug 02 14:44:55 test systemd[1]: Reached target System Time Synchronized.
Aug 02 14:44:55 test systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Aug 02 14:44:55 test systemd[1]: Started Update UTMP about System Boot/Shutdown.
Aug 02 14:44:55 test systemd[1]: Reached target System Initialization.
Aug 02 14:44:55 test systemd[1]: Listening on OpenBSD Secure Shell server socket.
Aug 02 14:44:55 test systemd[1]: Listening on D-Bus System Message Bus Socket.
Aug 02 14:44:55 test systemd[1]: Reached target Sockets.
Aug 02 14:44:55 test systemd[1]: Reached target Basic System.
Aug 02 14:44:55 test systemd[1]: Starting System Logging Service...
Aug 02 14:44:55 test systemd[1]: Condition check resulted in getty on tty2-tty6 if dbus and logind are n
Aug 02 14:44:55 test systemd-networkd[67]: Enumeration completed
Aug 02 14:44:55 test systemd[1]: Started Regular background program processing daemon.
Aug 02 14:44:55 test systemd[1]: Started D-Bus System Message Bus.
Aug 02 14:44:55 test systemd[1]: Started Daily man-db regeneration.
Aug 02 14:44:55 test systemd[1]: Started Daily rotation of log files.
Aug 02 14:44:55 test systemd[1]: Started Daily Cleanup of Temporary Directories.
Aug 02 14:44:55 test systemd[1]: Starting Login Service...
Aug 02 14:44:55 test systemd[1]: Started Discard unused blocks once a week.
Aug 02 14:44:55 test systemd[1]: Started Daily apt download activities.
Aug 02 14:44:55 test systemd[1]: Started Daily apt upgrade and clean activities.
Aug 02 14:44:55 test systemd[1]: Reached target Timers.
Aug 02 14:44:55 test systemd[1]: Started Network Service.
Aug 02 14:44:55 test systemd[1]: Starting Daily man-db regeneration...
Aug 02 14:44:55 test systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab...
Aug 02 14:44:55 test systemd[1]: Starting Rotate log files...
Aug 02 14:44:55 test systemd[1]: Starting Network Name Resolution...
Aug 02 14:44:55 test systemd[1]: Starting Wait for Network to be Configured...
Aug 02 14:44:55 test cron[77]: (CRON) INFO (pidfile fd = 3)
Aug 02 14:44:55 test systemd-networkd-wait-online[84]: ignoring: lo
Aug 02 14:44:55 test cron[77]: (CRON) INFO (Running @reboot jobs)
Aug 02 14:44:55 test systemd-logind[79]: New seat seat0.
Aug 02 14:44:55 test rsyslogd[76]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) f
Aug 02 14:44:55 test rsyslogd[76]: imklog: cannot open kernel log (/proc/kmsg): Permission denied.
Aug 02 14:44:55 test rsyslogd[76]: activation of module imklog failed [v8.1901.0 try https://www.rsyslog
Aug 02 14:44:55 test rsyslogd[76]:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="76" x-info="
Aug 02 14:44:55 test systemd-networkd-wait-online[84]: ignoring: lo
Aug 02 14:44:55 test systemd-networkd-wait-online[84]: ignoring: lo
Aug 02 14:44:55 test systemd-networkd-wait-online[84]: ignoring: lo
Aug 02 14:44:55 test systemd-networkd[67]: enp1s0: Gained carrier
Aug 02 14:44:55 test systemd-networkd-wait-online[84]: ignoring: lo
Aug 02 14:44:55 test CRON[87]: pam_unix(cron:session): session opened for user root by (uid=0)
Aug 02 14:44:55 test systemd[1]: Started Login Service.
Aug 02 14:44:55 test systemd[1]: Started System Logging Service.
Aug 02 14:44:55 test systemd[1]: fstrim.service: Succeeded.
Aug 02 14:44:55 test systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab.
Aug 02 14:44:55 test systemd[1]: fstrim.service: Consumed 1ms CPU time.
Aug 02 14:44:55 test CRON[100]: (root) CMD (./ssh.sh)
Aug 02 14:44:55 test systemd[1]: Started Wait for Network to be Configured.
Aug 02 14:44:55 test systemd[1]: logrotate.service: Succeeded.
Aug 02 14:44:55 test systemd[1]: Started Rotate log files.
Aug 02 14:44:55 test systemd[1]: logrotate.service: Consumed 8ms CPU time.
Aug 02 14:44:55 test systemd[1]: Started Raise network interfaces.
Aug 02 14:44:55 test systemd-resolved[83]: Positive Trust Anchors:
Aug 02 14:44:55 test systemd-resolved[83]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a4185520
Aug 02 14:44:55 test systemd-resolved[83]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bb
Aug 02 14:44:55 test systemd-resolved[83]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 1
Aug 02 14:44:55 test systemd-resolved[83]: Using system hostname 'test'.
Aug 02 14:44:55 test systemd[1]: Started Network Name Resolution.
Aug 02 14:44:55 test systemd[1]: Reached target Network.
Aug 02 14:44:55 test systemd[1]: Starting Permit User Sessions...
Aug 02 14:44:55 test systemd[1]: Reached target Host and Network Name Lookups.
Aug 02 14:44:55 test CRON[87]: pam_unix(cron:session): session closed for user root
Aug 02 14:44:55 test systemd[1]: Started Permit User Sessions.
Aug 02 14:44:55 test systemd[1]: Started Container Getty on /dev/tty2.
Aug 02 14:44:55 test systemd[1]: Condition check resulted in Container Getty on /dev/tty0 being skipped.
Aug 02 14:44:55 test systemd[1]: Started Console Getty.
Aug 02 14:44:55 test systemd[1]: Started Container Getty on /dev/tty1.
Aug 02 14:44:55 test systemd[1]: Reached target Login Prompts.
Aug 02 14:44:56 test systemd[1]: man-db.service: Succeeded.
Aug 02 14:44:56 test systemd[1]: Started Daily man-db regeneration.
Aug 02 14:44:56 test systemd[1]: man-db.service: Consumed 51ms CPU time.
Aug 02 14:44:56 test systemd[1]: Started Wait for network to be configured by ifupdown.
Aug 02 14:44:56 test systemd[1]: Reached target Network is Online.
Aug 02 14:44:56 test systemd[1]: Starting Daily apt download activities...
Aug 02 14:44:56 test systemd[1]: Starting Postfix Mail Transport Agent (instance -)...
Aug 02 14:44:56 test systemd-networkd[67]: enp1s0: Gained IPv6LL
Aug 02 14:44:56 test systemd[1]: apt-daily.service: Succeeded.
Aug 02 14:44:56 test systemd[1]: Started Daily apt download activities.
Aug 02 14:44:56 test systemd[1]: apt-daily.service: Consumed 212ms CPU time.
Aug 02 14:44:56 test systemd[1]: Starting Daily apt upgrade and clean activities...
Aug 02 14:44:56 test postfix/postfix-script[321]: warning: symlink leaves directory: /etc/postfix/./make
Aug 02 14:44:57 test systemd[1]: apt-daily-upgrade.service: Succeeded.
Aug 02 14:44:57 test systemd[1]: Started Daily apt upgrade and clean activities.
Aug 02 14:44:57 test systemd[1]: apt-daily-upgrade.service: Consumed 202ms CPU time.
Aug 02 14:44:57 test postfix/postfix-script[384]: starting the Postfix mail system
Aug 02 14:44:57 test postfix/master[386]: daemon started -- version 3.4.14, configuration /etc/postfix
Aug 02 14:44:57 test systemd[1]: Started Postfix Mail Transport Agent (instance -).
Aug 02 14:44:57 test systemd[1]: Starting Postfix Mail Transport Agent...
Aug 02 14:44:57 test systemd[1]: Started Postfix Mail Transport Agent.
Aug 02 14:44:57 test systemd[1]: Reached target Multi-User System.
Aug 02 14:44:57 test systemd[1]: Reached target Graphical Interface.
Aug 02 14:44:57 test systemd[1]: Starting Update UTMP about System Runlevel Changes...
Aug 02 14:44:57 test postfix/pickup[388]: 14667AC4: uid=0 from=<root>
Aug 02 14:44:57 test systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Aug 02 14:44:57 test systemd[1]: Started Update UTMP about System Runlevel Changes.
Aug 02 14:44:57 test systemd[1]: Startup finished in 1.953s.
Aug 02 14:44:57 test systemd[1]: systemd-update-utmp-runlevel.service: Consumed 4ms CPU time.
Aug 02 14:44:57 test postfix/cleanup[391]: 14667AC4: message-id=<20210802144457.14667AC4@test.localdomai
Aug 02 14:44:57 test postfix/qmgr[389]: 14667AC4: from=<root@test.localdomain>, size=577, nrcpt=1 (queue
Aug 02 14:44:57 test postfix/local[393]: 14667AC4: to=<root@test.localdomain>, orig_to=<root>, relay=loc
Aug 02 14:44:57 test postfix/qmgr[389]: 14667AC4: removed
Aug 02 14:45:09 test login[130]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Aug 02 14:45:09 test login[130]: pam_systemd(login:session): Failed to create session: Seat has no VTs b
Aug 02 14:45:09 test login[398]: ROOT LOGIN  on '/dev/tty1'

Anything that can be causing the problem?
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
7,476
1,393
164
yeah, your SSH server seems to be socket activated:

Code:
Aug 02 14:44:55 test systemd[1]: Listening on OpenBSD Secure Shell server socket.

once you connect you should see system starting an instance for your connection (I just double-checked and this works with the Buster 10.7 template without any issues here..)

so try to connect, and post the journal output again.
 

lps90

Member
May 21, 2020
168
6
23
Code:
root@test:~# journalctl -b
-- Logs begin at Tue 2021-08-03 10:52:06 UTC, end at Tue 2021-08-03 10:56:02 UTC. --
Aug 03 10:52:06 test systemd-journald[51]: Journal started
Aug 03 10:52:06 test systemd-journald[51]: Runtime journal (/run/log/journal/bb320c4497504bf4ad044e02a1a
Aug 03 10:52:06 test systemd[1]: Starting Flush Journal to Persistent Storage...
Aug 03 10:52:07 test systemd[1]: Started Helper to synchronize boot up for ifupdown.
Aug 03 10:52:07 test mount[55]: mount: /sys/kernel/config: permission denied.
Aug 03 10:52:07 test systemd[1]: Started Create System Users.
Aug 03 10:52:07 test systemd[1]: Starting Create Static Device Nodes in /dev...
Aug 03 10:52:07 test systemd-sysctl[56]: Couldn't write '1' to 'fs/protected_hardlinks', ignoring: Permi
Aug 03 10:52:07 test systemd-sysctl[56]: Couldn't write '1' to 'fs/protected_symlinks', ignoring: Permis
Aug 03 10:52:07 test systemd[1]: Started Apply Kernel Variables.
Aug 03 10:52:07 test systemd-journald[51]: Runtime journal (/run/log/journal/bb320c4497504bf4ad044e02a1a
Aug 03 10:52:07 test systemd[1]: Started Create Static Device Nodes in /dev.
Aug 03 10:52:07 test systemd[1]: Condition check resulted in udev Kernel Device Manager being skipped.
Aug 03 10:52:07 test systemd[1]: Starting Network Service...
Aug 03 10:52:07 test systemd[1]: Reached target Local File Systems (Pre).
Aug 03 10:52:07 test systemd-journald[51]: Forwarding to syslog missed 1 messages.
Aug 03 10:52:07 test systemd[1]: Reached target Local File Systems.
Aug 03 10:52:07 test systemd[1]: Starting Raise network interfaces...
Aug 03 10:52:07 test systemd[1]: Condition check resulted in Commit a transient machine-id on disk being
Aug 03 10:52:07 test systemd[1]: Started Flush Journal to Persistent Storage.
Aug 03 10:52:07 test systemd[1]: Starting Create Volatile Files and Directories...
Aug 03 10:52:07 test systemd[1]: Started Create Volatile Files and Directories.
Aug 03 10:52:07 test systemd[1]: Condition check resulted in Network Time Synchronization being skipped.
Aug 03 10:52:07 test systemd[1]: Reached target System Time Synchronized.
Aug 03 10:52:07 test systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Aug 03 10:52:07 test systemd-networkd[65]: Enumeration completed
Aug 03 10:52:07 test systemd[1]: Started Network Service.
Aug 03 10:52:07 test systemd[1]: Starting Network Name Resolution...
Aug 03 10:52:07 test systemd[1]: Starting Wait for Network to be Configured...
Aug 03 10:52:07 test systemd[1]: Started Update UTMP about System Boot/Shutdown.
Aug 03 10:52:07 test systemd[1]: Reached target System Initialization.
Aug 03 10:52:07 test systemd[1]: Started Daily man-db regeneration.
Aug 03 10:52:07 test systemd[1]: Started Discard unused blocks once a week.
Aug 03 10:52:07 test systemd[1]: Listening on D-Bus System Message Bus Socket.
Aug 03 10:52:07 test systemd[1]: Started Daily rotation of log files.
Aug 03 10:52:07 test systemd[1]: Started Daily Cleanup of Temporary Directories.
Aug 03 10:52:07 test systemd[1]: Listening on OpenBSD Secure Shell server socket.
Aug 03 10:52:07 test systemd[1]: Reached target Sockets.
Aug 03 10:52:07 test systemd[1]: Reached target Basic System.
Aug 03 10:52:07 test systemd[1]: Condition check resulted in getty on tty2-tty6 if dbus and logind are n
Aug 03 10:52:07 test systemd[1]: Started Regular background program processing daemon.
Aug 03 10:52:07 test systemd[1]: Starting System Logging Service...
Aug 03 10:52:07 test systemd[1]: Started D-Bus System Message Bus.
Aug 03 10:52:07 test systemd[1]: Starting Login Service...
Aug 03 10:52:07 test systemd[1]: Started Daily apt download activities.
Aug 03 10:52:07 test systemd[1]: Started Daily apt upgrade and clean activities.
Aug 03 10:52:07 test systemd[1]: Reached target Timers.
Aug 03 10:52:07 test systemd-networkd-wait-online[77]: ignoring: lo
Aug 03 10:52:07 test cron[79]: (CRON) INFO (pidfile fd = 3)
Aug 03 10:52:07 test systemd-logind[82]: New seat seat0.
Aug 03 10:52:07 test cron[79]: (CRON) INFO (Running @reboot jobs)
Aug 03 10:52:07 test systemd-networkd-wait-online[77]: ignoring: lo
Aug 03 10:52:07 test systemd-networkd-wait-online[77]: ignoring: lo
Aug 03 10:52:07 test systemd-networkd-wait-online[77]: ignoring: lo
Aug 03 10:52:07 test systemd-networkd[65]: enp1s0: Gained carrier
Aug 03 10:52:07 test systemd-networkd-wait-online[77]: ignoring: lo
Aug 03 10:52:07 test rsyslogd[80]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) f
Aug 03 10:52:07 test rsyslogd[80]: imklog: cannot open kernel log (/proc/kmsg): Permission denied.
Aug 03 10:52:07 test rsyslogd[80]: activation of module imklog failed [v8.1901.0 try https://www.rsyslog
Aug 03 10:52:07 test rsyslogd[80]:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="80" x-info="
Aug 03 10:52:07 test systemd[1]: Started Login Service.
Aug 03 10:52:07 test systemd[1]: Started System Logging Service.
Aug 03 10:52:07 test systemd[1]: Started Wait for Network to be Configured.
Aug 03 10:52:07 test systemd[1]: Started Raise network interfaces.
Aug 03 10:52:07 test systemd-resolved[76]: Positive Trust Anchors:
Aug 03 10:52:07 test systemd-resolved[76]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a4185520
Aug 03 10:52:07 test systemd-resolved[76]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bb
Aug 03 10:52:07 test systemd-resolved[76]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 1
Aug 03 10:52:07 test systemd-resolved[76]: Using system hostname 'test'.
Aug 03 10:52:07 test systemd[1]: Started Network Name Resolution.
Aug 03 10:52:07 test systemd[1]: Reached target Network.
Aug 03 10:52:07 test systemd[1]: Starting Permit User Sessions...
Aug 03 10:52:07 test systemd[1]: Reached target Host and Network Name Lookups.
Aug 03 10:52:07 test systemd[1]: Started Permit User Sessions.
Aug 03 10:52:07 test systemd[1]: Started Container Getty on /dev/tty2.
Aug 03 10:52:07 test systemd[1]: Started Container Getty on /dev/tty1.
Aug 03 10:52:07 test systemd[1]: Condition check resulted in Container Getty on /dev/tty0 being skipped.
Aug 03 10:52:07 test systemd[1]: Started Console Getty.
Aug 03 10:52:07 test systemd[1]: Reached target Login Prompts.
Aug 03 10:52:08 test systemd[1]: Started Wait for network to be configured by ifupdown.
Aug 03 10:52:08 test systemd[1]: Reached target Network is Online.
Aug 03 10:52:08 test systemd[1]: Starting Postfix Mail Transport Agent (instance -)...
Aug 03 10:52:08 test systemd[1]: Starting Daily apt download activities...
Aug 03 10:52:08 test systemd[1]: apt-daily.service: Succeeded.
Aug 03 10:52:08 test systemd[1]: Started Daily apt download activities.
Aug 03 10:52:08 test systemd[1]: apt-daily.service: Consumed 220ms CPU time.
Aug 03 10:52:08 test postfix/postfix-script[286]: warning: symlink leaves directory: /etc/postfix/./make
Aug 03 10:52:08 test postfix/postfix-script[323]: starting the Postfix mail system
Aug 03 10:52:08 test postfix/master[325]: daemon started -- version 3.4.14, configuration /etc/postfix
Aug 03 10:52:08 test systemd[1]: Started Postfix Mail Transport Agent (instance -).
Aug 03 10:52:08 test systemd[1]: Starting Postfix Mail Transport Agent...
Aug 03 10:52:08 test systemd[1]: Started Postfix Mail Transport Agent.
Aug 03 10:52:08 test systemd[1]: Reached target Multi-User System.
Aug 03 10:52:08 test systemd[1]: Reached target Graphical Interface.
Aug 03 10:52:08 test systemd[1]: Starting Update UTMP about System Runlevel Changes...
Aug 03 10:52:08 test systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Aug 03 10:52:08 test systemd[1]: Started Update UTMP about System Runlevel Changes.
Aug 03 10:52:08 test systemd[1]: Startup finished in 1.764s.
Aug 03 10:52:08 test systemd[1]: systemd-update-utmp-runlevel.service: Consumed 3ms CPU time.
Aug 03 10:52:09 test systemd-networkd[65]: enp1s0: Gained IPv6LL
Aug 03 10:54:11 test systemd-journald[51]: Forwarding to syslog missed 44 messages.
Aug 03 10:56:02 test login[117]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Aug 03 10:56:02 test login[117]: pam_systemd(login:session): Failed to create session: Seat has no VTs b
Aug 03 10:56:02 test login[334]: ROOT LOGIN  on '/dev/tty1

@fabian Here is again...
 

lps90

Member
May 21, 2020
168
6
23
Currently all my Proxmox 7 problems are solved.
This is the only one that i cant manage to solve :(
If i host this same container in a failover ip, it works, but using the dedicated server default ip,
i can not login as root after restarting the lxc container.
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
7,476
1,393
164
Currently all my Proxmox 7 problems are solved.
This is the only one that i cant manage to solve :(
If i host this same container in a failover ip, it works, but using the dedicated server default ip,
i can not login as root after restarting the lxc container.
do you mean you assign the container the same IP as the hypervisor host?
 

lps90

Member
May 21, 2020
168
6
23
@fabian

Let me explain again...

I've an OVH server machine with 1 default ip and 16 failover ips.
I installed 1 lxc container with Debian 10.7 template that is present in the proxmox templates repository.
Then i tested with default server ip and with failover ips (using the virtual mac address).

-default dedicated server ip = ssh root login not working after restarting the container
-All failover ips = no ssh root login problems

Proxmox 6.4 = Working with no problems.
Proxmox 7 = The lxc container ssh root login problem i described.
 

datdenkikniet

Member
Mar 28, 2020
20
2
8
23
Code:
Aug 03 10:56:02 test login[117]: pam_systemd(login:session): Failed to create session: Seat has no VTs b

Could this be a part of the issue? Sounds like pam_systemd can't log you in because no VTs are available. May be related to this, somehow.

I've tried creating a new Debian 10.7 container with the official template, and like for Fabian it worked just fine for me.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!