forum.opsi.org

opsi support forum
https://forum.opsi.org/

postinst:Backend error: Failed to install package - timed out atfer 600 seconds

https://forum.opsi.org/viewtopic.php?t=12536

Seite 1 von 1

postinst:Backend error: Failed to install package - timed out atfer 600 seconds

Verfasst: 28 Aug 2021, 17:11
von julia.spindler
Hallo zusammen,

wir sind aktuell dabei neben unserer bestehenden OPSI 4.1 Umgebung eine neues System parallel zu installieren, auf das später migriert werden soll. Dort läuft Ubuntu 20.04 sowie OPSI 4.2.

Leider kann kein Windows-Netboot-Produkt mittels "opsi-package-updater -v install" installiert werden, die Installationen schlagen immer fehl mit folgenden Meldungen:

Code: Alles auswählen

[3] [2021-08-28 14:48:34.265] [package_install] Command '/tmp/.opsi.unpack.t5WfK/OPSI/postinst' timed out atfer 600.0002253055573 seconds   (Product.py:460)
Traceback (most recent call last):
  File "OPSI/Util/Product.py", line 458, in _runPackageScript
  File "OPSI/System/Posix.py", line 982, in execute
RuntimeError: Command '/tmp/.opsi.unpack.t5WfK/OPSI/postinst' timed out atfer 600.0002253055573 seconds
[4] [2021-08-28 14:48:34.266] [package_install] Installation error. Not unlocking product 'win7-x64-captured' on depot 'gershwin.sgm.local'.   (Depotserver.py:223)
[3] [2021-08-28 14:48:34.266] [package_install] Failed to execute package script 'postinst' of package '/var/lib/opsi/repository/win7-x64-captured_4.2.0.1-2.opsi': Command '/tmp/.opsi.unpack.t5WfK/OPSI/postinst' timed out atfer 600.0002253055573 seconds   (Depotserver.py:502)
Traceback (most recent call last):
  File "OPSI/Util/Product.py", line 458, in _runPackageScript
  File "OPSI/System/Posix.py", line 982, in execute
RuntimeError: Command '/tmp/.opsi.unpack.t5WfK/OPSI/postinst' timed out atfer 600.0002253055573 seconds

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

Traceback (most recent call last):
  File "OPSI/Backend/Depotserver.py", line 500, in installPackage
  File "OPSI/Backend/Depotserver.py", line 488, in installPackage
  File "contextlib.py", line 119, in __exit__
  File "OPSI/Backend/Depotserver.py", line 245, in runPackageScripts
  File "OPSI/Util/Product.py", line 472, in runPostinst
  File "OPSI/Util/Product.py", line 464, in _runPackageScript
RuntimeError: Failed to execute package script 'postinst' of package '/var/lib/opsi/repository/win7-x64-captured_4.2.0.1-2.opsi': Command '/tmp/.opsi.unpack.t5WfK/OPSI/postinst' timed out atfer 600.0002253055573 seconds
[3] [2021-08-28 14:48:34.267] [               ] Backend error: Failed to install package '/var/lib/opsi/repository/win7-x64-captured_4.2.0.1-2.opsi' on depot 'gershwin.sgm.local': Failed to execute package script 'postinst' of package '/var/lib/opsi/repository/win7-x64-captured_4.2.0.1-2.opsi': Command '/tmp/.opsi.unpack.t5WfK/OPSI/postinst' timed out atfer 600.0002253055573 seconds   (opsipackageupdater.py:312)
Traceback (most recent call last):
  File "OPSI/Util/Product.py", line 458, in _runPackageScript
  File "OPSI/System/Posix.py", line 982, in execute
RuntimeError: Command '/tmp/.opsi.unpack.t5WfK/OPSI/postinst' timed out atfer 600.0002253055573 seconds

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

