<div dir="ltr"><div><div><div><div><div>Sorry to say so but I am very doubtful about the fact that lxc does not have anything to do with the garbled logs problem.<br></div>I have been using Debian servers (with or without xen) for many years and it is the first time I face such issues.<br></div><br>One relevant example is that my guest domain has iptables rules and logs dropped packets. <br>The logging rule is:<br><span style="font-family:courier new,monospace">iptables -A OUTPUT -j LOG --log-prefix " dropped by firewall (OUTPUT) "</span><br><br></div>so I find the following lines in kern.log: (when not garbled)<br><br><span style="font-family:courier new,monospace">Oct 29 12:22:31 myhost kernel: [68725.452738] dropped by firewall (OUTPUT)IN= OUT=eth0 SRC=ip_address DST=ip_address LEN=109 TOS=0x00 PREC=0x00 TTL=255 ID=5689 DF PROTO=41 </span><br><br></div>I discovered that I have similar lines in the kern.log of my containers while they have absolutely no iptables rules:<br><br><span style="font-family:courier new,monospace">Oct 29 13:10:04 localhost kernel: [71575.889092] dropped by firewall (OUTPUT)IN= OUT=eth0 SRC=ip_address DST=ip_address LEN=116 TOS=0x00 PREC=0x00 TTL=255 ID=7628 DF PROTO=41 </span><br><br><br><br></div><div>As suggested <a href="https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1003888">here</a>, I added the following lines in my containers conf file:<br><p id="yui_3_10_3_1_1414583699637_300"><span style="font-family:courier new,monospace">lxc.cap.drop = sys_module mac_admin syslog</span></p></div><div>but that did not help.<br><br></div><div><br><div><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">Commenting out/removing the line including “$ModLoad imklog” in /etc/rsyslog.conf as suggested is not an option since I need the logging possibilities.<br><br></span></div><div></div>Any help is greatly appreciated.<br><br>Thank you.<br><br></div><div>Yannick<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 28 October 2014 06:45, Hans Feldt <span dir="ltr"><<a href="mailto:hans.feldt@ericsson.com" target="_blank">hans.feldt@ericsson.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Regarding garbled logs, you should disable kernel logging in the guest by commenting out/removing the line including “$ModLoad imklog” in /etc/rsyslog.conf<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hans<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> lxc-users [mailto:<a href="mailto:lxc-users-bounces@lists.linuxcontainers.org" target="_blank">lxc-users-bounces@lists.linuxcontainers.org</a>]
<b>On Behalf Of </b>Yannick Barbeaux<br>
<b>Sent:</b> den 27 oktober 2014 17:08<br>
<b>To:</b> <a href="mailto:lxc-users@lists.linuxcontainers.org" target="_blank">lxc-users@lists.linuxcontainers.org</a><br>
<b>Subject:</b> [lxc-users] upgrade to LXC 1.0.6 : segfault<u></u><u></u></span></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi everyone,<u></u><u></u></p>
</div>
<p class="MsoNormal">my first post in the LXC world!<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I have been using LXC 1.0.3 on debian wheezy for a few months now and everything worked fine, except that the kern.log (and thus syslog too) on "Dom0" was garbled as soon as I started any container :
<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">example:<br>
<span style="font-family:"Courier New"">Oct 27 16:19:51 myserver kernel: rl(NU)I=r.0 U=MC0:05:00:1f:ac:1e:60:0SC0000DT24001LN3 O=x0PE=x0TL1I= FPOO2<br>
Oct 27 16:19:53 myserver kernel: 91845] rpe yfrwl IPT Nb012OT A=10:e0:00:e5:86:88:80 R=... S=2... E=2TS00 RC0C T= D0D RT= 2.233 rp ra NTIb.4U C10e001ece20480R0. =..E2S0R0 =DDR=4>[ 922.837874] dropped by firewall (INPUT) IN=br0105 OU=MC0:05:00:16:09:99:f0:0SC0000DT=2...
E=2TS00 RC0C T= D0D RT= ==x0PE=x0TL1I= FPOO2</span><u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">it seems that various processes write at the same time in the logs and thus it is totally messy.<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I thought that upgrading to LXC 1.0.6 could solve that issue. I downloaded the sources and compiled the new version with python enabled.<u></u><u></u></p>
</div>
<p class="MsoNormal">The real problems started with that new version: after rebooting, the containers would simply not start (<span style="font-family:"Courier New"">lxc-start -d -n p1
</span>does not do anything, nothing in the logs either). After investigations, I found out that the link to the liblxc pointed to the
<span style="font-family:"Courier New"">liblxc.so.1.1.0.alpha1.</span><u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">After deleting the symbolic link and recreating it to point to
<span style="font-family:"Courier New"">liblxc.so.1.0.6,</span><span style="font-family:"Arial","sans-serif""> I was able to launch the containers successfully but unfortunately, one of the command I used the most,
</span><span style="font-family:"Courier New"">lxc-ls --fancy </span><span style="font-family:"Arial","sans-serif"">was broken (Segmentation fault). Same issue for the
</span><span style="font-family:"Courier New"">lxc-autostart</span><span style="font-family:"Arial","sans-serif""> command.</span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Furthermore, after each reboot, the link to the alpha1 version of the lib is automatically recreated so before launching the containers, I have to execute those commands to recreate the correct
link:<br>
</span><span style="font-family:"Courier New"">rm /usr/local/lib/liblxc.so.1<br>
ln -s /usr/local/lib/liblxc.so.1.0.6 /usr/local/lib/liblxc.so.1</span><u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">And guess what, with the v1.0.6, my kern.log and syslog are still garbled so the upgrade was definitely not efficient in my case.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">To sum up, since the upgrade, I face the following issues:<br>
- garbled logs on "Dom0" (same issue as with v1.0.3)<br>
- link to the liblxc.so.1.1.0alpha is recreated at each system startup (and implies that I cannot launch my containers)<br>
- lxc-ls --fancy and lxc-autostart not working anymore<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Any help on this would be really appreciated.<br>
<br>
Thanks<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Yannick<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
</div></div></div>
</div>
<br>_______________________________________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br></blockquote></div><br></div>