Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1591771

Summary: Ceph container does not log cluster logs - ceph.log
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vikhyat Umrao <vumrao>
Component: ContainerAssignee: Sébastien Han <shan>
Status: CLOSED ERRATA QA Contact: Vasishta <vashastr>
Severity: high Docs Contact:
Priority: high    
Version: 3.0CC: ceph-eng-bugs, evelu, flucifre, gabrioux, kdreyer, rperiyas, shan
Target Milestone: z5   
Target Release: 3.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rhceph:ceph-3.0-rhel-7-containers-candidate-56395-20180712024109 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1591773 (view as bug list) Environment:
Last Closed: 2018-08-10 02:48:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1572368, 1591773    

Description Vikhyat Umrao 2018-06-15 13:50:01 UTC
Description of problem:
Ceph container does not log cluster logs - ceph.log

Comment 1 Federico Lucifredi 2018-06-21 00:31:05 UTC
Seb, Gregory -- do you think this could make z5? Seems like it would make the Support team's life simpler.

Comment 2 Sébastien Han 2018-06-26 15:55:04 UTC
Yes, it's possible.

Comment 3 Sébastien Han 2018-06-27 09:34:16 UTC
Now you have the following logs in a single stream:

cluster 2018-06-27 09:28:27.023631 mon.tarox mon.0 10.41.1.161:6789/0 2 : cluster [INF] mon.tarox is new leader, monstarox in quorum (ranks 0)
cluster 2018-06-27 09:28:27.031167 mon.tarox mon.0 10.41.1.161:6789/0 3 : cluster [DBG] monmap e1: 1 mons at {tarox=10.41.1.161:6789/0}
cluster 2018-06-27 09:28:27.056775 mon.tarox mon.0 10.41.1.161:6789/0 4 : cluster [DBG] fsmap
cluster 2018-06-27 09:28:27.093329 mon.tarox mon.0 10.41.1.161:6789/0 5 : cluster [DBG] osdmap e1: 0 total, 0 up, 0 in
cluster 2018-06-27 09:28:27.109418 mon.tarox mon.0 10.41.1.161:6789/0 6 : cluster [DBG] mgrmap e1: no daemons active
debug 2018-06-27 09:28:28.127 7fa9fc122700  1 mon.tarox@0(leader).log v3 unable to write to '/var/log/ceph/ceph.log' for channel 'cluster': (2) No such file or directory
debug 2018-06-27 09:32:34.213 7faa0012a700  0 mon.tarox@0(leader) e1 handle_command mon_command({"prefix": "status"} v 0) v1
debug 2018-06-27 09:32:34.214 7faa0012a700  0 log_channel(audit) log [DBG] : from='client.? 10.41.1.161:0/2460483619'entity='client.admin' cmd=[{"prefix": "status"}]: dispatch
audit 2018-06-27 09:32:34.214789 mon.tarox mon.0 10.41.1.161:6789/0 7 : audit [DBG] from='client.? 10.41.1.161:0/2460483619' entity='client.admin' cmd=[{"prefix": "status"}]: dispatch

This is what you will see from journalctl or docker logs

You have 'cluster', 'debug' and 'audit' logs.

Comment 4 Vikhyat Umrao 2018-06-27 16:21:28 UTC
Thank you, Seb.

Comment 8 errata-xmlrpc 2018-08-10 02:48:35 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2378