NetXMS Support Forum

Hi,

do you have other tunnels working? It could be certificate validation issue - you can check tunnel log on server side for more information.

Best regards,
Victor

Hi,

what exact error you are getting? Did you check that web server is running and listening?

Best regards,
Victor

Hi,

we will fix it in release 2.2.2. As a workaround, edit file /usr/share/netxms/sql/dbinit_mysql.sql and change line

var_name varchar(255) not null

to

var_name varchar(63) not null

Best regards,
Victor

Hi,

In 2.2 we have switched to using Visual Studio 2017 for building Windows components. I've seen exactly this effect on Windows XP SP2 which is not supported by VS 2017 runtime (only XP SP3 is supported). For Windows Server 2003 minimum requirements is Windows Server 2003 SP2. Do you have it?
For older systems I recommend to continue using latest agent in 2.1 branch.

Best regards,
Victor

Hi,

from the dump it seems that server crashes on shutdown because it tries to deallocate resources that were not allocated. But it is not the reason to not starting, just a side effect - it is some error during initialization that cause server to abort initialization process. Could you run it with debug level set to 9 and post log file?

Best regards,
Victor

Hi,

the idea was to be able to provide updates for default templates with new server versions - for example new parameters or fixes in configuration. But seems that it brings more troubles then benefits.

Best regards,
Victor

Hi,

we fix it in 2.2.2. Since 2.2.1 server does forced type conversion of input value to DCI's data type - that helps in situation when DCI is 64 bit integer for example but input value is small and detected as 32 bit integer. Now conversion will took place only if input value is a valid numerical value - otherwise it will be passed as string as before.

Best regards,
Victor

Hi,

likely is is because syslog message does not contain year in timestamp, only month and day. Server uses current year when parsing. So most likely those messages was delayed by few seconds, and actual parsing happens after midnight, and server just use current year, which was just changed. Probably we have to add some check for it - like if resulting timestamp is one year in the future and current date is 01.01 then assume previous year.

Best regards,
Victor

Hi,

sounds very strange. Could you provide some screenshots?

Best regards,
Victor

Hi,

in what sense? Put objects on logical network maps according to sysLocation or put them on geographical map resolving location?

Best regards,
Victor

Hi,

older versions of NetXMS did create "Status" DCI automatically. Newer versions (anything after 2.0 definitely) does not. If you need status DCI on all nodes you can create template with auto apply script that always returns true.

Best regards,
Victor

Hi,

I would suggest method 2 then (using nxshell). Script is executed on your workstation using same API, so as long as you can connect with console you'll be able to run it.

Best regards,
Victor

Версию 3.0-М1 планируем выпустить в конце января или начале февраля. Стабильный релиз 3.0 - где-то в конце весны скорее всего.

Hi,

how do you run nxshell - directly from jar or using wrapper (nxshell on UNIX or nxshell.exe on Windows)?

Best regards,
Victor

Hi,

please check with netstat that agent really listening on port 4700. You can also provide agent's log on startup.

Best regards,
Victor