On Fri, Dec 02, 2011 at 03:16:15PM +0800, Hunt Xu wrote:
> Hi, all!
> vdsm-logrotate kept reporting errors like "error: skipping
> "/var/log/core/core.3150.1321682189.dump" because parent directory has
> insecure permissions (It's world writable or writable by group which is
> not "root") Set "su" directive in config file to tell logrotate which
> user/group should be used for rotation."
> This was caused by setting /var/log/core world-writable in vdsm.spec.in.
> After I simply added "su root root" to the /var/log/core/*.dump rotation
> configuration, it seems to be solved now.
> So is this the way to fix the problem? Or any better else?

Vdsm configures a world-writable /var/log/core/ in order to help debugging
serious bugs in RHEV nodes (i.e. libvirtd/qemu/python crash). We were aware of
the problems in this approach, and were ready to pay the price in the product
RHEV. However, this may make less sense for a community project: if someone
wants to keep his qemu core dumps, he can configure this himself, or use abrt or

However, I am not aware of the specific error that you are seeing. Which vdsm
are you using? which kernel? where is the error log shown? What is your exact
patch to vdsm/vdsm-logrotate.conf?

And most interesting: what had its core dumped? why?

vdsm-devel mailing list

Reply via email to