AnsweredAssumed Answered

File Events migration from V10 to V12, added LOGIn objects

Question asked by Carsten_Schmitz on Jan 23, 2018
Latest reply on Jun 11, 2018 by Carsten_Schmitz
Hi.

A question.

In my understanding, in version 10, file events had no login object. They always ran with the permissions the agent ran with.

Meet version 12.1, where file events have LOGIN objects. The db migration from 10 to 12.1 leaves the login object empty, so an existing file event suddenly looks like this:

htfcvpa5drkv.png
(figure 1: a French file event. please don't ask my why my AWI is French today ... I was simply bored with the English one :)

It seems that there is a priviledge now (Événements de fichier : démarrer sans Login spécifié ... erm ... "execute events without a login object").

So far, so good.

But when someone doesn't have this priviledge, he get's an error message as follows:

'corrupt user 'root' password'

3895az48liad.png

My question to the community and, probably, someone from Automic:

Is this message just a poorly worded way of letting the user know he lacks the privilege, or is there, on top of lacking the privilege, actually an actual problem that the agent has with the root password, something that could be analyzed and/or fixed in order to get to a better error message for the user?

Thanks!

Outcomes