We noticed that NetXMS has been using the following path as the state directory for cca. 4-5 last minor versions:
org.netxms.nxmc.Startup - State directory: /var/lib/tomcat*/null/state
What's with the "/null/"?
Since this path doesn't exist by default, session settings customizations don't persist until the directory structure is manually created and rw permissions are configured for the tomcat user.
With the currently latest available version of nxmc, it seems to be working!
If possible, please make it so that it can run with the
<Loader jakartaConverter="TOMCAT" />
context setting in tomcat10. Hopefully this can be done without breaking backward compatibility.
Currently it throws an exception when attempting to do so.
This is an issue in Debian Bookworm. It has no Tomcat 9 available, only 10.
Hello,
What's the rough ETA on a Debian Bullseye build release, if any exists?
Thanks!
Thanks for your response, setting the parameter worked perfectly!
Yes, it is:
netxmsd: show flags
Flags: 0x4010906081380EF1
AF_DAEMON = 1
AF_USE_SYSLOG = 0
AF_PASSIVE_NETWORK_DISCOVERY = 0
AF_ACTIVE_NETWORK_DISCOVERY = 0
AF_ENABLE_8021X_STATUS_POLL = 1
AF_DELETE_EMPTY_SUBNETS = 1
AF_ENABLE_SNMP_TRAPD = 1
AF_ENABLE_ZONING = 1
AF_SYNC_NODE_NAMES_WITH_DNS = 0
AF_CHECK_TRUSTED_NODES = 1
AF_ENABLE_NXSL_CONTAINER_FUNCTIONS = 1
AF_USE_FQDN_FOR_NODE_NAMES = 1
AF_APPLY_TO_DISABLED_DCI_FROM_TEMPLATE = 0
AF_DEBUG_CONSOLE_DISABLED = 0
AF_ENABLE_OBJECT_TRANSACTIONS = 0
AF_WRITE_FULL_DUMP = 1
AF_RESOLVE_NODE_NAMES = 1
AF_CATCH_EXCEPTIONS = 1
AF_HELPDESK_LINK_ACTIVE = 0
AF_DB_LOCKED = 1
AF_DB_CONNECTION_LOST = 0
AF_NO_NETWORK_CONNECTIVITY = 0
AF_EVENT_STORM_DETECTED = 0
AF_SNMP_TRAP_DISCOVERY = 0
AF_TRAPS_FROM_UNMANAGED_NODES = 0
AF_RESOLVE_IP_FOR_EACH_STATUS_POLL = 1
AF_PERFDATA_STORAGE_DRIVER_LOADED = 0
AF_BACKGROUND_LOG_WRITER = 0
AF_CASE_INSENSITIVE_LOGINS = 0
AF_TRAP_SOURCES_IN_ALL_ZONES = 0
AF_SYSLOG_DISCOVERY = 0
AF_ENABLE_LOCAL_CONSOLE = 1
AF_CACHE_DB_ON_STARTUP = 1
AF_ENABLE_NXSL_FILE_IO_FUNCTIONS = 0
AF_ENABLE_EMBEDDED_PYTHON = 0
AF_DB_SUPPORTS_MERGE = 0
AF_PARALLEL_NETWORK_DISCOVERY = 0
AF_SINGLE_TABLE_PERF_DATA = 0
AF_MERGE_DUPLICATE_NODES = 1
AF_SYSTEMD_DAEMON = 0
AF_USE_SYSTEMD_JOURNAL = 0
AF_COLLECT_ICMP_STATISTICS = 1
AF_LOG_IN_JSON_FORMAT = 0
AF_LOG_TO_STDOUT = 0
AF_DBWRITER_HK_INTERLOCK = 0
AF_LOG_ALL_SNMP_TRAPS = 0
AF_ALLOW_TRAP_VARBIND_CONVERSION = 1
AF_TSDB_DROP_CHUNKS_V2 = 0
AF_SERVER_INITIALIZED = 1
AF_SHUTDOWN = 0
Sometime in the last few months, as we upgraded to one of the new versions of NetXMS, DNS lookups on status polls appear to have stopped working, and our dynamics DNS nodes aren't getting status polled anymore.
The option Objects.Nodes.ResolveDNSToIPOnStatusPoll is properly set to 1.
We're running version 3.8.226.
It looks like this could be a regression bug.
Please assist.
3.1.241 is displayed.
This pointed me towards the culprit: /var/cache/tomcat9 had the old cached information, which I now purged manually, and everything works now. Never had this kind of issue when upgrading previously.
Thank you.
Tried, several times. No effect. Tried older versions as well - didn't help.
Just upgraded to NetXMS version 3.2.400 from the Debian buster repository and also updated the web console with the following release:
https://www.netxms.org/download/releases/3.2/nxmc-3.2.400.war
Unfortunately, have been unable to connect to the NetXMS service via the web console; it gives the following error:
Server uses incompatible version of communication protocol (server=[52, 4, 1, 1, 1, 27, 1, 2] client=[52, 3, 1, 1, 1, 26, 1, 2])
Please assist.
