[Gelöst] Fehler wegen missing backend 'mysql nach OPSI Update

[WolleKette]

ich habe gestern unseren OPSI Server aktualisiert.
Ubuntu von 18.04.6 LTS auf 22.04.1 LTS und OPSI von 4.1.1.33 auf 4.2.0.183.

Wenn ich jetzt die Methode host_getIdents mit dem opsi-admin ausführe, dann erhalte ich zwar die Resultate, zusätzlich aber auch eine Fehlermeldung.

Adding missing backend 'mysql' in dispatch entry 'backend_.*' (__init__.py:305)

Code: Alles auswählen

opsi-admin -dS method host_getIdents
[4] [2022-09-27 10:30:01.928] [               ] Adding missing backend 'mysql' in dispatch entry 'backend_.*'   (__init__.py:305)
lnx1.neutron.lan
veeam.neutron.lan
vm-win7-office.neutron.lan
...

Ich habe nach dem Update bereits versucht opsi-setup --configure-mysql auszuführen, da kam aber eine weitere Fehlermeldung, wozu es auch einen eigenen Thread hier im Forum gibt.

Meine dispatch.conf (/etc/opsi/backendManager/) sieht übrigens wie folgt aus:

Code: Alles auswählen

backend_.*         : file, opsipxeconfd
host_.*            : file, opsipxeconfd
productOnClient_.* : file, opsipxeconfd
configState_.*     : file, opsipxeconfd
audit.*            : mysql
.*                 : file

[wolfbardo]

bitte dispatch.conf gemaess getting started anpassen.

Code: Alles auswählen

backend_.*         : file, mysql, opsipxeconfd

Gruss
Bardo Wolf

[WolleKette]

Danke. Das war's.

[SisterOfMercy]

How does your dispatch.conf look like now?

[WolleKette]

Exactly as before, except that mysql was inserted in the 1st line (backend_.*)

Code: Alles auswählen

backend_.*         : file, mysql, opsipxeconfd
host_.*            : file, opsipxeconfd
productOnClient_.* : file, opsipxeconfd
configState_.*     : file, opsipxeconfd
audit.*            : mysql
.*                 : file

[SisterOfMercy]

Uhmm. Why? Do you have the mysql extension? If so, why are you still using the files backend?

I think it should look like this, but you would have to create a backup first, and probably find a way to move the data.

Code: Alles auswählen

backend_.*         : mysql, opsipxeconfd
host_.*            : mysql, opsipxeconfd
productOnClient_.* : mysql, opsipxeconfd
configState_.*     : mysql, opsipxeconfd
audit.*            : mysql
.*                 : mysql

[WolleKette]

No, we don't have licenced the mysql extension. But I seem to remember that at some point it became free for audit.
So until this update out config looked like this:

Code: Alles auswählen

backend_.*         : file, opsipxeconfd
host_.*            : file, opsipxeconfd
productOnClient_.* : file, opsipxeconfd
configState_.*     : file, opsipxeconfd
audit.*            : mysql
.*                 : file

We have only a small number of clients and therefore the mysql extension is not worth it.

[SisterOfMercy]

Then I don't understand why it's now in the backend line and why that fixed things.
Hm, wait, it is also in the text in dispatch.conf

Because the free part can also do licenses, I think it should look like this:

Code: Alles auswählen

#       backend_.*         : file, mysql, opsipxeconfd
#       host_.*            : file, opsipxeconfd
#       productOnClient_.* : file, opsipxeconfd
#       configState_.*     : file, opsipxeconfd
#       license.*          : mysql
#       softwareLicense.*  : mysql
#       audit.*            : mysql
#       .*                 : file

Oh, but you don't have the license module.
Never mind! I am really not making much sense.