[SOLVED] LCX Container BlackScreen

M

manjotsc

Active Member
Jul 2, 2020
73
6
28
Montreal, Quebec
My 102 VM "LXC" not showing shell, it just blackscreen, I even tried rebooting proxmox, didn't help

Thanks,

Code: 
arch: amd64

cores: 2

hostname: WebServer

memory: 1000

mp0: /mnt/4TB/Plex,mp=/mnt/Plex

nameserver: 192.168.40.4 192.168.40.1

net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=2A:E7:4E:5E:19:F6,ip=dhcp,type=veth

onboot: 1

ostype: ubuntu

rootfs: VMDrive:102/vm-102-disk-0.raw,size=10G

searchdomain: manjot.net

swap: 1000

unprivileged: 1


Code: 
lxc-start -n 102 -F -l DEBUG -o /tmp/lxc-102.log

lxc-start: 102: utils.c: safe_mount: 1148 Invalid argument - Failed to mount "/sys/kernel/debug" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/kernel/debug"

                                                                                                                                                             lxc-start: 102: conf.c: lxc_setup_boot_id: 3250 Permission denied - Failed to mount /dev/.lxc-boot-id to /proc/sys/kernel/random/boot_id

                                                                                                                           systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)

Detected virtualization lxc.

Detected architecture x86-64.



Welcome to Ubuntu 18.04.4 LTS!



Set hostname to <WebServer>.

Failed to read AF_UNIX datagram queue length, ignoring: No such file or directory

File /lib/systemd/system/systemd-journald.service:36 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.

Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)

[  OK  ] Reached target Remote File Systems.

[  OK  ] Reached target User and Group Name Lookups.

[  OK  ] Reached target Swap.

system.slice: Failed to reset devices.list: Operation not permitted

[  OK  ] Created slice System Slice.

[  OK  ] Listening on Journal Socket.

system-postfix.slice: Failed to reset devices.list: Operation not permitted

[  OK  ] Created slice system-postfix.slice.

systemd-tmpfiles-setup-dev.service: Failed to reset devices.list: Operation not permitted

         Starting Create Static Device Nodes in /dev...

system-container\x2dgetty.slice: Failed to reset devices.list: Operation not permitted

[  OK  ] Created slice system-container\x2dgetty.slice.

[  OK  ] Started Forward Password Requests to Wall Directory Watch.

user.slice: Failed to reset devices.list: Operation not permitted

[  OK  ] Created slice User and Session Slice.

[  OK  ] Reached target Slices.

