- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Procurve Manager 2.2 Database Faults
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
тАО10-22-2007 07:48 AM
тАО10-22-2007 07:48 AM
Procurve Manager 2.2 Database Faults
Faulting application mysqld-max-nt.exe, version 0.0.0.0, faulting module mysqld-max-nt.exe, version 0.0.0.0, fault address 0x00138d34.
It doesn't matter if I access it using the CLI or the GUI interfaces, the service crashes. Does anyone have any insight into this problem?
stu...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-23-2007 05:42 AM
тАО10-23-2007 05:42 AM
Re: Procurve Manager 2.2 Database Faults
This sort of issue is very difficult to troubleshoot outside of the scope of the sort of data-gathering and problem isolation work of a formal trouble call.
This is not a known problem or symptom to the ProCurve Lab or Support.
Regards,
Ralph
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-23-2007 06:27 AM
тАО10-23-2007 06:27 AM
Re: Procurve Manager 2.2 Database Faults
thanks
stu...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-23-2007 09:49 AM
тАО10-23-2007 09:49 AM
Re: Procurve Manager 2.2 Database Faults
On further thought, I have a theory as to what may be going wrong, although I'll need you to give me the mySQL version so that I'll know whether my theory holds water.
I believe that mySQL tells you the version number when you execute mysql.exe from the command line.
Thanks,
Ralph
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-23-2007 10:58 AM
тАО10-23-2007 10:58 AM
Re: Procurve Manager 2.2 Database Faults
I've got version 5.0.2-alpha-nt-max running on the server.
Have we met?
stu...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-23-2007 11:32 AM
тАО10-23-2007 11:32 AM
Re: Procurve Manager 2.2 Database Faults
I am going to make a wild guess that your last name starts with a 'j', in which case I think that I have had the pleasure of working with you the past.
The correct mySQL version for PCM 2.2.1 and PCM 2.2 AU1 is '5.0.24a-community-nt-max', which is newer than the one you have installed.
There is a good chance that the failure that you've reported is fixed in the new mySQL.
Have you installed any PCM 2.2 Auto Updates yet?
Ralph
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-24-2007 10:12 PM
тАО10-24-2007 10:12 PM
Re: Procurve Manager 2.2 Database Faults
I knew I recognized your name! It's good to talk to you again.
I am up to date on PCM patches. However, I recently received some information on accessing the PCM database from an external machine. To do that, I installed the MySQL Query Browser. I am guessing that back-revved the PCM database engine. I have uninstalled the Query Browser, but the damage appears to be done.
I've tried re-applying the latest patch set to the server, but it will not re-install. I can't find any command line switches for the install program that will allow me to override this default behavior. Am I out of luck until the next PCM update is released? Or is there a way to fix this one.
I think DD has referred this to the lab folks as well, so hopefully we'll get a resolution one way or another.
thanks
stu...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-29-2007 10:22 PM
тАО10-29-2007 10:22 PM
Re: Procurve Manager 2.2 Database Faults
has Ralph solved your problem?