Traceback (most recent call last):
  File "OPSI/Backend/Depotserver.py", line 500, in installPackage
  File "OPSI/Backend/Depotserver.py", line 488, in installPackage
  File "contextlib.py", line 119, in __exit__
  File "OPSI/Backend/Depotserver.py", line 245, in runPackageScripts
  File "OPSI/Util/Product.py", line 472, in runPostinst
  File "OPSI/Util/Product.py", line 464, in _runPackageScript
RuntimeError: Failed to execute package script 'postinst' of package '/var/lib/opsi/repository/win7-x64-captured_4.2.0.1-2.opsi': Command '/tmp/.opsi.unpack.t5WfK/OPSI/postinst' timed out atfer 600.0002253055573 seconds

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

Traceback (most recent call last):
  File "opsiutils/opsipackageupdater.py", line 308, in main
  File "opsiutils/opsipackageupdater.py", line 280, in updater_main
  File "OPSI/Util/Task/UpdatePackages/Updater.py", line 363, in processUpdates
  File "<string>", line 1, in depot_installPackage
  File "OPSI/Backend/Base/Extended.py", line 123, in _executeMethod
  File "<string>", line 1, in depot_installPackage
  File "OPSI/Backend/Base/Extended.py", line 123, in _executeMethod
  File "<string>", line 1, in depot_installPackage
  File "OPSI/Backend/Base/Extended.py", line 123, in _executeMethod
  File "OPSI/Backend/Depotserver.py", line 122, in depot_installPackage
  File "OPSI/Backend/Depotserver.py", line 505, in installPackage
OPSI.Exceptions.BackendError: Backend error: Failed to install package '/var/lib/opsi/repository/win7-x64-captured_4.2.0.1-2.opsi' on depot 'gershwin.sgm.local': Failed to execute package script 'postinst' of package '/var/lib/opsi/repository/win7-x64-captured_4.2.0.1-2.opsi': Command '/tmp/.opsi.unpack.t5WfK/OPSI/postinst' timed out atfer 600.0002253055573 seconds
Installierte Pakete:

Code: Alles auswählen

root@gershwin:~# dpkg -l | grep -i opsi
ii  opsi-linux-bootimage                 20210618-1                            all          opsi bootimage for netboot tasks.
ii  opsi-linux-support                   4.2.0.0-1                             all          Configure system to be able to deploy Linux with opsi.
ii  opsi-server-full                     4.2.0.55-1                            all          opsi server
ii  opsi-tftpd-hpa                       5.2.8-76                              amd64        HPA's tftp server
ii  opsi-utils                           4.2.0.115-1                           amd64        Utilities for working with opsi
ii  opsi-windows-support                 4.2.0.0-1                             all          Install utilities useful for deploying Windows with opsi.
ii  opsiconfd                            4.2.0.190-1                           amd64        opsi configuration service
ii  opsipxeconfd                         4.2.0.19-1                            amd64        opsi pxe configuration service
root@gershwin:~#
Hat jemand eine Idee, was hier schief läuft und in welchem Log ich mehr Informationen finde? Ich bin nach der Getting-Started-Anleitung vorgegangen.


Grüße,
Julia

Re: postinst:Backend error: Failed to install package - timed out atfer 600 seconds

Verfasst: 30 Aug 2021, 17:08
von mattiasmab
Hallo Julia,

schau doch mal, welche Prozesse während der Installation im Hintergrund laufen. Evtl. kann man das eingrenzen, da im Postint der Windows-Pakete auch opsi-admin-Befehle abgesetzt werden, um dynamisch die Installfiles_dir-Property zu setzen/löschen. Evtl. hakt einer dieser API-Methoden. Das müsste sich dadurch zeigen, dass im Hintergrund ein solcher Prozess laufen müsste.

Code: Alles auswählen

ps -Af | grep "[o]psi"
Das warum ist dann etwas anders, schränkt die Suche innerhalb des Postinst jedoch drastisch ein.

