Thank you! Just added to the source tree. Note that before nxmc had only Chinese Traditional translation, so I have added yours as separate language entry "Chinese (Simplified)". Could you please also translate client error messages in src/client/java/netxms-client/src/main/resources/netxms-client-messages.properties? Best regards, Victor

Hi, Thank you for the effort. I'm not sure you'll be able to push it (judging by other pending issues in RCP/RAP), but there is good news as well - we'll migrate away from RAP in the near future. The new web is built from scratch and not Java-based. It currently exists as an internal beta.

That's due to user-configurable tool nature. If all system users use same language, you can just change tool names in server configuration. However, if different language must be supported currently there is no solution. I've registered issue in our tracker for adding localization support to object tools: https://github.com/netxms/netxms/issues/3243

Portuguese-Brazil translation file is src/client/nxmc/java/src/main/resources/po/pt_BR.po. Link to current version in repository: https://github.com/netxms/netxms/blob/84ef97d41905f3dc2cdf39a8b5c52d234b3fe1c0/src/client/nxmc/java/src/main/resources/po/pt_BR.po You can either edit it and send us updated version, or create a pull request with updated texts. Thank you! Best regards, Victor

Hello Alex! Thank you for your fast reply. The documentation states that there is a specific MariaDB driver and the “netxms-dbdrv-mariadb” package for Debian: https://www.netxms.org/documentation/adminguide/installation.html#mariadb So it didn’t exist on the Docker image, and I should use MySQL instead even after DB init? Because DB initialization still fails when using MariaDB as DBDriver on Docker, I think there's some issue where the code is not sharing the same code init template with MySQL for some reason. Edit: My bad, the fix works as expected; there is a PR that improves the error handling at: https://github.com/netxms/docker/pull/3

Hi Team, Is there any plans to add more features to the Network Discovery option in NetXMS Server and Proxies? We are keen on getting these features in line with nmap's discoveries added to Network Discovery - Port Scan Service/Version Detection OS Detection Regards, Mathew

Victor, thank you very much! I should have realized this myself...

@hmjvaline said in Server's configuration parameters on CodePage Case issues: so I think the settings of snmp.codepage may not be properly accessed when the service is restarted, You are right, there is a bug. Will be fixed in next patch release.

Hi there. I updated the NetXMC server to the 4.4.1-1 version. I did the same with the NetXMC client in MacOS 13.5.2 However, when I tried to connect to the server appeared a pop-up window with the following message: An error has ocurred See the log file /eclipse/ 1694720730883.log I share the first three lines of this file: !SESSION 2023-09-14 14:45:30.531 ----------------------------------------------- eclipse.buildId=unknown java.version=16.0.1 java.vendor=Azul Systems, Inc. However, I installed this Java version in this computer. $ /usr/libexec/java_home -V Matching Java Virtual Machines (1): 17.0.8 (x86_64) "Oracle Corporation".... Any idea how can I fix this eclipse issue ? Thanks in advance

Hi, there. I have netxms-sever to 4.4.1-1 version installed. When I log into the server in no time appear the following pop-up window: Any idea how to fix this communication issue? Thanks in advance [image: connectionetxms2023.png]

Hi, Victor. First I appreciate your time to read my message. Second, I will follow your directions to try to fix this NetXMC client issue.

Victor, this has been resolved.  Thank you!

For example with nxmc (Linux x86 GTK), I tried two ways as follows: Edit the file "src/java/netxms-eclipse/Core/src/org/netxms/ui/eclipse/console/ApplicationActionBarAdvisor.java" to add new Vietnamese language, and also add the all files "messages_vi.properties" to "netxms-eclipse" source codes (copy from the file "messages.properties" to "messages_vi.properties"). However, when compiling with Maven, it gives an errors. Using the available language (French), translate the contents of the all "messages_fr.properties" files in "netxms-eclipse" source codes. Recompile ""netxms-eclipse" source codes using Maven successfully. However, Vietnamese must use Unicode UTF-8, when running nxmc, there is a font error, the characters are displayed incorrectly (strange characters instead of Vietnamese). Can you show me how to properly display Vietnamese characters in the second case, what format the "messages_fr.properties" files must be saved (encode) for NXMC to display properly. Sorry I'm not familiar with the Babel implementation on Java/Eclipse.

Hi, you can create object tool that will execute NXSL script, and use SNMPSet function or set method in SNMP transport object (see reference here: https://www.netxms.org/documentation/nxsl-latest/#func-snmpset). Best regards, Victor

Hi Victor, Thank you very much for your detailed support. It works fine. Best regards, Zsolt

Hi! We are updating data dictionary periodically, but it not always follow schema changes immediately. I'll ask dev team to update it for current 3.9 version. Best regards, Victor

Thanks as always!

@victor said in New Docker Files Available! Asking for help with releases: We just published new release 3.8.366. I have added tag release-3.8.366 as well as GitHub release. Best regards, Victor Hey Victor, Thanks so much this, it makes my job handling automated releases much easier. I am currently in the process of scoping out the most efficient method of handling release automation. Currently the short list contains GitHub Bot GitHub Action Scheduled GitLab CI Job Scheduled I am leaning towards the GitHub action, I suspect it will end up that the action runs in the context of Matthew-Beckett/netxms-dockerfiles and will need a webhook from netxms/netxms to trigger the pipeline on creation of a Release.

Thank you Viktor! After applying it, the build was successful. Best regards

Two ways here: Set alarm timeout and what event will be generated, and then create another rule to terminate alarm on timeout event. Note that timeout event will be generated only if alarm will still be in outstanding state. Execute script action with required delay in same rule, and terminate alarm from that script. Best regards, Victor