NetXMS Support Forum

I'm running a NetXMS server at version 3.9.178 with multiple zones for our customers, one zone has a single proxy node configured. Whenever I try to update to a newer build the server service starts up but the "Poll Manager" goes to "not responding" within a few seconds. I am able to connect with the console right after the service start, if I'm fast, afterwards any new connection hangs after supplying the login credentials.

I'm not sure but I suspect it has to do with this item from the changelog:
*
* 3.9.229
*
[...]
- Fixed server deadlock related to multi-zone configuration
[...]

What is the best way to analyse this problem? I tried raising the debug level but I'm not sure what I should look for, there are many nodes configured and many connections are happening after server start.
The server runs on Windows Server 2019 with MySQL as database.

I know that. I was referring to these changelog entries of 2.2.3:

Quote- Additional information about captured Windows Event Log event passed to the server

QuoteNX-1258 (Option to pass event data from Windows event log to NetXMS event)

I found it out in the meantime: The additional information is accessable by the parameters-property of the event-class in NXSL. Currently the data is only accessable by array-index and the names-array is empty. I'm not sure if this is supposed to be this way...

Also, there seems to be a bug: When generating a NetXMS event from a Windows event the agent crashes (version 2.2.6). Nothing helpful in the log at trace level 9, it just stops after "matched":
2018.05.27 10:51:08.559 *D* [logwatch.parser    ] Publisher name is Microsoft-Windows-Security-Auditing
2018.05.27 10:51:08.559 *D* [logwatch.parser    ] Match event: source="Microsoft-Windows-Security-Auditing" id=4768 level=8 text="Ein Kerberos-Authentifizierungsticket (TGT) wurde angefordert.
2018.05.27 10:51:08.559 *D* [logwatch.parser    ] checking rule 1 ""
2018.05.27 10:51:08.559 *D* [logwatch.parser    ]   rule has no context
2018.05.27 10:51:08.559 *D* [logwatch.parser    ]   event id 0x000012a0 not in range 0x00001211 - 0x00001211
2018.05.27 10:51:08.559 *D* [logwatch.parser    ] checking rule 2 ""
2018.05.27 10:51:08.559 *D* [logwatch.parser    ]   rule has no context
2018.05.27 10:51:08.559 *D* [logwatch.parser    ]   negated matching against regexp Ergebniscode: 0x0
2018.05.27 10:51:08.559 *D* [logwatch.parser    ]   matched
<parser name="LogonFailure" trace="9">
   <file>*Security</file>
   <rules>
      <rule name="id4625">
         <match repeatCount="0" repeatInterval="120">(.*)</match>
         <id>4625</id>
         <source></source>
      </rule>
      <rule name="id4768">
         <match invert="true" repeatCount="0" repeatInterval="120">Ergebniscode: 0x0</match>
         <id>4768</id>
         <source></source>
<event params="1">100028</event>
      </rule>
...

Hi,
I've read in the changelog for 2.2.3 that parameters of Windows event log can be passed to the server. Is there an example how to do that?
I checked the code but my c++ is a bit rusty... I've seen that "EventData" is parsed, so can I match against these parameters in a parser rule? That would be quite useful!

Greetings,
Ben

Hi Victor,

thanks for the new release!

I'm currently on 2.0.8 and using MSSQL 2016 (database is in 2008-compatibility mode) and upgrading the database schema fails:

C:\NetXMS\bin>nxdbmgr.exe upgrade -t
NetXMS Database Manager Version 2.1-RC1 Build 9010 (2.1-RC1) (UNICODE)

