- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Re: Health Check
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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-09-2008 11:00 AM
тАО01-09-2008 11:00 AM
Health Check
Webes Health Check reported a problem at Wed, 9 Jan 2008 06:01:00 -0500
Hostname: tl-ms-sanman01
Version: 1.0
Error Code: E2E
Description:
Webes HeartBeat test failed to log event. Webes may not be in running state
CallStack:
Recommended Action:
Restart Webes Director or Contact HP services.
-.-.-
All services seem to be running. I've even rebooted the server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2008 04:56 AM
тАО01-10-2008 04:56 AM
Re: Health Check
Please take a look at Sam's note from:
http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1148958&admit=109447627+1199969677713+28353475
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2008 05:37 AM
тАО01-10-2008 05:37 AM
Re: Health Check
Try installing the new WEBES patch or the new Rules Update. This should solve the issue.
The links are:
WEBES Rules Update 1:
http://h18023.www1.hp.com/support/svctools/webes/50RUDownload.asp
WEBES Patch:
http://h18023.www1.hp.com/support/svctools/webes/50webespatchDownload.asp
If the problem still persists, kindly let me know.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2008 05:46 AM
тАО01-10-2008 05:46 AM
Re: Health Check
I followed the link in a prior message above and went through that process. However, even after a full reboot, I now get no notice on the wsea test, and in SEA I see no events, and if I click on the Full View beneath storage cells, it now says "Error starting manual analysis for file null". Additionally, I've now received this message twice:
System Event Analyzer reported a problem at Thu, 10 Jan 2008 08:30:14 -0500
Hostname: tl-ms-sanman01
Version: System Event Analyzer for Windows V5.0 RU1 Patch2 (Build 268)
Error Code: SEA_Analysis_HibernateThrowable
Description:
Cannot open connection
CallStack:
org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)
org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:426)
org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:119)
org.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:57)
org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1326)
com.compaq.svctools.ca.services.eventreaders.directories.HibEventDirectory.flushAddCache(HibEventDirectory.java:503)
com.compaq.svctools.ca.services.eventreaders.directories.HibEventDirectory.iterator(HibEventDirectory.java:1555)
com.compaq.svctools.ca.services.eventreaders.directories.HibEventDirectory.elements(HibEventDirectory.java:1172)
com.compaq.svctools.ca.services.analysis.engine.AbstractAnaEngine.getEvents(AbstractAnaEngine.java:360)
com.compaq.svctools.ca.services.analysis.engine.AnaEngineAuto.analyzeEventList(AnaEngineAuto.java:292)
com.compaq.svctools.ca.services.analysis.engine.AnaEngineAuto.analyzeDir(AnaEngineAuto.java:221)
com.compaq.svctools.ca.services.analysis.engine.AnaEngineAuto.run(AnaEngineAuto.java:698)
Recommended Action:
Re-initialize the HSQL database.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2008 07:21 AM
тАО01-10-2008 07:21 AM
Re: Health Check
Below is what needs to be done with attemps to reinitialize the database in v5.0. We have had some good success, but note it has not fixed every issue.
If it doesn't work, I would be on the lookout for WEBES v5.1, which is due out VERY soon. If not, you may consider re-install WEBES v5.0, without saving the configuration.
Also, we have seen by putting the patch on an already broken WEBES, it may not resolve the issue or prevent "e2e" failures.
****************************
* Stop DESTA and WCCProxy (net stop desta_service & wccproxy stop)
* Run C:\program files\hewlett-packard\svctools\common\share\WebesJavaKill.exe
* Save and clear the Windows Application event file
* Delete the following files in C:\program files\hewlett-packard\svctools\specific\desta\data
- destadb.*
- ed.*
- wbemdb.*
* Restart DESTA (net start desta_service) NOTE:WCCproxy automatically starts
* Test with wsea test.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2008 08:03 AM
тАО01-10-2008 08:03 AM
Re: Health Check
The process to reinit the db seems to have repaired whatever was wrong as far as the database connection issue. And, the SEATEST notices are coming through now.
I won't know for a few hours whether those pesky e2e's are gone or not however.
Thanks for the help, and I'll watch for 5.1.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2008 11:53 AM
тАО01-12-2008 11:53 AM
Re: Health Check
Can you let us know if the E2E events are still coming up.
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-14-2008 05:45 AM
тАО01-14-2008 05:45 AM
Re: Health Check
Thanks!
Warren
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2008 08:04 AM
тАО03-12-2008 08:04 AM
Re: Health Check
The e2e's have returned. I tried the same process again to get rid of them and that didn't help this time. So I downloaded and installed the latest Webes 5.1 and update 2 for it. Still getting the e2e warnings.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2008 11:24 AM
тАО07-02-2008 11:24 AM