Bug 1221464 - vdsm-logrotate fails to compress core dumps
Summary: vdsm-logrotate fails to compress core dumps
Keywords:
Status: CLOSED DUPLICATE of bug 1265547
Alias: None
Product: vdsm
Classification: oVirt
Component: General
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-3.6.1
: ---
Assignee: Yaniv Bronhaim
QA Contact: Lukas Svaty
URL:
Whiteboard: infra
Depends On:
Blocks: 1305135
TreeView+ depends on / blocked
 
Reported: 2015-05-14 05:52 UTC by RamaKasturi
Modified: 2019-04-28 10:48 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1305135 (view as bug list)
Environment:
Last Closed: 2015-11-04 10:18:40 UTC
oVirt Team: Infra
Embargoed:
ybronhei: ovirt-3.6.z?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description RamaKasturi 2015-05-14 05:52:28 UTC
Description of problem:
vdsm logs in /var/spool/mail/root with the following message details.
To: root.eng.blr.redhat.com
Subject: Cron <root@rhs-client24> run-parts /etc/cron.hourly
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
Precedence: bulk
X-Cron-Env: <XDG_SESSION_ID=52>
X-Cron-Env: <XDG_RUNTIME_DIR=/run/user/0>
X-Cron-Env: <LANG=en_US.UTF-8>
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <MAILTO=root>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Message-Id: <20150514053101.6F1DF801AC5C.eng.blr.redhat.com>
Date: Thu, 14 May 2015 11:01:01 +0530 (IST)

/etc/cron.hourly/vdsm-logrotate:

error: error opening /var/log/core/core.25201.1431495374.dump: Permission denied
error: error opening /var/log/core/core.4944.1431000847.dump: Permission denied



Version-Release number of selected component (if applicable):
vdsm-4.17.0-785.git4db8ccb.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 RamaKasturi 2015-05-14 05:54:37 UTC
Attaching vdsm and engine logs.

http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1221464/

Comment 2 Dan Kenigsberg 2015-05-14 09:54:32 UTC
what's

 ls -lZ /var/log/core/core.4944.1431000847.dump

? Do you something of relevant in audit.log?

Comment 3 RamaKasturi 2015-05-14 10:27:06 UTC
ls -lZ /var/log/core/core.4944.1431000847.dump
-rw-------. root root system_u:object_r:virt_cache_t:s0 /var/log/core/core.4944.1431000847.dump

I see the below AVC in the audit.log but not very sure if this is relevant. copying the audit.log file to the link mentioned in comment 1.

type=AVC msg=audit(1431598677.313:1084): avc:  denied  { getattr } for  pid=18593 comm="glusterd" path="/dev/random" dev="devtmpfs" ino=1032 scontext=system_u:system_r:glusterd_t:s0 tcontext=system_u:object_r:random_device_t:s0 tclass=chr_file


type=AVC msg=audit(1431596257.010:1063): avc:  denied  { getattr } for  pid=18593 comm="glusterd" path="/dev/random" dev="devtmpfs" ino=1032 scontext=
system_u:system_r:glusterd_t:s0 tcontext=system_u:object_r:random_device_t:s0 tclass=chr_file

Comment 4 Dan Kenigsberg 2015-05-14 11:33:32 UTC
The AVCs are unrelated to the coredumps, but to /dev/random. They should be reported as glusterd bugs.

what is your `getenforce`?

do you see any mention of logrotate or the core dumps on audit.log?

Comment 5 RamaKasturi 2015-05-14 11:58:16 UTC
getenforce

Permissive

I do not see any mention of logrotate or core dumps on audit.log

Comment 6 Yaniv Bronhaim 2015-08-02 15:52:59 UTC
Hi, is this bug reproducible ? can you please provide steps that lead to it so I check better?

Comment 7 Sandro Bonazzola 2015-09-29 09:09:48 UTC
This is an automated message.
oVirt 3.6.0 RC1 has been released. This bug has no target release and still have target milestone set to 3.6.0-rc.
Please review this bug and set target milestone and release to one of the next releases.

Comment 8 Yaniv Bronhaim 2015-11-04 10:18:40 UTC
I'm quite convinced that this issue is a duplication of Bug 1265547. Therefore closing it as DUP, please re-open if I'm wrong. There are no steps for in the description that I can try to verify myself.

*** This bug has been marked as a duplicate of bug 1265547 ***


Note You need to log in before you can comment on or make changes to this bug.