Vermutlich hilft bereits ein Blick ins Log. Dort stehen die Ausgaben des Scripts. Dies liegt unter `/var/log/opsi/opsiconfd/IP_OR_NAME.log`. IP_OR_NAME ist dabei die IP des PCs, von dem aus du den opsi-package-manager aufgerufen hast. Also meist die IP (oder der Name) des Servers selbst.

Re: postinst:Backend error: Failed to install package - timed out atfer 600 seconds

Verfasst: 30 Aug 2021, 18:55
von Jan.Schmidt
Not unlocking product 'win7-x64-captured'
?

Was habt ihr vor?

ich würde:
auf dem neuen opsi das depot vom alten opsi server mounten
dann auf dem neuen die pakete vom alten rüberkopieren, die genutzt werden
Und dann mit opsi-package-manager -i paketname das zeugs installaifizieren.

Re: postinst:Backend error: Failed to install package - timed out atfer 600 seconds

Verfasst: 31 Aug 2021, 11:58
von zylex
Moin,

ich habe gerade das gleiche Problem. Frischer OPSI 4.2 unter Ubuntu 18.04.

Beim Einspielen der Basisprodukte mittels "opsi-package-updater -v install" hängt die Installation für 10 Minuten, danach kommt der gleiche Fehler wie oben. Das passiert bei jedem win-netboot Produkt, egal ob win10, win8 oder sonst was. Anbei exemplarisch:

Code: Alles auswählen

[5] [2021-08-31 11:31:45.508] [package_install] Installing package file '/var/lib/opsi/repository/win10-x64_4.2.0.1-2.opsi' on depot 'opsi.domain.local'   (Depotserver.py:333)
[5] [2021-08-31 11:31:45.638] [package_install] Locking product 'win10-x64' on depot 'opsi.domain.local'   (Depotserver.py:208)
[5] [2021-08-31 11:31:45.649] [package_install] Running package script 'preinst'   (Product.py:446)
[5] [2021-08-31 11:31:46.423] [package_install] Running package script 'postinst'   (Product.py:446)
[3] [2021-08-31 11:41:46.424] [package_install] Command '/tmp/.opsi.unpack.mH7CL/OPSI/postinst' timed out atfer 600.0006549358368 seconds   (Product.py:460)
Traceback (most recent call last):
  File "OPSI/Util/Product.py", line 458, in _runPackageScript
  File "OPSI/System/Posix.py", line 982, in execute
RuntimeError: Command '/tmp/.opsi.unpack.mH7CL/OPSI/postinst' timed out atfer 600.0006549358368 seconds
[4] [2021-08-31 11:41:46.426] [package_install] Installation error. Not unlocking product 'win10-x64' on depot 'opsi.domain.local'.   (Depotserver.py:223)
[3] [2021-08-31 11:41:46.427] [package_install] Failed to execute package script 'postinst' of package '/var/lib/opsi/repository/win10-x64_4.2.0.1-2.opsi': Command '/tmp/.opsi.unpack.mH7CL/OPSI/postinst' timed out atfer 600.0006549358368 seconds   (Depotserver.py:502)
Traceback (most recent call last):
  File "OPSI/Util/Product.py", line 458, in _runPackageScript
  File "OPSI/System/Posix.py", line 982, in execute
RuntimeError: Command '/tmp/.opsi.unpack.mH7CL/OPSI/postinst' timed out atfer 600.0006549358368 seconds

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

Traceback (most recent call last):
  File "OPSI/Backend/Depotserver.py", line 500, in installPackage
  File "OPSI/Backend/Depotserver.py", line 488, in installPackage
  File "contextlib.py", line 119, in __exit__
  File "OPSI/Backend/Depotserver.py", line 245, in runPackageScripts
  File "OPSI/Util/Product.py", line 472, in runPostinst
  File "OPSI/Util/Product.py", line 464, in _runPackageScript
