[Users] syslog-ng issues in container

[Kir Kolyshkin]

The bug in question was fixed in kernel 042stab077.7, please give it a try.

On 04/12/2013 05:01 AM, Brad Alexander wrote:
> Todd,
>
> Thanks for responding. Actually, I did google for it, I guess I didn't 
> go down the list far enough to encounter this post.
>
> Thanks,
> --b
>
>
> On Wed, Apr 10, 2013 at 5:55 PM, Todd Mueller <toddmueller at gmail.com 
> <mailto:toddmueller at gmail.com>> wrote:
>
>     Maybe this . . .
>     http://www.carrier-lost.org/blog/syslog-ng-on-vserver-with-debian-lenny.
>
>     Google.
>
>     On Tue, Apr 9, 2013 at 1:33 PM, Brad Alexander <storm16 at gmail.com
>     <mailto:storm16 at gmail.com>> wrote:
>     > I just provisioned my first VM in quite a while. The template I
>     used was a
>     > rather old Debian/sid...So I upgraded and dist-upgraded it.
>     During the
>     > install, I got an error that none of the other containers are
>     getting this
>     > error:
>     >
>     > [....] Starting system logging: syslog-ngError opening file for
>     reading;
>     > filename='/proc/kmsg', error='Operation not permitted (1)'
>     > Error initializing source driver; source='s_all', id='s_all#2'
>     > Error initializing message pipeline;
>     >  failed!
>     > invoke-rc.d: initscript syslog-ng, action "start" failed.
>     > dpkg: error processing syslog-ng-core (--configure):
>     >  subprocess installed post-installation script returned error
>     exit status 1
>     >
>     > Which means I can't install the plethora of syslog-ng-* packages
>     that
>     > require syslog-ng to be configured.
>     >
>     > Does anyone know the cause of this? It doesn't happen on any of
>     the other
>     > containers on this box...
>     >
>     > Thanks,
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/users/attachments/20130422/d65431a3/attachment.html>