NetXMS Support Forum

I was worried that would be the case.  I'll look into some scripts to do this.

Cheers.

Hi gdodd I also get this error on latest agents when deploying it centrally to working agents.  In the past when I had this error it was because the agent version string had a build hash in the version string and the NPI had the correct version string.  Editing the NPI manually fixed that until the next agent release, but that doesn't seem to be the issue here, agent version and NPI seem to match for me.

Also having issues on older agents upgrading with .part01 appended to the end of installer transfers.  Have you had any of those issues too?

Quote from: gdodd on October 05, 2021, 04:10:21 AM
- Fixed bug in centralized agent upgrade on Windows

Does that mean once server and agent are on 3.9.298, future centralized agent upgrades should work? Or should it work with just server on 3.9.298?

I am trying to upgrade Windows agents 3.9.280 from Linux server 3.9.298 and get the "Agent's version doesn't match..." error message.

Still not having much luck with deploying central package upgrades even with new 3.9.298 for server/console and with agent packages.

Still get "file transfer failed" errors deploying to older windows nodes (since 3.9.235) that have not have their agents manually removed and re-installed locally (this in win7/10 32/64bit).  I can see in c:\netxms\var\ that there are duplicate copies of the 3.9.298 installer with part0 through part7 appended to the exe 1024 bytes each).  Does NX-2129 apply to agent deployment?

On the machines that I manually removed the agents and deleted the c:\netxms folder I'm also getting an error "Agents version doesn't match package version after upgrade" after central deployment even though as far as I can see NPI version string and installed agent version match (no build hash in the agent version for eg).

Where do agent install logs get saved locally, can't see anything in c:\netxms\logs (after taking ownership from SYSTEM).

Looks to be running under system, and hardened permissions are under that user. 

Server version is on 3.9.280, trying to upgrade windows 32/64 agents to 3.9.280 from a mix of 3.9.156 and 3.9.235

Perhaps not hardened permissions though, I've got one win10 and one win server 2016 that weren't installed with hardened permissions and had the same issue attempting to install from package manager.  Manual uninstall and reinstall of agent seems to fix it in that I don't then get file transfer failed errors in package manager when running a deployment (completed). 

I guess I only know if package manager install truly works when the next agent version is released to see if upgrades on these completed nodes also succeed then?

So definitely still getting the file transfer errors in .280 server/NXMC. 

If I manually uninstall the agent package on windows and take ownership of the c:\netxms folder and remove it (due to hardened system permissions) and then reinstall the agent package from scratch it starts working (in terms of file transfer and agent upgrades in the package manager).

So it looks like I might have to manually remove and reinstall out of band to netxms to get back to working.

Could it be an issue with hardened system permissions causing the file transfer / install to fail?  Guess you need logs next?

+1

Just tried new server and agent versions of .280 and still getting the same error when trying to push the agent install package to the end clients (files transfer failed).

Also if I manually try and run the windows 64bit installer I'm seeing errors about entry points in ssl libraries from the looks of it. Will attach some examples in the morning.

Great, thanks Filipp

Since upgrading to 3.9-235 for nxmc and server I can't deploy agent upgrades to windows clients.  I just get back an instant "file transfer failed" response.

Also get "cannot connect to NetXMS agent (internal error)" in status poll log on server.

Have restarted server (process and VM) no change.

nxdbmgr passes checks and is on the latest version.  Where should I look in the logs (and which level should I enable)?

Was about to ask the same thing having just updated.  Looks like that might have missed this release?

Hi when running nxdbmgr check on latest version I get asked if I want to delete orphaned tables.

The first few succeeded, however after the first few successful removals there are errors on subsequent tables re. constraint violations and the overall transaction fails:


# nxdbmgr check
NetXMS Database Manager Version 3.8.314 Build 3.8-314-g9d14b98df7 (UNICODE)