RuntimeError: Failed to execute package script 'postinst' of package '/var/lib/opsi/repository/win10-x64_4.2.0.1-2.opsi': Command '/tmp/.opsi.unpack.mH7CL/OPSI/postinst' timed out atfer 600.0006549358368 seconds
[3] [2021-08-31 11:41:46.428] [               ] Backend error: Failed to install package '/var/lib/opsi/repository/win10-x64_4.2.0.1-2.opsi' on depot 'opsi.domain.local': Failed to execute package script 'postinst' of package '/var/lib/opsi/repository/win10-x64_4.2.0.1-2.opsi': Command '/tmp/.opsi.unpack.mH7CL/OPSI/postinst' timed out atfer 600.0006549358368 seconds   (opsipackageupdater.py:312)
Traceback (most recent call last):
  File "OPSI/Util/Product.py", line 458, in _runPackageScript
  File "OPSI/System/Posix.py", line 982, in execute
RuntimeError: Command '/tmp/.opsi.unpack.mH7CL/OPSI/postinst' timed out atfer 600.0006549358368 seconds

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

Traceback (most recent call last):
  File "OPSI/Backend/Depotserver.py", line 500, in installPackage
  File "OPSI/Backend/Depotserver.py", line 488, in installPackage
  File "contextlib.py", line 119, in __exit__
  File "OPSI/Backend/Depotserver.py", line 245, in runPackageScripts
  File "OPSI/Util/Product.py", line 472, in runPostinst
  File "OPSI/Util/Product.py", line 464, in _runPackageScript
RuntimeError: Failed to execute package script 'postinst' of package '/var/lib/opsi/repository/win10-x64_4.2.0.1-2.opsi': Command '/tmp/.opsi.unpack.mH7CL/OPSI/postinst' timed out atfer 600.0006549358368 seconds

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

Traceback (most recent call last):
  File "opsiutils/opsipackageupdater.py", line 308, in main
  File "opsiutils/opsipackageupdater.py", line 280, in updater_main
  File "OPSI/Util/Task/UpdatePackages/Updater.py", line 363, in processUpdates
  File "<string>", line 1, in depot_installPackage
  File "OPSI/Backend/Base/Extended.py", line 123, in _executeMethod
  File "<string>", line 1, in depot_installPackage
  File "OPSI/Backend/Base/Extended.py", line 123, in _executeMethod
  File "<string>", line 1, in depot_installPackage
  File "OPSI/Backend/Base/Extended.py", line 123, in _executeMethod
  File "OPSI/Backend/Depotserver.py", line 122, in depot_installPackage
  File "OPSI/Backend/Depotserver.py", line 505, in installPackage
OPSI.Exceptions.BackendError: Backend error: Failed to install package '/var/lib/opsi/repository/win10-x64_4.2.0.1-2.opsi' on depot 'opsi.domain.local': Failed to execute package script 'postinst' of package '/var/lib/opsi/repository/win10-x64_4.2.0.1-2.opsi': Command '/tmp/.opsi.unpack.mH7CL/OPSI/postinst' timed out atfer 600.0006549358368 seconds
ERROR: Backend error: Failed to install package '/var/lib/opsi/repository/win10-x64_4.2.0.1-2.opsi' on depot 'opsi.domain.local': Failed to execute package script 'postinst' of package '/var/lib/opsi/repository/win10-x64_4.2.0.1-2.opsi': Command '/tmp/.opsi.unpack.mH7CL/OPSI/postinst' timed out atfer 600.0006549358368 seconds

Das wäre die Ausgabe der laufenden Prozesse:

Code: Alles auswählen

