Autumn Patch

[Tefters]

My lovely Solus picked up the Autumn DB patch last night and upgraded overnight but there's no workstation or full patch... of course now have incompatible DB everywhere...

 

Anyone else?

[Koldov]

I don't have SOLUS automatically install anything! I don't trust SIMS, CAPITA or SOLUS enough to be honest...

 

This is sitting on my SOLUS this morning though, full release is there for me I think - is that what you're looking for?

 

[Tefters]

I don't have SOLUS automatically install anything! I don't trust SIMS, CAPITA or SOLUS enough to be honest...

 

This is sitting on my SOLUS this morning though, full release is there for me I think - is that what you're looking for?

 

[ATTACH=CONFIG]39625[/ATTACH]

 

Yup thanks! On the phone to them now. 95% of the time the auto deployment works great and can't fault it however in this case the Autumn DB patch has appeared and applied but no full release patch on mine and check for updates shows nothing either so can only presume this is what causing the DB Incompatible error.

 

Hopefully they can add it to my Solus account.

[Tefters]

So I have what I can only presume to be a second line guy dial into my server to spend 5 minutes looking at that GUI, trying to redeploy the DB patch that had already applied successfully last night and then tell me "Ow you missing the Full Release Autumn Patch", Thanks... Didn't repeat this 6 times during our phone call...

@PhilNeal - I love Solus3 don't get me wrong here, 95% of the time its fantastic, auto patching works and all is good but how can I end up with a DB patch and no full release... I would imagine there is someone authorizing patches higher up behind the scenes... This has crippled me this morning and I haven't even had a coffee yet!

Edited November 8, 2016 by witch

[Banjo]

Download the full release from the Capita website and install it yourself outside of Solus3. The DB sounds like it's already been done so its just the clients to update.

[Koldov]

Actually @Tefters, now I look at it I may have been in the same situation as you at the beginning of last month if I'd had auto-patch enabled!

 

My SOLUS clearly shows an entry for a SIMS Autumn 2016 Database Only (3.62.574) Release date 12/10/2016, but there is no corresponding full release.

 

Only on the 28/10/2016 is there a Database release (3.62.575) and a full release (7.172.36).

 

Have you confirmed this is what has caused your issue? Have to say I do not understand the process, but why is there a Database only release at all?!

Edited November 8, 2016 by Koldov

[Tefters]

Actually @Tefters, now I look at it I may have been in the same situation as you at the beginning of last month if I'd had auto-patch enabled!

 

My SOLUS clearly shows an entry for a SIMS Autumn 2016 Database Only (3.62.574) Release date 12/10/2016, but there is no corresponding full release.

 

Only on the 28/10/2016 is there a Database release (3.62.575) and a full release (7.172.36).

 

Have you confirmed this is what has caused your issue? Have to say I do not understand the process, but why is there a Database only release at all?!

 

Yup its all sorted now and deploying, sort-of, the Solus3 service is throttling and struggling now...

 

The patch was apparently Authorized but wasn't on my end and they just re-authorized it then poof its there! Take that with a pinch of salt as I can only go by their word

[Tefters]

Urgh now after 2 1/2 hours my Solus3 is borked and the patch is stuck deploying but client machines are now constantly losing connection to the server and showing red.

 

Back on the phone to Capita...

[Tefters]

Over an hour on the phone with 2 technicians now remoted in together looking at the issue.

 

Just spent 20 mins wondering why the solus3 agent service starts and stops not realising the process is already loaded therefore the service cannot start it a second time...

 

Dogs chasing tails at the moment.

[whippy]

Urgh now after 2 1/2 hours my Solus3 is borked and the patch is stuck deploying but client machines are now constantly losing connection to the server and showing red.

 

Back on the phone to Capita...

 

Exactly the problem I'm having. Awaiting callback from level2.

They're getting chased now.

[Tefters]

Exactly the problem I'm having. Awaiting callback from level2.

They're getting chased now.

 

Ok so just hung up on 2x 2nd line techs who have been working on my issue with me on the phone for an hour as they started going "gun ho" and granting EVERYONE permissions all over the shop to RSA token files and wanted to do the same on my Solus3 repository and extraction folders which i refused point blank as that's the biggest load of horse sh*t i've ever heard.

 

They were pretty clueless when I was trying to show them the error of their ways on other avenues too...

 

NOT HAPPY!

 

Now awaiting a 3rd line tech to get in contact and I'll continue to look into the issue myself without dishing out EVERYONE permissions here, there and everywhere... Security much!?!

[whippy]

Ok so just hung up on 2x 2nd line techs who have been working on my issue with me on the phone for an hour as they started going "gun ho" and granting EVERYONE permissions all over the shop to RSA token files and wanted to do the same on my Solus3 repository and extraction folders which i refused point blank as that's the biggest load of horse sh*t i've ever heard.

 

Firstline did that with me on a microsoft RSA folder. No effect.

I believe it's an issue with solus communications as if you check the deployment logs it shows TCP connection refused errors by the server. Even with firewalls off.

[Tefters]

Firstline did that with me on a microsoft RSA folder. No effect.

I believe it's an issue with solus communications as if you check the deployment logs it shows TCP connection refused errors by the server. Even with firewalls off.

Is yours with the Autumn patch? Its got something to do with the Solus3 Agents on the machines and the way they are talking with the server I know it is but the 2 I was speaking to would not listen and just keep reading KB articles and whacking in permissions til I had enough.

