NetXMS Support Forum

If you restarted the server process and have ServerConfiguration->ImportConfigurationOnStartup set to 1 then it will overwrite templates and scripts.  This bit me a few times before I noticed it.

+1

I have thousands of these messages showing in the log file:

DCObject::isReadyForPolling: cannot obtain lock for data collection object xxxxxx

Is there something i can change to allow for more locks? or does it wait and retry the the lock on the object?

(mssql 2014, windows server 2012 r2)
thx
________

Sorry.... Netxms Version 2.1.1

Hi,

I have finally got agent-to-server connections working in version 2.1.1 (same certificate issues as Tursiops).

I created the nodes with the 0.0.0.0 address and bound the agents to the nodes and they connected, but any status or dci polls returned "<error>". 

Once I entered the external ip of the tunnel into the node everything started working.  I have about 45 of these sites set up this way and some of them have dhcp connections to their isp's so I don't know yet if a change of ip on the tunnel will break it.

Would it be possible to put some indication on the object details screen (capabilities or general grid) that a tunnel is connected and maybe its ip or id? ( assuming we have to go back to the 0.0.0.0 address )

thx

Then my next step would be to set the debuglevel on the agent to at least 5 and then telnet to agentsexternalip port 4700 then check the agents log file.

Is the node defined with the agents ip or the firewalls?

Maybe I am just blind or need more coffee....

Where can I change the number of threads for the "MAIN"  on the show threads display of the server console?

netxmsd: sho thr
MAIN
   Threads:      256 (8/256)
   Load average: 10.25 2.96 2.47
   Current load: 75%
   Usage:        100%
   Requests:     192

Most likely the template is being reloaded from xml file when the server is restarted.  It may have an autobind like
return $node->isAgent && $node->platformName like "windows-*";

You can disable the reloading of configs and templates in the server configuration:
  Key, current value, default value, need server restart?
"ImportConfigurationOnStartup","0","1","Yes"

Now you just have to figure out why it is crashing.......

Thx,  That did the trick.  History is now being kept on table DCI's.

mssql.ddr [Microsoft][SQL Server Native Client 10.0]

Microsoft SQL Server Management Studio      12.0.4100.1
Microsoft Analysis Services Client Tools      12.0.4100.1
Microsoft Data Access Components (MDAC)      6.3.9600.17415
Microsoft MSXML                  3.0 6.0
Microsoft .NET Framework               4.0.30319.42000
Operating System                  6.3.9600  (2012r2)

FYI: here is a copy of the template

Thx for the quick reply,

Yes there are about 200 or so objects doing this....

The 2 table dci's are "Switch: Stack Info" and "Switch: Port Information"

and you pointed me to the "history"  which yes whenever the "TABLE" dci's are polled the error shows in the log file and no new history is recorded.  Any newly created/recreated objects have no history being kept and any old objects only show history from rc1.

Is this a problem that i need to worry about or change?  or is there something i can check to see if it is a dci causing the problem. 

[08-Aug-2017 13:04:05.627] [ERROR] SQL query failed (Query = "INSERT INTO tdata_56226 (item_id,tdata_timestamp,tdata_value) VALUES (?,?,?)"): [Microsoft][SQL Server Native Client 10.0]COUNT field incorrect or syntax error

this is a new node (56226) that i just recreated after deleting the previous incarnation of this device. I have about 200 nodes that are all doing this .  I haven't checked them all but any that i have map to dell powerconnect switches.
These messages are filling the log files.  Is the simple solution to set LogFailedSQLQueries = no and ignore it or am I just covering up a bigger problem.


Thx.




info: 
server = netxms2.1.0 on win 2012r2 with MSSQL2014  (upgraded from 2.1rc1)
device = Dell Powerconnect 5524
driver = DELL-PWC

Template DCI's:

"ID","Origin","Description","Parameter","Data Type","Polling Interval","Retention Time","Status","Thresholds","Template"
"224355","SNMP","Switch: Stack Info",".1.3.6.1.4.1.89.53.14.1.1","<< TABLE >>","custom schedule","default","Active","",""
"224354","SNMP","Switch: Software Version",".1.3.6.1.4.1.674.10895.3000.1.2.100.4.0","String","custom schedule","default","Active","",""
"224353","SNMP","Switch: Service Tag",".1.3.6.1.4.1.674.10895.3000.1.2.100.8.1.4.1","String","custom schedule","default","Active","",""
"224352","SNMP","Switch: Port Information",".1.3.6.1.4.1.89.53.3.1.1","<< TABLE >>","7200","default","Active","",""
"224356","SNMP","Switch: Stack Units",".1.3.6.1.4.1.89.53.8.0","Integer","custom schedule","default","Active","",""
"224351","SNMP","Switch: Physical Serial Number",".1.3.6.1.4.1.674.10895.3000.1.2.100.8.1.2.1","String","custom schedule","default","Active","",""
"224350","SNMP","Switch: Model",".1.3.6.1.4.1.674.10895.3000.1.2.100.1.0","String","custom schedule","default","Active","",""
"224349","SNMP","Switch: Global Status",".1.3.6.1.4.1.674.10895.3000.1.2.110.1.0","Integer","3600","default","Active","last(1) == 5",""

There is a new system right. "View all alarm categories" that you need to enable for the user/group (even admins).

I know this is an old thread but what a difference tuning these values makes!!!!!

from around 8000-10000 in the data collection queue to less than 100.

The symptoms were timeouts in nxmc when changing anything or even just getting current dci values on a node.

So I went looking at the dci's on the server they looked normal or there was not much change since we started using netxms........or at least 2.1RC1.  But we have added a lot of objects lately, so you need to keep an eye on these values.  I increased the value of NumberOfDataCollectors from 20 -> 40 -> 80 ->160 which leveled it off at about 1000.  I finally increased it to 200 and now it seems to be able to keep up.
--------------

FYI:
netxmsd: sho stat
Total number of objects:     38382
Number of monitored nodes:   4535
Number of collectable DCIs:  22988

netxmsd: sho q
Data collector                   : 0
DCI cache loader                 : 0
Database writer                  : 0
Database writer (IData)          : 0
Database writer (raw DCI values) : 0
Event processor                  : 0
Node poller                      : 0
Syslog processing                : 0
Syslog writer                    : 0

Hope this helps someone.