[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.

[  OK  ] Listening on Journal Socket (/dev/log).

systemd-modules-load.service: Failed to reset devices.list: Operation not permitted

         Starting Load Kernel Modules...

sys-kernel-debug.mount: Failed to check directory /sys/kernel/debug: Permission denied

sys-kernel-debug.mount: Failed to reset devices.list: Operation not permitted

         Mounting Kernel Debug File System...

keyboard-setup.service: Failed to reset devices.list: Operation not permitted

         Starting Set the console keyboard layout...

[  OK  ] Listening on Syslog Socket.

systemd-journald.service: Failed to reset devices.list: Operation not permitted

         Starting Journal Service...

sys-fs-fuse-connections.mount: Failed to reset devices.list: Operation not permitted

[  OK  ] Started Create Static Device Nodes in /dev.

sys-kernel-debug.mount: Mount process exited, code=exited status=32

sys-kernel-debug.mount: Failed with result 'exit-code'.

[FAILED] Failed to mount Kernel Debug File System.

See 'systemctl status sys-kernel-debug.mount' for details.

[  OK  ] Started Load Kernel Modules.

systemd-sysctl.service: Failed to reset devices.list: Operation not permitted

         Starting Apply Kernel Variables...

sys-kernel-config.mount: Failed to reset devices.list: Operation not permitted

         Mounting Kernel Configuration File System...

sys-kernel-config.mount: Mount process exited, code=exited status=32

sys-kernel-config.mount: Failed with result 'exit-code'.

[FAILED] Failed to mount Kernel Configuration File System.

See 'systemctl status sys-kernel-config.mount' for details.

[  OK  ] Started Journal Service.

         Starting Flush Journal to Persistent Storage...

[  OK  ] Started Apply Kernel Variables.

[  OK  ] Started Set the console keyboard layout.

[  OK  ] Started Dispatch Password Requests to Console Directory Watch.

[  OK  ] Reached target Paths.

[  OK  ] Reached target Local Encrypted Volumes.

[  OK  ] Reached target Local File Systems (Pre).

[  OK  ] Reached target Local File Systems.

         Starting Set console font and keymap...

         Starting ebtables ruleset management...

         Starting Tell Plymouth To Write Out Runtime Data...

         Starting AppArmor initialization...

[  OK  ] Started Flush Journal to Persistent Storage.

[  OK  ] Started Set console font and keymap.

         Starting Create Volatile Files and Directories...

[  OK  ] Started Tell Plymouth To Write Out Runtime Data.

[  OK  ] Started AppArmor initialization.

[  OK  ] Started ebtables ruleset management.

[  OK  ] Reached target Network (Pre).

         Starting Network Service...

[FAILED] Failed to start Network Service.

See 'systemctl status systemd-networkd.service' for details.

[  OK  ] Stopped Network Service.

         Starting Network Service...

[FAILED] Failed to start Network Service.

See 'systemctl status systemd-networkd.service' for details.

[  OK  ] Stopped Network Service.

         Starting Network Service...

[FAILED] Failed to start Network Service.

See 'systemctl status systemd-networkd.service' for details.

[  OK  ] Stopped Network Service.

         Starting Network Service...

[FAILED] Failed to start Network Service.

See 'systemctl status systemd-networkd.service' for details.

[  OK  ] Stopped Network Service.

         Starting Network Service...

[FAILED] Failed to start Network Service.

See 'systemctl status systemd-networkd.service' for details.

[  OK  ] Stopped Network Service.

[FAILED] Failed to start Network Service.

See 'systemctl status systemd-networkd.service' for details.

[  OK  ] Started Create Volatile Files and Directories.

         Starting Update UTMP about System Boot/Shutdown...

         Starting Network Name Resolution...

[  OK  ] Reached target System Time Synchronized.

[  OK  ] Started Update UTMP about System Boot/Shutdown.

[  OK  ] Reached target System Initialization.

[  OK  ] Listening on UUID daemon activation socket.

[  OK  ] Started Message of the Day.

[  OK  ] Started Daily Cleanup of Temporary Directories.

[  OK  ] Started Clean PHP session files every 30 mins.

[  OK  ] Listening on D-Bus System Message Bus Socket.

[  OK  ] Reached target Sockets.

[  OK  ] Reached target Basic System.

         Starting Login Service...

         Starting LSB: Start/stop the postgrey daemon...

         Starting System Logging Service...

         Starting Dispatcher daemon for systemd-networkd...

         Starting Accounts Service...

         Starting LSB: saslauthd startup script...

[  OK  ] Started Regular background program processing daemon.

[  OK  ] Started D-Bus System Message Bus.
 

Attachments

  • Annotation 2020-07-13 211553.png
    Annotation 2020-07-13 211553.png
    58.6 KB · Views: 13
Last edited:
Code: 
root@vms:/home/sshprox# lxc-attach 102
# systemctl status systemd-networkd.service
● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-07-14 01:48:36 UTC; 18min ago
     Docs: man:systemd-networkd.service(8)
  Process: 155 ExecStart=/lib/systemd/systemd-networkd (code=exited, status=217/USER)
 Main PID: 155 (code=exited, status=217/USER)

Jul 14 01:48:36 WebServer systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Jul 14 01:48:36 WebServer systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5.
Jul 14 01:48:36 WebServer systemd[1]: Stopped Network Service.
Jul 14 01:48:36 WebServer systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Jul 14 01:48:36 WebServer systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Jul 14 01:48:36 WebServer systemd[1]: Failed to start Network Service.
#
 
I just had to comment the ldap line in /etc/nsswitch.conf, its working fine now. It was trying to authenticate against LDAP server.

Thanks,
 
Last edited:
  • Like
Reactions: Moayad
Use the IPV6 Static .
1698489469706.png

Probably, a conflict in your router which has IPV6 disabled.
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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 yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back