Problem beim Upgrade: OPSI RPC Error (4.2 > 4.3)

[marniii]

Server OS: Ubuntu 22.04

Hello,

ich habe heute auch versucht von 4.2 auf 4.3 das Upgrade durchzuführen. Der Befehl "opsiconfd health-check --upgrade-check" signalisierte alles tutti.

Also dachte ich mir "Auf gehts, wird schon schief gehen".

Im Upgrade Vorgang kam folgendes vor:

Code: Alles auswählen

opsi-server (4.3.1.1-1) wird eingerichtet ...
[5] [2023-12-01 14:42:51.011] [               ] Running opsiconfd setup   (__init__.py:182)
[5] [2023-12-01 14:42:54.805] [               ] Setup grafana plugin grafana-simple-json-datasource (install)   (grafana.py:330)
[4] [2023-12-01 14:43:05.001] [               ] Could not install grafana plugin via grafana-cli: Command '['grafana-cli', 'plugins', 'install', 'grafana-simple-json-datasd non-zero exit status 1.   (grafana.py:338)
Trigger für man-db (2.10.2-1) werden verarbeitet ...

Lief aufjedenfall weiter durch. Wenn ich jetzt versuche die Paket auf 4.3 zu aktualisieren mit dem Befehl: opsi-package-updater -v update

Erhalte ich folgende Ausgabe:

Code: Alles auswählen

[5] [2023-12-01 14:51:52.690] [               ] Sending mail notification   (Notifier.py:92)
[5] [2023-12-01 14:51:52.876] [               ] Email successfully sent   (Notifier.py:120)
[3] [2023-12-01 14:51:52.891] [               ] Opsi rpc error: No client id attribute defined for table PRODUCT_ON_DEPOT using ace RPCACE(method_re=re.compile('.*'), type='self', id='XXXX.xxx.XXX.de', allowed_attributes=set(), denied_attributes=set())   (opsipackageupdater.py:454)
Traceback (most recent call last):
  File "opsiutils/opsipackageupdater.py", line 450, in main
  File "opsiutils/opsipackageupdater.py", line 420, in updater_main
  File "opsiutils/update_packages/Updater.py", line 249, in processUpdates
  File "opsiutils/update_packages/Updater.py", line 681, in get_packages
  File "opsiutils/update_packages/Updater.py", line 972, in getInstalledProducts
  File "<string>", line 1, in productOnDepot_getObjects
  File "opsicommon/client/opsiservice.py", line 1203, in jsonrpc
opsicommon.exceptions.OpsiRpcError: Opsi rpc error: No client id attribute defined for table PRODUCT_ON_DEPOT using ace RPCACE(method_re=re.compile('.*'), type='self', id='XXXX.xxx.XXX.de', allowed_attributes=set(), denied_attributes=set())
ERROR: Opsi rpc error: No client id attribute defined for table PRODUCT_ON_DEPOT using ace RPCACE(method_re=re.compile('.*'), type='self', id='XXXX.xxx.XXX.de', allowed_attributes=set(), denied_attributes=set())

Ich weiß nicht wirklich, was ich noch tun soll. Ich habe vorerst alles zurückgebaut, kann den Fehler jedoch problemlos reproduzieren

acl.conf sieht wie folgt aus:

Code: Alles auswählen

backend_deleteBase     : sys_group(opsiadmin)
backend_.*             : all
hostControl.*          : sys_group(opsiadmin); opsi_depotserver
host_get.*             : sys_group(opsiadmin); opsi_depotserver; self; opsi_client(attributes(!opsiHostKey,!description,!lastSeen,!notes,!hardwareAddress,!inventoryNumber))
auditSoftware_delete.* : sys_group(opsiadmin); opsi_depotserver
auditSoftware_.*       : sys_group(opsiadmin); opsi_depotserver; opsi_client
auditHardware_delete.* : sys_group(opsiadmin); opsi_depotserver
auditHardware_.*       : sys_group(opsiadmin); opsi_depotserver; opsi_client
.*_get.*               : sys_group(opsiadmin); opsi_depotserver; opsi_client
.*                     : sys_group(opsiadmin); opsi_depotserver; self

Vielleicht hat jemand eine Idee, vielen Dank im voraus!
Marni

[n.doerrer]

Hallo,

in der ".*"-Zeile der acl.conf darf kein "self" stehen.
Ich schau mal, ob wir das einfach in den upgrade-check mit aufnehmen können.

Also einfach das "; self" am Ende entfernen, den opsiconfd neustarten und dann sollte es laufen.

[marniii]

Vielen Dank, für die schnelle Antwort.

