configed startet nicht mehr

Antworten
knebb
Beiträge: 21
Registriert: 14 Mär 2017, 08:14

configed startet nicht mehr

Beitrag von knebb »

Hallo,

unser System:
Opsi 4.0.7.16
auf Univention Corporate Server v4.x (aktuell)

Unser opsiconfi-Editor (Das Java- Admin- Interface) ist nicht mehr erreichbar. Habe etwas Fehlersuche betrieben, der Port 4447 ist geschlossen, der Dienst nicht gestartet. In Windows-Manier auch mal den SErver neu gestartet, aber keine Änderung.
Das sind die letzten Einträge im opsiconfd.log:

Code: Alles auswählen

==================================================================
=             opsi configuration service starting                =
================================================================== (Logger.py|847)
[5] [Oct 28 00:03:54] Creating pid file u'/var/run/opsiconfd/opsiconfd.pid' (opsiconfd.py|653)
[5] [Oct 28 00:03:54] Starting opsiconfd main thread (opsiconfd.py|469)
[5] [Oct 28 00:03:54] Opening socket /var/run/opsiconfd/opsiconfd.socket for interprocess communication. (opsiconfd.py|438)
[5] [Oct 28 00:03:54] Added static content '/' which points to directory '/usr/share/opsiconfd/static' (opsiconfd.py|291)
[5] [Oct 28 00:03:54] Running on depot server 'opsi.evs-nb.de', exporting repository directory (opsiconfd.py|308)
[5] [Oct 28 00:03:54] Running on depot server 'opsi.evs-nb.de', exporting depot directory (opsiconfd.py|321)
[5] [Oct 28 00:03:54] Added webdav content 'repository' which points to directory '/var/lib/opsi/repository' () (opsiconfd.py|354)
[5] [Oct 28 00:03:54] Added webdav content 'depot' which points to directory '/var/lib/opsi/depot' () (opsiconfd.py|354)
[5] [Oct 28 00:03:54] Added webdav content 'configed' which points to directory '/usr/lib/configed' (u'noauth',) (opsiconfd.py|354)
[5] [Oct 28 00:03:54] Accepting HTTPS requests on 0.0.0.0:4447 (opsiconfd.py|407)
[5] [Oct 28 00:03:54] Publishing opsiconfd over zeroconf as 'opsi configuration daemon' on '4447' (opsiconfd.py|421)
[3] [Oct 28 00:03:54] Failed to publish opsiconfd over zeroconf: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory (opsiconfd.py|426)
[5] [Oct 30 09:43:23] Stopping opsiconfd main thread (opsiconfd.py|180)
[5] [Oct 30 09:43:23] Deleting all sessions (Session.py|231)
[5] [Oct 30 09:43:23] Uptime: 2 days, 9:39:31.367183 (opsiconfd.py|500)
[5] [Oct 30 09:43:23] Statistics:  (opsiconfd.py|502)
[5] [Oct 30 09:43:23] Methodname        Callcount       Average processing duration (opsiconfd.py|503)
[5] [Oct 30 09:43:23] accessControl_authenticated       1       0.000s (opsiconfd.py|507)
[5] [Oct 30 09:43:23] backend_getInterface      1       0.013s (opsiconfd.py|507)
[5] [Oct 30 09:43:23] backend_info      2       0.001s (opsiconfd.py|507)
[5] [Oct 30 09:43:23] backend_setOptions        2       0.001s (opsiconfd.py|507)
[5] [Oct 30 09:43:23] configState_getObjects    2       0.142s (opsiconfd.py|507)
[5] [Oct 30 09:43:23] dispatcher_getConfig      1       0.001s (opsiconfd.py|507)
[5] [Oct 30 09:43:23] log_write 1       0.011s (opsiconfd.py|507)
[5] [Oct 30 09:43:23] productOnClient_getObjects        1       0.051s (opsiconfd.py|507)
[5] [Oct 30 09:43:23] Opsiconfd main thread exiting... (opsiconfd.py|494)
Seitdem keine Einträge mehr. Versuche, den opsiconfiged zu starten ergeben eine Fehlermeldung im syslog:

Code: Alles auswählen

Nov 20 10:09:55 opsi opsiconfd[814]: chown: ungültiger Benutzer: „opsiconfd“
Nov 20 10:09:55 opsi opsiconfd[814]: chown: ungültiger Benutzer: „opsiconfd“
Nov 20 10:09:55 opsi opsiconfd[814]: chown: ungültiger Benutzer: „opsiconfd“
Nov 20 10:09:55 opsi opsiconfd[814]: chown: ungültiger Benutzer: „opsiconfd“
Nov 20 10:09:55 opsi opsiconfd[814]: chown: ungültiger Benutzer: „opsiconfd:opsiadmin“
Nov 20 10:09:55 opsi opsiconfd[814]: Kein Passworteintrag für Benutzer »opsiconfd«

