NetXMS Support Forum

Hi Victor,

M5 release for Agent is not working on Solaris:

[root] /opt/netxms/bin $ ./nxagentd
ld.so.1: nxagentd: fatal: libappagent.so.2: open failed: No such file or directory
Killed

[root] /opt/netxms/bin $ ls -la /opt/netxms/lib/libappagent.so*
lrwxrwxrwx   1 root     root          20 Jul 17 13:06 /opt/netxms/lib/libappagent.so -> libappagent.so.1.0.0
lrwxrwxrwx   1 root     root          20 Jul 17 13:06 /opt/netxms/lib/libappagent.so.1 -> libappagent.so.1.0.0
-rwxr-xr-x   1 root     root      151568 Apr 29 20:30 /opt/netxms/lib/libappagent.so.1.0.0

Best regards,
Marcin

Hello,

I observe that every day memory consumption of netxmsd is increasing by around 1GB.
After two weeks netxsmd consumed 20GB of physical memory on Solaris system.
Server was restarted 13.07. Two days later memory usage already increased to 4GB:

I'm attaching pmap output.

Best regards,
Marcin

Thank you for a quick answer.

Could we send email only when new alarm is created and not for subsequent alarms with the same key?
I assume it's not possible.

Is there a better way than using a Situation Manager and storing there timestamp of the event:
processing rule: SetEventParameter($event, "eventtimestamp", $event->timestamp);
situation attribute: %<eventtimestamp>
and then comparing for each event stored timestamp by using FindSituation with current timestamp?

"store timestamp of first event in node's custom attributes" - is it the same procedure as I described above?

Best regards,
Marcin

Hi Victor,

Problem:
Due to technical failure, one of the network devices started sending SNMP traps to NetXMS every couple of seconds with information's about problem.
NetXMS is configured to generate an alarm and one of the actions is to send an e-mail to the group of technicians.
As a result NetXMS generated hundreds of emails during a very short period of time.

Question:
How we can limit number of e-mail send by NetXMS in relation to one alarm?
Could we send email only when new alarm is created and not for subsequent alarms with the same key?

Best regards,
Marcin

Hello,

Is it possible to change default event attributes in the filtering script?
Based on the SNMP varbind I would like to modify severity of the event and then create correct alarm.

I tried:
$event->severity = 1;
but I get an error while compiling processing policy rule: "Unknown object's attribute"

I tried also: SetEventParameter($event, severity, 1);
but without success.

Best regards,
Marcin

Hi Victor,

I have seen this recommendation in one of your ealier replies.
This is why I tried with ServiceCheck.HTTPS timeout set to 1000 (AgentCommandTimeout = 4000).
I will try again.

Best regards,
Marcin

Hello,

I have configured ServiceCheck.HTTPS to monitor status of internal web application every minute. It works fine when application is UP (returned value = 0) and when application is shut-down for maintenance reasons (returned value = 2). Unfortunately it does not work if application is overloaded and web page is almost not accessible (rendering web page takes 5-10 seconds).

No matter what timeout value I configure (I tried: 1000, 3000, 5000) NetXMS is not returning any status.
Below is the example history of collected data.
"Timestamp","Value"
"10.04.2015 12:20:23","0"
"10.04.2015 12:09:23","0"
"10.04.2015 12:05:23","0"
"10.04.2015 12:01:23","0"
"10.04.2015 11:55:23","0"
"10.04.2015 11:54:23","0"
"10.04.2015 11:52:23","0"
"10.04.2015 11:51:23","0"
"10.04.2015 11:50:23","0"
"10.04.2015 11:49:23","0"
"10.04.2015 11:48:23","0"
"10.04.2015 11:47:23","0"
"10.04.2015 11:46:23","0"
"10.04.2015 11:45:23","0"
"10.04.2015 11:44:23","0"
"10.04.2015 11:43:23","0"
"10.04.2015 11:42:23","0"
"10.04.2015 11:41:23","0"
"10.04.2015 11:40:23","0"
"10.04.2015 11:39:23","0"
"10.04.2015 11:38:23","0"
"10.04.2015 11:37:23","0"
"10.04.2015 11:36:23","0"
"10.04.2015 11:35:23","0"
"10.04.2015 11:34:23","0"
"10.04.2015 11:33:23","0"
"10.04.2015 11:32:23","0"
"10.04.2015 11:31:23","0"
"10.04.2015 11:30:23","0"

At the beginning it works fine. Checks are executed every minute, but later around 12:00, when website is not responsive at all, timestamp changes from 1 minuted to several minutes.

I'm using NetXMS 2.0-M2.

How this issue can be resolved?

Best regards,
Marcin

Hi Victor,

Yes, it works. Missing semicolon caused wrong rule processing.

Best regards,
marcin

Hello,

In event processing rule number 1 I define:
SetEventParameter($event, "WeblogicENV", "TEST");
This event parameter is used in message text for alarm creation (%<WeblogicENV>).
This works fine.

Then I wanted to use the same event parameter defined in filtering script of rule number 1 in the rule number 2.
Unfortunately:
GetEventParameter($event, "WeblogicENV");
returns NULL.

Is it normal that this additional even parameter is lost or maybe I have a mistake somewhere in the code?

Best regards,
Marcin

Hello,

What would be the best way to define an action (send e-mail) for an alarms generated only during specified time frame (between 09:00 and 17:00)? There is a restart of a service during a night, and termination of the alarm when the service is up. In this case an e-mail should not be sent.

The only way is to create a new event processing policy and use filtering script (previous one + new condition)?
If yes, how to do it?
Ex. strftime(%H,$event->timestamp) with "if" statement?

Best regards,
Marcin

After UPDATE in DB I run nxdbmgr . It worked:

