Container braucht 5 minuten zum boot (netzwerk)

A

Alianaa

Member
Nov 11, 2021
13
2
8
26
Hallo,

Irgendwas stimmt mit meinen settings nicht. Bei jedem boot braucht der Container 5 min bis er erreichbar ist. z.B. die Console (webinterface) geht solange nicht.

Ich habe einen neuen leeren debian-11 container erstellt um das zu verifizieren.
Hier ein paar logs:

Code: 
root@pcTestNetwork:~# systemctl status
● pcTestNetwork
    State: starting
     Jobs: 15 queued
   Failed: 2 units
    Since: Fri 2021-11-12 12:00:42 UTC; 2min 53s ago
   CGroup: /
           ├─.lxc
           │ ├─185 /bin/bash
           │ ├─191 systemctl status
           │ └─192 less
           ├─init.scope
           │ └─1 /sbin/init
           └─system.slice
             ├─systemd-networkd.service
             │ └─73 /lib/systemd/systemd-networkd
             ├─cron.service
             │ └─83 /usr/sbin/cron -f
             ├─networking.service
             │ ├─ 70 /sbin/ifup -a --read-environment
             │ ├─101 /sbin/dhclient -4 -v -i -pf /run/dhclient.eth0.pid -lf /var/lib/>
             │ ├─166 /bin/sh -c /sbin/dhclient -6 -v -pf /run/dhclient6.eth0.pid -lf >
             │ ├─167 /sbin/dhclient -6 -v -pf /run/dhclient6.eth0.pid -lf /var/lib/dh>
             │ └─168 /sbin/dhclient -6 -v -pf /run/dhclient6.eth0.pid -lf /var/lib/dh>
             ├─systemd-journald.service
             │ └─52 /lib/systemd/systemd-journald
             ├─rsyslog.service
             │ └─86 /usr/sbin/rsyslogd -n -iNONE
             ├─systemd-resolved.service
             │ └─93 /lib/systemd/systemd-resolved
             ├─dbus.service
             │ └─84 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopid>
             └─systemd-logind.service
               └─87 /lib/systemd/systemd-logind
root@pcTestNetwork:~# systemctl status
● pcTestNetwork
    State: degraded
     Jobs: 0 queued
   Failed: 3 units
    Since: Fri 2021-11-12 12:00:42 UTC; 7min ago
   CGroup: /
           ├─.lxc
           │ ├─185 /bin/bash
           │ ├─363 systemctl status
           │ └─364 less
           ├─init.scope
           │ └─1 /sbin/init
           └─system.slice
             ├─systemd-networkd.service
             │ └─73 /lib/systemd/systemd-networkd
             ├─cron.service
             │ └─83 /usr/sbin/cron -f
             ├─systemd-journald.service
             │ └─52 /lib/systemd/systemd-journald
             ├─rsyslog.service
             │ └─86 /usr/sbin/rsyslogd -n -iNONE
             ├─console-getty.service
             │ └─199 /sbin/agetty -o -p -- \u --noclear --keep-baud console 115200,38>
             ├─system-postfix.slice
             │ └─postfix@-.service
             │   ├─355 /usr/lib/postfix/sbin/master -w
             │   ├─357 pickup -l -t unix -u -c
             │   └─358 qmgr -l -t unix -u
             ├─systemd-resolved.service
             │ └─93 /lib/systemd/systemd-resolved
             ├─system-container\x2dgetty.slice
             │ ├─container-getty@2.service
             │ │ └─201 /sbin/agetty -o -p -- \u --noclear --keep-baud tty2 115200,384>
             │ └─container-getty@1.service
             │   └─200 /sbin/agetty -o -p -- \u --noclear --keep-baud tty1 115200,384>
             ├─dbus.service
             │ └─84 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopid>
             └─systemd-logind.service
               └─87 /lib/systemd/systemd-logind
