I have a few Windows 2003 R2 64-bit boxes running SQL 2005 64-bit. The Hyperic agent on each box was unable to discover the SQL service. I manually added the MsSQL 2005 service and the agent successfully discovered the service and all of the databases. Is there a reason why the agent could not auto discover the service and the databases?
The best way to approach finding out what may be going on with autodiscovery is to invoke discovery manually from the command-line. This will provide us with the output that is generated when the autodiscovery runs normally.
Full documentation on invoking plugins standalone can be found here:
Hi, I have the same problem, I've tried with "java -jar pdk\lib\hq-product.jar -p mssql -m discover" but the agent has discovered nothing. What do you mean when you say I have added Mssql service manually?, by using the server web interface adding the check in the auto discover page? on the client using a command line instruction like "java -jar pdk\lib\hq-product.jar -p mssql -m discover"? or in a different way???
(The server use win2003 64bit SP1, and SQL 2005 64bit)
Let us know if the workaround helps and I'll post an update when we have the real fix.
On Jan 2, 2007, at 3:10 AM, massimo casali wrote:
> Hi, I have the same problem, I've tried with "java -jar pdk\lib\hq- > product.jar -p mssql -m discover" but the agent has discovered > nothing. What do you mean when you say I have added Mssql service > manually?, by using the server web interface adding the check in > the auto discover page? on the client using a command line > instruction like "java -jar pdk\lib\hq-product.jar -p mssql -m > discover"? or in a different way??? > > > (The server use win2003 64bit SP1, and SQL 2005 64bit) > > > Max >
It looks like you entered the IP address for the service_name property? You need to use the Service name of the Windows service.
(Windows) Start -> Administrative Tools -> Services Right click the SQL Server service, select Properties. On the General tab, use the value of 'Service name:'.
For a named instance, this will be Service name: MSSQL $YOUR_INSTANCE_NAME For the default instance, this will be Service name: MSSQLSERVER
On Jan 4, 2007, at 9:25 AM, massimo casali wrote:
> Hi, > I'have tried but it doesn't work, when I add new server, and then I > try to put on in the auto-discover database I find this message > > The configuration has not been set for this resource due to : > Invalid configuration: Error retrieving value: > \10.101.12.193:Databases(_Total)\Active Transactions > > I suppose the problem is that this is a cluster (infact the IP > address of the node is 10.101.12.190 but the answer is from the IP > of the cluster 10.101.12.193). > > I have try to add the server from the platform view of the server > 10.101.12.190 (the cluster node number 2) > > the database files are on 2 disks that are in use only in the > active node of the cluster. > > Max >
Hi, I'm sorry if I replay only today but I may work on this SQL cluster only two times a week, usually, tuesday and thursday. I have seen that the instance has the deafult name and so I do not have to use the structure MSSQL$instancename, this has resolved the problem in auto discovering but only on the active node of the cluster (so the procedure described in http://jira.hyperic.com/browse/HHQ-459 it is OK on the active node). Now I prove to do a mouve group of the cluster because on the other node I have the same message of the previous time. I also try to lunch the agent by using the cluster ip (the ip shared by the two node 10.101.12.193)
Thanks a lot for your replay, I'll try this, probabilly not today but thursday, and that I'll let you know the result.