Ich habe die ACL.conf korrigiert und den opsiconfd neugestartet.

Bekomme jetzt leider folgende Fehlermeldung:

Befehl: opsi-package-updater -v update

Code: Alles auswählen

[5] [2023-12-03 12:09:20.339] [               ] Sending mail notification   (Notifier.py:92)
[5] [2023-12-03 12:09:20.476] [               ] Email successfully sent   (Notifier.py:120)
[3] [2023-12-03 12:09:20.500] [               ] HTTPSConnectionPool(host='opsipackages.43.opsi.org', port=443): Max retries exceeded with url: /stable/packages.msgpack.zstd (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f9d26f3fa10>, 'Connection to opsipackages.43.opsi.org timed out. (connect timeout=None)'))   (opsipackageupdater.py:454)
Traceback (most recent call last):
  File "urllib3/connection.py", line 203, in _new_conn
  File "urllib3/util/connection.py", line 85, in create_connection
  File "urllib3/util/connection.py", line 73, in create_connection
TimeoutError: [Errno 110] Connection timed out

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "urllib3/connectionpool.py", line 790, in urlopen
  File "urllib3/connectionpool.py", line 491, in _make_request
  File "urllib3/connectionpool.py", line 467, in _make_request
  File "urllib3/connectionpool.py", line 1092, in _validate_conn
  File "urllib3/connection.py", line 611, in connect
  File "urllib3/connection.py", line 212, in _new_conn
urllib3.exceptions.ConnectTimeoutError: (<urllib3.connection.HTTPSConnection object at 0x7f9d26f3fa10>, 'Connection to opsipackages.43.opsi.org timed out. (connect timeout=None)')

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "requests/adapters.py", line 486, in send
  File "urllib3/connectionpool.py", line 844, in urlopen
  File "urllib3/util/retry.py", line 515, in increment
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='opsipackages.43.opsi.org', port=443): Max retries exceeded with url: /stable/packages.msgpack.zstd (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f9d26f3fa10>, 'Connection to opsipackages.43.opsi.org timed out. (connect timeout=None)'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "opsiutils/opsipackageupdater.py", line 450, in main
  File "opsiutils/opsipackageupdater.py", line 420, in updater_main
  File "opsiutils/update_packages/Updater.py", line 249, in processUpdates
  File "opsiutils/update_packages/Updater.py", line 683, in get_packages
  File "opsiutils/update_packages/Updater.py", line 197, in get_new_packages_per_repository
  File "opsiutils/update_packages/Updater.py", line 981, in getDownloadablePackages
  File "opsiutils/update_packages/Updater.py", line 1035, in getDownloadablePackagesFromRepository
  File "opsiutils/update_packages/Updater.py", line 1022, in fetch_repository_metafile
  File "requests/sessions.py", line 602, in get
  File "requests/sessions.py", line 589, in request
  File "requests/sessions.py", line 703, in send
  File "requests/adapters.py", line 507, in send
requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='opsipackages.43.opsi.org', port=443): Max retries exceeded with url: /stable/packages.msgpack.zstd (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f9d26f3fa10>, 'Connection to opsipackages.43.opsi.org timed out. (connect timeout=None)'))
ERROR: HTTPSConnectionPool(host='opsipackages.43.opsi.org', port=443): Max retries exceeded with url: /stable/packages.msgpack.zstd (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f9d26f3fa10>, 'Connection to opsipackages.43.opsi.org timed out. (connect timeout=None)'))

Befehl: dig opsipackages.43.opsi.org

Code: Alles auswählen

; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> opsipackages.43.opsi.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52864
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;opsipackages.43.opsi.org.      IN      A

;; ANSWER SECTION:
opsipackages.43.opsi.org. 600   IN      A       168.119.85.193

;; Query time: 36 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Sun Dec 03 12:21:29 CET 2023
;; MSG SIZE  rcvd: 69

viele Grüße
Marni

[n.doerrer]

Ich tippe auf ein Proxy-Problem.
Es könnte sein, dass in /etc/opsi/opsi-package-updater.conf ein proxy konfiguriert ist, der Probleme.

Ansich ist auch möglich, dass proxy server keine Partial-requests zulassen.
Klappt denn ein zsync-Aufruf für eins der auf opsipackages.43.opsi.org gehosteten Pakete manuell?

Per opsi-package-updater -vvv update gibt es ggfs mehr Kontext zu dem Fehler

[marniii]

Es war wirklich der Proxy, stand nicht in der opsi-package-updater.conf, sondern an einer anderen Stelle, vielen Dank für die Hilfe.