~$ ps -Af | grep "[o]psi"
avahi      761     1  0 11:13 ?        00:00:00 avahi-daemon: running [opsi-lp-depot.local]
whoopsie   996     1  0 11:13 ?        00:00:00 /usr/bin/whoopsie -f
opsiadm+  1843     1  0 11:14 ?        00:00:00 /lib/systemd/systemd --user
opsiadm+  1844  1843  0 11:14 ?        00:00:00 (sd-pam)
opsiadm+  1857     1  0 11:14 ?        00:00:00 /usr/bin/gnome-keyring-daemon --daemonize --login
opsiadm+  1861  1839  0 11:14 tty2     00:00:00 /usr/lib/gdm3/gdm-x-session --run-script env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
opsiadm+  1863  1861  0 11:14 tty2     00:00:11 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
opsiadm+  1873  1843  0 11:14 ?        00:00:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
opsiadm+  1876  1861  0 11:14 tty2     00:00:00 /usr/lib/gnome-session/gnome-session-binary --session=ubuntu
opsiadm+  1971  1876  0 11:14 ?        00:00:00 /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
opsiadm+  1977  1843  0 11:14 ?        00:00:00 /usr/lib/at-spi2-core/at-spi-bus-launcher
opsiadm+  1982  1977  0 11:14 ?        00:00:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
opsiadm+  1984  1843  0 11:14 ?        00:00:00 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
opsiadm+  2010  1876  1 11:14 tty2     00:00:25 /usr/bin/gnome-shell
opsiadm+  2020  1843  0 11:14 ?        00:00:00 /usr/lib/gvfs/gvfsd
opsiadm+  2025  1843  0 11:14 ?        00:00:00 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
opsiadm+  2036     1  2 11:14 ?        00:00:41 /usr/bin/pulseaudio --start --log-target=syslog
opsiadm+  2047  1843  1 11:14 ?        00:00:25 /opt/teamviewer/tv_bin/TeamViewer_Desktop
opsiadm+  2057  1843  3 11:14 ?        00:00:51 /opt/teamviewer/tv_bin/TeamViewer
opsiadm+  2059  2010  0 11:14 tty2     00:00:00 ibus-daemon --xim --panel disable
opsiadm+  2062  1843  0 11:14 ?        00:00:00 /usr/libexec/xdg-permission-store
opsiadm+  2067  2059  0 11:14 tty2     00:00:00 /usr/lib/ibus/ibus-dconf
opsiadm+  2070     1  0 11:14 tty2     00:00:00 /usr/lib/ibus/ibus-x11 --kill-daemon
opsiadm+  2073  1843  0 11:14 ?        00:00:00 /usr/lib/ibus/ibus-portal
opsiadm+  2083  1843  0 11:14 ?        00:00:00 /usr/lib/gnome-shell/gnome-shell-calendar-server
opsiadm+  2091  1843  0 11:14 ?        00:00:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
opsiadm+  2095  1843  0 11:14 ?        00:00:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
opsiadm+  2099  1843  0 11:14 ?        00:00:00 /usr/lib/evolution/evolution-source-registry
opsiadm+  2106  1843  0 11:14 ?        00:00:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor
opsiadm+  2110  1843  0 11:14 ?        00:00:00 /usr/lib/gvfs/gvfs-goa-volume-monitor
opsiadm+  2114  1843  0 11:14 ?        00:00:00 /usr/lib/gnome-online-accounts/goa-daemon
opsiadm+  2137  1843  0 11:14 ?        00:00:00 /usr/lib/gnome-online-accounts/goa-identity-service
opsiadm+  2140  1843  0 11:14 ?        00:00:00 /usr/lib/gvfs/gvfs-afc-volume-monitor
opsiadm+  2155  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-power
opsiadm+  2158  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-print-notifications
opsiadm+  2162  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-rfkill
opsiadm+  2165  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
opsiadm+  2167  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-sharing
opsiadm+  2175  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-smartcard
opsiadm+  2180  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-xsettings
opsiadm+  2182  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-wacom
opsiadm+  2184  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-sound
opsiadm+  2191  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-a11y-settings
opsiadm+  2192  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-clipboard
opsiadm+  2196  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-color
opsiadm+  2198  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-datetime
opsiadm+  2199  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-housekeeping
opsiadm+  2202  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-keyboard
opsiadm+  2204  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-media-keys
opsiadm+  2210  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-mouse
opsiadm+  2237     1  0 11:14 tty2     00:00:00 /usr/lib/gnome-settings-daemon/gsd-printer
opsiadm+  2263  1876  0 11:14 tty2     00:00:00 /usr/lib/gnome-disk-utility/gsd-disk-utility-notify
opsiadm+  2264     1  0 11:14 tty2     00:00:01 /usr/bin/vmtoolsd -n vmusr --blockFd 3
opsiadm+  2278  1876  0 11:14 tty2     00:00:01 nautilus-desktop
opsiadm+  2293  2020  0 11:14 ?        00:00:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.22 /org/gtk/gvfs/exec_spaw/0
opsiadm+  2299  1843  0 11:14 ?        00:00:00 /usr/lib/evolution/evolution-calendar-factory
opsiadm+  2309  2059  0 11:14 tty2     00:00:00 /usr/lib/ibus/ibus-engine-simple
opsiadm+  2321  1843  0 11:14 ?        00:00:00 /usr/lib/dconf/dconf-service
opsiadm+  2328  2299  0 11:14 ?        00:00:00 /usr/lib/evolution/evolution-calendar-factory-subprocess --factory all --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2299x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2299/2
opsiadm+  2339  1843  0 11:14 ?        00:00:00 /usr/lib/evolution/evolution-addressbook-factory
opsiadm+  2349  2339  0 11:14 ?        00:00:00 /usr/lib/evolution/evolution-addressbook-factory-subprocess --factory all --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx2339x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/2339/2
opsiadm+  2384  2020  0 11:14 ?        00:00:00 /usr/lib/gvfs/gvfsd-network --spawner :1.22 /org/gtk/gvfs/exec_spaw/1
opsiadm+  2389  2020  0 11:14 ?        00:00:00 /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.22 /org/gtk/gvfs/exec_spaw/2
opsiadm+  2398  2020  0 11:14 ?        00:00:00 /usr/lib/gvfs/gvfsd-dnssd --spawner :1.22 /org/gtk/gvfs/exec_spaw/3
opsiadm+  2404  1843  0 11:14 ?        00:00:00 /usr/lib/gvfs/gvfsd-metadata
opsiadm+  2428  1876  0 11:15 tty2     00:00:00 update-notifier
opsiadm+  2430  1876  0 11:15 tty2     00:00:02 /usr/bin/gnome-software --gapplication-service
opsiadm+  2595  1843  0 11:21 ?        00:00:01 /usr/lib/gnome-terminal/gnome-terminal-server
opsiadm+  2605  2595  0 11:21 pts/0    00:00:00 bash
opsiadm+  3103  2595  0 11:25 pts/1    00:00:00 bash
root      3493     1  0 11:30 ?        00:00:00 ./opsiconfd start --log-level-stderr=0
opsicon+  3494  3493  0 11:30 ?        00:00:02 ./opsiconfd start --log-level-stderr=0
root      3593     1  0 11:30 ?        00:00:00 ./opsipxeconfd start
opsicon+  3602  3494  0 11:30 ?        00:00:00 /usr/lib/opsiconfd/opsiconfd -B -S -E -s -c from multiprocessing.semaphore_tracker import main;main(25)
opsicon+  3603  3494  0 11:30 ?        00:00:02 /usr/lib/opsiconfd/opsiconfd --multiprocessing-fork tracker_fd=26 pipe_handle=27
root      3706  2605  0 11:31 pts/0    00:00:00 sudo opsi-package-updater -v install
root      3707  3706  0 11:31 pts/0    00:00:00 /usr/lib/opsi-utils/opsi-package-updater -v install
root      3708  3707  3 11:31 pts/0    00:00:11 /usr/lib/opsi-utils/opsi-package-updater -v install
root      4099  3708  0 11:31 pts/0    00:00:00 /bin/sh -c /tmp/.opsi.unpack.mH7CL/OPSI/postinst
root      4100  4099  0 11:31 pts/0    00:00:00 /bin/bash /tmp/.opsi.unpack.mH7CL/OPSI/postinst
root      4150  4100  0 11:31 pts/0    00:00:00 /usr/lib/opsi-utils/opsi-python
root      4151  4150  0 11:31 pts/0    00:00:00 /usr/lib/opsi-utils/opsi-python
opsiadm+  4157  3103  0 11:37 pts/1    00:00:00 ps -Af
opsiadm+  4158  3103  0 11:37 pts/1    00:00:00 grep --color=auto [o]psi

