Bug 711359 - monitoring fails to check disk usage, when running gnome under root
Summary: monitoring fails to check disk usage, when running gnome under root
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Monitoring
Version: 541
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2011-06-07 09:57 UTC by Jiri Kastner
Modified: 2015-05-29 20:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-29 20:11:16 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jiri Kastner 2011-06-07 09:57:43 UTC
Description of problem:
gnome mounts under logged user $HOME/.gvfs gvfs file system, which is accessible only by logged user. if there is logged root user, disk usage probe fails due permission denied on /root/.gvfs.

Version-Release number of selected component (if applicable):
satellite 5.4.1

How reproducible:
when root is running gnome session

Steps to Reproduce:
1. enable monitoring on satellite
2. enable monitoring scout on satellite
3. on client install rhnmd
4. register client to satellite
5. on system create disk usage probes, one for root and one for home (when necessary) interval 1 min.
6. on client install vnc server and whole GNOME Desktop Env. group
7. login as root to client and run vncpasswd and vncserver
8. if necessary edit /root/.vnc/xstartup to launch gnome session
9. vncserver -kill :1
10. on webui push monitoring scout
11. wait when monitoring tab on system shows some status
12. when there is no waiting probe, go to client and run vncserver under root
13. check probe status

  
Actual results:
Status:	UNKNOWN, Command failed with status 1: /bin/df: `/root/.gvfs': Permission denied

Expected results:
Status: CRITICAL, GOOD, etc... some known status

Additional info:


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