root@pcTestNetwork:~# systemd-analyze critical-path
Unknown command verb critical-path.
root@pcTestNetwork:~# systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @5min 1.752s
└─multi-user.target @5min 1.752s
  └─postfix.service @5min 1.739s +12ms
    └─postfix@-.service @5min 1.179s +557ms
      └─network-online.target @5min 1.177s
        └─network.target @5min 1.176s
          └─systemd-resolved.service @1.312s +200ms
            └─systemd-networkd.service @1.006s +303ms
              └─systemd-sysusers.service @688ms +296ms
                └─systemd-remount-fs.service @628ms +30ms
                  └─systemd-journald.socket @583ms
                    └─system.slice @559ms
                      └─-.slice @559ms
root@pcTestNetwork:~# sudo systemctl list-units --failed
bash: sudo: command not found
root@pcTestNetwork:~# systemctl list-units --failed
  UNIT                          LOAD   ACTIVE SUB    DESCRIPTION
● sys-kernel-config.mount       loaded failed failed Kernel Configuration File System
● networking.service            loaded failed failed Raise network interfaces       
● systemd-journald-audit.socket loaded failed failed Journal Audit Socket
LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
3 loaded units listed.
root@pcTestNetwork:~# systemctl status sys-kernel-config.mount           
● sys-kernel-config.mount - Kernel Configuration File System
     Loaded: loaded (/lib/systemd/system/sys-kernel-config.mount; static)
     Active: failed (Result: exit-code) since Fri 2021-11-12 12:00:42 UTC; 9min ago
      Where: /sys/kernel/config
       What: configfs
       Docs: https://www.kernel.org/doc/Documentation/filesystems/configfs/configfs.t>
             https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
        CPU: 2ms
Nov 12 12:00:43 pcTestNetwork mount[63]: mount: /sys/kernel/config: permission denied.
Warning: journal has been rotated since unit was started, output may be incomplete.
root@pcTestNetwork:~# systemctl status networking.service     
● networking.service - Raise network interfaces
     Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: >
     Active: failed (Result: timeout) since Fri 2021-11-12 12:05:43 UTC; 4min 34s ago
       Docs: man:interfaces(5)
    Process: 70 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAI>
   Main PID: 70 (code=exited, status=1/FAILURE)
        CPU: 137ms
Nov 12 12:05:04 pcTestNetwork ifup[168]: RCV: Advertise message on eth0 from fe80::ea>
Nov 12 12:05:04 pcTestNetwork ifup[168]: RCV:  X-- Server ID: 00:03:00:01:e8:df:70:6a>
Nov 12 12:05:04 pcTestNetwork ifup[168]: PRC: Lease failed to satisfy.
Nov 12 12:05:43 pcTestNetwork systemd[1]: networking.service: start operation timed o>
Nov 12 12:05:43 pcTestNetwork systemd[1]: networking.service: Main process exited, co>
Nov 12 12:05:43 pcTestNetwork ifup[70]: Got signal Terminated, terminating...
Nov 12 12:05:43 pcTestNetwork ifup[70]: ifup: failed to bring up eth0
Nov 12 12:05:43 pcTestNetwork systemd[1]: networking.service: Killing process 104 (is>
Nov 12 12:05:43 pcTestNetwork systemd[1]: networking.service: Failed with result 'tim>
Nov 12 12:05:43 pcTestNetwork systemd[1]: Failed to start Raise network interfaces.
root@pcTestNetwork:~# systemctl status systemd-journald-audit.socket
● systemd-journald-audit.socket - Journal Audit Socket
     Loaded: loaded (/lib/systemd/system/systemd-journald-audit.socket; static)
     Active: failed (Result: resources)
   Triggers: ● systemd-journald.service
       Docs: man:systemd-journald.service(8)
             man:journald.conf(5)
     Listen: audit 1 (Netlink)
root@pcTestNetwork:~# exit
exit
root@homeserveraugsburg:~# pct config 101
arch: amd64
cores: 1
features: nesting=1
hostname: pcTestNetwork
memory: 512
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=FE:39:B8:68:B4:A0,ip=dhcp,ip6=dhcp,type=veth
ostype: debian
rootfs: enc1:101/vm-101-disk-0.raw,size=8G
swap: 512
unprivileged: 1



Was ist da falsch eingestellt? Nach den 5 minuten ist der container erreichbar und ich kann mich auch über das webinterface einloggen.
 
  • Like
Reactions: bytegetter
You must log in or register to reply here.
Top Bottom