opsiclientd startet nicht / ewiger Windows Systemstart

[acremer]

Guten Morgen zuammen,

ich habe seit gut 2 Wochen ein Problem mit nahezu all unseren PCs. Auf diesen läuft überall Windows 7 Professional 64 Bit.
Das Problem ist, dass sich das System beim Login quasi aufhängt. Sobald man beim normalen Startbildschirm Strg-Alt-Entf drückt, verschwindet diese Meldung und dann (je nach Geschwindigkeit des Rechners) hat man erst einmal einen blauen Bildschirm (sprich der normale Hintergrund des Loginbildschirms) für 5-20 Minuten. Danach ist es dann problemlos möglich sich einzuloggen.
Dazu kommt, dass beim näheren Hinsehen der Dienst opsiclientd nicht gestartet wird und ich diesen auch nicht manuell über Windows im Anschluss starten kann (Fehlermeldung 1053).

Eine Neuinstallation (neueste Version des opsi-client-agent) brachte für 2-3 Systemstarts eine Besserung, jetzt ist alles wie zuvor und das Problem besteht wieder. Somit kann ich auch über den OPSI keine Software mehr verteilen, da der Dienst ja nicht startet und dem entsprechend nicht mit dem Server kommuniziert.

Hat jemand diesbezüglich eine Idee?

Die einzige Anpassung, die ich in dieser Zeit vorgenommen habe ist die Anpassung an die CI und dabei die Änderung der Notifier und des Hintergrundes des opsi winstskin.

Die Logdatei sagt (wobei die Dauer da jeweils wie gesagt variiert):

Code: Alles auswählen

[5] 2015-10-12 09:27:10 ------------------------------------------------------------------------------------
[5] 2015-10-12 09:27:10 START OpsiLoginBlocker
[5] 2015-10-12 09:27:10 ------------------------------------------------------------------------------------
[5] 2015-10-12 09:27:10 Getting config from registry
[5] 2015-10-12 09:27:10 LoginBlockerLogLevel is: 5
[5] 2015-10-12 09:27:10 Read LoginBlockerLogDir from Registry and switch to Logfile 'C:\opsi.org\log'
[5] 2015-10-12 09:27:10 According to LoginBlockerLogDir Logfile='C:\opsi.org\log\opsi_loginblocker.log'
[5] 2015-10-12 09:27:10 LoginBlockerStart is: 1
[5] 2015-10-12 09:27:10 LoginBlockerTimeoutConnect is: 120 seconds
[5] 2015-10-12 09:27:10 Config read from registry.
[5] 2015-10-12 09:27:10 handleLogfileAging started.
[5] 2015-10-12 09:27:10 Check logfile age: 12.10.2015 - current date: 12.10.2015
[5] 2015-10-12 09:27:10 ------------------------------------------------------------------------
[5] 2015-10-12 09:27:10 Keep current logfile.
[5] 2015-10-12 09:27:10 ------------------------------------------------------------------------
[5] 2015-10-12 09:27:10 OS Version: 6.1 (Windows 7)
[5] 2015-10-12 09:27:10 Filtering credential providers
[5] 2015-10-12 09:27:10 Registry: start of opsiclientd service is enabled, waiting for service to start ...
[5] 2015-10-12 09:27:10 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:13 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:16 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:19 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:22 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:25 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:28 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:31 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:34 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:37 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:40 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:43 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:46 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:49 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:52 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:55 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:27:58 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:01 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:04 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:07 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:10 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:13 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:16 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:19 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:22 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:25 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:28 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:31 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:34 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:37 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:40 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:43 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:46 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:49 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:52 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:55 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:28:58 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:29:01 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:29:04 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-12 09:29:07 Service opsiclientd is not running (SERVICE_STOPPED)
[4] 2015-10-12 09:29:10 write timeout file C:\opsi.org\log\opsiclientd_timeout.txt
[3] 2015-10-12 09:29:10 ** Timeout at: 2015-10-12 09:29:10, created timeout file C:\opsi.org\log\opsiclientd_timeout.txt
[3] 2015-10-12 09:29:10 *** ABORT Loginblocker: no connect to opsiclientd ***
[3] 2015-10-12 09:29:10 *****************************************************
[5] 2015-10-12 09:29:20 ------------------------------------------------------------------------------------
[5] 2015-10-12 09:29:20 START OpsiLoginBlocker
[5] 2015-10-12 09:29:20 ------------------------------------------------------------------------------------
[5] 2015-10-12 09:29:20 Getting config from registry
[5] 2015-10-12 09:29:20 LoginBlockerLogLevel is: 5
[5] 2015-10-12 09:29:20 Read LoginBlockerLogDir from Registry and switch to Logfile 'C:\opsi.org\log'
[5] 2015-10-12 09:29:20 According to LoginBlockerLogDir Logfile='C:\opsi.org\log\opsi_loginblocker.log'
[5] 2015-10-12 09:29:20 LoginBlockerStart is: 1
[5] 2015-10-12 09:29:20 LoginBlockerTimeoutConnect is: 120 seconds
[5] 2015-10-12 09:29:20 Config read from registry.
[5] 2015-10-12 09:29:20 handleLogfileAging started.
[5] 2015-10-12 09:29:20 Check logfile age: 12.10.2015 - current date: 12.10.2015
[5] 2015-10-12 09:29:20 ------------------------------------------------------------------------
[5] 2015-10-12 09:29:20 Keep current logfile.
[5] 2015-10-12 09:29:20 ------------------------------------------------------------------------
[5] 2015-10-12 09:29:20 OS Version: 6.1 (Windows 7)
[5] 2015-10-12 09:29:20 Filtering credential providers
[5] 2015-10-12 09:29:20 Registry: start of opsiclientd service is enabled, waiting for service to start ...
[5] 2015-10-12 09:29:20 Service opsiclientd is not running (SERVICE_STOPPED)
[4] 2015-10-12 09:29:20 ** last timeout: 2015-10-12 09:29:10 (Timeout file found C:\opsi.org\log\opsiclientd_timeout.txt)
[4] 2015-10-12 09:29:20 ** boot time at: 2015-10-12 09:14:00
[4] 2015-10-12 09:29:20 ** timeout already occured during this uptime
[3] 2015-10-12 09:29:20 *** ABORT Loginblocker: no connect to opsiclientd ***
[3] 2015-10-12 09:29:20 *****************************************************

