NetXMS Support Forum

Command line tool for integration already exist - it's called nxevent. It's available on WIndows in server and management console packages, and if you need to build it on UNIX, you must use --with-client option for configure. This tool uses client library for communication with server, and therefore requires login and password. User used for sending event must have "Send events" right on object given as source for event.

Best regards,
Victor

Sorry, looks like this will not help, because modern Windows version ignores local copy of msvcrt.dll and always use one from system directory because it's in a list of "known DLL". I suspect that there could be incompatibility with new versions of msvcrt.dll, because netxmsd.exe built with VC6. I'll try to do special build this evening.

Best regards,
Victor

Could you please try to put attached msvcrt.dll into NetXMS bin directory and restart server?

Best regards,
Victor

Hi!

It's not possible now to change event source directly - only by resending event via external commands on behalf of different node. I'll think about built-in functionality for changing event source or easy event resending.

Best regards,
Victor

Hi!

FindNodeObject can return null in two cases: if requested node was not found or access to it was denied. By default access from script running for one node to another nodes are not allowed for security reasons (because if, for example, you have a user with write access to node A and no access to node B, it can create transformation script which will access node B and get information about it, thus breaking your security settings). You can disable this behavior completely by setting server's configuration variable CheckTrustedNodes to 0. Otherwise, you have to maintain trusted nodes lists for each node being accessed from another node's scripts. For example, if $node in your scripts refers to NODE1, and you call FindNodeObject($node, "NODE2"), NODE1 must be added to list of trusted nodes for NODE2.

Hope this helps!

Best regards,
Victor

Alarm termination by regular expression implemented in 1.0.7. You have to upgrade both server and management console to be able to configure it.

Best regards,
Victor

Hi!

Please try to upgrade to 1.0.7, and select "Install PDB files" in components during upgrade. If it will continue to crash, and you are running on multiprocessor/multicore server, try to bound netxmsd process to single core by adding

ProcessAffinityMask = 1

to netxmsd.conf. This will bound server process to CPU #0. If you wish to bound to CPU #1 or other, use value 2 for CPU #1, 4 for CPU #2, 8 for CPU #3, and so on.

Best regards,
Victor

Hi all!

NetXMS version 1.0.7 is out. It's a minor bugfix release. Changes from version 1.0.6:

- Implemented automatic alarm termination using regular expressions
- Added support for ODBC connection strings in ODBCQUERY subagent and ODBC database driver
- Added server configuration parameter ProcessAffinityMask
- Fixed issues: #309, #310

Best regards,
Victor

Agent reload config on restart - so if change agent's config, you have to restart it. Maybe you just press "Save" instead of "Save & Apply" after first change?

Best regards,
Victor

Hi!

This can be done by setting "proxy" attribute for a DCI. For example, if you need to have DCI on node A, but get information from node B, you can configure DCI on node A and set it's "proxy" attribute to node B. For security reasons, you must also add node A to list of trusted nodes for node B, or disable trusted nodes checking globally.

Best regards,
Victor

No, it's secure. Login process using certificate is following:

1. Server send random challenge to client
2. Client sign server's challenge with his certificate's private key and send signed challenge along with public part of certificate to server
3. Server validates certificate using CA certificate
4. If certificate is valid, server validates challenge signature using certificate's public key
5. If signature is valid, server compares certificate subject with mapping data from user record
6. If mapping data match with certificate subject, access is granted

So, to login successfully, user must posses valid certificate with private key. Having just public part of certificate is not enough. Authentication by certificate also allows smart card login - you just need to store certificate used for login on smart card instead of local certificate store.

Best regards,
Victor

Hi!

Attached is 64 bit version. I plan to make a bugfix release in a few days. About 2nd question - in fact, attached version already supports connection strings in place of DSN names. The only limitation now is that connection string should not contain colon ( : ) character.

Best regards,
Victor

I'll try to check this. Also, could you please enable crash dump generation on server and send generated dumps to [email protected]? This can greatly simplify debugging. You can enable crash dump generation by setting two parameters in netxmsd.conf:

CreateCrashDumps = yes
DumpDirectory = some existing directory writable by server process

Also, could you please run command "nxadm -i" on server machine post output of the following commands:

show pollers
show queues
show flags
show mutex

Best regards,
Victor

I have fixed few bugs in odbcquery subagent. Could you please try attached version?

Best regards,
Victor

Hi!

You should go to properties of user account and set authentication method to "Certificate". Then, you should select certificate mapping method - either "Subject" or "Public key" - and enter appropriate information into "certificate mapping data" field. I usually use "subject" mapping. You can use openssl to read certificate's subject:


C:\Source\NetXMS-1.0.x>openssl x509 -subject -in victor.crt
subject= /C=LV/ST=Riga/L=Riga/O=Raden Solutions/CN=victor/emailAddress=email@domain
-----snip-----


or any other tool.

Best regards,
Victor