[PVE-User] lxc container can't start on a newly added cluster node

Michael Cooper mcooper at coopfire.com
Fri Jan 11 12:12:38 CET 2019


Ok I was just checking......

On Fri, Jan 11, 2019, 6:10 AM Marco M. Gabriel <marcomgabriel at gmail.com
wrote:

> Yes, all the mount points are the same on each node. As the container
> doesn't start, an existing /dev/pts/x on any other node wouldn't make a
> difference.
>
> I also can create other virtual terminals (screen, tmux, ssh, etc.) and I
> can see new /dev/pts/* devices being created, only lxc-start seems to have
> a problem creating/mounting a console there.
>
> Am Fr., 11. Jan. 2019 um 12:05 Uhr schrieb Michael Cooper <
> mcooper at coopfire.com>:
>
> > The reason I asked if this is the mount point (/dev/pts/x) on the other 3
> > nodes, then it has to be the same on the 4th node for it to migrate
> > properly.
> >
> >
> > Let me know,
> > Michael A Cooper
> > Infrastruture Engineer
> > http://www.coopfire.com
> >
> >
> > From: Marco M. Gabriel
> > Sent: Friday, January 11, 2019 5:18 AM
> > To: PVE User List
> > Subject: [PVE-User] lxc container can't start on a newly added cluster
> node
> >
> > Hi there,
> >
> > we recently added a 4th proxmox node to our 3-node proxmox cluster. When
> > trying to migrate or start an lxc container to the new node, it doesn't
> > start because it can't mount /dev/pts/x to /dev/console. I can move the
> lxc
> > container to each of the 3 old nodes and start it there, but it refuses
> to
> > start on the new node.
> >
> > Nodes 1 to 3 were installed with Version 4.4 and upgraded until the
> > current 5.3-6/37b3c8df (running kernel: 4.15.18-9-pve)
> > Node 4 was installed a few days ago, but is on exactly the same version
> > now.
> >
> > The lxc container is an ubuntu 16.04 based container from the proxmox
> > repository and was installed about a month ago.
> >
> > Trace log of lxc-start (shortened):
> >
> > lxc-start 116 20190111094747.940 INFO     conf -
> > conf.c:lxc_fill_autodev:1220 - Populating "/dev"
> > lxc-start 116 20190111094747.940 DEBUG    conf -
> > conf.c:lxc_fill_autodev:1235 - Created device node "/dev/full"
> > lxc-start 116 20190111094747.940 DEBUG    conf -
> > conf.c:lxc_fill_autodev:1235 - Created device node "/dev/null"
> > lxc-start 116 20190111094747.940 DEBUG    conf -
> > conf.c:lxc_fill_autodev:1235 - Created device node "/dev/random"
> > lxc-start 116 20190111094747.940 DEBUG    conf -
> > conf.c:lxc_fill_autodev:1235 - Created device node "/dev/tty"
> > lxc-start 116 20190111094747.940 DEBUG    conf -
> > conf.c:lxc_fill_autodev:1235 - Created device node "/dev/urandom"
> > lxc-start 116 20190111094747.940 DEBUG    conf -
> > conf.c:lxc_fill_autodev:1235 - Created device node "/dev/zero"
> > lxc-start 116 20190111094747.940 INFO     conf -
> > conf.c:lxc_fill_autodev:1297 - Populated "/dev"
> > lxc-start 116 20190111094747.940 ERROR    utils -
> utils.c:safe_mount:1791 -
> > No such file or directory - Failed to mount /dev/pts/3 onto /dev/console
> > lxc-start 116 20190111094747.940 ERROR    conf -
> > conf.c:lxc_setup_dev_console:1765 - Failed to mount "/dev/pts/3" on
> > "/dev/console"
> > lxc-start 116 20190111094747.940 ERROR    conf - conf.c:lxc_setup:3656 -
> > Failed to setup console
> > lxc-start 116 20190111094747.940 ERROR    start - start.c:do_start:1246 -
> > Failed to setup container "116"
> >
> > Any hints how to fix this or what happens here?
> >
> > Best regards,
> > Marco
> > _______________________________________________
> > pve-user mailing list
> > pve-user at pve.proxmox.com
> > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> >
> > _______________________________________________
> > pve-user mailing list
> > pve-user at pve.proxmox.com
> > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> >
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>


More information about the pve-user mailing list