Data collection table (TDATA) for node [816] not found. Create? (Y/N)  (Y/N) y
Data collection table (TDATA) for node [819] not found. Create? (Y/N)  (Y/N) y
Data collection table (TDATA) for node [822] not found. Create? (Y/N)  (Y/N) y
* Checking data tables...                                             [FIXED ]
33 errors was found, 33 errors was corrected
All errors in database was fixed
Commit changes? (Y/N) y

nxdbmgr check caused some changes in NetXMS configuration. I see alarms that were not present before.
For example there was an event processing policy without defined event.
It was not working, now after stasrting NetMXS server it started generating alarms for every event.

Thank you,
Marcin

Removing invalid object ID 116 does not solve the problem.
Another nxdbmgr check few minutes later is reporting again the same issue.

Regards,
Marcin

Below is the output:

VAR_NAME      VAR_VALUE
---------------------------------------------------------------
LocationHistory
CREATE TABLE gps_history_%d (latitude varchar(20), longitude varchar(20), accuracy integer not null, start_timestamp integer not null, end_timestamp integer not null, PRIMARY KEY(start_timestamp))

SchemaVersion
344

Syntax
ORACLE

IDataTableCreationCommand
CREATE TABLE idata_%d (item_id integer not null,idata_timestamp integer not null,idata_value varchar(255) null)

IDataIndexCreationCommand_0
CREATE INDEX idx_idata_%d_id_timestamp ON idata_%d(item_id,idata_timestamp DESC)

TDataTableCreationCommand_0
CREATE TABLE tdata_%d (item_id integer not null,tdata_timestamp integer not null,record_id number(20) not null,UNIQUE(record_id))

TDataTableCreationCommand_1
CREATE TABLE tdata_records_%d (record_id number(20) not null,row_id number(20) not null,instance varchar(255) null,PRIMARY KEY(record_id),FOREIGN KEY(record_id) REFERENCES tdata_%d(record_id) ON DELETE CASCADE)

TDataTableCreationCommand_2
CREATE TABLE tdata_rows_%d (row_id number(20) not null,column_id integer not null,value varchar(255) null,PRIMARY KEY(row_id,column_id),FOREIGN KEY (row_id) REFERENCES tdata_records_%d(row_id) ON DELETE CASCADE)

TDataIndexCreationCommand_0
CREATE INDEX idx_tdata_%d_id_timestamp ON tdata_%d(item_id,tdata_timestamp)

TDataIndexCreationCommand_1
CREATE INDEX idx_tdata_rec_%d_instance ON tdata_records_%d(instance)


10 rows selected.

Hello,

After upgrading NetXMS from 1.2.16 to 2.0-M2 I see following errors in the netxms log file:

[12-Feb-2015 14:09:43.618] [ERROR] SQL query failed (Query = "INSERT INTO tdata_records_822 (record_id,row_id,instance) VALUES (?,?,?)"): ORA-00001: unique constraint (NETXMSOWNER.SYS_C0040248) violated
[12-Feb-2015 14:09:43.618] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:10:43.645] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:10:48.485] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:14:17.166] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:14:18.103] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:15:43.556] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:15:48.396] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:19:18.031] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:19:19.029] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:20:43.484] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:20:48.308] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:24:18.945] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:24:19.955] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:25:43.396] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:25:48.219] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:29:19.867] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:29:20.867] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:30:43.325] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:30:48.128] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:34:20.858] [ERROR] Invalid object identifier 116 in event processing policy
[12-Feb-2015 14:34:21.791] [ERROR] Invalid object identifier 116 in event processing policy

and following errors when running check on the database:
[root] $ /opt/netxms/bin/nxdbmgr check
NetXMS Database Manager Version 2.0-M2 Build 8007

Checking database (excluding collected data):
* Checking zone objects...                                            [PASSED]
* Checking node objects...                                            [PASSED]
* Checking interface objects...                                       [PASSED]
* Checking network service objects...                                 [PASSED]
* Checking cluster objects...                                         [PASSED]
* Checking template to node mapping...                                [PASSED]
* Checking object properties...                                       [PASSED]
Invalid object ID 116 used in policy. Delete it from policy? (Y/N) y
* Checking event processing policy...                                 [FIXED ]
* Checking network map links...                                       [PASSED]
Data collection table (TDATA) for node [110] not found. Create? (Y/N)  (Y/N) y
SQL query failed (ORA-02270: no matching unique or primary key for this column-list):
CREATE TABLE tdata_rows_110 (row_id number(20) not null,column_id integer not null,value varchar(255) null,PRIMARY KEY(row_id,column_id),FOREIGN KEY (row_id) REFERENCES tdata_records_110(row_id) ON DELETE CASCADE)
Data collection table (TDATA) for node [192] not found. Create? (Y/N)  (Y/N) y
SQL query failed (ORA-02270: no matching unique or primary key for this column-list):
CREATE TABLE tdata_rows_192 (row_id number(20) not null,column_id integer not null,value varchar(255) null,PRIMARY KEY(row_id,column_id),FOREIGN KEY (row_id) REFERENCES tdata_records_192(row_id) ON DELETE CASCADE)
Data collection table (TDATA) for node [194] not found. Create? (Y/N)  (Y/N) y
SQL query failed (ORA-02270: no matching unique or primary key for this column-list):
CREATE TABLE tdata_rows_194 (row_id number(20) not null,column_id integer not null,value varchar(255) null,PRIMARY KEY(row_id,column_id),FOREIGN KEY (row_id) REFERENCES tdata_records_194(row_id) ON DELETE CASCADE)

During every execution of nxdbmgr the same errors occurs (also for Invalid object ID 116).

Could help in resolving this issue?

Best regards,
Marcin

Hi Victor,

Before I start installing new version... Was this issue corrected in netxms-2.0-M1?

Regards,
Marcin