NetXMS Support Forum

when I set sever variable 'CheckTrustedNodes' to 0 (and restart the NetXMS server of course), I get the nodes on the map. But I get no connectors on the map beside VPN-connectors. Why? Connectors are no NetObj objects.... so no filtering on that. Is this the same on your installation?

I don't understand exactly why 'CheckTrustedNodes' has an influence here.
But when I set all nodes in a container to the Trusted Nodes of this container, this nodes appear on the map.

Thanks for the hint with the 'direct' parents.

Have you done a configuration poll on these nodes?

Thanks for your fast reply Tomas.

using $object instead of $1 -> Error 17 (Argument is not of string type and cannot be converted to string. So I changed to
parents = GetNodeParents($object);
-> Error 21 (Bad or incompatible object class), it's NetObj not Node class. So I tried this (most logical for me):
parents = GetObjectParents($object);
No error, but now the map is empty :-(

I registered a ticket for the disable-bug

thanks
Dani

I have a Layer3 map where I only want nodes from container 'London'.

I tried with the following filter script but got always all nodes instead of only those in container 'London':

parents = GetNodeParents((FindObject($1));
if (parents == null) return false;
foreach(p : parents)
{
   if (p->type == 5 && p->name == "London") return true;
}
return false;

• Do I have a typo or an error in reasoning?
• What is the input of the filtering script? An object? An ID? (didn't found it in documentation)
• When you temporarily disable the filter, the filtering script will be deleted (bug or feature?)

Thanks for any input!

Hi

In VPN-Connector it's not possible to set the peer gateway anymore . You can choose one and exit with 'ok'. But if you open the VPN connector configuration again the field 'Peer gateway' ist '<none>' again. I use the java console on Win-x64. The server is V2.0-M5 on linux-x64 compiled from sources.
Is this a known bug? If yes, is there a workaround?

Edit:
I narrowed down the problem.
When you create a new VPN connector, than edit this connector filling in the peer gateway, the local and the remote networks, everything is ok.
But when you create a new VPN connector, than edit this connector filling in only the local and the remote networks (missing the peer gateway) and finish with 'ok'. Than you edit the VPN connection again filling in the missing peer gateway, this field will not be saved!

thanks
Dani

Have you found anything in the debug log file?

Thanks Victor

Only a first short test on Win2012R2 with your fixed agent installer:

• no crashes yet
• it's possible to stop the service in control panel without error
• configuration poll on this node can get network interface configuration
• configuration poll on this node can get installed software packages

thanks for the quick fix, I will test more tomorrow

Dani

Here the crash dump of a Win-x64 agent. If you need more information, please ask.

Update the windows agents from NetXMS console (V2.0-M4 to V2.0-M5) worked ok (for Win-32bit for the first time in this verson!).

I also see the Windows agent crashes on some nodes, the agent is always restarted from the watchdog process but immediately crashs again.
When I try to stop windows agent from control panel on all Windows nodes I get the error "Error 109: The pipe has been ended". After that the agent ist stopped and can be started again.

Configuration poll on windows agents always give:

[21.06.2015 15:18:15] Capability check finished
[21.06.2015 15:18:15] Checking interface configuration...
[21.06.2015 15:18:15] Unable to get interface list from node
[21.06.2015 15:18:15] Interface configuration check finished
[21.06.2015 15:18:15] Checking node name
[21.06.2015 15:18:15] Node name is OK
[21.06.2015 15:18:15] Reading list of installed software packages
[21.06.2015 15:18:15] Unable to get information about installed software packages
[21.06.2015 15:18:15] Finished configuration poll for node node.domain.com
[21.06.2015 15:18:15] Node configuration was not changed after poll


So get installed software and interface list are not possible.

Downgrade to V2.0-M5 from the NetXMS console works only for nodes where the agent not crash all the time.

Linux agents are ok.

And there also no entries in 'View - Evenlog' ('Syslog Monitor' is only the live view)?

Is syslog activated in Server Configuration? (EnableSyslogDaemon = 1)
Check also what you have in the Server Configuration Value 'SyslogNodeMatchingPolicy', default is '0', so the NetXMS syslog server tries first matching incoming syslog-messages by source IP address (check that incoming messages come from primary IP address of this node in NetXMS) and than by 'Host Name' field in the syslog-message itself.
Maybe that helps finding the cause.

is the sending device existing as a node in NetXMS?

Hi Victor

Have you found anything about this?

thanks
Dani

that's the right server setting, yes.

Hi Victor

Here the agent log with debuglevel=2. There was no "LogWatch: EvtQuery failed (...)".
There were these events for example before the NetXMS agent started:
Event-ID 41, Source=Kernel-Power, severity=critical, 04.05.2015 18:19:34
Event-ID 6008, Source=EventLog, severity=error, 04.05.2015 18:19:36

thanks
Dani

I have updated to V2.0-M4, but I see the same issue as before.

I tested like this:

parser xml:
<parser name="SystemLog">
  <file>*System</file>
  <rules>
    <rule>
      <match>(.*)</match>
      <level>1</level>
      <event params="1">100845</event>
    </rule>
  </rules>
</parser>

I turned off hardly a Win7-x64 virtual machine and started again. But I don't get an event '100845' in NetXMS for the windows error 6008 (last shutdown was unexpected) in the system eventlog.

Other windows events while the node is normal working are parsed ok and generate NetXMS events.