[Lxc-users] error message with dual bridge setting
Koji Takiguchi
kojiel at gmail.com
Mon Oct 22 19:07:33 UTC 2012
Hello,
I'm trying dual bridge network setting(br0 and br1) for route
redundancy(like 192.168.100.1/24 and 192.168.200.1/24).
Host and Guest OS is CentOS6.3(2.6.32-279.11.1.el6) and Host is running on
VMware Player.
Lxc version is 0.8.0-rc2.
Container is running successfully and some checking is seeing ok(ssh remote
login, isolated devpts, etc).
But I get two error messages.
1.When reboot/shutdown in container, I get following log in Host's
/var/log/messages.
------------------------------------------------------------------
Oct 23 01:09:26 localhost kernel: br0: port 2(vethD7p1uW) entering disabled
state
Oct 23 01:09:26 localhost kernel: br0: port 2(vethD7p1uW) entering disabled
state
Oct 23 01:09:26 localhost kernel: ------------[ cut here ]------------
Oct 23 01:09:26 localhost kernel: WARNING: at kernel/sysctl.c:2372
unregister_sysctl_table+0xb1/0x120() (Not tainted)
Oct 23 01:09:26 localhost kernel: Hardware name: VMware Virtual Platform
Oct 23 01:09:26 localhost kernel: Modules linked in: veth bridge stp llc
ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables
ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack
ip6table_filter ip6_tables ipv6 ppdev parport_pc parport snd_ens1371
snd_rawmidi snd_ac97_codec ac97_bus snd_seq snd_seq_device snd_pcm
snd_timer snd soundcore snd_page_alloc e1000 vmware_balloon i2c_piix4
i2c_core sg shpchp ext4 mbcache jbd2 sd_mod crc_t10dif sr_mod cdrom mptspi
mptscsih mptbase scsi_transport_spi pata_acpi ata_generic ata_piix
dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan]
Oct 23 01:09:26 localhost kernel: Pid: 10, comm: netns Not tainted
2.6.32-279.11.1.el6.x86_64 #1
Oct 23 01:09:26 localhost kernel: Call Trace:
Oct 23 01:09:26 localhost kernel: [<ffffffff8106b7a7>] ?
warn_slowpath_common+0x87/0xc0
Oct 23 01:09:26 localhost kernel: [<ffffffff8106b7fa>] ?
warn_slowpath_null+0x1a/0x20
Oct 23 01:09:26 localhost kernel: [<ffffffff81076aa1>] ?
unregister_sysctl_table+0xb1/0x120
Oct 23 01:09:26 localhost kernel: [<ffffffffa02ff10b>] ?
__ipv6_dev_mc_dec+0xcb/0x120 [ipv6]
Oct 23 01:09:26 localhost kernel: [<ffffffff81443e87>] ?
neigh_sysctl_unregister+0x27/0x50
Oct 23 01:09:26 localhost kernel: [<ffffffffa02e3fea>] ?
addrconf_ifdown+0x29a/0x3d0 [ipv6]
Oct 23 01:09:26 localhost kernel: [<ffffffffa02e76bd>] ?
addrconf_notify+0xdd/0x970 [ipv6]
Oct 23 01:09:26 localhost kernel: [<ffffffff810e1265>] ?
call_rcu_sched+0x15/0x20
Oct 23 01:09:26 localhost kernel: [<ffffffff810e127e>] ? call_rcu+0xe/0x10
Oct 23 01:09:26 localhost kernel: [<ffffffff815038f5>] ?
notifier_call_chain+0x55/0x80
Oct 23 01:09:26 localhost kernel: [<ffffffff810981b6>] ?
raw_notifier_call_chain+0x16/0x20
Oct 23 01:09:26 localhost kernel: [<ffffffff8143b91b>] ?
call_netdevice_notifiers+0x1b/0x20
Oct 23 01:09:26 localhost kernel: [<ffffffff8143c397>] ?
rollback_registered+0x77/0x130
Oct 23 01:09:26 localhost kernel: [<ffffffff8143c472>] ?
unregister_netdevice+0x22/0x70
Oct 23 01:09:26 localhost kernel: [<ffffffffa03e222a>] ?
veth_dellink+0x1a/0x30 [veth]
Oct 23 01:09:26 localhost kernel: [<ffffffff8143dd2a>] ?
default_device_exit+0x9a/0x100
Oct 23 01:09:26 localhost kernel: [<ffffffff81437410>] ?
cleanup_net+0x0/0xa0
Oct 23 01:09:26 localhost kernel: [<ffffffff8143747e>] ?
cleanup_net+0x6e/0xa0
Oct 23 01:09:26 localhost kernel: [<ffffffff8108c7f0>] ?
worker_thread+0x170/0x2a0
Oct 23 01:09:26 localhost kernel: [<ffffffff81092160>] ?
autoremove_wake_function+0x0/0x40
Oct 23 01:09:26 localhost kernel: [<ffffffff8108c680>] ?
worker_thread+0x0/0x2a0
Oct 23 01:09:26 localhost kernel: [<ffffffff81091df6>] ? kthread+0x96/0xa0
Oct 23 01:09:26 localhost kernel: [<ffffffff8100c14a>] ? child_rip+0xa/0x20
Oct 23 01:09:26 localhost kernel: [<ffffffff81091d60>] ? kthread+0x0/0xa0
Oct 23 01:09:26 localhost kernel: [<ffffffff8100c140>] ? child_rip+0x0/0x20
Oct 23 01:09:26 localhost kernel: ---[ end trace a3e2fc9bc2611149 ]---
Oct 23 01:09:26 localhost kernel: br1: port 2(vethFUgOpJ) entering disabled
state
Oct 23 01:09:26 localhost kernel: br1: port 2(vethFUgOpJ) entering disabled
state
------------------------------------------------------------------
This log appear only dual bridge and reboot/shutdown in container.
I've try one bridge setting, not appear this message.
I've try to change container's ipv6 setting(to disable by
/etc/sysctl.conf), not appear too.
(ipv6 setting refference:
http://lifeofageekadmin.com/disable-ipv6-on-centos-6/)
And I've try to stop container with lxc-stop, not appear.
2.When running lxc-start with -o test.log option, I get following WARN
message in test.log
------------------------------------------------------------------
lxc-start 1350923335.375 DEBUG lxc_cgroup - using cgroup mounted
at '/cgroup'
lxc-start 1350923335.375 DEBUG lxc_cgroup - lxc_cgroup_path_get:
returning /cgroup/lxc63_01 for subsystem devices.allow
lxc-start 1350923335.375 DEBUG lxc_conf - cgroup 'devices.allow'
set to 'c 254:0 rwm'
lxc-start 1350923335.375 INFO lxc_conf - cgroup has been setup
lxc-start 1350923335.375 INFO lxc_conf - console has been setup
lxc-start 1350923335.379 INFO lxc_conf - 4 tty(s) has been setup
lxc-start 1350923335.382 DEBUG lxc_conf - mountpoint for old
rootfs is '/usr/local/lib/lxc/rootfs/mnt'
lxc-start 1350923335.382 DEBUG lxc_conf - pivot_root syscall to
'/usr/local/lib/lxc/rootfs' successful
lxc-start 1350923335.382 DEBUG lxc_conf - umounted '/mnt/dev/pts'
lxc-start 1350923335.382 DEBUG lxc_conf - umounted '/mnt/dev/shm'
lxc-start 1350923335.383 DEBUG lxc_conf - umounted
'/mnt/proc/bus/usb'
lxc-start 1350923335.383 DEBUG lxc_conf - umounted
'/mnt/proc/sys/fs/binfmt_misc'
lxc-start 1350923335.383 DEBUG lxc_conf - umounted '/mnt/sys'
lxc-start 1350923335.383 DEBUG lxc_conf - umounted '/mnt/boot'
lxc-start 1350923335.383 DEBUG lxc_conf - umounted '/mnt/cgroup'
lxc-start 1350923335.383 DEBUG lxc_conf - umounted '/mnt/proc'
lxc-start 1350923335.383 INFO lxc_conf - lazy unmount of '/mnt'
>> lxc-start 1350923335.383 WARN lxc_conf - failed to unmount
'/mnt/dev'
lxc-start 1350923335.383 DEBUG lxc_conf - capabilities has been
setup
lxc-start 1350923335.384 NOTICE lxc_conf - 'lxc63_01' is setup.
lxc-start 1350923335.384 NOTICE lxc_start - exec'ing '/sbin/init'
lxc-start 1350923335.384 NOTICE lxc_start - '/sbin/init' started
with pid '3349'
lxc-start 1350923335.384 DEBUG lxc_utmp - Added
'/proc/3349/root/var/run' to inotifywatch
lxc-start 1350923335.609 DEBUG lxc_utmp - got inotify event 256
for utmp
lxc-start 1350923335.635 DEBUG lxc_utmp - got inotify event 2 for
utmp
lxc-start 1350923335.635 DEBUG lxc_utmp - got inotify event 2 for
utmp
lxc-start 1350923335.635 DEBUG lxc_utmp - utmp handler - run level
is ^@/3
------------------------------------------------------------------
Probably, this WARN is not for dual bridge setting...
So I search google and checking lxc source code, but I couldn't judge that
two message is critical or not critical.
Anyone can help?
At last, I describe about how to create my environment.
My script is in github.(lxc-centos template).
(https://github.com/koji--/lxc-centos)
I take command for creating container, like this.
----------------------------------------------------------------------------
[root at localhost ~]# lxc-centos --name=lxc63_01 --utsname=
lxc63_01.example.com --path=/home/lxc
--first-ipv4=192.168.1.129/24--second-ipv4=
192.168.2.129/24 --arch=x86_64 --arch-base=x86_64
----------------------------------------------------------------------------
And running container like this.
----------------------------------------------------------------------------
[root at localhost ~]# lxc-start -n lxc63_01 -f /home/lxc/lxc63_01/config -o
test.log -l DEBUG
----------------------------------------------------------------------------
Host's /etc/fstab is like this.
------------------------------------------------------------------------------------------
[root at localhost ~]# cat /etc/fstab | grep 'devpts\|cgroup'
devpts /dev/pts devpts
gid=5,mode=620,newinstance,ptmxmode=0666 0 0
none /cgroup cgroup defaults 0 0
------------------------------------------------------------------------------------------
Sorry for such a long text...
Thanks.
Koji Takiguchi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20121023/46772674/attachment.html>
More information about the lxc-users
mailing list