« Back
You are in :
Recent Topics »
OpManager »Download the Hotfix- Build 6011
What is a release without bugs or breakages?
Some suggestions:
- A good release?
A proper release?
A professional release?
Anyway - are these the only issues addressed in this release? has anything been done about the erratic SNMP (the heart of the system no less) issues people are seeing?
So far so very good
Hi,
Thanks for the suggestions:-)
These are the issues addressed in this Hot Fix. It will help to know if you have any specific SNMP-based monitoring issues. Often, the request sent by OpManager to the SNMP agent in the device gets timed out. The option here is to increase the timeout period in OpManager for the SNMP request.
Let us know the issues in your environment so that we can assist further.
Regards
Vidya
Anyway - are these the only issues addressed in this release? has anything been done about the erratic SNMP (the heart of the system no less) issues people are seeing?
Thanks for the suggestions:-)
These are the issues addressed in this Hot Fix. It will help to know if you have any specific SNMP-based monitoring issues. Often, the request sent by OpManager to the SNMP agent in the device gets timed out. The option here is to increase the timeout period in OpManager for the SNMP request.
Let us know the issues in your environment so that we can assist further.
Regards
Vidya
Hi vidya - thanks - we have actually filed a ticket, and got the same response (that its a timeout issue) but that actually isn't the problem we are seeing, as we explained as well. we did apply the timeout hack, but the problem persists, and we were informed it would be addressed in the hotfix. and it wasn't. SNMP on our hosts is *very* fast, and using other snmp tools yields good and fast results.
need the patch
If you are referring to the hotfix patch, its given in the original post above. Here is the link again:
http://manageengine.adventnet.com/products/opmanager/service-packs.html
Regards
Vidya
http://manageengine.adventnet.com/products/opmanager/service-packs.html
Regards
Vidya
Hi vidya - thanks - we have actually filed a ticket, and got the same response (that its a timeout issue) but that actually isn't the problem we are seeing, as we explained as well. we did apply the timeout hack, but the problem persists, and we were informed it would be addressed in the hotfix. and it wasn't. SNMP on our hosts is *very* fast, and using other snmp tools yields good and fast results.
Hi,
Will check up the ticket and get back to you.
Thanks
Vidya
thx
I am running OpManager on the background. It works as before, but now I cannot shutdown OpManager by script which actually calls "ShutDownOpManager.sh" in OpManager bin directory. When I try to run this shutdown script manualy (sh ShutDownOpManager.sh admin password) I get this error message:
Usage: java StandAloneShutDown [-h host] [-wp webServerPort] [-rp rmiRegPort] [-tp tcpPort] [-u username] [-p password]
Usage: java StandAloneShutDown [-h host] [-wp webServerPort] [-rp rmiRegPort] [-tp tcpPort] [-u username] [-p password] quitting
When I applied OpManager SP1 (6010) patch earlier, MibBroweser stopped to work - I get "blank page" (no error message) when I click on MibBrowser Icon. I expected that this will be fixed in new hotfix but it's not.
I would like to ask, how to change timeout (4 seconds is too short) for OpManager to connect to MySQL database during statup. It works fine when OpManager starts when the server is already UP and running, but when I try to start OpManager at server startup, it will fail.
Usage: java StandAloneShutDown [-h host] [-wp webServerPort] [-rp rmiRegPort] [-tp tcpPort] [-u username] [-p password]
Usage: java StandAloneShutDown [-h host] [-wp webServerPort] [-rp rmiRegPort] [-tp tcpPort] [-u username] [-p password] quitting
When I applied OpManager SP1 (6010) patch earlier, MibBroweser stopped to work - I get "blank page" (no error message) when I click on MibBrowser Icon. I expected that this will be fixed in new hotfix but it's not.
I would like to ask, how to change timeout (4 seconds is too short) for OpManager to connect to MySQL database during statup. It works fine when OpManager starts when the server is already UP and running, but when I try to start OpManager at server startup, it will fail.
Hi,
I am using a trial version and planning to go in for a full version within a week or two. Before that i would like to know if we can inventory the machines using this tool. I need to do the asset management viz serial no's of pcs, the HDD, RAM capacity etc etc. Is this possible ?
Regards,
Sudesh
I am using a trial version and planning to go in for a full version within a week or two. Before that i would like to know if we can inventory the machines using this tool. I need to do the asset management viz serial no's of pcs, the HDD, RAM capacity etc etc. Is this possible ?
Regards,
Sudesh
Hi,
There is a breakage in Build 6010 which causes the ShutDownOpManager.sh script to print only the usage but does not execute when the username and password arguments are passed
We will fix this in our next hotfix, expected to be released in few days.
Till then, either replace the existing script with the attached one after renaming it to .sh file, or execute without the arguments so that a dialog pops up prompting to enter user name and password. Or, do a Ctrl + C in the console where you have started OpManager to shutdown.
Sorry for the trouble caused.
Best Regards
Raja
There is a breakage in Build 6010 which causes the ShutDownOpManager.sh script to print only the usage but does not execute when the username and password arguments are passed
We will fix this in our next hotfix, expected to be released in few days. Till then, either replace the existing script with the attached one after renaming it to .sh file, or execute without the arguments so that a dialog pops up prompting to enter user name and password. Or, do a Ctrl + C in the console where you have started OpManager to shutdown.
Sorry for the trouble caused.
Best Regards
Raja
OK
Post Actions
Corp