Thank you Victor! With one answer you solved two problems! Just in case anyone has the same problem I'll post the working code as example of both script: # coding: utf-8 class SetPrimaryName: def out(self): i=0 PrimaryNames = open("PATH/TO/FILE/PRIMARYNAME.TXT").readlines() for nome in open("/PATH/TO/FILE/HOSTNAMESTOMODIFY.TXT").readlines(): nodo = session.findObjectByName(nome.strip()) primaryName = PrimaryNames[i] if nodo: nodeID =nodo.getObjectId() print "To node %s with id %d I want to set Primary Name %s"%(nome.strip(), nodeID, primaryName) modificatore = NXCObjectModificationData(nodeID) modificatore.setPrimaryName(primaryName) session.modifyObject(modificatore) i+=1 spn = SetPrimaryName() spn.out() If you want to set custom attributes in already existing nodes, or if you want another example, you can find the script here.

Thanks for considering our problem for the 1.2.8 release. Best regards

I wanted to add to this thread a Windows equivalent which I needed for myself. I've added two new DCI's to my agent's config file: ExternalParameter = DNS.Lookup(*):dig +noall +short @$1 $2 A ExternalParameterShellExec = DNS.Check(*):dig +noall +short @$1 $2 A | find /c "$3" The first returns the IP looked up as I wanted to be able to check it for myself, the second is the equivalent of the example from Victor that returns just a code. The reason for the "ShellExec" is because "find" is a built-in function of the command-prompt, and "/c" returns the count. You'll also need a copy of "dig" for Windows which can be found here.

That's excellent, thanks they worked perfectly now. I think it was the 100s in the last two fields that I was not getting right.

OK, i choose to Disable SNMP for all polls for the "problematic" nodes, that are already on Netxms. The problem is resolved, thank you so much!

@anrkey said in error while loading shared libraries: libnetxms.so.1: @mariposa said in error while loading shared libraries: libnetxms.so.1: I just solve the problem, thanks anyway Forced this is what I have done : go to /etc/ld.so.conf.d/libc.conf and check if it contains line "/usr/local/lib", if not, add it run "ldconfig" as root (it will produce no output) After that run "ldconfig -p|grep libnetxms" to verify (it will have output) run /usr/local/bin/nxdbmgr init /usr/local/share/netxms/sql/dbinit_mysql.sql it will work and now you can run agent and server Thanks, this fixed me up right away Thanks! Helped for me also!

Hi! It should be in 1.2.8. Best regards, Victor

Hi! I've seen similar behavior on a site I'm supporting. In 1.2.7 I've added additional locks to ensure database integrity. Looks like this feature causing excessive internal locks under some circumstances. I'll make it configurable and turned off by default in 1.2.8. Best regards, Victor

There was the problem with housekeeper process not clearing SNMP trap log. But I have fixed this in 1.2.6 or 1.2.7. What NetXMS version you are running? Best regards, Victor

Hi! Core dump could be really helpful. Please send them to [email protected], and I'll take a look at it. Best regards, Victor

@sperlm said in scripting management functions [SOLVED]: The "null" parameter in findObjectNode was not clear to me (but it works with it too). It's a reference to already known object. Here is the explanation: http://wiki.netxms.org/wiki/SG:Security_Issues. Best regards, Victor

Hi, in attachment the export of the Event Log for the node. After the 6 June the icmp ping of the node return stable, now only snmp pool don't work. Thank you. Event_log.txt

Hi! When node will be shown as down again, try to run status poll from console and post it's output. Also, check log of agents running as proxy - they could exceed maximum number of allowed connections, so you may need to increase it. Best regards, Victor

no ideas? it would be great if somebody could take the time to respond... 

Hi Victor, i've copied it in the bin Folder and restarted NetXMS Core. I think the cause of my Problem was, that the Server had Problems with sending Mailnotifications. I'd disabled this processing and it seems to work now. I will activate the policy, so the error could hapen again.

Thank you Victor for you constant support! I'm waiting with confident. Bye, Giovanni

Hi! It's a bug. Best regards, Victor

After replacing files in C:\NetXMS\lib\sql by your files, export works. Thank you very much.

Hi! Yes, it's possible. You can define "proxy node" for any DCI. If proxy node is defined, real data collection will happen on proxy node, not n the node where DCI is configured. You have to add node where you create proxied DCI to proxy node's "trusted nodes" list, or turn off trusted nodes checking by setting server configuration variable CheckTrustedNodes to 0. A bit more detailed explanation of trusted nodes concept is here: http://wiki.netxms.org/wiki/SG:Security_Issues. Best regards, Victor

While using the source, one could still face the issue already reported for release 1.2.3 at: [b]https://www.netxms.org/forum/installation/error-compiling-v1-2-3/[\b] So as advised by Victor, deleting old NetXMS agent lib files solve the issue - at least in our scope. Br, Jdamien