NetXMS Support Forum

Is there a documentation of the cache feature?
There are 3 level for this feature:

• server default setting 'DefaultAgentCacheMode' (which number is which setting?)
• settings on the agent (on, off, default, is default the setting from the server settings?
• settings on the individual DCI (on, off, default)

Are there limitations with V2.0-RC2?

thanks
Dani

I was out of office for a few hours.
But now I recompiled the server with your patched file. I also revert the agent on the NetXMS server itself back to cache mode = default. Then I rebooted the NetXMS server. The problem is here again. So I stopped the agent and deleted nxagentd.db again and started the agent again.
Now It's quite ;-)
Than I rebooted the server again for testing. At the moment I see the problem no more.
But to be sure I have to check again tomorrow.

Thanks Victor and Alex

Dani

see attached file from the agent on the NetXMS server itself:

Ok, I started the server, turned off the cache mode for the agent on the NetXMS server.
Than I deleted nxagent.db and started the agent. All the DCIs on other nodes where the NetXMS server is the source node (on these DCIs there is still cache enabled because of this thread: https://www.netxms.org/forum/general-support/best-practice-to-analyse-event-'sys_thread_hang') get no values.

So i rebooted the server once. After that I got again 500 false alerts.

I have to shutdown the server again.

edit:
I only disabled the agent on the server and started the server again (I had to disable my EPP rule which automaticaly restarts the agent when crashed)

thanks
Dani

Hi Victor

The download link is ok now, thanks for that.

After deleting the nxagent.db file and restart of server and agent, it's quite for a few seconds or minutes. After that the same goes on, 1000 of the same error messages in the agent log and 1000 up and down emails in a few minutes.
I have to stop the agent and server again. When I only stop the agent, the agent is autom. restarted after a while.

kind regards
Dani

After update from V2.0RC1 to V2.0RC2 we get thousands of this errors in the nxagentd-log on the NetXMS server:

[17-Oct-2015 12:18:14.018] [ERROR] SQL query failed (Query = "INSERT INTO dc_queue (server_id,dci_id,dci_type,dci_origin,snmp_target_guid,timestamp,value) VALUES (?,?,?,?,?,?,?)"): UNIQUE constraint failed: dc_queue.server_id, dc_queue.dci_id, dc_queue.timestamp

So we also get thousands of false alarms (and emails) per minute.

Server is Linux x64 build from sources.

I have to stop the agent. Maybe revert to RC1. Or is there a quick fix?

best regards
Dani

Edit:
Once we get this error in server log:
[17-Oct-2015 12:32:03.639] [ERROR] SQL query failed (Query = "INSERT INTO alarm_events (alarm_id,event_id,event_code,event_name,severity,source_object_id,event_timestamp,message) VALUES (?,?,?,?,?,?,?,?)"): 23505 ERROR:  duplicate key value violates unique constraint "alarm_events_pkey"
DETAIL:  Key (alarm_id, event_id)=(9342, 5208076) already exists.


On the download page the Generic Linux static version for x64 is missing.

Hi Victor

Thanks you for your analyse.
I changed all 'Service-Check'-DCIs to Agent Cache Mode = ON (are all DCIs with Soucre-node = NetXMS server). Seems to be the solution (ok a little bit early for all-clear)!

Is this feature fully implemented now in V2.0-RC1?
Is there also a disadvantage of Cache-mode=on or is it ok to change all agent-DCIs to cache-mode=on?
What are the possible values for server configuration variable "DefaultAgentCacheMode"? I couldn't found it in the Wiki.
Is there a short documentation of the agent-cache-mode feature?


thanks
Dani

Hi Victor

Here the output.

thanks
Dani

We also have no solution yet.

We use the attached MIBs to monitor HP server through HP iLO (LOM).

We see this problem also again, here on V2.0-RC1 on Linux x64.

Console to server: TCP 4701
Server to agent: TCP 4700

ok, so I moved the content of these folders manually:

• images
• files
• packages
• backgrounds

and removed the old folders in 'share'. Maybe that helps others

Thanks Victor for your fast reply. That fixed it!
Are there other changes in directory structure? And are they documented anywhere?
Maybe I can delete some old dirs not used anymore.

edit1:
I see that Server File Manager files are not moved to the new directory too.