NetXMS Support Forum

Hello.

Check this: http://wiki.netxms.org/wiki/How_to_send_e-mail_notification_when_disk_space_is_low

У нас есть свой nexus, в ближайшее время я его чуть причешу и открою публичный доступ.

Hello.

"Disable" will turn discovery off completely.

Active/passive modes:

Passive: information about new nodes are extracted from ARP and routing tables on all nodes available in NetXMS. This way you need to add at least one "seed" node (most of the time server itself is this node, and it's sufficient).
Active: same as passive, but server will scan all addresses in in configured subnets / ranges, as set in "Active discovery targets" section.

In both cases, resulting addresses can be outside of desired range (e.g. multiple interfaces on the router) and you need to filter them.
You can use either custom script (which should just return true/false) or in your case – use automatically generated script. In "Filter" section select "Automatically generate script with following rules", then check "Accept node if it is within given range or subnet" and then add all desired subnets/ranges in "Address Filters" section.

I need to check, but I think that if server was started with discovery disabled, it will be reenabled only on next server restart, so save discovery settings and restart netxmsd.

Hello.

Yes, we spent some time on it, but unfortunately can't find root of this problem. Can you please run server under valgrind, until crash?

Hello.

I just pushed schema file into git: http://git.netxms.org/public/netxms.git/blob/develop:/src/java/nxreporting/sql/mysql/nxreporting.sql

Second issue will be also fixed in 1.2.17.

You can also change column by executing query "alter table user_groups modify description null"

Hello.

For historical reasons (however I'll change that in a future), all password except quartz's, should be encrypted by nxencpasswd:AirAlk:~() $ nxencpasswd netxms netxms1
H02kxYckADXCpgp+8SvHuMKmCn7xK8e4wqYKfvErx7g=

Sample config (login=netxms, password=netxms1):
system.datasource.username = netxms
system.datasource.password = H02kxYckADXCpgp+8SvHuMKmCn7xK8e4wqYKfvErx7g=
report.datasource.username = netxms
report.datasource.password = H02kxYckADXCpgp+8SvHuMKmCn7xK8e4wqYKfvErx7g=
org.quartz.dataSource.myDS.user = netxms
org.quartz.dataSource.myDS.password = netxms1


Thank you for contributing, awesome work.

I did a quick check, and it seems that you missed couple of functions:

FindAllDCIs
GetDCIValues
_exit (instead of "exit")

There is also "nxinstall" command line tool, which provide couple more functions. I don't think that anyone except us use this tool, but here is list, just for the reference:

CopyFile
DeleteFile
RenameFile
access
chdir
fclose
feof
fgets
fopen
fputs
mkdir
rmdir
system

Hello.

It's unfinished yet, I'll try to push complete version today.

Reporting server can be downloaded here  or built from sources (http://git.netxms.org/public/netxms.git/tree/develop:/src/java/nxreporting). I also put sample configuration and report into archive.

I'm actually writing this piece of documentation right now. Will be available here later today.

Please provide backtrace of this crash (details on how to get a backtrace: https://wiki.debian.org/HowToGetABacktrace#Running_gdb)

Check nxclapi.h for complete list: http://git.netxms.org/public/netxms.git/blob/HEAD:/include/nxclapi.h?js=1#l132

Type "bt" on gdb prompt "(gdb)", this will produce complete backtrace

Note about enabled filemgr subagent on the large network, there are two ways:

1) Create configuration policy and deploy to all agents, where required.
Sample policy:
<config>
  <agent>
    <subagent>filemgr.nsm</subagent>
  </agent>

  <filemgr>
    <RootFolder>/opt</RootFolder>
    <RootFolder>/private/etc</RootFolder>
  </filemgr>
</config>

2) Use nxshell-based script to fetch existing agent config remotely, modify it and reapply. I don't have script on hand at the moment, but can share it later.

Quote from: flynao on August 04, 2014, 11:41:46 PM
the only way I found to deploy these xml files to my nodes was as follows:

I created a npi file for each file, so then I uploaded the xml files as a software using the package manager, then as usual I deployed the files to the nodes (the files have been stores at the directory set up on the agent's configuration file.

Package manager should not be affected by changes in file transfer (and introducing filemgr subagent). Could you please check it with "nxupload" command line tool? Syntax is "nxupload AGENT_IP local_file_name". File should be uploaded into FileStore (C:\NetXMS\etc in your case).

I'd use slightly different way (but you'll need file manager subagent for that):

1) Tools -> Upload File to Server (select target XML configuration as "local file", leave "remote name" empty to use local name)
2) Right click on any node or container and select "File upload". Click on "select" button and select file you uploaded in step 1, leave name blank
3) Click "Ok"