Ein Log mit der IP oder dem Namen des Servers gibt es unter "/var/log/opsi/opsiconfd/" nicht, lediglich ein Log Names "opsiconfd.log" mit folgendem Inhalt:

Code: Alles auswählen

[4] [2021-08-31 10:38:52.505] [               ] Failed to set RLIMIT_NOFILE: current limit exceeds maximum limit   (setup.py:50)
[1] [2021-08-31 10:38:54.293] [               ] Switching to user opsiconfd   (main.py:170)
[1] [2021-08-31 10:38:54.294] [               ] opsiconfd is starting   (main.py:186)
[1] [2021-08-31 10:38:54.296] [               ] Register zeroconf service   (zeroconf.py:45)
[4] [2021-08-31 10:56:19.773] [               ] Failed to set RLIMIT_NOFILE: current limit exceeds maximum limit   (setup.py:50)
[1] [2021-08-31 10:56:21.543] [               ] Switching to user opsiconfd   (main.py:170)
[1] [2021-08-31 10:56:21.544] [               ] opsiconfd is starting   (main.py:186)
[1] [2021-08-31 10:56:21.546] [               ] Register zeroconf service   (zeroconf.py:45)
[4] [2021-08-31 11:13:12.963] [               ] Failed to set RLIMIT_NOFILE: current limit exceeds maximum limit   (setup.py:50)
[1] [2021-08-31 11:13:15.171] [               ] Switching to user opsiconfd   (main.py:170)
[1] [2021-08-31 11:13:15.172] [               ] opsiconfd is starting   (main.py:186)
[1] [2021-08-31 11:13:15.175] [               ] Register zeroconf service   (zeroconf.py:45)
[4] [2021-08-31 11:30:06.657] [               ] Failed to set RLIMIT_NOFILE: current limit exceeds maximum limit   (setup.py:50)
[1] [2021-08-31 11:30:08.656] [               ] Switching to user opsiconfd   (main.py:170)
[1] [2021-08-31 11:30:08.656] [               ] opsiconfd is starting   (main.py:186)
[1] [2021-08-31 11:30:08.659] [               ] Register zeroconf service   (zeroconf.py:45)