Upgrading database...
Upgrading from version 410 to 411
>>> SELECT var_value FROM metadata WHERE var_name='TdataTableUpdated'
>>> SELECT var_name,var_value FROM metadata WHERE var_name LIKE 'TDataTableCreationCommand_%' OR var_name LIKE 'TDataIndexCreationCommand_%'
>>> DELETE FROM metadata WHERE var_name LIKE 'TDataTableCreationCommand_%' OR var_name LIKE 'TDataIndexCreationCommand_%'
>>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataTableCreationCommand_0','CREATE TABLE tdata_%d (item_id integer not null,tdata_timestamp integer not null,tdata_value text null)')
>>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataIndexCreationCommand_0','CREATE CLUSTERED INDEX idx_tdata_%d ON tdata_%d(item_id,tdata_timestamp)')
>>> SELECT id FROM nodes
Converting table tdata_111:   0%>>> EXEC sp_rename 'tdata_111','tdata_temp_111'
>>> SELECT var_value FROM metadata WHERE var_name='TDataTableCreationCommand_0'
>>> CREATE TABLE tdata_111 (item_id integer not null,tdata_timestamp integer not null,tdata_value text null)
>>> SELECT var_value FROM metadata WHERE var_name='TDataTableCreationCommand_1'
>>> SELECT var_value FROM metadata WHERE var_name='TDataTableCreationCommand_2'
>>> SELECT var_value FROM metadata WHERE var_name='TDataTableCreationCommand_3'
>>> SELECT var_value FROM metadata WHERE var_name='TDataTableCreationCommand_4'
>>> SELECT var_value FROM metadata WHERE var_name='TDataTableCreationCommand_5'
>>> SELECT var_value FROM metadata WHERE var_name='TDataTableCreationCommand_6'
>>> SELECT var_value FROM metadata WHERE var_name='TDataTableCreationCommand_7'
>>> SELECT var_value FROM metadata WHERE var_name='TDataTableCreationCommand_8'
>>> SELECT var_value FROM metadata WHERE var_name='TDataTableCreationCommand_9'
>>> SELECT var_value FROM metadata WHERE var_name='TDataIndexCreationCommand_0'
>>> CREATE CLUSTERED INDEX idx_tdata_111 ON tdata_111(item_id,tdata_timestamp)
>>> SELECT var_value FROM metadata WHERE var_name='TDataIndexCreationCommand_1'
>>> SELECT var_value FROM metadata WHERE var_name='TDataIndexCreationCommand_2'
>>> SELECT var_value FROM metadata WHERE var_name='TDataIndexCreationCommand_3'
>>> SELECT var_value FROM metadata WHERE var_name='TDataIndexCreationCommand_4'
>>> SELECT var_value FROM metadata WHERE var_name='TDataIndexCreationCommand_5'
>>> SELECT var_value FROM metadata WHERE var_name='TDataIndexCreationCommand_6'
>>> SELECT var_value FROM metadata WHERE var_name='TDataIndexCreationCommand_7'
>>> SELECT var_value FROM metadata WHERE var_name='TDataIndexCreationCommand_8'
>>> SELECT var_value FROM metadata WHERE var_name='TDataIndexCreationCommand_9'
>>> DROP TABLE tdata_111
>>> EXEC sp_rename 'tdata_temp_111','tdata_111'
failed
>>> DELETE FROM metadata WHERE var_name LIKE 'TDataTableCreationCommand_%' OR var_name LIKE 'TDataIndexCreationCommand_%'
>>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataIndexCreationCommand_0','CREATE CLUSTERED INDEX idx_tdata_%d_id_timestamp ON tdata_%d(item_id,tdata_timestamp)')
>>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataIndexCreationCommand_1','CREATE INDEX idx_tdata_rec_%d_instance ON tdata_records_%d(instance)')
>>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataIndexCreationCommand_2','CREATE INDEX idx_tdata_rec_%d_id ON tdata_records_%d(record_id)')
>>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataTableCreationCommand_0','CREATE TABLE tdata_%d (item_id integer not null,tdata_timestamp integer not null,record_id bigint not null,UNIQUE(record_id))')
>>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataTableCreationCommand_1','CREATE TABLE tdata_records_%d (record_id bigint not null,row_id bigint not null,instance varchar(255) null,PRIMARY KEY(row_id),FOREIGN KEY (record_id) REFERENCES tdata_%d(record_id) ON DELETE CASCADE)')
>>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataTableCreationCommand_2','CREATE TABLE tdata_rows_%d (row_id bigint 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)')
Rolling back last stage due to upgrade errors...
Database upgrade failed



