Hide Forgot
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:
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.
(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
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
They're gone in Revision 1-11. LKB
this looks corrected in the pdf.. waiting for Sachin/Kedar to confirm
The CDS log location needs to be updated in the doc. /var/log/pulp-cds/gofer.log
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
<listitem> <para> <filename>/var/log/pulp-cds/gofer.log</filename> </para> <para> CDS logs </para> </listitem> Revision 1-15 LKB
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
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