[GELÖST] opsiconfd startet nicht mehr

[b.boos]

Sehr geehrtes Opsi Team,

ich habe eben ein UpDate durchgeführt, nun startet der Opsiconfd garnicht mehr.

Ich bekomme lediglich ein faild angezeigt. Ist irgendetwas bekannt?


MfG
Björn

PS: die opsiconfd.socket wird angelegt.

[b.boos]

ein opsiconfd -l6 bringt folgendes

Code: Alles auswählen

[1] [Sep 27 10:58:08]
==================================================================
=             opsi configuration service starting                =
==================================================================
 (Logger.py|831)
[5] [Sep 27 10:58:08] Starting opsiconfd main thread (opsiconfd.py|430)
[5] [Sep 27 10:58:08] Opening socket /var/run/opsiconfd/opsiconfd.socket for interprocess communication. (opsiconfd.py|414)
[6] [Sep 27 10:58:08] Creating backend instance (opsiconfd.py|250)
[6] [Sep 27 10:58:08] * BackendManager is creating BackendDispatcher (BackendManager.py|139)
[6] [Sep 27 10:58:08] Backend context was set to <OPSI.Backend.BackendManager.BackendManager instance at 0x8fc638c> (Backend.py|171)
[6] [Sep 27 10:58:08] Loading dispatch config file '/etc/opsi/backendManager/dispatch.conf' (BackendManager.py|220)
[6] [Sep 27 10:58:08] Loading backend config '/etc/opsi/backends/file.conf' (BackendManager.py|261)
[6] [Sep 27 10:58:08] Backend context was set to <OPSI.Backend.BackendManager.BackendDispatcher instance at 0x8fc662c> (Backend.py|171)
[6] [Sep 27 10:58:08] Loading backend config '/etc/opsi/backends/opsipxeconfd.conf' (BackendManager.py|261)
[6] [Sep 27 10:58:08] Backend context was set to <OPSI.Backend.BackendManager.BackendDispatcher instance at 0x8fc662c> (Backend.py|171)
[6] [Sep 27 10:58:08] * BackendManager is creating ExtendedConfigDataBackend (BackendManager.py|143)
[6] [Sep 27 10:58:08] Setting context to backend <OPSI.Backend.Backend.ExtendedConfigDataBackend instance at 0x8ffa06c> (Backend.py|379)
[6] [Sep 27 10:58:08] * BackendManager is creating BackendExtender (BackendManager.py|162)
[6] [Sep 27 10:58:08] Setting context to backend <OPSI.Backend.BackendManager.BackendExtender instance at 0x9014a8c> (Backend.py|379)
[6] [Sep 27 10:58:09] Reading config file '/etc/opsi/backendManager/extend.d/10_opsi.conf' (BackendManager.py|415)
[6] [Sep 27 10:58:09] Reading config file '/etc/opsi/backendManager/extend.d/20_legacy.conf' (BackendManager.py|415)
[6] [Sep 27 10:58:09] Reading config file '/etc/opsi/backendManager/extend.d/70_dynamic_depot.conf' (BackendManager.py|415)
[6] [Sep 27 10:58:09] Creating site (opsiconfd.py|259)
[5] [Sep 27 10:58:09] Added static content '/' which points to directory '/usr/share/opsiconfd/static' (opsiconfd.py|272)
[5] [Sep 27 10:58:09] Running on depot server 'opsi4.zentrale.bsa-ba-akademie.de', exporting repository directory (opsiconfd.py|290)
[5] [Sep 27 10:58:09] Running on depot server 'opsi4.zentrale.bsa-ba-akademie.de', exporting depot directory (opsiconfd.py|303)
[5] [Sep 27 10:58:09] Added webdav content 'repository' which points to directory '/var/lib/opsi/repository' () (opsiconfd.py|336)
[5] [Sep 27 10:58:09] Added webdav content 'depot' which points to directory '/opt/pcbin/install' () (opsiconfd.py|336)
[5] [Sep 27 10:58:09] Added webdav content 'configed' which points to directory '/usr/lib/configed' () (opsiconfd.py|336)
[6] [Sep 27 10:58:09] Creating ports (opsiconfd.py|341)
[5] [Sep 27 10:58:09] Accepting HTTPS requests on 0.0.0.0:4447 (opsiconfd.py|383)
[5] [Sep 27 10:58:09] Publishing opsiconfd over zeroconf as 'opsi configuration daemon' on '4447' (opsiconfd.py|397)
[4] [Sep 27 10:58:09] Failed to publish ZeroconfService: avahi/dbus module missing (opsiconfd.py|98)
--- hier blieb es hängen und wurde abgebrochen ---
[5] [Sep 27 11:01:02] Stopping opsiconfd main thread (opsiconfd.py|175)
[5] [Sep 27 11:01:02] Deleting all sessions (Session.py|217)
[5] [Sep 27 11:01:02] Opsiconfd main thread exiting... (opsiconfd.py|447)

in /var/log/opsi/opsiconfd/opsiconfd.log steht folgendes

Code: Alles auswählen

==================================================================
 (Logger.py|831)
[5] [Sep 27 11:11:42] Starting opsiconfd main thread (opsiconfd.py|430)
[5] [Sep 27 11:11:42] Opening socket /var/run/opsiconfd/opsiconfd.socket for interprocess communication. (opsiconfd.py|414)
[5] [Sep 27 11:11:42] Added static content '/' which points to directory '/usr/share/opsiconfd/static' (opsiconfd.py|272)
[5] [Sep 27 11:11:43] Running on depot server 'opsi4.FQDN.de', exporting repository directory (opsiconfd.py|290)
[2] [Sep 27 11:11:43] Traceback: (Logger.py|742)
[2] [Sep 27 11:11:43]      line 437 in 'run' in file '/usr/lib/python2.4/site-packages/opsiconfd/opsiconfd.py' (Logger.py|742)
[2] [Sep 27 11:11:43]      line 299 in '_createSite' in file '/usr/lib/python2.4/site-packages/opsiconfd/opsiconfd.py' (Logger.py|742)
[2] [Sep 27 11:11:43]      ==>>> Cannot add webdav content 'repository': permissions on directory '/var/lib/opsi/repository' not sufficient. (opsiconfd.py|449)

allerdings kann ich opsi-setup --set-rights nicht mehr aufrufen, er findet opsi-setup nicht mehr.

[b.boos]

Ich habe es mit etwas Handarbeit selber hinbekommen.

Die Berechtigungen von
/var/lib/opsi/repository
/opt/pcbin/install
waren beide auf root.root gesetzt, ich habe beide auf opsiconfd.pcpatch gesetzt.

Leider fehlt opsi-setup nach dem Update.

MfG
Björn

[ueluekmen]

Hi,

sieht nach einem fehlenden oder fehlerhaft installierten Paket aus.

Was sagt denn:

Code: Alles auswählen

yum list installed | grep opsi