NetXMS Forum

Yes, it's already fixed in the code and will be in 6.2.6, which isn't released yet: https://github.com/netxms/netxms/issues/3656. Only the agent on the Windows machine needs to be updated.

Hi, Thanks, my bad. Fixed now.

Hi Alex, thanks for the hint. I give it a try... Greetings Marco

Try escaping $ in the query

Just upgraded to 6.0.5 (server and webui), now it works as expected! Thanks Victor!

Hi Filipp, it worked!! Background Update has completed the task ... :~$ nxdbmgr background-upgrade NetXMS Database Manager Version 5.2.8 Build 5.2-506-g7d4137c08a Background upgrade is locked by another process Are you sure you want to start background upgrade? (Yes/No) yes Running background upgrade procedure for version 52.24 Background upgrade procedure for version 52.24 completed ...and the update to V6.0.1 worked without any error messages... Many thanks for the support... Greetings Marco

We have this information in Audit log, but if you need it in Event Log - there's Hook::login script in script library that you can use for that. Make sure that this script returns true, otherwise it will prevent users from logging in. To see what attributes are available in this script you can try this - it will log details to server log: for (a : $user.__class.attributes) trace(0, "$user." .. a .. " = " .. $user.__get(a)); for (a : $session.__class.attributes) trace(0, "$session." .. a .. " = " .. $session.__get(a)); return true; Then you can use PostEvent() or PostEventEx() to create the event (https://netxms.org/documentation/nxsl-latest/#func-postevent), drop us a line if you need more help with scripting.

Hi,  Sorry, vacation time here so answering was delayed.  Setting number of samples to 24 means that all 24 samples should return "true". It would trigger only if 24 consecutive data collections will return different value. So not what we need here.  We don't have built-in thing for "no changes within given time", so we will use a bit of scripting. In the Transformation page of your DCI put the following:  oldValue = GetDCIRawValue($node, $dci.id); if (oldValue != $1) { $node.setCustomAttribute("lastChangeTime", time()); } lastChangeTime = $node.getCustomAttribute("lastChangeTime"); if (lastChangeTime == null) lastChangeTime = 0; return time() - lastChangeTime; Set Data type after transformation to Integer (this is relatively new feature, if you don't have it, upgrade to 5.x). On the General page set Units to Uptime. This should be it. Now how it works - in the transformation script we compare new value to the previous raw walue. If they differ we save timestamp into custom attribute on the node. And we subtract value of this custom attribute from current time - so result of the DCI is time in seconds since last change of the value. You can just set a treshold > 86400 and it should work.

Hi Filipp, you are my hero!!!  ;D Thanks for the infos. I truncate the table and postgres frees up the storage space... Many thanks! Greetings Marco

Hello Filipp, this Version works for me... The error message is gone. Greetings Marco

Historically there are two approaches to WIndows Event Log - Log Synchronization mentioned by Tatjana and Log File Monitoring. First one has the benefit that whole text of events is stored on the server. Second approach does not require to modify agent configuration file - configuration is uploaded via policy, events are generated by agent. Let me describe it in more details: Under "Templates" create a new template. Third tab in the template - "Agent Policies". Create a new "Log Parser" policy, give it some name. In the policy click "Add file" and put *Security into File path field. This means that Windows security log will be parsed. Add a new rule. You can filter by Level, ID and Source as well as by log entry text ("Matching regular expression" field, it parses all lines of the entry as one long string).  For testing you can use (.*) as the regex - it will capture whole message as parameter of the generated event - if you double-click an entry en event log, you'll see all the information. I am not sure about correct event ID, but it seems that 4624 is capturing logon events, so regex .* and ID 4624 will capture these events. You need to specify an event in the rule. Create event template, this defines what parameters are included into message field. E.g. the following in the message field: User %<variable6> was successfully logged on (Event ID: %<eventId>, Severity: %<severity>, Network Address: %<variable19>)

Server reads VLAN names from 1.3.6.1.2.1.17.7.1.4.3.1.1, then ports from 1.3.6.1.2.1.17.7.1.4.2.1.5 and 1.3.6.1.2.1.17.7.1.4.2.1.4, optionally also 1.3.6.1.2.1.17.7.1.4.3.1.2. For all those 3 tables index is VLAN ID and value is byte string, where each bit represent port membership in VLAN. You can check what values are actually returned. Below is description from Q-BRIDGE-MIB: Each octet within this value specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying ports 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port.  Thus, each port of the bridge is represented by a single bit within the value of this object.  If that bit has a value of '1' then that port is included in the set of ports; the port is not included if its bit has a value of '0'. Also note that "port number" in this context is bridge port number (as obtained from 1.3.6.1.2.1.17.1.4.1.2), not interface index. Best regards, Victor

Hi Filipp, thanks for the hint... I restartet NetXMS server, but the templates where not applied to the NetXMS Server Agent. The println($node.isLocalManagement); show "true" for the NetXMS Server Agent node. After that, i imported the netxms_server.xml into NetXMS and deploy the template to the NetXMS Server Agent Node and voila... it worked ;D all DCI's from NetXMS Server are in place... Thanks for the help... Greetings Marco

Hi Filipp, thanks for your answer. I added the verify-host=false to my configs and voila: it worked again... Many thanks for that hint...  Greetings  Marco

Seen this thread?: https://www.netxms.org/forum/general-support/webui-v4-4-0-mismatch-communication-protocoll-ubuntu/

View state saving is planned for 5.0 which should be out in January. Rearranging items might require some work, so could be expected somewhere later.

Good evening. To solve this problem, simply install server version 4.4.0 on your host machine. By itself it should have already automatically installed version 4.4.0 for the web interface. I tested it now and it worked. If you use the windows client you have to do the same of course https://netxms.org/download/releases/4.4/netxms-server-4.4.0-x64.exe https://netxms.org/download/releases/4.4/netxms-webui-4.4.0-x64.exe https://netxms.org/download/releases/4.4/netxms-client-4.4.0-x64.exe

Hi, definitely, should be available soon. Best regards, Victor

Hello @all, at my NetXMS Server (Win10, MySQL V5.7.30, 16GB RAM) i see the follow event in the windows event log:  InnoDB: Over 67 percent of the buffer pool is occupied by lock heaps or the adaptive hash index! Check that your transactions do not set too many row locks. Your buffer pool size is 16 MB. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics, including lock heap and hash index sizes.For more information, see Help and Support Center at http://www.mysql.com.  Has anyone an idea what buffer pool size i have to use? On this machine is only NetXMS running and no other DB's. Thanks in advance... Greetings Marco

Hi Victor, thanx for the fast response... downloaded, tried and worked for me... But i have to shutdown NetXMS Server, in cause of a locked library...  Now NetworkService.Status is working... Many thanx..  Greetings Marco