Seite 1 von 1

Nach python-opsi Update OPSI Configed defekt

Verfasst: 09 Aug 2019, 13:57
von Grugi
Hallo Leute,

ich habe heute auf unserem System die neue Version von python-opsi 4.1.1.67-1 installiert. Jetzt kommt der opsiconfd Dienst nicht mehr hoch.

Code: Alles auswählen

➜  log service opsiconfd status
● opsiconfd.service - Opsi Configuration Service
   Loaded: loaded (/lib/systemd/system/opsiconfd.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Fri 2019-08-09 13:38:41 CEST; 3s ago
  Process: 4820 ExecStart=/usr/bin/opsiconfd -D (code=exited, status=1/FAILURE)
  Process: 4817 ExecStartPre=/bin/chown -R opsiconfd /var/run/opsiconfd/ (code=exited, status=0/SUCCESS)
  Process: 4814 ExecStartPre=/bin/mkdir -p /var/run/opsiconfd (code=exited, status=0/SUCCESS)

Aug 09 13:38:41 opsi systemd[1]: Failed to start Opsi Configuration Service.
Aug 09 13:38:41 opsi systemd[1]: opsiconfd.service: Unit entered failed state.
Aug 09 13:38:41 opsi systemd[1]: opsiconfd.service: Failed with result 'exit-code'.
Kann mir vor dem Wochenende noch jemand helfen? Kann weder das Webinterface aufrufen noch den Config Editor starten.
Jemand eine Idee?

Vielen Dank schon mal und liebe Grüße

Grugi

Re: Nach python-opsi Update OPSI Configed defekt

Verfasst: 09 Aug 2019, 15:04
von SisterOfMercy
Have you already tried opsi-setup --set-rights?

Re: Nach python-opsi Update OPSI Configed defekt

Verfasst: 09 Aug 2019, 15:10
von Grugi
SisterOfMercy hat geschrieben:Have you already tried opsi-setup --set-rights?
opsi opsi-setup --set-rights
[5] [Aug 09 15:08:58] Setting rights on directory u'/etc/opsi' (Rights.py|116)
[5] [Aug 09 15:08:58] Setting rights on directory u'/var/log/opsi' (Rights.py|116)
[5] [Aug 09 15:08:58] Setting rights on directory u'/var/lib/opsi' (Rights.py|116)
[5] [Aug 09 15:09:10] Setting rights on directory u'/home/opsiproducts' (Rights.py|116)
[5] [Aug 09 15:09:11] Setting rights on directory u'/tftpboot/linux' (Rights.py|116)
[5] [Aug 09 15:09:11] Setting rights on directory u'/var/lib/opsi/depot' (Rights.py|116)
[5] [Aug 09 15:09:15] Setting rights on directory u'/var/www/html/opsi' (Rights.py|116)
➜ opsi service opsiconfd start
Job for opsiconfd.service failed because the control process exited with error code.
See "systemctl status opsiconfd.service" and "journalctl -xe" for details.

Geht leider noch immer nicht.

Re: Nach python-opsi Update OPSI Configed defekt

Verfasst: 09 Aug 2019, 15:19
von SisterOfMercy
This is on RHEL or CentOS?

Any chance of more details from the logs? /var/log/opsi/opsiconfd/opsiconfd.log for instance.

Re: Nach python-opsi Update OPSI Configed defekt

Verfasst: 09 Aug 2019, 16:42
von Grugi
SisterOfMercy hat geschrieben:This is on RHEL or CentOS?

Any chance of more details from the logs? /var/log/opsi/opsiconfd/opsiconfd.log for instance.
Hi again,

we are using distro Debian 9.9 (stretch).

Since the error, there is no writing in the opsiconfd.log.
Also there is only some logs of established sessions inside the opsiconfd.log file.

I just tried starting the opsiconfd in my own user context with

Code: Alles auswählen

sudo opsiconfd
This is working as long as I am logged in.

There must be something wrong with the opsi user respectively its permissions.

Re: Nach python-opsi Update OPSI Configed defekt

Verfasst: 09 Aug 2019, 16:58
von Grugi
After a reboot and setting the rights I can access the config editor again.
But while creating or altering an existing package I get several errors.
Also when a package should be installed I get permission errors..

Here is an extraction of the package.log as requested. Hope you can help:

Code: Alles auswählen

 (Logger.py|798)
[2] [Aug 12 09:04:14]   File "/usr/bin/opsi-package-manager", line 1868, in processRemoveCommand
    self._opm.uninstallPackages()
 (Logger.py|798)
[2] [Aug 12 09:04:14]      ==>>> At least one package failed to uninstall, please check /var/log/opsi/package.log for more information (opsi-package-manager|1623)
[2] [Aug 12 09:04:14] Traceback: (Logger.py|798)
[2] [Aug 12 09:04:14]   File "/usr/bin/opsi-package-manager", line 2064, in <module>
    OpsiPackageManagerControl()
 (Logger.py|798)
[2] [Aug 12 09:04:14]   File "/usr/bin/opsi-package-manager", line 1624, in __init__
    raise RuntimeError(u"Failed to process command '%s': %s" % (self.config['command'], processingError))
 (Logger.py|798)
[2] [Aug 12 09:04:14]      ==>>> Failed to process command 'remove': At least one package failed to uninstall, please check /var/log/opsi/package.log for more information (opsi-package-manager|$
[4] [Aug 12 09:48:44] WARNING: Product PAKET1 not installed on depot OPSISERVER. (opsi-package-manager|1429)
[2] [Aug 12 09:48:45] Traceback: (Logger.py|798)
[2] [Aug 12 09:48:45]   File "/usr/bin/opsi-package-manager", line 1621, in __init__
    self.processCommand()
 (Logger.py|798)
[2] [Aug 12 09:48:45]   File "/usr/bin/opsi-package-manager", line 1638, in processCommand
    self.processRemoveCommand()
 (Logger.py|798)
[2] [Aug 12 09:48:45]   File "/usr/bin/opsi-package-manager", line 1868, in processRemoveCommand
    self._opm.uninstallPackages()
 (Logger.py|798)
[2] [Aug 12 09:48:45]      ==>>> At least one package failed to uninstall, please check /var/log/opsi/package.log for more information (opsi-package-manager|1623)
[2] [Aug 12 09:48:45] Traceback: (Logger.py|798)
[2] [Aug 12 09:48:45]   File "/usr/bin/opsi-package-manager", line 2064, in <module>
    OpsiPackageManagerControl()
 (Logger.py|798)
[2] [Aug 12 09:48:45]   File "/usr/bin/opsi-package-manager", line 1624, in __init__
    raise RuntimeError(u"Failed to process command '%s': %s" % (self.config['command'], processingError))
 (Logger.py|798)
[2] [Aug 12 09:48:45]      ==>>> Failed to process command 'remove': At least one package failed to uninstall, please check /var/log/opsi/package.log for more information (opsi-package-manager|$
[4] [Aug 12 09:53:38] WARNING: Product PAKET2 not installed on depot OPSISERVER. (opsi-package-manager|1429)
[2] [Aug 12 09:53:39] Traceback: (Logger.py|798)
[2] [Aug 12 09:53:39]   File "/usr/bin/opsi-package-manager", line 1621, in __init__
    self.processCommand()
 (Logger.py|798)
[2] [Aug 12 09:53:39]   File "/usr/bin/opsi-package-manager", line 1638, in processCommand
    self.processRemoveCommand()
 (Logger.py|798)
[2] [Aug 12 09:53:39]   File "/usr/bin/opsi-package-manager", line 1868, in processRemoveCommand
    self._opm.uninstallPackages()
 (Logger.py|798)
[2] [Aug 12 09:53:39]      ==>>> At least one package failed to uninstall, please check /var/log/opsi/package.log for more information (opsi-package-manager|1623)
[2] [Aug 12 09:53:39] Traceback: (Logger.py|798)
[2] [Aug 12 09:53:39]   File "/usr/bin/opsi-package-manager", line 2064, in <module>
    OpsiPackageManagerControl()
 (Logger.py|798)
[2] [Aug 12 09:53:39]   File "/usr/bin/opsi-package-manager", line 1624, in __init__
    raise RuntimeError(u"Failed to process command '%s': %s" % (self.config['command'], processingError))
 (Logger.py|798)
[2] [Aug 12 09:53:39]      ==>>> Failed to process command 'remove': At least one package failed to uninstall, please check /var/log/opsi/package.log for more information (opsi-package-manager|$
[4] [Aug 12 09:54:28] WARNING: Product PAKET not installed on depot OPSISERVER. (opsi-package-manager|1429)
[2] [Aug 12 09:54:29] Traceback: (Logger.py|798)
[2] [Aug 12 09:54:29]   File "/usr/bin/opsi-package-manager", line 1621, in __init__
    self.processCommand()
 (Logger.py|798)
[2] [Aug 12 09:54:29]   File "/usr/bin/opsi-package-manager", line 1638, in processCommand
    self.processRemoveCommand()
 (Logger.py|798)
[2] [Aug 12 09:54:29]   File "/usr/bin/opsi-package-manager", line 1868, in processRemoveCommand
    self._opm.uninstallPackages()
 (Logger.py|798)
[2] [Aug 12 09:54:29]      ==>>> At least one package failed to uninstall, please check /var/log/opsi/package.log for more information (opsi-package-manager|1623)
[2] [Aug 12 09:54:29] Traceback: (Logger.py|798)
[2] [Aug 12 09:54:29]   File "/usr/bin/opsi-package-manager", line 2064, in <module>