Help with upgrade from Solus 3.9 to 3.11 issue

[MrWu]

Hi all

 

Having a bit of an issue upgrading to Solus 3.11

 

The plan was to go from 3.9 to 3.11 then to 3.12

 

I updated to Solus 3.11, initially seemed successful but noe only 4 machines have updated to 3.11 and it looks like Solus 3 just sits there now saying in progress.

 

The Solus 3 deployment UI still has version 3.9 on the top of the info bar.

 

It has now sat there for 1 hour with only 4 machines updated.

 

I have turned Solus 3 off and on via UI .. no effect

 

Any ideas? Just anxious there’s an issue with updating since I might need to patch things for exam results ..

 

Thanks as always!

 

Wil

[MrWu]

Jesus, looks like it is updating the agents but at a really slow pace, did another 5 in over an hour, will wait overnight ...

[Cache]

I think 3.9 was the last of the dudogy updating pratices, 3.11 is much quicker in kicking them off.

 

3.9 I think will go int eh batches of the number of simultaneous downloads, wait for the batch to either complete, fail or timeout (which by default is 30 mins from memory) and will then move on to the next batch.

[MrWu]

It does seem a bit dodgy indeed, overnight it did do 70 plus machines then the deployment failed flagging up a database tolerance error

 

I started a new deployment, it attempted about 4 machines then fell over again with the same error

 

I have attached an error log, any ideas?

 

cheers!

 

Wil

solus 3 error.txt

[MrWu]

I have noticed in the error log it's trying to update SOLUS 3 on an old SIM server name however (which was migrated by Capita a few years ago, can't seem to remove it from SOLUS 3 GUI since apparently it's still tied to the SOLUS 3 interface. Could this be the issue with tolerance error?

 

 

2018-08-05 08:47:05.6238|***

2018-08-05 08:47:05.6238|*** Deploying Solus 3 - 3.11.61 to Solus 3 GUI (64Bit) targets at SOLUS3 System (99999999-9999999)

2018-08-05 08:47:05.6238|***

 

2018-08-05 08:47:05.6348|ds|Info|1 agent target(s) found for Solus 3 GUI at site SOLUS3 System.|SetAgentTargetsForThisDeployment()

2018-08-05 08:47:05.6468|srv-sims01|Info|Target version 3.9.0.18, expected target version 3.11.61.2, update will be deployed|ProcessAgentTargets()

2018-08-05 08:47:05.6498|srv-sims01|Info|Attempting wake on lan.|AgentIsAvailable()

2018-08-05 08:47:55.6537|ds|Info|Waiting for target Solus 3 GUI to complete deployment for 1 sites 99999999-9999-9999-9999-999999999999|BackgroundWorkerDoWork()

2018-08-05 08:48:55.7138|ds|Info|Waiting for target Solus 3 GUI to complete deployment for 1 sites 99999999-9999-9999-9999-999999999999|BackgroundWorkerDoWork()

2018-08-05 08:49:55.8090|ds|Info|Waiting for target Solus 3 GUI to complete deployment for 1 sites 99999999-9999-9999-9999-999999999999|BackgroundWorkerDoWork()

2018-08-05 08:50:55.9043|ds|Info|Waiting for target Solus 3 GUI to complete deployment for 1 sites 99999999-9999-9999-9999-999999999999|BackgroundWorkerDoWork()

2018-08-05 08:51:55.9999|ds|Info|Waiting for target Solus 3 GUI to complete deployment for 1 sites 99999999-9999-9999-9999-999999999999|BackgroundWorkerDoWork()

2018-08-05 08:52:06.1721|srv-sims01|Info|Wake on lan failed.|AgentIsAvailable()

2018-08-05 08:52:16.2037|ds|Info|Deployment to site SOLUS3 System (99999999-9999-9999-9999-999999999999) has been completed.|RunInternal()

2018-08-05 08:52:16.2037|ds|Info|Deployment plan has failed to install at site SOLUS3 System 99999999-9999999|RunInternal()

 

2018-08-05 08:52:26.0391|***

2018-08-05 08:52:26.0391|*** Checking tolerance for Solus 3 GUI (64Bit) targets

2018-08-05 08:52:26.0391|***

 

2018-08-05 08:52:26.0391|ds|Info|Site count: 1, no failed site deployments: 1, required tolerance: 100, calculated tolerance: 0, tolerance passed: False|CheckTolerance()