[whippy]

Yes, Autumn Full update.

I stupidly had the auto deploy box checked.

 

Solus Agent also had an update last week to 3.11 so it could be that.

[SHimmer45]

i had a similar issue with deploying a discover update and it ended up being the version of SOLUS that i was running on the sever being out of date.

though i am pretty sure it doesnt mention such things in the release notes?

[ItsOggy]

Is your SOLUS UI console the correct version, I updated SOLUS to 3.11 and everything (service, agents, SOLUS db) updated automatically but the UI console didn't so had to run manually.

[Tefters]

Going to check soon after Whippy first mentioned above

[Tefters]

Just checked and all ok on that deployment, everything is 3.11.56 or something like that.

 

The Solus3 seems bolloxed completely now so I'm going to restore the DB from last nights backup and work from there, don't know what the 2 second line guys were doing but it appears to be worse as the gui shows majority of my agents offline and the agents (clients) are red with a pop up box with the server name but you can't click save as the entry is already there, closing and opening the agent gui exe seems to get it working again for 5 mins before it craps out again and nothing can deploy from the server nor can the clients update the applications through the pull mechanism.

 

Edit - By restoring DB I mean the Solus3 DB, can't do SIMS now as the DB has data in after its upgrade.

Also facing having to go round every machine with Sims tomorrow now and run the patch in manually from the solus3extraction share via the good old SIMSApplicationSetup.

 

Still chuckling over them spending 20 minutes trying to get the Solus3 client service running on the SIMS server not realising why it kept stopping straight away due to the process the service calls already being loaded as it was triggered manually from exe directly, it was at this point I knew I was onto a long and pointless call.

Edited November 8, 2016 by Tefters

[Tefters]

So here's a further update nice and simple.

I just backed up the Solus3 DB (yeah it's fubar by the looks but what the hey!) and restored last night from Veeam, god bless Veeam...!

 

So now I have last nights Solus DB live again from 01:30 (technically today but I'm tired now, gimme a break!) and it's all working again as per this morning meaning I have the Autumn DB patch in there and successfully deployed according to the GUI on my DB which is true and no Full Autumn Patch.

 

I click check for updates and it shows nothing to download so guess I now need Capita to authorise the patch again (3rd time now) however technically the files are downloaded, extracted and ready in my deployment repository as I only restored the DB.

 

All the clients are now showing online again and I can remote into any machine and do the client update application manually to trigger a pull request for the patch but it says it will download and install the summer patch (obviously because that's what it thinks is the latest patch it has is, be interesting to see if it downloads the Autumn patch in the repository thinking it's the summer, will test...), have used the agent to download the install the FMS Autumn patch onto existing clients that had that so the deployment are working again.

[Tefters]

Ok so I can't update the clients as Solus3 agent reports there is no update that matches the DB version so there is some signature check in the Solus3 agent and DB entries which is good.

 

I will now have to get the full update again tomorrow and then try deployment again and see if it Fubars Solus3 again

[Tefters]

So this morning everything is resolved and the patch is deploying to Workstations and Installing as it should.

 

I called Capita up again first thing and asked for the patch to be re-authorised, as soon as it appeared in Solus again I Simply deployed it and Voula off it went!

As of typing I have 90% of the workstations updated now as should within the space of 20 minutes.

 

What was the overall issue? Fcuk knows... The workstation patch not being there was 1 and needed re-authorising for whatever reason and then 2 Solus3 decided to spas out during deployment and screw everything over at a database level (Solus3 DB not SIMS).

Simply restoring the DB back to the night before, having the patch re-authorised and deploy again and all is good.

 

So glad I didn't let people go "gun ho" on permissions all over the shop!

[whippy]

I've developed my own workaround as still waiting for my callback from Line2 support.

Stopped all deployments, rebooted all pc's, restarted Solus Deployment service on the server and manually installed the update on a few machines that were struggling with deployment throwing tcp errors.

 

The agents are now connecting and staying connected. I can also manually deploy via the Applications tab in Solus Agent and redeploy the agent from the server.

Gone from >100 systems missing the update for more than 3 days down to less than 10 that I'm having powered on to update. (No WOL, grrrr).

[Tefters]

I got 99% coverage now, 8 machines stuck on "package already downloaded" which I presume should then trigger the install but the Solus client just stays on that message.

 

Installed update manually, restarted PC all seems well although I'm probably going to uninstall the client through the server and reinstall for the client to pickup the correct pc Sims version

[CHU]

Glad to hear this wasn't just us! OneEd wanted us to check GPO's for blocked ports, permissions on the RSA folder the lot. 3 days they didn't solve it. I ended up manually updating the deployment service and agent on MIS and it came back to life, did half the workstations and then went off again, exactly 8hrs later it started working again by itself and pushed out the other half. All very odd. So far it's stayed connected, but I haven't released the Autumn update yet! Hoped these days were behind us, only moved to SOLUS3 last term.

 

Auto-deployment disabled now!

[Banjo]

What's really annoying is that there is no user/password for the Solus3 deployment GUI. The amount of 'techies' or external ICT contractors that login to the SIMS servers and tinker with the settings and we end up with an incompatible database is getting ridiculous. Solus 2 required a user/pass to run an upgrade so why is this missing from Solus 3?