Vielen Dank für die Unterstützung!

Mit freundlichem Gruß,

Alexander

[andre_m87]

Das gleiche Problem haben wir in unserer Umgebung auch. Der Client-Agent-Dienst startet auf den Clients nicht mehr - beim Hochfahren der PCs gibt's den beschriebenen Timeout.
Erschwerend kommt hinzu dass die Clients nach der Anmeldung mehrfach einfrieren und ein Arbeiten für ca. 10 Minuten nicht möglich ist. Versucht man den Client-Agent-Dienst manuell zu starten erscheint folgende Fehlermeldung:

Code: Alles auswählen

Der Dienst "opsiclientd" auf "Lokaler Computer" konnte nicht gestartet werden.

Fehler 1053: Der Dienst antwortet nicht rechtzeitig auf die Start- oder Steuerungsanforderung.

[ueluekmen]

Hi,

ist das System schon auf dem neuesten Stand, also 4.0.6? Wird eine opsiclientd.log auf dem Client erstellt? Wenn ja, steht was drin? Das der Client nicht startet, muss einen Grund haben und dem muss man auf den Grund gehen.

Er hat zwei bis drei starts geschafft steht da in einem Post... hast du mal die Logdateien miteinader verglichen? Da muss irgendeine Systematik drin sein, dass klingt sehr kurios.

[Aiko]

Hallo,

bei uns stimmten die Dateien im Ordner /opt/pcbin/install/opsi-client-agent nicht mit den Dateien der aktuellen Version des OPSI Clients überein.
Das Löschen des Ordners und erneute Installieren des Clients über opsi-package-manager -i hat das Problem behoben.

Das geschilderte Problem (blauer Bildschirm nach STRG-ALT-ENTF) tritt danach nicht mehr auf und der Agent wird erfolgreich auf unseren Systemen gestartet.

Viele Grüße

[andre_m87]

Moin zusammen,

bei unseren Clients wird das opsiclientd Log nicht geschrieben. Lediglich das opsi_lockinblocker Log wird - mit den oben beschriebenen Einträgen - geschrieben.
Hier nochmal ein aktueller Auszug:

