NetXMS Support Forum

Hi,

just sent upload link in PM.

Best regards,
Victor

So rest of connections were not discovered. I see that all discovered connections were discovered using spanning tree information. This is less reliable method and used by server as last resort. Is it possible to turn on LLDP or CDP on your switches? It will greatly improve discovery accuracy. If not possible, make sure that you have spanning tree protocol enabled on all switches.

Best regards,
Victor

Seems that they are not published. However, you can find javadoc archives in Maven Central: http://central.maven.org/maven2/org/netxms/netxms-client/2.2.6/netxms-client-2.2.6-javadoc.jar

Best regards,
Victor

Hi,

I cannot reproduce this issue. Could be packaging error. How do you run nxshell and what package you are using?

Best regards,
Victor

Hi,

those methods was renamed in 3.0. For 2.2 branch, use syncEventTemplates, getCachedEventTemplates and findEventTemplateByCode.

Best regards,
Victor

Hi,

it is deprecated in 3.0 branch (latest javadoc generated from 3.0), you can safely use it in 2.2 branch. In 3.0 you should call DataCollectionConfiguration.modifyObject with data collection object ID set to 0 (but this will not work in 2.2).

Best regards,
Victor

Hi,

getScriptLibrary() call intended to retrieve list of available scripts (because script source could be quite big). Source code for each script should be retrieved individually using getScript() method. The following script will show sources for all scripts:


scripts = session.getScriptLibrary()
for script in scripts:
    script = session.getScript(script.getId())
    print('id={0} name={1} source={2}'.format(
             script.getId()
            ,script.getName()
            ,script.getSource()
        )
    )


Best regards,
Victor

Hi,

can you share exact errors you have? What database driver you are using?

Best regards,
Victor

Can you please reproduce timeout issue again, with server running at debug level 7 and agent at debug level 6, and send me synchronized log files for period during synchronization?

Best regards,
Victor

It looks that from time to time database cannot cope with incoming data rate and so writer queue grows. You may need to fine tune your database server. But it seems to happen on few occasions so it should not be a root cause for data synchronization timeouts.

Best regards,
Victor

Hi,

please check object ID for MAINCR_GSX (you can find it on overview tab), then run the following command on NetXMS server command line:

nxadm -c "show topology <id>"

(replace <id> with actual node ID) and post it's output.

Best regards,
Victor

Hi,

what is your idata writer queue size? You can check it in server debug console with command "show queue". If you have historical graph for idata queue please also share it.
Also, how many DCIs you have? You can check it in server debug console with command "show stats".

Best regards,
Victor

Hi,

looks like server is locked on sending object updates to one of user sessions. We encounter same issue in another installation recently and already changed object update notification mechanism in current development branch, so there are good chance that upgrade to 2.2.9 will fix your issue.

Best regards,
Victor

Hi,

load on thread pool MAIN is definitely not normal. Could you please capture thread stack traces using attached script (you will need gdb installed)?

Best regards,
Victor

I was able to reproduce this issue. It is fixed in development branch and fix will be included into next release.

Best regards,
Victor