Re: postinst:Backend error: Failed to install package - timed out atfer 600 seconds

Verfasst: 31 Aug 2021, 12:38
von mattiasmab
zylex hat geschrieben: ↑31 Aug 2021, 11:58 Ein Log mit der IP oder dem Namen des Servers gibt es unter "/var/log/opsi/opsiconfd/" nicht, lediglich ein Log Names "opsiconfd.log" mit folgendem Inhalt:
Das wäre auch nur bei einem "opsi-package-manager -i". Der "opsi-package-updater" hat hingegen sein eigenes. Stell das Loglevel mal viel höher (`-l 7`) - ich meine (nicht sicher!), dann sieht man die einzelnen Chunks, die das Skript Postinst zurückgibt, da dafür zumindest die POSIX.execute genutzt wird. So sieht man wo es hakt. Laut Prozessliste hängt da ja ein opsi-python Befehl - also vermutlich doch der opsi-admin, der ja nur ein opsi-python skript ist.
Ich hatte das bei dem win2019 letztens auch (auf Centos8), konnte es aber nicht reproduzieren, da es mit dem manuellen opsi-package-manager anschließend normal durchlief.

Bei einer Ersteinrichtung kann aber nur ein opsi-python Befehl im Postinst ausgeführt werden und ich frage mich, warum der blockieren sollte.

