NetXMS Support Forum

Hi,

agent and server version 3.9.178
I created a DCI with the agent parameter System.CurrentTime.
I validated timezone settings for multiple windows servers on which agents are running and the collected time is the same.
Should System.CurrentTime represent the current local time of the windows server where the agent is installed?

Thanks. 

Version = 3.9.178
Windows Server 2019
Postgres Db backend

Receiving these on NetXMS core server - it does appear the watchdog has restarted in every occurrence.

Alarm
Thread "Poll Manager" is not responding

and server.log entries?
2021.09.06 19:28:28.406 *E* [watchdog           ] Thread "Poll Manager" does not respond to watchdog thread
2021.09.06 19:28:28.421 *I* [watchdog           ] Thread "Poll Manager" returned to running state

Hi,

We are implementing Jira (Cloud Version) and looking to integrate with NetXMS.  It would be great if you had Jira integration for the Cloud version. 

I can make it work as-is. I have determined to use NetXMS Action to create issue via Jira Rest API, and create Alarm comment with JiraIssue={issueKey}.  Using Jira Webhooks, update NetXMS on issue status change (I have extended WebAPI to support updates via a GraphQL API).  Jira would Acknowledge Alarm when assigned and add Alarm comment with user assigned JiraUserAssigned={jiraUserName}.  On Jira issue close, Resolve Alarm and add comment as needed.  Then as routine maintenance, terminate resolved alarms using scripting. 

It would be helpful to have update access to the NetXMS alarm helpdeskReference field using similar session methods such as session.updateAlarm(Alarm alarm) or session.linkHelpdeskIssue(long alarmId, string helpdeskReference).

Is there any visual indication in NetXMS Alarm browser for helpdesk linked alarms?

Thanks.

The System.Services agent table is great! 
Even better would be to add
Configured "logon as" or "run as" account.
Startup type "auto (delayed start)"

Thanks.

Thanks!
I installed and tested nxagent-3.8.262-x64.exe on Windows Server 2012R2, 2016, and 2019.  All appears to be running normally, with no CRT error detected.

I think I have narrowed it down to having SubAgent = logwatch.nsm enabled.  When a logwatch event is raised I receive the CRT error detected.
<parser trace="0" name="LogParser-EL-Application">
   <file encoding="UTF-8">*Application</file>
   <rules>
      <rule name="ApplicationEventLogError" break="true">
         <match repeatCount="0" repeatInterval="60">(.*)</match>
         <event>EL_APPLICATION_ERROR</event>
         <level>1</level>
      </rule>
      <rule name="ApplicationEventLogWarning" break="true">
         <match repeatCount="0" repeatInterval="60">(.*)</match>
         <event>EL_APPLICATION_WARNING</event>
         <level>2</level>
      </rule>
      <rule name="ApplicationWindowsErrorReporting" break="true">
         <match repeatCount="0" repeatInterval="1">(.*)</match>
         <event>EL_APPLICATION_WINDOWS_ERROR_REPORTING</event>
         <level>4</level>
         <id>1001</id>
         <source>Windows Error Reporting</source>
      </rule>
   </rules>
   <macros/>
</parser>

I am having the exact problem with running the 3.8.226 x64 and 3.8.250 x64 agent running on windows 2012R2, 2016, and 2019 against netxms core 3.4.313 on windows server 2016.  The agent will run for a few minutes and then start filling up the system event log with the following error.
Log Name:      System
Source:        NetXMS Win32 Agent
Date:          4/4/2021 1:14:18 PM
Event ID:      1000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mycomputer.mydomain.com
Description:
CRT error detected
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetXMS Win32 Agent" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-04-04T17:14:18.692060400Z" />
    <EventRecordID>12345</EventRecordID>
    <Channel>System</Channel>
    <Computer>mycomputer.mydomain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>CRT error detected</Data>
  </EventData>
</Event>

Once the error storm starts, agent computer has high CPU usuage and netxms core starts consuming high memory.

Hi,

NetXMS Agent version = 3.5.90

I have added a DCI to track memory use of the NetXMS Agent process using built-in Process.WkSet("nxagentd.exe").
Overtime I see a trend of increased memory use - I have attached chart of trend.  You can see the drops indicating restart of node or agent service.
Is this a memory leak?
What is normal memory use?

Thanks.

Version 3.4
It would be very helpful to allow change owner of scheduled task from any admin user account.  My work-a-round - I have created a special user and edit scheduled task so that the event is logged as that user.  We have several scheduled nodes with startup/shutdown times with associated scheduled tasks.  I plan to create a conditional script for maintenance mode enter/leave to account for node being placed in maintenance manually to over-ride schedule.

Thanks.

Hi,

Has this functionality been added to 3.x line?

Thanks.

Yep - worked like a charm!

parentId = objects.GenericObject.NETWORK # Entire Network root
cd = NXCObjectCreationData(objects.GenericObject.OBJECT_ZONE, "Sample Zone", parentId);
zoneId = session.createObject(cd) # createObject return ID of newly created object
print '"Sample Zone" created, id=%d' % (zoneId, )

The Object Tool is very useful for building tools that require context.  Adding a dropdown or list of choices input field would be a helpful addition.

Would be helpful to have DCI right-click context tool.  This could enable remediation for DCI's in alert status.  I do currently have an Object Tool that uses Alarm message context.

Thanks.  I will give that a try and post my code snippet when I get it working.

Hi,

Is it possible to create a new zone using nxshell in version 3.5?

Thanks.