NetXMS Support Forum

Quote from: Alex on February 26, 2008, 02:06:38 PM
Еще одна проблема выскочила. Логинюсь под admin все путем. Но если я логинюсь под обычным пользователем пишет: Unable to connect: Access denied. Хотя в dev2 все работало прекрасно. Что интересно такая же бодяга как на рабочем сервере, так и на тестовом Менял права юзверям, однофигственно. В чем может быть проблема?

Eto bug, vilozil installer s ispravlennoj konsol'ju.

Quote from: weec on February 26, 2008, 01:47:49 PM
хотелось бы увидеть изменения RC1->RC2

Primerno vot on:

- move dlja template'ov
- "stop processing" flazok v event processing policy
- nxalarm
- Sinhronizacija imen ob'ektov node s DNS
- Interface names polling

Nu i iz nedodelannogo - advanced event corelation.

I razlichnie melkie izmenenija - no SNMP biblioteku ja vrode kak davno uze ne trogal...

Quote from: Alex on February 26, 2008, 11:45:28 AM
Нашлась проблема с SNMP

# /usr/local/bin/nxsnmpwalk -c public host .1
SNMP Error: Request timed out

при этом

# snmpwalk -c public host .1
SNMPv2-MIB::sysDescr.0 = STRING: SunOS release:5.8 version:Generic_117350-02 machine:sun4u
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.99.1.1.3.34
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (31764508) 3 days, 16:14:05.08

A esli poprobovat' zadat' versiju: "-v 1" ili "-v 2c" ?

AlarmViewer uses Internet Explorer to render the information page, and it looks like after upgrade to IE7 something was broken. We are working on a comletely new Alarm Viewer which will replace the old one.

Best regards,
Victor

Vilozil RC2 v download/rc.

Best regards,
Victor

Нет такой возможности пока. Сделал в 0.2.20.

С уважением,
Виктор

It should be safe. Agent will accept connections only from hosts listed in configuration file. Connections from all other addresses will be closed immediatelly without sending or receiving any data. Also, you may configure agent to require additional authentication with shared secret, and to require encrypted connections.

Best regards,
Victor

Yes, then you will get more detailed picture. From my experience, I often configure only common System.IO.DiskQueue parameter on all servers, and then add per disk queue/time for those servers where I see need for more detailed information.

Best regards,
Victor

Должна. Похоже что у вас wxWidgets собраны под UNICODE, 0.2.19 это не поддерживал. 0.2.20 должен собираться нормально. Пока-что можно попробовать 0.2.20-rc1 или дождаться сегодня-завтра rc2.

Dolzen bit' bukval'no na dnjah. Menja so vseh storon osazdajut na temu novoj versii Ja planiruju v eti vihodnie plotno porabotat' i taki k ponedel'niku ee vidat'.

You should use $1 instead of $i. Do you use $1 in when trying short form? Also, you example has syntax error - there are missing ; after return statement.
It should be like this:


sub main()
{
   return ($1 / 2);
}


Best regards,
Victor

Btw, is there libeay32.dll in NetXMS\bin directory? It supposed to be installed with NetXMS.

Best regards,
Victor

Quote from: kghammond on February 13, 2008, 10:39:25 PM
I was just going to ask that question.  I assume then that process.io.xxx with a transformation will actually be more accurate.

They should be the same - in both cases you get average value for 60 second, the only difference is that for built-in counters you have calculation on server side (so using fewer cpu cycles on machine with agent) and that you can easily use them in templates without any changes in appropriate agent configs.

Quote from: kghammond on February 13, 2008, 10:39:25 PM
At the same time, my working set counter will be more accurate than process.wkset because it will be averaged over 60 seconds.  Is that correct?

Yes, that's correct.

Best regards,
Victor

Hello!

There are various errors. First, in many counters you miss leading backslash. Also, there should be a white space between % sign and "Disk Read Time" or "Disk Write Time". And finally, you should enclose description in double quotes if you are using colon. Correct section should looks like this:


*WinPerf
Counter = UserProcess.SQLServer.CPU:"\Process(sqlservr)\% Processor Time":60:A:INT:Average % CPU Time for sqlservr.exe over past minute
Counter = UserProcess.SQLServer.IO.ReadBytes:"\Process(sqlservr)\IO Read Bytes/sec":60:A:INT:Average I/O Read Bytes for sqlservr.exe over past minute
Counter = UserProcess.SQLServer.IO.WriteBytes:"\Process(sqlservr)\IO Write Bytes/sec":60:A:INT:Average I/O Write Bytes for sqlservr.exe over past minute
Counter = UserProcess.SQLServer.IO.OtherBytes:"\Process(sqlservr)\IO Other Bytes/sec":60:A:INT:Average I/O Other Bytes for sqlservr.exe over past minute
Counter = UserProcess.SQLServer.Memory:"\Process(sqlservr)\Working Set":60:A:INT:Average Memory usage for sqlservr.exe over past minute
Counter = System.IO.DiskReadTime:"\LogicalDisk(C:)\% Disk Read Time":60:A:INT:"Average Disk Read Time C:"
Counter = System.IO.DiskWriteTime:"\LogicalDisk(C:)\% Disk Write Time":60:A:INT:"Average Disk Write Time C:"
Counter = System.IO.DiskReadBytes:"\LogicalDisk(C:)\Disk Read Bytes/sec":60:A:INT:"Average Disk Read Bytes Per Sec C:"
Counter = System.IO.DiskWriteBytes:"\LogicalDisk(C:)\Disk Write Bytes/sec":60:A:INT:"Average Disk Write Bytes Per Sec C:"
Counter = System.IO.DiskReadTime:"\LogicalDisk(D:)\% Disk Read Time":60:A:INT:"Average Disk Read Time D:"
Counter = System.IO.DiskWriteTime:"\LogicalDisk(D:)\% Disk Write Time":60:A:INT:"Average Disk Write Time D:"
Counter = System.IO.DiskReadBytes:"\LogicalDisk(D:)\Disk Read Bytes/sec":60:A:INT:"Average Disk Read Bytes Per Sec D:"
Counter = System.IO.DiskWriteBytes:"\LogicalDisk(D:)\Disk Write Bytes/sec":60:A:INT:"Average Disk Write Bytes Per Sec D:"


Also, you may find useful built-in parameters Process.WkSet and Process.IO.xxx. You can find short description of built-in parameters here:
https://www.netxms.org/documentation/common_parameters.html

However there are difference between your custom parameters and built-in Process.IO.xxx - you define average value for last minute, while built-in parameters is a totals since process start - but you can calculate an average value using delta transformation for DCI on server side.

Best regards,
Victor

For process counters in question, if process does not exist, counter will return 0. But in general, if you try to add non-existing performance counter, it may fail on agent startup, or may return error to data collection requests - depending on what PDH returns to agent.

Best regards,
Victor