Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Cannot start tc Runtime server via Control Actions

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.5 Sprint 28, 4.5 M6, 4.5
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    HQ-server 4.5.0-EE-91 running on RHEL 5.4
    HQ-agent 4.5.0-EE-91 running on CentOS 5.4
     - tc Server 2.5.0.CI-156 installed on hq-agent
  • Case Links:
    none
  • Regression:
    No
  • Tags:

Description

Cannot start tc Runtime server via Control Actions.

Executing the Start command via Control Action results in Error with the Command Status:

cannot touch `/opt/springsource/springsource-tc-server-standard/myserver/logs/catalina.out': Permission denied /opt/springsource/springsource-tc-server-standard/tomcat-6.0.29.B.CI-3/bin/catalina.sh: line 338: /opt/springsource/springsource-tc-server-standard/myserver/logs/catalina.out: Permission denied /opt/springsource/springsource-tc-server-standard/tomcat-6.0.29.B.CI-3/bin/catalina.sh: line 349: /opt/springsource/springsource-tc-server-standard/myserver/logs/tcserver.pid: Permission denied

The command was issued as hqadmin user.

The agent.log reports:
2010-09-08 16:59:05,329 DEBUG [Thread-234] [ActionThread] Adding job 10607 to 2:11514 queue
2010-09-08 16:59:05,329 DEBUG [Thread-234] [ActionThread] Running job 10607
2010-09-08 16:59:05,329 INFO [Thread-234] [TomcatServerControlPlugin] doCommand args=[/opt/springsource/springsource-tc-server-standard/myserver/bin/tcruntime-ctl.sh, start]
2010-09-08 16:59:05,350 DEBUG [Thread-234] [Execute] Waiting process
2010-09-08 16:59:07,396 DEBUG [Thread-234] [Execute] End waiting, stop threads
2010-09-08 16:59:07,396 DEBUG [Thread-234] [Execute] Watchdog stopped
2010-09-08 16:59:07,396 DEBUG [Thread-234] [Execute] Stream handler stopped
2010-09-08 16:59:07,396 DEBUG [Thread-234] [Execute] Done exit=1 /opt/springsource/springsource-tc-server-standard/myserver/bin/tcruntime-ctl.sh start
2010-09-08 16:59:07,396 INFO [Thread-234] [TomcatServerControlPlugin] doCommand result=-1, exitCode=1
2010-09-08 16:59:07,397 DEBUG [Thread-234] [ActionThread] Removed job 10607 from the queue

Expected Result:
Able to execute Control Action via UI successfully

Actual Result:
Start Control Action fails

Steps to Reproduce:
1. Install and start hq-agent on platform running tc Server
2. Log into Hyperic
3. Add to inventory from auto-discover
4. Go to Inventory tab and set Configuration Properties for tc Runtime
5. Go to Control tab
6. Stop the tc Server from the command line
7. Select Start from the Control Action dropdown list
8. Click the Execute (play) button
9. Note the process times out with the reported Error failure

Work around:
Start tc Server with command line option

Additional Information:
The tc Server Standard 2.5.0.CI-156 build was used with the springsource-tc-server-hq-plugin-server/agent-2.5.0-Ci-64 build.

Activity

Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    42 weeks, 1 day ago