Important update on this topic.
Cross posting to -devel as well.
Seems there is a different issue other than the older object id bug that
they fixed. This problem relates to a symlink in /dev for kmsg pointing
to console. This, apparently, creates a logging loop and causes
systemd-journald to
I support a bugzilla for LXC. Also, if anybody can analyze it
properly, what is the difference between docker and LXC?
Philip
On Wed, Jul 30, 2014 at 6:32 AM, mxs kolo koloma...@gmail.com wrote:
Hi
AFA CentOS 7 in general goes - I have not yet had the time to
incorporate the systemd logic from
On Wed, 2014-07-30 at 14:32 +0400, mxs kolo wrote:
Hi
AFA CentOS 7 in general goes - I have not yet had the time to
incorporate the systemd logic from the Fedora template into the CentOS
template. I just got back from being out of pocket for the last three
weeks (and still completely not
I have had great success with Fedora 20 templates. My scheme in
production is: ubuntu 14.04 as server and Fedora 20 as container.
On Wed, Jul 30, 2014 at 7:16 AM, Michael H. Warfield m...@wittsend.com wrote:
On Wed, 2014-07-30 at 14:32 +0400, mxs kolo wrote:
Hi
AFA CentOS 7 in general goes -
HI all
When container with centos-7 x86_64 started, process systemd-journald
eat cpu in next loop:
epoll_wait(7, {{EPOLLIN|EPOLLERR|EPOLLHUP, {u32=8, u64=8}}}, 1, -1) = 1
writev(2, [{/dev/kmsg buffer overrun, some messages lost., 45},
{\n, 1}], 2) = 46
read(8, , 8192) = 0
On Tue, 2014-07-29 at 20:37 +0400, mxs kolo wrote:
HI all
When container with centos-7 x86_64 started, process systemd-journald
eat cpu in next loop:
That's a journald problem that they (systemd) had claimed (in their
bugzilla report) was fixed. Had something to do with object id's and
