- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Webes HeartBeat test failed to log event. Webes ma...
Insight Remote Support
1745857
Members
4738
Online
108723
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2010 10:02 AM
01-11-2010 10:02 AM
Webes HeartBeat test failed to log event. Webes may not be in running state
Webes 5,6, update 1 set up on a windows 2003 64 Bit Enterprise node.
Every time the scheduled job runs to do the end ot end san check, it generates the alert.
I have trusted the version of Java that comes with webes (1.6.12) and log notification is on. Restarting the server and desta service does not make a difference. I have cleared out the application log and manually restarted all webes services but it consistently generates the alert.
The monitoring system is for a command view 8000, 8100 and 4000. It seems to be detecting events ok as alerts for hardware failure and merging states seems to make a difference.
Webes is not installed in the defualt directory as it is installed in c:\program files (x86)\hp\svctools\. The software works from another client where it is running on a 32 bit node and installed to the defualt directory.
I have a tciket open with HP but am finding it difficult to contact them as I missed their call.
Every time the scheduled job runs to do the end ot end san check, it generates the alert.
I have trusted the version of Java that comes with webes (1.6.12) and log notification is on. Restarting the server and desta service does not make a difference. I have cleared out the application log and manually restarted all webes services but it consistently generates the alert.
The monitoring system is for a command view 8000, 8100 and 4000. It seems to be detecting events ok as alerts for hardware failure and merging states seems to make a difference.
Webes is not installed in the defualt directory as it is installed in c:\program files (x86)\hp\svctools\. The software works from another client where it is running on a 32 bit node and installed to the defualt directory.
I have a tciket open with HP but am finding it difficult to contact them as I missed their call.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP