Oh I cause that bug. It is not relate to the unsigned integer problem. Because the counter of the inflow will be zero when the agent restart. for example, the agent network infolw  now is 1000000000,and it save to the DB and the agent machine reatart. the network infolw will set to zero. When the server get the "Net.Interface.BytesIn(eth0)" from the same agent again. 0 mimus 1000 is a negative number. So That bug cause: 1)when the agent machine restart 2)the first point I have said above.

Hi! Yes, you are right. When I read GetTimeZoneInformation description, I had thought that Bias field contains current bias, calculated accordingly to DST. I have fixed it already, next build will contain correct code. Thank you for digging it out! Best regards, Victor

@xatteg said in alarms actions: One thing I also would like to have is when you change alarm status to "Resolved" the alarm highlights should be removed from devices. Yes, I agree. Will be done in next release. Best regards, Victor

@victor said in Monitoring Hyper-V cluster on Windows Server 2008 R2 Enterprise ed.: @jmp_3f8h said in Monitoring Hyper-V cluster on Windows Server 2008 R2 Enterprise ed.: I forgot to mention that in this scenario the event source for the alarm should be the container and not a specific node. But I don't know if promoting a container to source for alamr has other side effects. This can cause some side effects. For example, now you have $node variable in filtering scripts in event processing policy. If container and/or cluster objects can be event sources as well, you will have to check with what object class you are dealing with before accessing object properties for example. It will be quite complicated change, mostly because lot of places in the code will need to be checked. Best regards, Victor I was thinking about a $container to be checked for events generated by those objects. Probably a superclass object $some_entity extended by $node and $container can be substituted to the current $node in most of the places. But even without considering the implementation effects (heavy, as far as I understood), the real problem is that I'm not totally convinced that a similar approach can be 100% semantically correct. Marco PS May be my comments are totally foolish since I don't know how it is currently implemented. Sorry in advance!

It is built with --disable-iconv now, that is the only disable i have. Encryption isn't that important for me on my own private network at home. I can communicate with the node so it's not an issue now ^^

Hello Victor, I have added SNMP string polling and it has the same effect as ODBC polling. Current polled value is good and stored are ruined. Best regards, Roman

Hello Victor, It is working now! It compiled in both cases with and without --with-all-static (I'm using without). The thing is it was trying to copy odbc.so to <netxms-install-dir>/odbc.ddr when I issued "make install". So I had to go to "src/agent" subdir and issue "make install" there, and everything installed fine.

Hello, Thank you for the build. Provisionally looks good, running as expected and memory usage is stable with no obvious signs of the issue. Many thanks Aron

Hi! I'm already back from vacation I don't know exact release date for 1.2.3 yet. Most likely it will be somewhere in the end of August. Best regards, Victor

hi victor, i looked at the switches and i found that there is a difference between stack ports an 10gb ports. there are module sockets for either 10gb uplink or stack ports and the module attached is for stack ports therefor the status indication of the switches are correct. i was not familiar with this configuration which is different from cisco, hence my mistake Best Regards, Lindeamon

fixed. incorrect DataDirectory in /etc/netxmsd.conf

hi victor, again, i can get enough from this app and happy to give you a hand in making it better and better Best Regards, Lindeamon

hi victor, i have searched the file before posting it and i haven't saw this. i will check the node's arp table. i wonder what application could have done it i have mcafee epo and windows deployment services and wsus. thanks for the lead in the solution, Best Regards, Lindeamon

hi victor, of course i am using 1.2.2  ;D i will do the check again and let you know Best Regards, Lindeamon

Victor, Thanks for the info. As you may guess I'm looking forwards the release of 1.2.3. (nice number)  Meanwhile I found the node for my mysterious MAC but that's a different story... Regards, Dan

Yes, it could be useful. I'll add it as low priority feature request. Best regards, Victor

Binary was built for version 1.2.2, but it will work with earlier client library versions too. Best regards, Victor

You can access trap-originated event's parameters in script, but only by index, like this: $event->parameters[2] Best regards, Victor

@lweidig said in Netxms 1.2.1 on debian 6 : netxmsd -d don't start!: For the database part of your question just use the native database tools to handle this.  I would probably suggest stopping the server and agent before any of these items.  For example using MySQL since that is what your configuration shows to change the password for the netnxms user on a MySQL system: $ mysql -u root -p # Enter root password when promted mysql> use mysql; mysql> update user set password=PASSWORD("NEW-PASSWORD-HERE") where User='netxms'; mysql> exit $ vi /etc/netxmsd.conf # Updated DbPassword with NEW-PASSWORD-HERE in configuration Similarly, if you wanted to start over with a clean database you would run the following: BE WARNED THIS WILL WIPE YOUR DB SETUP COMPLETELY TO INITIAL VALUES!!! $ mysql -u root -p # Enter root password when promted mysql> drop database netxms; mysql> exit $ /usr/local/bin/nxdbmgr init /usr/share/netxms/sql/dbinit_mysql.sql # Path might be /usr/local/share... based on install tnx, sorry but i'm write this reply for another theme, my mistake, sorry again > https://www.netxms.org/forum/general-support/nxdbmbr-bug/ i knew it, but i mean remove configuration only. i think using another or bultin tools is a wrong way.

Ok, now that I can see the keys ins 1.2.2 I was able to find the problem and have worked out a solution. When we get a SNMP_LINK_DOWN event we create an alarm with key SNMP_IF_DOWN_%i_%2, then on the SNMP_LINK_UP we terminate alarm SNMP_IF_DOWN_%i_2.  This is working and the event is clearing as it should be.  However, further down our processing policy have an event that creates an alarm NOTIFY_%i_%1.  To start a process of notification to pagers if an event does not clear.  Of course when I get the clearing event for this pair %1 is different than the first time as that contains the OID of the trap.  I have fixed this and we now seem to be fine. Thanks for adding the Alarm key in 1.2.2 display!