Unable to Poll - Timestamp and Status not Updating

Started by Sympology, August 19, 2008, 02:46:18 PM

Previous topic - Next topic

Sympology

I'm having trouble polling devices. SNMP traps are ok and the Performance charts for CPU, Disk etc work.

I'm setting up a Data Collection for NetXMS Agents

I select ServiceCheck.Custom(SQLSERVER) Data type Integer. (I Have tried other services)

I click OK and poll the Node, it comes back Value 0 (which I know means running) but the Time Stamp is always 01-Jan-1970 00:00:01.
If I stop the service the Value never changes from 0, even if I poll again.

I get the same when polling SNMP devices, but that my be the devices themselves :-(

Have I forgotten to do something?

Victor Kirhenshtein

Quote from: Sympology on August 19, 2008, 02:46:18 PM
I'm setting up a Data Collection for NetXMS Agents

I select ServiceCheck.Custom(SQLSERVER) Data type Integer. (I Have tried other services)

ServiceCheck.Custom intended to check TCP connectivity. If you wish to check state of Windows service, you should use parameter System.ServiceState, like below:


System.ServiceState(SQLSERVER)


Best regards,
Victor

Sympology

Thanks for the answer. But I'm unable to still get stats. However I'm thinking, does the system need AD permisions to access the data.
For example our test monitoring system is a local system, but the server is a Domain server. Should the Monitoring server be on the domain as well?

Sympology

Forgot to mention, Status says "Not Supported"
Server is Windows 2003

Victor Kirhenshtein

No, it shouldn't be in a domain. All information gathered via NetXMS agent, which by default is running under Local SYstem acount and usually has all necessary rights. Problem is that for MS SQL Server service name is MSSQLSERVER, so correct parameter should be

System.ServiceState(MSSQLSERVER)

Best regards,
Victor

Sympology

Thanks for the reply. I had made a mistake but had problems with others. However now have it working

On our network it seems
Monitoring system- NetXMS Core service has to run under domain\Account that has access to the servers.
The agent on the server is ok under service account.

Thanks for your help. A great product! still much to learn  ;D