Automic Workload Automation

Hi.

Has anyone experienced issues with Centralized Agent Update on UNIX, in particular:

We did a few for Windows and they worked fine. But I just did one on a UNIX host that has multiple agents (started from different directories) and additionally multiple instances of one agent from the same directory. And CAU updated the wrong agent!

It did not update the one in /opt/ae/12/agents/unix_v12_for_replicating_stuff/bin on port 2303 as I instructed it, but the one in  /opt/ae/current/agents/unix/bin on port 2300.

I'm certain I clicked the right agent and colleague looked over my shoulder as well, and the logs in the particular directories back this up, too.

I can't replicate this now, it won't let me update either agent now. The log says (sorry, it's in German):

2018-09-25 12:36:42 - U00020930 Der Benutzer 'UC/UC' hat die Aktualisierung von '1' Agenten angestoßen. 2018-09-25 12:36:42 - U00020929 Agent 'SUDEB000051_V12_REPL': Upgrade von Version '12.1.2+build.2045' auf Version '12.2.0+build.2108' wurde gestartet. 2018-09-25 12:36:43 - U00011693 Agent 'SUDEB000051_V12_REPL': Update fehlgeschlagen. Erwartete Version '12.2.0+build.2108', tatsächliche Version '12.1.2+build.2045'.

So the gist is, it says it wants to update from 12.1.2 to 12.2, but then complains about finding 12.1.2. This makes no sense at all.

Thx.

Following...

Hi Carsten_Schmitz

This does not sound like something easily reproducible.

Did you already report this to support ? If not, I would suggest to.

Best regards,

Antoine

Hi Antoine,

to be honest, no, I didn't.

I thought about it, but as you said it's not easily reproducible, and the system where it happens is not a system where I can freely test. My experience about reporting this class of issues in this setting has, in part due to the inherent difficulty of pinning it, not been sublime. Therefore, and because I encounter way to many issues day to day to reasonably report all of them, I have recently decided to pick my battles as far as support cases are concerned. One factor in this is whether other people encounter the same issues as I do, hence the leading community question.

(yes, this is not an ideal state of affairs probably on neither end, I am well aware of that ...)

Best regards,

Carsten

Fwiw, I am planning to discuss some things with someone from Automic outside of support cases when I get the chance. Mostly for the ZDU on a more top-down, systemic level, and maybe we can discuss CAU in that regard as well.

Hi Carsten, 

Thanks for your feedback. 

Well, I agree. Hard to investigate on an issue that cannot be easily captured  / reproduced. Did you maybe try loading the CAU package for Unix agent again ? Maybe the package is the problem. 

Best regards,

Antoine

Did you maybe try loading the CAU package for Unix agent again ?

No, didn't do that. I downloaded it yesterday and it unzipped okay, so I assume it must at least be uncorrupted

Just suggesting this as it could be a quick win. Minimal risk and effort  

Best regards,

Antoine

Much appreciated Just tried it though, doesn't change a thing ...