Thank you for your help. Kindest regards.

Thanks.

That's it! I didn't realize it was a status object, thank you for the help! Thanks, Zach

Hi, Just found a previous post regarding MySQL database size and shrinking the file size: https://www.netxms.org/forum/general-support/mysql-db-fast-grow-how-to-free-space/ It includes a link that may help. Another link that may be helpful: http://www.thegeekstuff.com/2016/02/mysql-innodb-file-per-table/ This is not a NetXMS specific issue, it is simply how the database software itself (in your case MySQL, presumably using InnoDB) operates. Hope the links help.

Hi all, I have three nodes that are the same object (found, I assume, through network discovery). Normally when this happens, the nodes appear to have some difference between their interfaces, and I chalk the duplication up to that. However, these three have all the same interfaces. Is there any way to de-duplicate this node? They all have different primary hostnames, of course, but under the interfaces tab there's no difference. Any guesses? Thanks, Zach

Ok, Solved. Running nxdbmgr check-data-tables fixed the issue. Up and running again  Thank you for help! Ronald

Hi Victor, I've tried changing the server configuration setting AgentCommandTimeout as you suggested, but it doesn't seem to make any difference. No matter what I set that value to, the server still says the sending SMS failed and requests a second try (and then a third) after 30 seconds. The success appears approximately 41 seconds after the send request.

Hi, most likely. It could be due to slow database response - you can check that by setting server configuration parameter LongRunningQueryThreshold to non-zero value - it will log all SQL queries with execution time longer than given number of milliseconds. Best regards, Victor

If you use context menu it will extract currently selected DCIs. You can also use "export all" option in view menu (in top right corner). Best regards, Victor

P.S. Actually, for Windows servers you can use performance counters to get momentary CPU usage - select "Windows performance counter" as DCI source and configure appropriate counter.

Hi, I see few options to improve this: rename "Remove" option on template to "Remove from node" (or something similar that will not imply destruction of template itself); add context menu option "remove from template" to node under template, which will remove node from that particular template. Best regards, Victor

Implemented in 2.1-M1 (agent will be compatible with 2.0.5 server). Best regards, Victor

Hi, but desktop console can connect? Try to find log file on web UI (it is called .log and should be within application's working directory - in my case it is /var/lib/tomcat7/work/Catalina/localhost/nxmc/eclipse/workspace/.metadata/.log). Best regards, Victor

Hi, wheezy should be available now as well. Best regards, Victor

For now there is no option to create any button type widgets on dashboards. But you can create 2 Gauge objects with Text type. This type of gauge changes color depending on configuration. [image: gauge_config.png]

Looks like my issues are related to previously reported bugs regarding server crashes on deleting Instance DCIs and templates applying DCIs twice. Have updated Bugtracker accordingly. Happy to help out in any way to resolve those. Prior to finding that, I tried to just start fresh with the template by returning false on the auto-apply script. The result is that right now our NetXMS is pretty much unusable - it crashes within a minute of starting. In between it manages to delete some of the DCIs that is has in it's queue for deletion (turned on debug logging to level 9 to see the queries). I'm running netxmsd in a while loop now to restart within 15 seconds of crashing. I'm not expecting to get any useful data out of this, but do hope it will eventually catch up with the deletions... If it still has issues after a day, I'll probably have to dig into the database to work out what I need to remove and do it manually.

Personally I haven't done this yet, but I would try this: Create a PowerShell script that collects all the data you want/need. The script should either push all that information into a separate event log entry or mail it straight out (I would assume both of these would work with PRTG monitoring, too?) Create an Action in the agent's configuration file to run that PowerShell script Create a new event and configure event processing policies to trigger the action you just created when your newly created event is triggered Configure the CPU DCI to probably check every 5 seconds, set the threshold to trigger the event you created on three consecutive values over 80% If your script just sends a mail directly, that'd be it. If the script creates an event log entry, you'd also have to set up event log monitoring in NetXMS for your Windows system and create another event (in NetXMS) and action to be triggered (moving the email/SMS or whichever action you wish to trigger to the NetXMS server). See https://wiki.netxms.org/wiki/UM:Log_Monitoring

Ok, this will probably be much faster in person. Feel free to add me on Skype at t.kirnak[at]atris[dot]sk.

Thanks Victor.  Just did an upgrade to 2.0.4 (which was surprisingly easy) and it's all good now. Rich

Never mind i figured it out.  I just did a mysql dump then restore on the new server and then ran the nxdbmgr upgrade ... Not sure why but when I tried using nxdbmgr to export then import on the new server it always failed