 noel_david
		
			noel_david
		
		
		
		
		
		
		
		
	
			
		
		
			
					
		
			on 
    
	
		
		
		21 Nov 2024
	
		
		08:11 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
 - edited on 
    
	
		
		
		30 May 2025
	
		
		08:16 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
 by 
				
		 MaciejNeumann
		
			MaciejNeumann
		
		
		
		
		
		
		
		
	
			
		
Below are the three common scenarios during the Dynarace One agent update. Let's check how it's fixable.
Scenario 1.
This happens in Windows machines.
This is not a Dynatrace issue; the error message points to the MS error code, which can happen for many reasons. For more details, please check the page below.
MSI installation error 1603 - Windows Server | Microsoft Learn
Scenario 2.
This happens in Linux hosts.
In the OS logs we can see the warning message for this
Error: Detected that /opt/dynatrace/oneagent is a dangling symlink, please remove it and then retry the installation
It means the installation directory is soft-linked, which is not supported. The installation path must be the real directory. This is why the Agent update keeps failing.
Scenario 3.
 
This is a self-explanatory issue; the updates can fail due to insufficient disk space.
Scenario 4.
 This issue happens in Linux hosts; this can be due to many reasons.
Running the health check will show the details.
./oneagentctl --healthcheck
Hi, about scenario 3, how can we check in advance if a host has sufficient disk space?
My idea is to run a check 2 weeks before oneagents update to detect hosts on which to increase disk space when it is insufficient.
Thanks
 noel_david
		
			noel_david
		
		
		
		
		
		
		
		
	
			
		
		
			
					
		Hi Paolo,
The logic of checking if there are enough spaces is invoked during the update/installation step. As of now, it's not possible to check the disk space in advance.
But this page will be helpful.
https://docs.dynatrace.com/docs/shortlink/oneagent-disk-requirements-windows#updates