NetXMS Forum

Thanks!  Looking forward to 1.2.7.

Thanks, this worked perfectly.

I noticed that if I install the webui and leave the port to default (8787) that everything works properly.  If I install the webui and specify a different port then it doesn't work properly.  How do I change the webui to use a different port?

There were no changes in portcheck subagent since 1.2.2. Return code 3 means that connection was successful, but reply didn't match regexp. Could you check request/response with tcpdump?

Thanks, it works like a charm!

Hi! @rabid said in Couple of questions: First question, I have a WMI Query WMI.Query(root\cimv2,"select * from Win32_PerfFormattedData_PerfDisk_PhysicalDisk Where Name = '_total'",DiskWriteBytesPersec) and it yields results but yet when I try to graph this DCI I get a flat line of 0. check what data type is set for DCI. It should be set to some numeric type. @rabid said in Couple of questions: Second question, is it possible to monitor all windows services that are set to "automatic" and if any are not started to get an alert.  I believe Nagios does something like this. it's not possible now. After we add threshold functionality to tabuilar DCIs, it will become possible. Best regards, Victor

Hi! It's not possible with server 1.0.12. In 1.1.5 and higher, threshold and actual value passed as parameters %5 and %6 respectively (or as named parameters thresholdValue and currentValue). Best regards, Victor

Hi I am try to compile netxms-1.0.12 in vc 6 in window xp service pack 2 and facing these problems 1 fatal error C1083: Cannot open include file: 'winevt.h': No such file or directory Error executing cl.exe. First I installes Microsoft SDK 2003  and also try  Microsoft Visual Studio 2008 SDK but unable to solved the problem.  plz indicate version of sdk. 3 fatal error C1083: Cannot open include file: 'Scintilla.h': No such file or directory When I install scintilla  and try to compile . These errors occur   C:\Net XMS project\software\scintilla\lexlib\Accessor.h(23) : error C2504: 'LexAccessor' : base class undefined C:\Net XMS project\software\scintilla\lexlib\Accessor.h(26) : error C2629: unexpected 'class Accessor (' C:\Net XMS project\software\scintilla\lexlib\Accessor.h(26) : error C2238: unexpected token(s) preceding ';' C:\NET XMS PROJECT\SOFTWARE\SCINTILLA\INCLUDE\WindowAccessor.h(15) : error C2079: 'WindowAccessor' uses undefined class 'SCILEXER_EXPORTABLE' 3  Compiling .\parser.y 'bison' is not recognized as an internal or external command, operable program or batch file. Error executing c:\windows.0\system32\cmd.exe. PlZ tell me how it can besolved Also tell which satiable version of  netXms Best Regard

Hi! Last error is ok if you do not have DRBD installed. It cannot affect agent's communications. When you do configuration poll for node in NetXMS, did you get anything in agent's log? You should see at least lines like this: [01-Nov-2011 09:48:34] Incoming connection from 127.0.0.1 If you don't, that means that server cannot even establish TCP session with the agent, and problem is on the network layer - firewall, routing, etc. Best regards, Victor

I looked at the documentation and apparently I can't seem to follow along to correctly set up a Windows Event Log monitoring process.  I was wondering if someone could walk me thru setting up a monitor for Event ID 538 in the Security log. I don't know if it makes a difference but it is for Windows 2008 R2 and 2003 servers.  I am using 1.0.10 console and clients. Thanks in advance.

Hi! Server considers node as down if all it's interfaces is not reachable and node cannot be contacted by SNMP or via agent. How long a reboot was taken? If it was relatively fast, then it is possible that moment when node was completely unreachable fall between two status polls (each 60 seconds by default), and server never seen these two nodes as completely down. If this is the case, solution depends on your goal - for example, if you wish to detect that node was rebooted, you can add monitoring of system uptime, and if it below some small value, like 100 seconds, that means that node was just rebooted and you can generate appropriate event. Best regards, Victor

Under the server config I changed DiscoveryPollingInterval to 3600 and it now fires an email after being down for a minute (default was for 4 minutes).  Hopefully this was correct.

Because you are monitoring services using DCIs, you will not get service down events in case of entire node down, because there will be no new values for DCI, and therefore no events will be triggered. Btw, it is not recommened to use SYS_xxx events in thresholds - they are generated by server in various situations, and you can get unexpected results. SYS_SERVICE_DOWN and SYS_SERVICE_UP generated by server during status poll of network services. Until you are not using network service objects, you are fine, but if you eventually configure some, you will get unexpected events. Better approach is to create your own events. Best regards, Victor