No, from the host:
Oct 10 06:25:01 srvc15 kernel: imklog 4.4.2, log source = /proc/kmsg
started.
Oct 10 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com";] (re)start
Oct 11 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com";] rsyslogd was
HUPed, type 'restart'.
Oct 11 06:25:01 srvc15 kernel: imklog 4.4.2, log source = /proc/kmsg
started.
Oct 11 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com";] (re)start
Oct 12 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com";] rsyslogd was
HUPed, type 'restart'.
Oct 12 06:25:01 srvc15 kernel: Kernel logging (proc) stopped.
Oct 12 06:25:01 srvc15 kernel: imklog 4.4.2, log source = /proc/kmsg
started.
Oct 12 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com";] (re)start
Oct 13 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com";] rsyslogd was
HUPed, type 'restart'.
Oct 13 06:25:01 srvc15 kernel: Kernel logging (proc) stopped.
Oct 13 06:25:01 srvc15 kernel: imklog 4.4.2, log source = /proc/kmsg
started.
Oct 13 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com";] (re)start
>From the container:
Oct 10 06:25:01 srvc15c0 kernel: imklog 3.18.6, log source = /proc/kmsg
started.
Oct 10 06:25:01 srvc15c0 rsyslogd: [origin software="rsyslogd"
swVersion="3.18.6" x-pid="299" x-info="http://www.rsyslog.com";] restart
Oct 11 06:25:01 srvc15c0 kernel: imklog 3.18.6, log source = /proc/kmsg
started.
Oct 11 06:25:01 srvc15c0 rsyslogd: [origin software="rsyslogd"
swVersion="3.18.6" x-pid="299" x-info="http://www.rsyslog.com";] restart
Oct 12 06:25:01 srvc15c0 kernel: imklog 3.18.6, log source = /proc/kmsg
started.
Oct 12 06:25:01 srvc15c0 rsyslogd: [origin software="rsyslogd"
swVersion="3.18.6" x-pid="299" x-info="http://www.rsyslog.com";] restart
Oct 13 06:25:01 srvc15c0 kernel: imklog 3.18.6, log source = /proc/kmsg
started.
Oct 13 06:25:01 srvc15c0 rsyslogd: [origin software="rsyslogd"
swVersion="3.18.6" x-pid="299" x-info="http://www.rsyslog.com";] restart
That's all :(
Jorge E. Espada
On Wed, Oct 13, 2010 at 9:45 AM, Daniel Lezcano <dlezc...@fr.ibm.com> wrote:
> On 10/13/2010 02:42 PM, jorge espada wrote:
>
>> The error was ICMP "no route to host", but now i change the conf and
>> instead of vepa I used bridge...after destroy and create the containers
>> with
>> the new conf, seems to be working as expected for a while, but from time
>> to
>> time "the container became unresponsive".. no ping (100% packet lost). The
>> curious thing is, if I login into the host and then to the container
>> (lxc-console) and ping another container or host the " unresponsive
>> container " become alive again (ping OK)....so I'm a bit lost..
>>
>
> Is there any trace in /var/log/messages ?
>
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Lxc-devel mailing list
Lxc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-devel
