[PVE-User] Ubuntu 14.04 boot fail on PVE 5.3-7

lord_Niedzwiedz sir_Misiek1 at o2.pl
Tue Jan 15 11:46:23 CET 2019


> Hello,
>
> since weekend I have problems with LXC containers (upstart based) booting on Proxmox 5.3-7. Today I have created new container and after starting it only few upstart processes are running:
> root at ubuntu14:~# ps ax
>    PID TTY      STAT   TIME COMMAND
>      1 ?        Ss     0:00 /sbin/init
>     37 ?        S      0:00 @sbin/plymouthd --mode=boot --attach-to-session
>     39 ?        Ss     0:00 plymouth-upstart-bridge
>     47 ?        S      0:00 mountall --daemon
>    283 ?        S      0:00 upstart-socket-bridge --daemon
>   1445 ?        Ss     0:00 /bin/bash
>   1481 ?        R+     0:00 ps ax
> root at ubuntu14:~# ifconfig
> lo        Link encap:Local Loopback
>            inet addr:127.0.0.1  Mask:255.0.0.0
>            inet6 addr: ::1/128 Scope:Host
>            UP LOOPBACK RUNNING  MTU:65536  Metric:1
>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
>
> After switching to runlevel 2 container continues to boot:
> root at ubuntu14:~# ifup eth0; telinit 2
> root at ubuntu14:~# ps ax; ifconfig
>    PID TTY      STAT   TIME COMMAND
>      1 ?        Ss     0:00 /sbin/init
>     47 ?        S      0:00 mountall --daemon
>    283 ?        S      0:00 upstart-socket-bridge --daemon
>   1445 ?        Ss     0:00 /bin/bash
>   1550 ?        Ss     0:00 /usr/sbin/sshd -D
>   1559 ?        S      0:00 /bin/sh /etc/network/if-up.d/ntpdate
>   1562 ?        S      0:00 lockfile-create /var/lock/ntpdate-ifup
>   1569 ?        Ss     0:00 cron
>   1585 ?        Ss     0:00 /usr/sbin/irqbalance
>   1687 ?        Ss     0:00 /usr/lib/postfix/master
>   1691 ?        S      0:00 pickup -l -t unix -u -c
>   1692 ?        S      0:00 qmgr -l -t unix -u
>   1708 ?        S      0:00 /bin/sh /etc/init.d/ondemand background
>   1714 ?        S      0:00 sleep 60
>   1716 console  Ss+    0:00 /sbin/getty -8 38400 console
>   1718 lxc/tty2 Ss+    0:00 /sbin/getty -8 38400 tty2
>   1719 lxc/tty1 Ss+    0:00 /sbin/getty -8 38400 tty1
>   1734 ?        R+     0:00 ps ax
> eth0      Link encap:Ethernet  HWaddr 6a:f7:05:0c:43:a4
>            inet addr:192.168.xxx.239  Bcast:192.168.xxx.255  Mask:255.255.255.0
>            inet6 addr: fe80::68f7:5ff:fe0c:43a4/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:36 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:3647 (3.6 KB)  TX bytes:2342 (2.3 KB)
>
> lo        Link encap:Local Loopback
>            inet addr:127.0.0.1  Mask:255.0.0.0
>            inet6 addr: ::1/128 Scope:Host
>            UP LOOPBACK RUNNING  MTU:65536  Metric:1
>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> What can I do to have fully booted container without runlevel switching?
>
> BR,
> Michal Szamocki
> Cirrus
     Hi Michał.

I heave this same with fedora.

Try this:

chkconfig --levels 2345 network on
#systemctl disable NetworkManager

# in file /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=wanwww5
GATEWAY=84.204.162.20


Best regards
Grzegorz Misiek  ;-]


More information about the pve-user mailing list