Checking database (excluding collected data):
* Zone object properties                                               [PASSED]
* Node object properties                                               [PASSED]
* Node to subnet bindings                                              [PASSED]
* Interface object properties                                          [PASSED]
* Interface bindings                                                   [PASSED]
* Network service object properties                                    [PASSED]
* Network service bindings                                             [PASSED]
* Cluster object properties                                            [PASSED]
* Cluster member nodes                                                 [PASSED]
* Template to node mapping                                             [PASSED]
* Object properties                                                    [PASSED]
* Container membership                                                 [PASSED]
* Event processing policy                                              [PASSED]
* Network map links                                                    [PASSED]
* Data tables                                                          [PASSED]
* Orphaned data tables                                                 [  12% ]
Data collection table tdata_1124 belongs to deleted object and no longer in use. Delete it? (Y/N)  (Yes/No/All/Skip) a
SQL query failed (2BP01 ERROR:  cannot drop table tdata_1124 because other objects depend on it
DETAIL:  constraint tdata_records_1124_record_id_fkey on table tdata_records_1124 depends on table tdata_1124
HINT:  Use DROP ... CASCADE to drop the dependent objects too.):
DROP TABLE tdata_1124
* Orphaned data tables                                                 [  12% ]
Data collection table tdata_1126 belongs to deleted object and no longer in use. Delete it? (Y/N)  (Yes/No/All/Skip) Y
SQL query failed (25P02 ERROR:  current transaction is aborted, commands ignored until end of transaction block):
DROP TABLE tdata_1126
* Orphaned data tables                                                 [  12% ]
Data collection table tdata_1128 belongs to deleted object and no longer in use. Delete it? (Y/N)  (Yes/No/All/Skip) Y
SQL query failed (25P02 ERROR:  current transaction is aborted, commands ignored until end of transaction block):
DROP TABLE tdata_1128
* Orphaned data tables                                                 [  12% ]
Data collection table tdata_1130 belongs to deleted object and no longer in use. Delete it? (Y/N)  (Yes/No/All/Skip) Y
SQL query failed (25P02 ERROR:  current transaction is aborted, commands ignored until end of transaction block):
DROP TABLE tdata_1130
* Orphaned data tables                                                 [  13% ]
Data collection table tdata_1132 belongs to deleted object and no longer in use. Delete it? (Y/N)  (Yes/No/All/Skip) Y
SQL query failed (25P02 ERROR:  current transaction is aborted, commands ignored until end of transaction block):
DROP TABLE tdata_1132
* Orphaned data tables                                                 [  13% ]
Data collection table tdata_1189 belongs to deleted object and no longer in use. Delete it? (Y/N)  (Yes/No/All/Skip) Y
SQL query failed (25P02 ERROR:  current transaction is aborted, commands ignored until end of transaction block):
DROP TABLE tdata_1189
* Orphaned data tables                                                 [  13% ]
<<SNIPPED>>


etc to the bottom:


<<SNIPPED>>
* Orphaned data tables                                                 [ERROR ]
* DCI configuration                                                    [   0SQL query failed (25P02 ERROR:  current transaction is aborted, commands ignored until end of transaction block):
SELECT item_id,node_id FROM items WHERE node_id NOT IN (SELECT object_id FROM object_properties)
SQL query failed (25P02 ERROR:  current transaction is aborted, commands ignored until end of transaction block):
SELECT item_id,node_id FROM dc_tables WHERE node_id NOT IN (SELECT object_id FROM object_properties)
[PASSED]
* Raw DCI values table                                                 [   0SQL query failed (25P02 ERROR:  current transaction is aborted, commands ignored until end of transaction block):
SELECT item_id FROM raw_dci_values
SQL query failed (25P02 ERROR:  current transaction is aborted, commands ignored until end of transaction block):
SELECT count(*) FROM raw_dci_values WHERE last_poll_time>1620602557
[PASSED]
* DCI thresholds                                                       [   0SQL query failed (25P02 ERROR:  current transaction is aborted, commands ignored until end of transaction block):
SELECT threshold_id,item_id FROM thresholds
[PASSED]
* Table DCI thresholds                                                 [   0SQL query failed (25P02 ERROR:  current transaction is aborted, commands ignored until end of transaction block):
SELECT id,table_id FROM dct_thresholds
[PASSED]
100 errors was found, 0 errors was corrected
Database still contain errors
Database check completed



I imagine cascade could be a risky thing to use by default?

I deleted what I could and left the other orphaned tables in there.  Wait for a patch or is there a manual alternative?

Cheers.

Could it depend on your scaling mode of the screen resolution?

Just piping in to say I also see this on windows 10 workstations with the agent installed.

Happy to test out any changes to fix it.

Cheers.

Confirm its fixed in the latest patch.

Thanks again.

Thanks Filipp and Victor, good to hear it could be replicated. 

Thanks for the great software!