Bug 706045

Summary: Required changes in monitoring section
Product: Red Hat Update Infrastructure for Cloud Providers Reporter: Sachin Ghai <sghai>
Component: DocumentationAssignee: Lana Brindley <lbrindle>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.0CC: jason.dobies, kbidarka, mhideo, tsanders
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-29 04:48:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Sachin Ghai 2011-05-19 10:05:54 UTC
Description of problem:
As per the current implementation, following things needs to be there in RHUI2.0 install guide under monitoring section.

Version-Release number of selected component (if applicable):
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/pdf/Installation_Guide/Red_Hat_Update_Infrastructure-2.0-Installation_Guide-en-US.pdf

How reproducible:


Steps to Reproduce:
==>Chapter 11
==> Monitoring the RHUI (Page 60 )

  
Actual results:


Expected results:
IN RHUI2.0, we can check the status of CDS instances using "rhui-manager status" command:

Status codes:

we can check the status by numeric codes; as per my knowledge two status codes are available at the moment:

Status Code:

0 --> Sucess
1 --> Failure ( like when CDS node is down; resultant status code would be 1 )

---------------------------------------------------------------------------
[root@dhcp193-136 ~]# rhui-manager status
cds0073 ..................................................... [  UP  ]

[root@dhcp193-136 ~]# rhui-manager status --code
0

[root@dhcp193-136 ~]# rhui-manager status
cds0073 ..................................................... [ DOWN ]

[root@dhcp193-136 ~]# rhui-manager status --code
1
----------------------------------------------------------------------------



Required changes in log files location:
===========================================

As per the current implementation, following log files needs to be there in RHUI2.0 documentation

On RHUI-Manager
==========

rhui-manager logs should be at:  ~/.rhui/rhui.log


ON RHUA Server:
===========
RHUA logs should be at:  /var/log/pulp/pulp.log

Package synchronization logs:  /var/log/pulp/grinder.log

I *think* following note is applicable for both pulp.log/grinder.log

Note: The pulp.log file is automatically written to a new enumerated log file when the base file reaches 1MB in size. The most recent four versions are kept in addition to the currently written file.


On CDS server:
============
/var/log/pulp-cds/gofer.log




Additional info:

Comment 1 Sachin Ghai 2011-05-19 10:34:27 UTC
I logged this defect just to track the monitoring section. 

I'm not completely aware about all changes since product is still under development. So copying to Jdob on this defect for review/update the contents for this section.

Comment 2 Lana Brindley 2011-05-24 04:15:30 UTC
(In reply to comment #0)
> Description of problem:
> As per the current implementation, following things needs to be there in
> RHUI2.0 install guide under monitoring section.
> 
> Version-Release number of selected component (if applicable):
> http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/pdf/Installation_Guide/Red_Hat_Update_Infrastructure-2.0-Installation_Guide-en-US.pdf
> 
> How reproducible:
> 
> 
> Steps to Reproduce:
> ==>Chapter 11
> ==> Monitoring the RHUI (Page 60 )
> 
> 
> Actual results:
> 
> 
> Expected results:
> IN RHUI2.0, we can check the status of CDS instances using "rhui-manager
> status" command:
> 
> Status codes:
> 
> we can check the status by numeric codes; as per my knowledge two status codes
> are available at the moment:
> 
> Status Code:
> 
> 0 --> Sucess
> 1 --> Failure ( like when CDS node is down; resultant status code would be 1 )
> 
> ---------------------------------------------------------------------------
> [root@dhcp193-136 ~]# rhui-manager status
> cds0073 ..................................................... [  UP  ]
> 
> [root@dhcp193-136 ~]# rhui-manager status --code
> 0
> 
> [root@dhcp193-136 ~]# rhui-manager status
> cds0073 ..................................................... [ DOWN ]
> 
> [root@dhcp193-136 ~]# rhui-manager status --code
> 1
> ----------------------------------------------------------------------------
> 

This is mentioned in the RHUI Manager section, "Using RHUI Manager from the Shell Prompt": http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/html/Installation_Guide/sect-Installation_Guide-RHUI_Manager-Using_RHUI_Manager_from_the_Shell_Prompt.html

This Monitoring section only covers monitoring that can be performed within RHUI Manager, not at the shell prompt.

> 
> 
> Required changes in log files location:
> ===========================================
> 
> As per the current implementation, following log files needs to be there in
> RHUI2.0 documentation
> 
> On RHUI-Manager
> ==========
> 
> rhui-manager logs should be at:  ~/.rhui/rhui.log
> 
> 
> ON RHUA Server:
> ===========
> RHUA logs should be at:  /var/log/pulp/pulp.log
> 
> Package synchronization logs:  /var/log/pulp/grinder.log
> 
> I *think* following note is applicable for both pulp.log/grinder.log
> 
> Note: The pulp.log file is automatically written to a new enumerated log file
> when the base file reaches 1MB in size. The most recent four versions are kept
> in addition to the currently written file.
> 

I have updated the table in this chapter. Please review on the stage for accuracy.

Revision 1-9.

LKB

Comment 3 Sachin Ghai 2011-05-26 08:33:15 UTC
Thanks for updating the log section. However we need to remove existing log files. 

Please remove following logs files:
/var/log/rhui.log
/var/log/rhua/rhua.log
/var/log/cds/repo_entitlement.log

and add one more log location for CDS:

/var/log/pulp-cds/gofer.log

Comment 4 Lana Brindley 2011-05-26 23:28:49 UTC
They're gone in Revision 1-11.

LKB

Comment 5 wes hayutin 2011-05-27 02:19:39 UTC
this looks corrected in the pdf.. waiting for Sachin/Kedar to confirm

Comment 6 Kedar Bidarkar 2011-05-27 07:41:43 UTC
The CDS log location needs to be updated in the doc.

/var/log/pulp-cds/gofer.log

Comment 7 Sachin Ghai 2011-06-24 06:42:00 UTC
Verified under revision 1-14, CDS log location still missing under Monitoring section in the doc at

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/pdf/Installation_Guide/Red_Hat_Update_Infrastructure-2.0-Installation_Guide-en-US.pdf

Comment 8 Lana Brindley 2011-06-26 20:41:40 UTC
<listitem>
	<para>
		<filename>/var/log/pulp-cds/gofer.log</filename>
	</para>
	<para>
		CDS logs
	</para>
</listitem>

Revision 1-15

LKB

Comment 9 Sachin Ghai 2011-06-27 05:46:27 UTC
Fixed under revision 1-15. 

Added CDS log location under Monitoring section at:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/html/Installation_Guide/chap-Installation_Guide-Monitoring_the_RHUI.html

Chapter 10: Monitoring the RHUI

Comment 10 Lana Brindley 2011-07-29 04:48:50 UTC
This book is now available at http://docs.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/html/Installation_Guide/index.html

Please raise a new bug for any further changes.

LKB