NetXMS Support Forum

File is present and md5 hash is same.

It seems that "nxagent-3.2.350-x64.exe" is uploaded to "var" but after that error "File transfer failed" is received.

Level 6 debug:
2020.02.28 08:23:55.327 *D* [comm.cs.2          ] Requesting parameter "System.PlatformName"
2020.02.28 08:23:55.327 *D* [comm.cs.2          ] Sending message CMD_REQUEST_COMPLETED (ID 3; size 56; uncompressed)
2020.02.28 08:23:55.329 *D* [comm.cs.2          ] Received message CMD_TRANSFER_FILE (4)
2020.02.28 08:23:55.329 *D* [comm.cs.2          ] CommSession::recvFile(): Preparing for receiving file "nxagent-3.2.350-x64.exe"
2020.02.28 08:23:55.329 *D* [comm.cs.2          ] CommSession::recvFile(): Writing to local file "C:\NetXMS\var\nxagent-3.2.350-x64.exe"
2020.02.28 08:23:55.332 *D* [comm.cs.2          ] Sending message CMD_REQUEST_COMPLETED (ID 4; size 32; uncompressed)
2020.02.28 08:23:55.339 *D* [comm.cs.2          ] Received raw message CMD_FILE_DATA
  [Repeats alot]
2020.02.28 08:23:55.341 *D* [comm.cs.2          ] Received raw message CMD_FILE_DATA
2020.02.28 08:24:01.203 *D* [comm.cs.2          ] Sending message CMD_REQUEST_COMPLETED (ID 4; size 32; uncompressed)
2020.02.28 08:24:01.203 *D* [comm.cs.2          ] Communication channel closed by peer
2020.02.28 08:24:01.204 *D* [comm.cs.2          ] Session with [NetXmsIP] closed
2020.02.28 08:24:01.204 *D* [comm.cs.2          ] Session unregistered
2020.02.28 08:24:01.204 *D* [comm.cs.2          ] Receiver thread stopped

i have lvl 9 debug also but thats litle big for posting

Hello

Where could i find information about failed package deployment. When new version came out, most of the agents upgraded fine, but 5 did not. I get error "File transfer failed" or "Unable to start upgrade process"

Egert

Few things i noticed:

Alarm windows shows warning: Only 4096 most recent alarms shown and alarm window is filled with agent messages "[Normal]   Node name   Package xxx updated from  to unset"

Cant find DCI for: "New internal parameters for server stats (object count, alarm count, etc.)"

Future idea:

Would it be possible to add version check to agent upgrade process? When upgrading alot of agents then it is unneccesary to reupload package and install when version is already updated.

Maybe its somthing similar to my post, worth reading

https://www.netxms.org/forum/general-support/cant-get-powershell-script-to-run/msg27392/#msg27392

Thanks for the reply. In later posts i changed the polling method to script file instead of direct command in agent conf. When i changed script content to simple output where i could change execution time, then depending on run time > 4835ms:error | < 4835ms:good. So i think path variable is working.

$age = 1500;
Start-Sleep -Milliseconds 4840
$Output = 'Parameter.Name=' + $age
echo $Output


Currently working method:

Agent Conf:
ExternalParametersProvider=powershell.exe C:\NetXMS\script\ReturnInfo.ps1:1800

ReturnInfo.ps:
$DataFile = "C:\NetXMS\script\output.txt"

$Array = "";

if (Test-Path -Path $DataFile) {

    $Content = Get-Content $DataFile
    $Array = $Content.split('|');

}


return $Array

Output.txt is generated from different script that is running with task scheduler.

Thanks for tip.

I went with following solution:

Agent conf:
Query = Alarms-Outstanding:db1:300:SELECT COUNT (alarm_state) as Alarms FROM [netxms_db].[dbo].[alarms] WHERE alarm_state = 0

Dci parameter: DB.QueryResult(Alarms-Outstanding)

Hello

Is it possible to log statistics shown in console 'sh sta'? For example poll them via dci script?

Resurecting an old topic.

What i am trying to do is make tool->restart ssh command (for ubiquiti wireless device).

is "$node->executeSSHCommand("reboot");" correct syntax ? when i run it it returns null as value and device doesent reboot. Ssh credentials are filled out in node config.

Have you configured switch snmp, does netxms discover node as snmp compatible?

Map mode is custom map, automatic layout is disabled. Only "show grid" / "snap to grid" are enabled when editing.

Preview:

Have tested in win 7 and win server 2008 r2. Management console version 3.1.300

Hello

Not realy sure if its a bug or ment to be like so. Basicly when creating custom network map and drag/drop a new node into map it always ends up in top left cornern. When map gets bigger it is annoying to constantly have to scroll back up to find new node and drag it back to where ever it needs to go. It would be nice if node appears where it was dropped to.

Win 7 Pro

$PSVersionTable:
Name                           Value                                                                                                                                                                                                                             
----                           -----                                                                                                                                                                                                                             
PSVersion                      4.0                                                                                                                                                                                                                               
WSManStackVersion              3.0                                                                                                                                                                                                                               
SerializationVersion           1.1.0.1                                                                                                                                                                                                                           
CLRVersion                     4.0.30319.42000                                                                                                                                                                                                                   
BuildVersion                   6.3.9600.16406                                                                                                                                                                                                                   
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0}                                                                                                                                                                                                             
PSRemotingProtocolVersion      2.2   


Currently i have setup where i run PS script with task scheduler and save result into txt file. Then with netxms agent i run a script that reades value out of txt file. That way it stays well under 1 sec runtime and works perfectly. Currently testing in 8 different machines.

ExternalParametersProvider=powershell.exe C:\NetXMS\script\ReturnInfo.ps1:1800

Seems like it is Bug / error on netxms, did quick and simple test:

Script:
$age = 1500;
Start-Sleep -Milliseconds 4840
$Output = 'Parameter.Name=' + $age
echo $Output

if script ran 4835 ms or more then no result to agent. Anything less and agent received value.

Also "The pipe has been ended." doesent mean error, it comes with 0 or 1 value.