Code: Alles auswählen

[5] 2015-10-13 07:09:48 Old Logfile from: 25.9.2015 renamed - new Logfile created: 13.10.2015
[5] 2015-10-13 07:09:48 ------------------------------------------------------------------------
[5] 2015-10-13 07:09:48 OS Version: 6.1 (Windows 7)
[5] 2015-10-13 07:09:48 Filtering credential providers
[5] 2015-10-13 07:09:48 Registry: start of opsiclientd service is enabled, waiting for service to start ...
[5] 2015-10-13 07:09:48 Service opsiclientd is not running (SERVICE_STOPPED)
[4] 2015-10-13 07:09:48 ** last timeout: 2015-09-23 14:19:51 (Timeout file found C:\opsi.org\log\opsiclientd_timeout.txt)
[4] 2015-10-13 07:09:48 ** boot time at: 2015-09-23 14:17:42
[4] 2015-10-13 07:09:48 ** timeout already occured during this uptime
[3] 2015-10-13 07:09:48 *** ABORT Loginblocker: no connect to opsiclientd ***
[3] 2015-10-13 07:09:48 *****************************************************
[5] 2015-10-13 07:12:13 ------------------------------------------------------------------------------------
[5] 2015-10-13 07:12:13 START OpsiLoginBlocker
[5] 2015-10-13 07:12:13 ------------------------------------------------------------------------------------
[5] 2015-10-13 07:12:13 Getting config from registry
[5] 2015-10-13 07:12:13 LoginBlockerLogLevel is: 5
[5] 2015-10-13 07:12:13 Read LoginBlockerLogDir from Registry and switch to Logfile 'C:\opsi.org\log'
[5] 2015-10-13 07:12:13 According to LoginBlockerLogDir Logfile='C:\opsi.org\log\opsi_loginblocker.log'
[5] 2015-10-13 07:12:13 LoginBlockerStart is: 1
[5] 2015-10-13 07:12:13 LoginBlockerTimeoutConnect is: 120 seconds
[5] 2015-10-13 07:12:13 Config read from registry.
[5] 2015-10-13 07:12:13 handleLogfileAging started.
[5] 2015-10-13 07:12:13 Check logfile age: 13.10.2015 - current date: 13.10.2015
[5] 2015-10-13 07:12:13 ------------------------------------------------------------------------
[5] 2015-10-13 07:12:13 Keep current logfile.
[5] 2015-10-13 07:12:13 ------------------------------------------------------------------------
[5] 2015-10-13 07:12:13 OS Version: 6.1 (Windows 7)
[5] 2015-10-13 07:12:13 Filtering credential providers
[5] 2015-10-13 07:12:13 Registry: start of opsiclientd service is enabled, waiting for service to start ...
[5] 2015-10-13 07:12:13 Service opsiclientd is not running (SERVICE_STOPPED)
[4] 2015-10-13 07:12:13 ** last timeout: 2015-09-23 14:19:51 (Timeout file found C:\opsi.org\log\opsiclientd_timeout.txt)
[4] 2015-10-13 07:12:13 ** boot time at: 2015-10-13 07:12:04
[4] 2015-10-13 07:12:13 ** delete old timeout file C:\opsi.org\log\opsiclientd_timeout.txt
[5] 2015-10-13 07:12:16 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:19 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:22 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:25 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:28 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:31 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:34 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:37 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:40 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:43 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:46 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:49 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:52 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:55 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:12:58 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:01 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:04 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:07 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:10 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:13 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:16 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:19 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:22 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:25 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:28 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:31 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:34 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:37 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:40 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:43 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:46 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:49 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:52 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:55 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:13:58 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:14:01 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:14:04 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:14:07 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:14:10 Service opsiclientd is not running (SERVICE_STOPPED)
[4] 2015-10-13 07:14:13 write timeout file C:\opsi.org\log\opsiclientd_timeout.txt
[3] 2015-10-13 07:14:13 ** Timeout at: 2015-10-13 07:14:13, created timeout file C:\opsi.org\log\opsiclientd_timeout.txt
[3] 2015-10-13 07:14:13 *** ABORT Loginblocker: no connect to opsiclientd ***
[3] 2015-10-13 07:14:13 *****************************************************
[5] 2015-10-13 07:17:13 ------------------------------------------------------------------------------------
[5] 2015-10-13 07:17:13 START OpsiLoginBlocker
[5] 2015-10-13 07:17:13 ------------------------------------------------------------------------------------
[5] 2015-10-13 07:17:13 Getting config from registry
[5] 2015-10-13 07:17:13 LoginBlockerLogLevel is: 5
[5] 2015-10-13 07:17:13 Read LoginBlockerLogDir from Registry and switch to Logfile 'C:\opsi.org\log'
[5] 2015-10-13 07:17:13 According to LoginBlockerLogDir Logfile='C:\opsi.org\log\opsi_loginblocker.log'
[5] 2015-10-13 07:17:13 LoginBlockerStart is: 1
[5] 2015-10-13 07:17:13 LoginBlockerTimeoutConnect is: 120 seconds
[5] 2015-10-13 07:17:13 Config read from registry.
[5] 2015-10-13 07:17:13 handleLogfileAging started.
[5] 2015-10-13 07:17:13 Check logfile age: 13.10.2015 - current date: 13.10.2015
[5] 2015-10-13 07:17:13 ------------------------------------------------------------------------
[5] 2015-10-13 07:17:13 Keep current logfile.
[5] 2015-10-13 07:17:13 ------------------------------------------------------------------------
[5] 2015-10-13 07:17:13 OS Version: 6.1 (Windows 7)
[5] 2015-10-13 07:17:13 Filtering credential providers
[5] 2015-10-13 07:17:13 Registry: start of opsiclientd service is enabled, waiting for service to start ...
[5] 2015-10-13 07:17:13 Service opsiclientd is not running (SERVICE_STOPPED)
[4] 2015-10-13 07:17:13 ** last timeout: 2015-10-13 07:14:13 (Timeout file found C:\opsi.org\log\opsiclientd_timeout.txt)
[4] 2015-10-13 07:17:13 ** boot time at: 2015-10-13 07:17:05
[4] 2015-10-13 07:17:13 ** delete old timeout file C:\opsi.org\log\opsiclientd_timeout.txt
[5] 2015-10-13 07:17:16 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:19 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:22 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:25 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:28 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:31 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:34 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:37 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:40 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:43 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:46 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:49 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:52 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:55 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:17:58 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:01 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:04 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:07 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:10 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:13 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:16 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:19 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:22 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:25 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:28 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:31 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:34 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:37 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:40 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:43 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:46 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:49 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:52 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:55 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:18:58 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:19:01 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:19:04 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:19:07 Service opsiclientd is not running (SERVICE_STOPPED)
[5] 2015-10-13 07:19:10 Service opsiclientd is not running (SERVICE_STOPPED)
[4] 2015-10-13 07:19:13 write timeout file C:\opsi.org\log\opsiclientd_timeout.txt
[3] 2015-10-13 07:19:13 ** Timeout at: 2015-10-13 07:19:13, created timeout file C:\opsi.org\log\opsiclientd_timeout.txt
[3] 2015-10-13 07:19:13 *** ABORT Loginblocker: no connect to opsiclientd ***
[3] 2015-10-13 07:19:13 *****************************************************
[5] 2015-10-13 07:22:39 ------------------------------------------------------------------------------------
[5] 2015-10-13 07:22:39 START OpsiLoginBlocker
[5] 2015-10-13 07:22:39 ------------------------------------------------------------------------------------
[5] 2015-10-13 07:22:39 Getting config from registry
[5] 2015-10-13 07:22:39 LoginBlockerLogLevel is: 5
[5] 2015-10-13 07:22:39 Read LoginBlockerLogDir from Registry and switch to Logfile 'C:\opsi.org\log'
[5] 2015-10-13 07:22:39 According to LoginBlockerLogDir Logfile='C:\opsi.org\log\opsi_loginblocker.log'
[5] 2015-10-13 07:22:39 LoginBlockerStart is: 1
[5] 2015-10-13 07:22:39 LoginBlockerTimeoutConnect is: 120 seconds
[5] 2015-10-13 07:22:39 Config read from registry.
[5] 2015-10-13 07:22:39 handleLogfileAging started.
[5] 2015-10-13 07:22:39 Check logfile age: 13.10.2015 - current date: 13.10.2015
[5] 2015-10-13 07:22:39 ------------------------------------------------------------------------
[5] 2015-10-13 07:22:39 Keep current logfile.
[5] 2015-10-13 07:22:39 ------------------------------------------------------------------------
[5] 2015-10-13 07:22:39 OS Version: 6.1 (Windows 7)
[5] 2015-10-13 07:22:39 Filtering credential providers
[5] 2015-10-13 07:22:39 Registry: start of opsiclientd service is enabled, waiting for service to start ...
[3] 2015-10-13 07:22:39 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:22:42 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:22:45 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:22:48 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:22:51 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:22:54 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:22:57 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:00 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:03 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:06 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:09 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:12 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:15 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:18 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:21 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:24 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:27 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:30 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:33 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:36 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:39 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:42 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:45 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:48 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:51 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:54 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:23:57 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:24:00 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:24:03 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:24:06 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:24:09 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:24:12 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:24:15 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:24:18 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:24:21 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:24:24 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:24:27 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:24:30 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:24:33 Opening Service Control Manager failed with error=1060
[3] 2015-10-13 07:24:36 Opening Service Control Manager failed with error=1060
[4] 2015-10-13 07:24:39 write timeout file C:\opsi.org\log\opsiclientd_timeout.txt
[3] 2015-10-13 07:24:39 ** Timeout at: 2015-10-13 07:24:39, created timeout file C:\opsi.org\log\opsiclientd_timeout.txt
[3] 2015-10-13 07:24:39 *** ABORT Loginblocker: no connect to opsiclientd ***
[3] 2015-10-13 07:24:39 *****************************************************