Code: Alles auswählen

echo "Removing product property definition installfiles_dir..."
opsi-admin -d method productProperty_delete $PRODUCT_ID $PRODUCT_VERSION $PACKAGE_VERSION $property_id
EDIT: Problem vermutlich gefunden und es würde zur Prozessliste passen, da ich mich über die cmdline wunderte. Zum Test um welche Version es sich handelt, wird der opsi-python-Interpreter ebenfalls einfach aufgerufen und wenn ich den als Subskript ausführe, dann geht er in den interaktiven Modus. Wieso dies nur beim opsi-package-updater, aber nicht beim opsi-package-manager ist, ist mir aber auch schleierhaft.

Code: Alles auswählen

set +e
/usr/bin/opsi-python      <-------- das hier blockiert
ret=$?
set -e
if [ $ret -eq 0 ]; then
	# Python 3 - opsi 4.2 or later
	echo "Running on opsi 4.2 or later. Nothing to do."
else
	echo "Running on opsi 4.1. Patching scripts..."
	# Python 2 - opsi 4.1
	sed --in-place "s_/usr/bin/opsi-python_/usr/bin/python_" "$CLIENT_DATA_DIR/show_drivers.py"
	sed --in-place "s_/usr/bin/opsi-python_/usr/bin/python_" "$CLIENT_DATA_DIR/create_driver_links.py"
fi
Sollte UIB als Bug gemeldet werden - oder ließt hier sogar jemand mit?

Re: postinst:Backend error: Failed to install package - timed out atfer 600 seconds

Verfasst: 31 Aug 2021, 15:41
von zylex
Ich hab mal das Loglevel in der config vom "opsi-package-updater" auf 7 gesetzt. Das Log ist dann zwar ausführlicher, aber leider wird die Ausgabe des postinst Scripts dort nicht mitgeloggt.

Ich denke auch, dass das ein Bug ist. Normalerweise kommt hier auch recht zeitnah eine Reaktion von UIB bei solchen Fehlern :-)

Re: postinst:Backend error: Failed to install package - timed out atfer 600 seconds

Verfasst: 31 Aug 2021, 21:48
von j.schneider
Hallo,

ja, das Problem ist der Aufruf von opsi-python im postinst-Skript.
Das Problem haben wir bereits vor einiger Zeit gelöst.
Die Pakete sind jedoch aktuell noch in Testing:

https://download.uib.de/opsi4.2/testing ... s/netboot/

Grüße
Jan Schneider

Re: postinst:Backend error: Failed to install package - timed out atfer 600 seconds

Verfasst: 01 Sep 2021, 08:53
von zylex
Hi,

danke für das Feedback.

Ich habe die Pakete gestern auch wie @mattiasmab über den "opsi-package-manager" installiert. Damit klappt es auch mit den alten Paketen.

Nur aus Interesse: Wenn es an den Paketen selber liegt, warum werden diese dann von beiden Tools (manager/updater) unterschiedlich behandelt?

Grüße

Re: postinst:Backend error: Failed to install package - timed out atfer 600 seconds

Verfasst: 02 Sep 2021, 15:50
von m.radtke
Hi

die Windows Netboot Pakete die das Problem fixen sind heute in stable gelandet. Version 4.2.0.1-4.

Gruß
Mathias
Alle Zeiten sind UTC+02:00
Seite 1 von 1

Powered by phpBB® Forum Software © phpBB Limited

Deutsche Übersetzung durch phpBB.de