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

WebLogic Plugin Control Action Start cannot start WebLogic

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.3
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    HQ-server 4.3.0-EE-1433 running on CentOS 5.4
    HQ-agent 4.3.0-EE-1433 running on RHEL 5.4
     - Oracle WLS 11gR1 (10.3.2) running with HQ-agent
  • Case Links:
    none
  • Regression:
    No

Description

WebLogic Plugin Control Action Start cannot start WebLogic. After approximately 10 minutes, the command status reports an error:

Cannot run program "../../bundles/agent-4.3.0-EE-
1434/pdk/../background.sh" (in directory
"/opt/s2/wls/wlserver_10.3/domains/HQTestDomain"):
java.io.IOException: error=2, No such file or directory

Expected Result:
The Control Action Start should function just as the Control Action Stop correctly works.

Actual Result:
The Control Action Start does not start WebLogic.

Steps to reproduce:
1. On WLS server, install hq-agent
2. Ensure hq-agent is running and WLS is auto-discovered by HQ
3. Log into the HQ Server Dashboard
4. Browse and select the WLS platform
5. Select the WLS Admin Server from under the Deployed Servers Health section
6. Select the Control tab
7. Select Stop from the Control Action and click the execute (play) button
8. Note WebLogic is successfully stopped
9. Select Start from the Control Action and click the execute (play) button
10. Note the operation times out and the reported error is displayed

Work around:
Manually restart WebLogic from the WLS server using startWebLogic.

Additional Notes:
Agent.log reports:
2010-05-12 16:55:05,987 ERROR [ScheduleThread] [ScheduleThread] Metric unreachable: java.net.ConnectException: t3://10.150.29.94:7049: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination

See attached weblogic-start.jpg

Activity

Hide
German Laullon added a comment -
  • improve autodicovery of starts script
  • improve use of background.sh script
Show
German Laullon added a comment -
  • improve autodicovery of starts script
  • improve use of background.sh script
Hide
Frederic Calindas added a comment -

Issue still persists; cannot start weblogic.

New Command Status:
java.io.IOException: /opt/s2/hq/hyperic-hq-agent-4.3.0-EE/bundles/agent-4.3.0-EE-1443/background.sh: cannot execute Date Scheduled: 05/18/2010 03:51 PM
Elapsed Time: 00:10:02.117

Show
Frederic Calindas added a comment - Issue still persists; cannot start weblogic. New Command Status: java.io.IOException: /opt/s2/hq/hyperic-hq-agent-4.3.0-EE/bundles/agent-4.3.0-EE-1443/background.sh: cannot execute Date Scheduled: 05/18/2010 03:51 PM Elapsed Time: 00:10:02.117
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:
    40 weeks, 6 days ago