Was könnte denn da passiert sein?

Danke!
/KNEBB
knebb
Beiträge: 21
Registriert: 14 Mär 2017, 08:14

Re: configed startet nicht mehr

Beitrag von knebb »

Noch eine Ergänzung:

Komischerweise haben wir bei dem zweiten Server genau das gleiche Problem und ähnliche Einträge in den Logfiles:

Code: Alles auswählen

==================================================================
=             opsi configuration service starting                =
================================================================== (Logger.py|847)
[5] [Oct 21 00:04:54] Creating pid file u'/var/run/opsiconfd/opsiconfd.pid' (opsiconfd.py|653)
[5] [Oct 21 00:04:54] Starting opsiconfd main thread (opsiconfd.py|469)
[5] [Oct 21 00:04:54] Opening socket /var/run/opsiconfd/opsiconfd.socket for interprocess communication. (opsiconfd.py|438)
[5] [Oct 21 00:04:54] Added static content '/' which points to directory '/usr/share/opsiconfd/static' (opsiconfd.py|291)
[5] [Oct 21 00:04:55] Running on depot server 'opsi2.evs-nb.de', exporting repository directory (opsiconfd.py|308)
[5] [Oct 21 00:04:55] Running on depot server 'opsi2.evs-nb.de', exporting depot directory (opsiconfd.py|321)
[5] [Oct 21 00:04:55] Added webdav content 'repository' which points to directory '/var/lib/opsi/repository' () (opsiconfd.py|354)
[5] [Oct 21 00:04:55] Added webdav content 'depot' which points to directory '/var/lib/opsi/depot' () (opsiconfd.py|354)
[5] [Oct 21 00:04:55] Added webdav content 'configed' which points to directory '/usr/lib/configed' (u'noauth',) (opsiconfd.py|354)
[5] [Oct 21 00:04:55] Accepting HTTPS requests on 0.0.0.0:4447 (opsiconfd.py|407)
[5] [Oct 21 00:04:55] Publishing opsiconfd over zeroconf as 'opsi configuration daemon' on '4447' (opsiconfd.py|421)
[3] [Oct 21 00:04:55] Failed to publish opsiconfd over zeroconf: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory (opsiconfd.py|426)
[5] [Oct 28 00:04:17] Stopping opsiconfd main thread (opsiconfd.py|180)
[5] [Oct 28 00:04:17] Deleting all se[5] [Oct 30 20:44:53] Stopping opsiconfd main thread (opsiconfd.py|180)
[5] [Oct 30 20:44:53] Deleting all sessions (Session.py|231)
[5] [Oct 30 20:44:54] Uptime: 2 days, 20:39:55.117459 (opsiconfd.py|500)
[5] [Oct 30 20:44:54] Statistics:  (opsiconfd.py|502)
[5] [Oct 30 20:44:54] Methodname        Callcount       Average processing duration (opsiconfd.py|503)
[5] [Oct 30 20:44:54] Opsiconfd main thread exiting... (opsiconfd.py|494)
Umnd auch hier im Syslog:

Code: Alles auswählen

Oct 30 20:46:14 opsi2 opsiconfd[734]: chown: ungültiger Benutzer: „opsiconfd“
Oct 30 20:46:14 opsi2 opsiconfd[734]: chown: ungültiger Benutzer: „opsiconfd“
Oct 30 20:46:14 opsi2 opsiconfd[734]: chown: ungültiger Benutzer: „opsiconfd“
Oct 30 20:46:14 opsi2 opsiconfd[734]: chown: ungültiger Benutzer: „opsiconfd“
Oct 30 20:46:14 opsi2 univention-saml[862]: .
Oct 30 20:46:14 opsi2 systemd[1]: Started LSB: Univention Security Assertion Markup Language integration.
Oct 30 20:46:14 opsi2 systemd[1]: Started Terminate Plymouth Boot Screen.
Oct 30 20:46:14 opsi2 systemd[1]: Starting Starting univention-welcome screen...
Oct 30 20:46:14 opsi2 systemd[1]: Started Starting univention-welcome screen.
Oct 30 20:46:14 opsi2 opsiconfd[734]: chown: ungültiger Benutzer: „opsiconfd:opsiadmin“
Oct 30 20:46:14 opsi2 opsiconfd[734]: Kein Passworteintrag für Benutzer »opsiconfd«
Und nein, ich wüßte nicht, was am 30.10.2017 geändert wurde :oops:
knebb
Beiträge: 21
Registriert: 14 Mär 2017, 08:14

Re: configed startet nicht mehr

Beitrag von knebb »

Kommando zurück.

Ein "service opsiconfiged start" brachte Erfolg. :shock:

ich werde das mal beobachten....
Antworten