NetXMS Support Forum

Hi,

I want to know the unit of following Data Collection item.
-----
Description: Average disk busy time for last minute
Data Parameter:System.IO.DiskTime
-----

Best Regards,

Hi.

DB Upgrede ERROR.

-----------------
c:\bin\NetXMS\bin>nxdbmgr upgrade
NetXMS Database Manager Version 1.1.5

Upgrading database...
Upgrading from version 105 to 217
Upgrading from version 217 to 218
Upgrading from version 218 to 219
SQL query failed ([Microsoft][SQL Server Native Client 10.0][SQL Server]There is
already an object named 'images' in the database.):
CREATE TABLE images (   guid varchar(36) not null,   mimetype varchar(64) not nu
ll,   name varchar(255) not null,   category varchar(255) not null,   protected
integer default 0,      PRIMARY KEY(guid),   UNIQUE(name, category))
Rolling back last stage due to upgrade errors...
Database upgrade failed
-----------------

Manager Server:
Windows 2008
SQL Server 2008

Please help it.

Hi,

I use a multi-language with Windwos server.
"Call to EvtFormatMessage failed: The resource loader failed to find MUI file."

I put Japanese MUI, but want to output a message in English because I am garbled.
How can you pick up a message in English if you set it?

I want to pick up a built-in syslog server  in event, but cannot pick it up even if I set "syslog parser".
------------------------
<parser>
      <rules>
         <rule>match>(*)</match><event params="1">100024</event></rule>
      </rules>
</parser>
------------------------

If there are samples, please show it.

Best regards,

Hi,

As for logwatch, it is a question.

The message generated in the past is detected two or more times.
Isn't there method of not detecting the message in the past detected once?

--------------------------------------------------

#The first
sysmem date       time             Node        Level             log messages
02-Mar-2011   16:00:21   server-99   Warning   "16:00:17.284 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   16:00:26   server-99   Warning   "16:00:21.350 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   16:00:26   server-99   Warning   "16:00:25.247 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   16:00:31   server-99   Warning   "16:00:29.472 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   16:00:36   server-99   Warning   "16:00:32.820 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   16:00:41   server-99   Warning   "16:00:37.331 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     

#The second
02-Mar-2011   18:12:27   server-99   Warning   "16:00:17.284 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   18:12:27   server-99   Warning   "16:00:21.350 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   18:12:27   server-99   Warning   "16:00:25.247 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   18:12:27   server-99   Warning   "16:00:29.472 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   18:12:27   server-99   Warning   "16:00:32.820 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   18:12:27   server-99   Warning   "16:00:37.331 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"

#The third
02-Mar-2011   19:55:29   server-99   Warning   "16:00:17.284 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   19:55:29   server-99   Warning   "16:00:21.350 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   19:55:29   server-99   Warning   "16:00:25.247 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   19:55:29   server-99   Warning   "16:00:29.472 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   19:55:29   server-99   Warning   "16:00:32.820 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"     
02-Mar-2011   19:55:29   server-99   Warning   "16:00:37.331 0 SYSTEM XXX 'aaaaaaaaa' has updated the eeeeeeee Keys"

--------------------------------------------------

Agent: version 1.0.8    Linux
Manager: version 1.0.8 Windows 2008 64bit

Best regards.

Dear all,

Agent Status & status returns a normal value "0" though has passed since the server was downed ten minutes from five minutes.

Why is not abnormality detected?

Which configuration does only have to be changed though it wants to be going to detect abnormality of the server in about one minute?

The down of "NIC" detection is also slow. It takes 15 minutes from about five minutes.
Isn't there improvement method?

Manager ----- OS Windows server 2008  64bit
                    NetXMS Manager 1.0.8     32bit
                    NetXMS Agent 1.1.0        64bit
Agent   ----- OS Redhat 5.5                 64bit
                   NetXMS Agent 1.0.8         64bit