Der Fehler "error=1060" trat auf, nachdem ich den aktuellen OPSI-Client (4.0.6.3-3) installiert habe.

Das opsi-client-agent.log kann ich leider nicht posten, da es zu lang ist. Wenn dies für Sie von Interesse ist kann ich es ihnen gerne zur Verfügung stellen.

LG,
André Meier

[Aiko]

Moin,

wie bereits erwähnt bitte einmal den aktuellen OPSI Client auf deinem Server neu installieren und an die Client-Systeme verteilen. Danach sollte der Fehler Service opsiclientd is not running (SERVICE_STOPPED) verschwinden.

Viele Grüße aus Ostfriesland

[edvbuo]

Hi,

wir hatten dasselbe Problem auf den Windows Pc`s. Geholfen hat, den neuesten Client zu Installieren UND das Property "depends_on_service" zu leeren.

Der Dienst DNScache war bei den PC`s meist nie gestartet und Opsi Client hatte damit ein Problem.

Beste Grüße
Niels

[andre_m87]

Moin,

wir haben tatsächlich den aktuellen Client in unserem Depot installiert. Die Dateien des Depots stimmen mit denen des Repositorys (opsi-client-agent 4.0.6.3-3) überein.

LG aus Lüneburg

[Aiko]

Wir verteilen den Client über folgenden Befehl neu:
/var/lib/opsi/depot/opsi-client-agent/opsi-deploy-client-agent -u ".\Administrator" -p "$passwort" -v $pcname.$domain
opsi-admin -d method setProductActionRequest opsi-client-agent $pcname.$domain setup

$pcname wird aus einer *.txt Datei (AD Export der PC-Namen) gezogen, $domain und $passwort wurde im Skript festgelegt. Die zweite Zeile setzt den Agent für das System noch einmal auf "Setup" damit auch Install at Shutdown ordnungsgemäß ausgeführt wird.

[andre_m87]

Hi,

wir hatten dasselbe Problem auf den Windows Pc`s. Geholfen hat, den neuesten Client zu Installieren UND das Property "depends_on_service" zu leeren.

Der Dienst DNScache war bei den PC`s meist nie gestartet und Opsi Client hatte damit ein Problem.

Beste Grüße
Niels

DAS IST ES! Vielen Dank für die Info. Da wir bei uns die WAN-Extension nutzen musste ich die "depends_on_service" Variable in der "setup.ins" direkt editieren. Nach der Deinstallation des aktuellen Agents und der Installation der angepassten Version hats funktioniert!
Dieser "Bug" scheint ja etwas gravierender zu sein, nehmt ihr das als todo für die nächste opsi-client-agent Version auf?

LG,
André