2018-08-05 08:52:26.0391|ds|Info|Tolerance not met for target Solus 3 GUI, deployment stopping.|CheckTolerance()

[MrWu]

Looking at the first time it failed (last night) seems the pattern would be it falls over on checking tolerances for SOLUS 3 64Bit deployments: (but still could be related to the old server name..)

 

 

 

2018-08-05 00:46:42.4307|***

2018-08-05 00:46:42.4307|*** Deploying Solus 3 - 3.11.61 to Solus 3 GUI (64Bit) targets at SOLUS3 System (99999999-9999999)

2018-08-05 00:46:42.4307|***

 

2018-08-05 00:46:42.4307|ds|Info|2 agent target(s) found for Solus 3 GUI at site SOLUS3 System.|SetAgentTargetsForThisDeployment()

2018-08-05 00:46:42.4463|srv-sims01|Info|Target version 3.9.0.18, expected target version 3.11.61.2, update will be deployed|ProcessAgentTargets()

2018-08-05 00:46:42.4463|srv-sims01|Info|Attempting wake on lan.|AgentIsAvailable()

2018-08-05 00:46:42.4619|srv-mis01|Info|Target version 3.9.0.18, expected target version 3.11.61.2, update will be deployed|ProcessAgentTargets()

2018-08-05 00:46:42.5244|srv-mis01|Info|Agent is available for target id 811.|AgentIsAvailable()

2018-08-05 00:46:42.5244|srv-mis01|Debug|Throttling - Download slot now available|AgentIsAvailable()

2018-08-05 00:46:42.5244|srv-mis01|Debug|Target id 811 instructed to deploy.|Execute()

2018-08-05 00:46:42.5557|ds|Debug|CreateAgentPackageSiteRecord updating _agentTargeted for agent target id 811|SendExecuteCommandToAgent()

2018-08-05 00:46:43.0244|srv-mis01|Info|Started downloading package 'Solus 3 - 3.11.61 (Solus 3 GUI)'|UpdateProgress()

2018-08-05 00:46:43.9151|srv-mis01|Info|Successfully finished downloading update 'Solus 3 - 3.11.61 (Solus 3 GUI)'. |UpdateProgress()

2018-08-05 00:46:43.9307|srv-mis01|Debug|Throttling - Downloaded update, download slot has been cleared|b__0()

2018-08-05 00:47:32.5100|ds|Info|Waiting for target Solus 3 GUI to complete deployment for 1 sites 99999999-9999-9999-9999-999999999999|BackgroundWorkerDoWork()

2018-08-05 00:48:32.6056|ds|Info|Waiting for target Solus 3 GUI to complete deployment for 1 sites 99999999-9999-9999-9999-999999999999|BackgroundWorkerDoWork()

2018-08-05 00:48:51.5902|srv-mis01|Info|Tgt 811, Pkg 5b3b135b-47cd-46d5-90b0-bc3af2494a15, TasksetRunner|Running task, 'Upgrade UI', in Backup mode.|UpdateProgress()

2018-08-05 00:48:51.6527|srv-mis01|Info|Tgt 811, Pkg 5b3b135b-47cd-46d5-90b0-bc3af2494a15, TasksetRunner|Result was Ignored for task 'Upgrade UI' with message 'Task does not implement rollback strategy.'|UpdateProgress()

2018-08-05 00:48:51.7308|srv-mis01|Info|Tgt 811, Pkg 5b3b135b-47cd-46d5-90b0-bc3af2494a15, TasksetRunner|Running task, 'Upgrade UI', in Install mode.|UpdateProgress()

2018-08-05 00:49:05.2623|ds|Info|Creating agent update records.|Execute()

2018-08-05 00:49:12.0905|srv-mis01|Info|Tgt 811, Pkg 5b3b135b-47cd-46d5-90b0-bc3af2494a15, TasksetRunner|Result was Succeeded for task 'Upgrade UI'|UpdateProgress()

2018-08-05 00:49:12.1530|srv-mis01|Info|Tgt 811, Pkg 5b3b135b-47cd-46d5-90b0-bc3af2494a15, Package runner completed successfully.|UpdateProgress()