Hi Victor,

a really nice release with some great new features, works fine for now 

I have some wishes on the new rack-feature:
- Drag and Drop on the rack would be nice to move the components around
- I would like to have front and rear view for a rack
- Rack-placement for clusters would be nice; for example I have some NetApp SANs which consists of two monitored heads, but are build in one enclosure
- Popup on mouseover on the components, same as on network maps

Thanks for the new file upload feature, finally a can push my PowerShell scripts to the nodes.
Can you give some example how to use it?

Keep on the superb work, love your tool!

Hello Victor,

is it possible to add the user name of the Windows event log entry to the event parameters?
I monitor a terminal server farm for application crashes which works really nice, but I like to know in the event which user session is affected.

Greetings
Ben

Thanks for your reply. I haven't found time yet but I will definitivly test that.

Hi Victor,

is it possible that this feature is some sort of broken in version 2.0-RC1?
I tried to use it for a some printers attached to a single print server, because I like to have separate node with status for each printer. But I can't set the printers IP to the same as of the print server after I check the option "This is address of remote management node", because of an IP address conflict.

Regards,
Ben

Thanks for your answer, Victor.
Is there a NXSL function to upload files to an agent? I thought I read something some time ago but I can't find it anymore...

Hello,

I have a some powershell scripts which i use on windows agents by the ExternalParameter or ExternalList-options. This works quite well, but currently I copy these scripts manually to the agents data folder.
Is it possible that that agent automatically loads additional files in its data folder? I guess the configuration poll hook would be a good place for such an "action", but I can't find any info how to upload or download a file to the agent by NXSL.
Or is there even a simpler method to copy files from server to agent for some library files?

Regards,
Ben

I've used this solution in past and it works very well.
Actually I've added an ExternalList, so the available sensors can be discovered by instance discovery.




Line in Agent config file:
ExternalList = OpenHardwareMonitor.Sensors:powershell -NonInteractive -Command "& { get-wmiobject -namespace root\OpenHardwareMonitor -query 'select * from Sensor' | foreach { $$_.InstanceId } }"



WMI.Query(root\OpenHardwareMonitor,"select * from Sensor where InstanceId='{instance}'",Value)



SensorType = AgentReadParameter($node, "WMI.Query(root\OpenHardwareMonitor,\"select * from Sensor where InstanceId='" . $1 . "'\",SensorType)");
Name = AgentReadParameter($node, "WMI.Query(root\OpenHardwareMonitor,\"select * from Sensor where InstanceId='" . $1 . "'\",Name)");
Identifier = AgentReadParameter($node, "WMI.Query(root\OpenHardwareMonitor,\"select * from Sensor where InstanceId='" . $1 . "'\",Identifier)");

return %(SensorType == "Temperature", $1, Name . "  [" . Identifier . "]");

Hi,

I'm currently struggling about monitoring clusters.
For example I'd like to add a cluster container with some Hyper-V cluster nodes. On the cluster "Last Values" tab I'd like to have the CPU usage of all virtual machines hosted by the cluster. Intuitively I'd like to add each virtual machine to the cluster's resources, but here starts my problem: I guess cluster resources are assigned to cluster nodes by MAC address match? I don't know how to do that with virtual machines...
My wish would be that the owner of cluster resources can be assigned by script execution, not only by virtual IP. It would be easy to determine the hosting cluster node of a virtual machine by a wmi query. Also there would be may more possibilities using cluster resources, which currently I rarely use...

Hello Victor,

the Windows client keeps crashing immediatly after it is contactad by the server. It happens on all machines. I reverted the client to 2.0-M4 which runs without any problems.

It seems there are still some database issues. I did a fresh install with a new database today (Windows x64, MSSQL) and netxmsd keeps crashing after installation. Then I installed 1.2.14 and did an upgrade to 1.2.16, which worked without any problems.