Bug 1509374

Summary:	[RADOS]: "ceph log last" is not fetching exact number of lines specified
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	shylesh <shmohan>
Component:	RADOS	Assignee:	Kefu Chai <kchai>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Manohar Murthy <mmurthy>
Severity:	low	Docs Contact:	Bara Ancincova <bancinco>
Priority:	unspecified
Version:	3.0	CC:	ceph-eng-bugs, dzafman, hnallurv, kchai, kdreyer, nojha
Target Milestone:	z2
Target Release:	3.3
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	.`ceph log last` does not display the exact number of specified lines The `ceph log last <number>` command shows the specified number of lines from the cluster log and cluster audit log, by default located at `/var/log/ceph/<cluster-name>/.log` and `/var/log/ceph/<cluster-name>.audit.log`. Currently, the command does not display the exact number of specified lines. To work around this problem, use the `tail -<number> <log-file>` command.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-27 18:22:11 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:	1494421

Comment 4 Kefu Chai 2017-11-06 16:04:44 UTC

> `tail <number> <log-file>` command.

the command is 

tail -<number> <log-file>

and this is not accurate. for cluster log, <log-file> is by default /var/log/ceph/${cluster_name}.log, for audit log, /var/log/ceph/${cluster_name}.audit.log

they are configurable using "mon_cluster_log_file". in the form of 

default=/var/log/ceph/$cluster.$channel.log,cluster=/var/log/ceph/$cluster.log

see http://docs.ceph.com/docs/master/rados/troubleshooting/log-and-debug/.

Comment 10 Giridhar Ramaraju 2019-08-05 13:09:01 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 11 Giridhar Ramaraju 2019-08-05 13:10:22 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri