NetXMS Forum

Hi, I see that database writer queue is quite high (5721598 in log file you've sent). Try to monitor it for some time (you can use internal DCIs on server node or debug console command "show queues"). If it is constantly growing it may indicate database performance issue and can cause excessive memory consumption (because more and more data kept in memory). Best regards, Victor

Hi, I don't see anything wrong in the dump - all threads seems to be waiting on something. Try to comment out all subagents in nxagentd.conf and restart agent. If CPU usage stay low, enable them one by one to find out which is responsible. Best regards, Victor

There is MySQL monitoring subagent, it could possibly work on MariaDB as well, but it seems to be not documented. You can get some information from it's source code here - https://github.com/netxms/netxms/tree/master/src/agent/subagents/mysql and I will ask next week to update administration guide as well. Best regards, Victor

@zachow said in installing on Centos 7: @91jme said in installing on Centos 7: You may find the directory is actually "/usr/local/lib/netxms/". Thanks for the suggestion. I took a look, and there is a .ddr file, but this doesnt seem to be the DB file. (I have attached screenshot) I havent changed any settings regarding the DB. Any other suggestions? Have you already tried starting the daemon as root? "sudo /usr/local/bin/nxagentd -d"?

Assuming you want to compile with MQTT support, you'll need to install the matching mosquitto-devel package. https://breadfit.wordpress.com/2015/06/24/installing-mosquitto-under-centos/ might help (it's a guide on installing Mosquitto on CentOS 7, not specifically mentioning the mosquitto-devel package though). If you don't need MQTT, simply compiling without it should remove the need for mosquitto-devel.

Hi, are you sure you download correct agent again? I just downloaded agent 2.2.4 (https://netxms.org/download/releases/2.2/2.2.4/nxagent-2.2.4-linux-x86_64.tar.gz) and get the following ldd output:     linux-vdso.so.1 =>  (0x00007fffe67fb000)     libappagent.so.2 => /home/victor/tmp/agent/opt/netxms/lib/libappagent.so.2 (0x00007fe6af982000)     libnxagent.so.2 => /home/victor/tmp/agent/opt/netxms/lib/libnxagent.so.2 (0x00007fe6af77d000)     libnxdb.so.2 => /home/victor/tmp/agent/opt/netxms/lib/libnxdb.so.2 (0x00007fe6af569000)     libnetxms.so.2 => /home/victor/tmp/agent/opt/netxms/lib/libnetxms.so.2 (0x00007fe6af2dc000)     libnxsnmp.so.2 => /home/victor/tmp/agent/opt/netxms/lib/libnxsnmp.so.2 (0x00007fe6af0c6000)     libnxexpat.so.2 => /home/victor/tmp/agent/opt/netxms/lib/libnxexpat.so.2 (0x00007fe6aeea3000)     libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fe6aec6e000)     libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fe6aea51000)     libssl.so.1.0.0 => /home/victor/tmp/agent/opt/netxms/lib/libssl.so.1.0.0 (0x00007fe6ae7e1000)     libcrypto.so.1.0.0 => /home/victor/tmp/agent/opt/netxms/lib/libcrypto.so.1.0.0 (0x00007fe6ae3a7000)     libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fe6ae025000)     libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fe6add1c000)     libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fe6adb05000)     libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fe6ad73b000)     libnxtre.so.5 => /opt/netxms/lib/libnxtre.so.5 (0x00007fe6ad529000)     libnxzlib.so.1 => /home/victor/tmp/agent/opt/netxms/lib/libnxzlib.so.1 (0x00007fe6ad314000)     libnxjansson.so.4 => /home/victor/tmp/agent/opt/netxms/lib/libnxjansson.so.4 (0x00007fe6ad108000)     /lib64/ld-linux-x86-64.so.2 (0x000055d0dfb86000)     libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007fe6acede000)     libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fe6accc4000)     libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007fe6acaa8000)     libjemalloc.so.1 => /usr/lib/x86_64-linux-gnu/libjemalloc.so.1 (0x00007fe6ac871000) As you see it references correct libssl library from it's own directory. Best regards, Victor

Hi! You can uninstall NetXMS server completely (it will left database intact), and then install it without installing bundled SQL Server client and attach to existing database. Best regards, Victor

Hi, currently screenshot requires read access. We can change it to separate access right in next release. I've added it as feature request: https://track.radensolutions.com/issue/NX-1147. Best regards, Victor