<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>This seems relevant from syslog:</p>
<p><br>
</p>
<p><br>
Dec 6 16:36:43 cliffjumper kernel: [22402.625004] lxcbr0: port
1(veth4KDYR9) entered blocking state<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.625005] lxcbr0: port
1(veth4KDYR9) entered disabled state<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.625103] device
veth4KDYR9 entered promiscuous mode<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.625310] IPv6:
ADDRCONF(NETDEV_UP): veth4KDYR9: link is not ready<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.679427] eth0: renamed
from vethKOVFCJ<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.697517] IPv6:
ADDRCONF(NETDEV_CHANGE): veth4KDYR9: link becomes ready<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.697570] lxcbr0: port
1(veth4KDYR9) entered blocking state<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.697572] lxcbr0: port
1(veth4KDYR9) entered forwarding state<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.811868] sh[17085] <b>vsyscall
attempted with vsyscall=none</b> ip:ffffffffff600400 cs:33
sp:7ffd2b8d2078 ax:ffffffffff600400 si:7ffd2b8d3f4a di:0<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.811872] sh[17085]:
segfault at ffffffffff600400 ip ffffffffff600400 sp
00007ffd2b8d2078 error 15<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.812093] init[17056]<b>
vsyscall attempted with vsyscall=none</b> ip:ffffffffff600400
cs:33 sp:7ffea782d3f8 ax:ffffffffff600400 si:7fd2d4b31039
di:7ffea782d4c8<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.812230] sh[17086]
vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33
sp:7fff0386f648 ax:ffffffffff600400 si:7fff03870f60 di:0<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.812233] sh[17086]:
segfault at ffffffffff600400 ip ffffffffff600400 sp
00007fff0386f648 error 15<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.812988] init[17056]
vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33
sp:7ffea782c9e8 ax:ffffffffff600400 si:7fd2d4b31039
di:7ffea782cab8<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.813643] lxcbr0: port
1(veth4KDYR9) entered disabled state<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.816241] device
veth4KDYR9 left promiscuous mode<br>
Dec 6 16:36:43 cliffjumper kernel: [22402.816244] lxcbr0: port
1(veth4KDYR9) entered disabled state<br>
</p>
<br>
<div class="moz-cite-prefix">On 05/12/16 21:42, Evgeni Golov wrote:<br>
</div>
<blockquote
cite="mid:20161205104247.ntj4o22uezjcaegh@t440s.egolov.redhat.com"
type="cite">
<pre wrap="">On Mon, Dec 05, 2016 at 08:59:07PM +1100, Dean Hamstead wrote:
</pre>
<blockquote type="cite">
<pre wrap="">it seems if i drop back to 2.0.5 the problem still occurs. so i am guessing
some other thing upgraded and its not lxc-start's fault
</pre>
</blockquote>
<pre wrap="">
can you try an older lxcfs, it was updated at (almost) the same time.
mind you, just downgrading the package is not enough, the daemon is not
restarted automatically as this would break running containers. restart
it yourself or reboot :)
</pre>
<blockquote type="cite">
<pre wrap="">
On 05/12/16 19:25, Evgeni Golov wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Dean,
thanks for the report,
On Mon, Dec 05, 2016 at 05:58:40PM +1100, Dean Hamstead wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Since upgrading, centos6 containers fail to start.
</pre>
</blockquote>
<pre wrap="">Is that a regression from 2.0.5? Or anything older?
</pre>
<blockquote type="cite">
<pre wrap="">I am guessing that upstart is doing something crappy and lxc is now carefull enough to notice?
</pre>
</blockquote>
<pre wrap="">Could totally be, but I would guess upstream would have tested with
upstart (on older Ubuntu LTS releases). Well, let's see if I can
reproduce tonight.
Greets
Evgeni
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
</blockquote>
<br>
</body>
</html>