2018-08-05 00:49:12.3718|srv-mis01|Info|Tgt 811, Pkg 5b3b135b-47cd-46d5-90b0-bc3af2494a15, Update was successfully installed|UpdateProgress()

2018-08-05 00:49:32.7002|ds|Info|Waiting for target Solus 3 GUI to complete deployment for 1 sites 99999999-9999-9999-9999-999999999999|BackgroundWorkerDoWork()

2018-08-05 00:49:51.4037|ds|Info|Creating agent update records.|Execute()

2018-08-05 00:49:51.9662|srv-remote02|Info|Started downloading package 'Solus 3 - 3.11.61 (Solus 3 Agent)'|UpdateProgress()

2018-08-05 00:49:57.3726|srv-remote02|Info|Successfully finished downloading update 'Solus 3 - 3.11.61 (Solus 3 Agent)'. |UpdateProgress()

2018-08-05 00:50:32.7959|ds|Info|Waiting for target Solus 3 GUI to complete deployment for 1 sites 99999999-9999-9999-9999-999999999999|BackgroundWorkerDoWork()

2018-08-05 00:51:32.8919|ds|Info|Waiting for target Solus 3 GUI to complete deployment for 1 sites 99999999-9999-9999-9999-999999999999|BackgroundWorkerDoWork()

2018-08-05 00:51:43.1423|srv-sims01|Info|Wake on lan failed.|AgentIsAvailable()

2018-08-05 00:51:53.1896|ds|Info|Agent srv-mis01, target id 811 reported target version number 3.11.61.2, expected target version is 3.11.61.2.|WaitForAgentResponse()

2018-08-05 00:51:53.1896|srv-mis01|Info|Agent has responded|Execute()

2018-08-05 00:52:03.2212|ds|Info|Deployment to site SOLUS3 System (99999999-9999-9999-9999-999999999999) has been completed.|RunInternal()

2018-08-05 00:52:03.2212|ds|Info|Deployment plan has failed to install at site SOLUS3 System 99999999-9999999|RunInternal()

2018-08-05 00:52:04.7681|srv-remote02|Info|Tgt 1337, Pkg a9d8c3c7-7ebf-493e-9cfc-ed8a7c91fa1e, TasksetRunner|Running task, 'Upgrade Agent', in Backup mode.|UpdateProgress()

2018-08-05 00:52:04.8150|srv-remote02|Info|Tgt 1337, Pkg a9d8c3c7-7ebf-493e-9cfc-ed8a7c91fa1e, TasksetRunner|Result was Ignored for task 'Upgrade Agent' with message 'Task does not implement rollback strategy.'|UpdateProgress()

2018-08-05 00:52:04.8619|srv-remote02|Info|Tgt 1337, Pkg a9d8c3c7-7ebf-493e-9cfc-ed8a7c91fa1e, TasksetRunner|Running task, 'Upgrade Agent', in Install mode.|UpdateProgress()

 

2018-08-05 00:52:12.9560|***

2018-08-05 00:52:12.9560|*** Checking tolerance for Solus 3 GUI (64Bit) targets

2018-08-05 00:52:12.9560|***

 

2018-08-05 00:52:12.9560|ds|Info|Site count: 1, no failed site deployments: 1, required tolerance: 100, calculated tolerance: 0, tolerance passed: False|CheckTolerance()

2018-08-05 00:52:12.9560|ds|Info|Tolerance not met for target Solus 3 GUI, deployment stopping.|CheckTolerance()

 

 

 

2018-08-05 00:52:12.9560|***

2018-08-05 00:52:12.9560|*** Rollback starting

2018-08-05 00:52:12.9560|***

[Cache]

Yes it's saying the tollerance for installing the Solus3 GUI isn't met, if you go into Settings -> Solus 3 at the top should be a link to Show Solus3 targets (I think it's the same in 3.9)

 

You should have 3 - GUI, Database, Deployment Service and they should all say that they are on your current server - there might be some additional ones there which as long as they are present on another agent you should be able to remove. If they are listed there on your old server and you can't remove them you'll need to get in touch with Capita and ask them about it, I had an issue where the server was renamed after Solus3 had been installed so the old server name was still marked as the active target and they needed to update the target name/id in the database to allow it to work as it should.

[MrWu]

@Cache

 

Thanks ! What you suggested did the trick !

[Cache]

No probs, pleased you've got sorted!