ist es möglich mit einem opsi-server mit 2 netzwerk-karten clients in 2 getrennten segmenten/subnetzen zu bedienen ?
gruss
boris
multi-homed opsi-server
-
borissynak
- Beiträge: 6
- Registriert: 25 Mai 2014, 13:15
multi-homed opsi-server
look, he's crawling up my wall
black and hairy, very small
now he's up above my head
hanging by a little thread
black and hairy, very small
now he's up above my head
hanging by a little thread
Re: multi-homed opsi-server
Hi,
generell ja. Aber eine zweite Netzwerkkarte in einen Server ein zu bauen ist nicht so einfach wie es klingt. Da du eine direkte Verbindung zwischen zwei Netzwerken herstellst (was ja jemand bewusst nicht will, sonst würde es keine zwei Netzwerke geben) solltest du die Netze voreinander schützen.
Auch das Routing ist nicht so einfach mit zwei Netzwerkkarten. Wenn du Netzwerktechnisch und Linuxtechnisch nicht einiges an Basiswissen hast, wird das schwierig.
Erfahrungsgemäß ist es einfacher diese Anforderung über die Netzwerkinfrastruktur zu lösen.
generell ja. Aber eine zweite Netzwerkkarte in einen Server ein zu bauen ist nicht so einfach wie es klingt. Da du eine direkte Verbindung zwischen zwei Netzwerken herstellst (was ja jemand bewusst nicht will, sonst würde es keine zwei Netzwerke geben) solltest du die Netze voreinander schützen.
Auch das Routing ist nicht so einfach mit zwei Netzwerkkarten. Wenn du Netzwerktechnisch und Linuxtechnisch nicht einiges an Basiswissen hast, wird das schwierig.
Erfahrungsgemäß ist es einfacher diese Anforderung über die Netzwerkinfrastruktur zu lösen.
Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.
Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.
uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de
-
borissynak
- Beiträge: 6
- Registriert: 25 Mai 2014, 13:15
Re: multi-homed opsi-server
hallo,
danke fuer die prompte antwort !
konnte meine tests erst heute fortsetzen, leider mit maessigem erfolg.
versuchsaufbau mit virtuellen maschinen
ausgangssituation:
funktionierender opsi-server mit eth0 ( 192.168.97.234/24 = Net_A )
nic eth1 ( 192.168.98.234/24 = Net_B ) hinzugefuegt
ipforwarding disabled
isc-dchp-server für beide netze konfiguriert
via opsi config editor sind folgende Parameter gesetzt:
Server: client.configserver.url https://192.168.97.234:4447/rpc, https://192.168.98.234:4447/rpc
client001 ( Net_A ): client.configserver.url https://192.168.97.234:4447/rpc
client002 ( Net_B ): client.configserver.url https://192.168.98.234:4447/rpc
windows 7 installation
client001 ( Net_A ): alles OK
"%programfiles%\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf"
client002 ( Net_B ):
pxe-boot ok
infos des hwaudit werden in server-log zurueckgeschrieben
installation win7 funktioniert
aber bei der installation des opsi-client-agent wird in
"%programfiles%\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf"
folgendes eingetragen:
haendisches korrigieren der config-service-url und eintragen von depot_id, url und drive fuehrt zum erfolg
daher meine frage:
wie wird fuer den opsiclientd die ip-adresse des config-servers und die infos zum depot-server ermittelt ?
bzw.
watt mach ich falsch ??
sorry fuer den laengeren roman und danke vorab
boris
danke fuer die prompte antwort !
konnte meine tests erst heute fortsetzen, leider mit maessigem erfolg.
versuchsaufbau mit virtuellen maschinen
ausgangssituation:
funktionierender opsi-server mit eth0 ( 192.168.97.234/24 = Net_A )
nic eth1 ( 192.168.98.234/24 = Net_B ) hinzugefuegt
ipforwarding disabled
isc-dchp-server für beide netze konfiguriert
via opsi config editor sind folgende Parameter gesetzt:
Server: client.configserver.url https://192.168.97.234:4447/rpc, https://192.168.98.234:4447/rpc
client001 ( Net_A ): client.configserver.url https://192.168.97.234:4447/rpc
client002 ( Net_B ): client.configserver.url https://192.168.98.234:4447/rpc
windows 7 installation
client001 ( Net_A ): alles OK
"%programfiles%\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf"
[global]
host_id = client001.test.local
...
[config_service]
url = https://192.168.97.234:4447/rpc
...
[depot_server]
depot_id = opsi-server.test.local
url = smb://opsi-server/opsi_depot
drive = p:
username = pcpatch
...
client002 ( Net_B ):
pxe-boot ok
infos des hwaudit werden in server-log zurueckgeschrieben
installation win7 funktioniert
aber bei der installation des opsi-client-agent wird in
"%programfiles%\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf"
folgendes eingetragen:
damit schlagen natuerlich alle weiteren opsi-versuche des clients fehl.[global]
host_id=client002.test.local
...
[config_service]
url=https://192.168.97.234:4447/rpc
...
[depot_server]
depot_id=
url=
drive=
username=pcpatch
...
haendisches korrigieren der config-service-url und eintragen von depot_id, url und drive fuehrt zum erfolg
daher meine frage:
wie wird fuer den opsiclientd die ip-adresse des config-servers und die infos zum depot-server ermittelt ?
bzw.
watt mach ich falsch ??
sorry fuer den laengeren roman und danke vorab
boris
look, he's crawling up my wall
black and hairy, very small
now he's up above my head
hanging by a little thread
black and hairy, very small
now he's up above my head
hanging by a little thread
Re: multi-homed opsi-server
Hi,
was Du vorhast, ist derzeit in den Installroutinen nicht vorgesehen.
Folgendes Problem tritt auf:
Bei der Installation des opsi-client-agent Paketes auf dem Server (!) wird in der Datei /var/lib/opsi/depot/opsi-client-agent/files/opsi/cfg.config.ini
in der Sektion [opsiclientd] für den Wert config_service.url die Standard IP des Serververs rein geschrieben.
Diese Adresse wird bei der Installation des opsi-client-agents in die opsiclientd.conf übertragen und verwendet um den opsiserver zu erreichen.
Wenn über diese Adresse der opsi Server nicht erreichbar ist funktioniert die Sache nicht.
Man müsste die Sache so erweitern, das es möglich ist mehrere Adressen zu hinterlegen und das bei der Installation geprüft wird unter welcher der Server erreichbar ist und dann diese verwenden.
Viel Arbeit ist das nicht aber etwas schon.
Hast Du einen Supportvertrag ?
gruß
d.oertel
was Du vorhast, ist derzeit in den Installroutinen nicht vorgesehen.
Folgendes Problem tritt auf:
Bei der Installation des opsi-client-agent Paketes auf dem Server (!) wird in der Datei /var/lib/opsi/depot/opsi-client-agent/files/opsi/cfg.config.ini
in der Sektion [opsiclientd] für den Wert config_service.url die Standard IP des Serververs rein geschrieben.
Diese Adresse wird bei der Installation des opsi-client-agents in die opsiclientd.conf übertragen und verwendet um den opsiserver zu erreichen.
Wenn über diese Adresse der opsi Server nicht erreichbar ist funktioniert die Sache nicht.
Man müsste die Sache so erweitern, das es möglich ist mehrere Adressen zu hinterlegen und das bei der Installation geprüft wird unter welcher der Server erreichbar ist und dann diese verwenden.
Viel Arbeit ist das nicht aber etwas schon.
Hast Du einen Supportvertrag ?
gruß
d.oertel
Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.
Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.
uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de
-
borissynak
- Beiträge: 6
- Registriert: 25 Mai 2014, 13:15
Re: multi-homed opsi-server
hallo herr oertel
leider hat's etwas gedauert bis ich mich der fragestellung annehmen konnte ( support-vertrag habe ich nicht ).
zunaechst danke fuer den tip, der mich erst in die richtige richtung gefuehrt hat !!
bin zu folgender loesung gekommen, die ich gerade intensiv teste.
1.
beide interfaces des servers sind als "clientconfig.configserver.url" definiert:
2.
"<packagedir>/CLIENT_DATA/utils/patch_config_file.py" ist so angepasst, das beide urls in bei installation des paketes auf dem server
in "<packagedir>/CLIENT_DATA/files/opsi/cfg/config.ini" eingetragen werden.
siehe folgender output von "diff -u patch_config_file.py.org patch_config_file.py.new"
3.
"<packagedir>/CLIENT_DATA/files/opsi/setup.ins" ist so angepasst, das fuer die gegebenen urls getestet wird ob die fragliche ip
via ping vom client aus erreicht werden kann. falls ja wird diese url fuer den fraglichen client verwendet und als "clientconfig.configserver.url" des clients
beim server eingetragen.
siehe folgender output von "diff -u setup.ins.org setup.ins.new"
rueckmeldung / kritik herzlich willkommen
boris
leider hat's etwas gedauert bis ich mich der fragestellung annehmen konnte ( support-vertrag habe ich nicht ).
zunaechst danke fuer den tip, der mich erst in die richtige richtung gefuehrt hat !!
bin zu folgender loesung gekommen, die ich gerade intensiv teste.
1.
beide interfaces des servers sind als "clientconfig.configserver.url" definiert:
Code: Alles auswählen
opsi-admin -d method getGeneralConfigValue "clientconfig.configserver.url" "opsi-server.test.local"
"https://192.168.97.234:4447/rpc,https://192.168.98.234:4447/rpc"
"<packagedir>/CLIENT_DATA/utils/patch_config_file.py" ist so angepasst, das beide urls in bei installation des paketes auf dem server
in "<packagedir>/CLIENT_DATA/files/opsi/cfg/config.ini" eingetragen werden.
siehe folgender output von "diff -u patch_config_file.py.org patch_config_file.py.new"
Code: Alles auswählen
--- patch_config_file.py.org 2014-10-15 14:55:52.614172321 +0200
+++ patch_config_file.py.new 2014-10-15 14:55:52.614172321 +0200
@@ -52,9 +52,30 @@
configs = b.config_getObjects(id = 'clientconfig.configserver.url')
if configs:
- configurl = configs[0].defaultValues[0]
- if configurl.endswith("/rpc"):
- configurl = configurl[:-4]
+
+#####################################
+# <boris.synak@zobelsoft.de>
+#####################################
+
+ configurl = ""
+ for url in configs[0].defaultValues:
+ if url.endswith("/rpc"):
+ url = url[:-4]
+ configurl += url
+ configurl += ", "
+ print configurl
+
+ configurl = configurl[:-2]
+ print configurl
+
+# configurl = configs[0].defaultValues[0]
+# if configurl.endswith("/rpc"):
+# configurl = configurl[:-4]
+
+#####################################
+# </boris.synak@zobelsoft.de>
+#####################################
+
else:
configurl = "https://" + configServerIp + ":4447"
"<packagedir>/CLIENT_DATA/files/opsi/setup.ins" ist so angepasst, das fuer die gegebenen urls getestet wird ob die fragliche ip
via ping vom client aus erreicht werden kann. falls ja wird diese url fuer den fraglichen client verwendet und als "clientconfig.configserver.url" des clients
beim server eingetragen.
siehe folgender output von "diff -u setup.ins.org setup.ins.new"
Code: Alles auswählen
--- setup.ins.org 2014-10-15 15:10:43.330157493 +0200
+++ setup.ins.new 2014-10-15 15:10:43.330157493 +0200
@@ -12,6 +12,20 @@
; INST = used while installation
; Script variables with prefix INST
+;*************************************
+; <boris.synak@zobelsoft.de>
+;*************************************
+
+DefVar $OCD_WORKING_config_service.url$
+DefStringList $OCD_POSSIBLE_config_service.urls$
+DefVar $OCD_TEST_URL_IP$
+DefVar $OCD_PING_RESULT$
+
+;*************************************
+; </boris.synak@zobelsoft.de>
+;*************************************
+
+
;******** installation vars **********
DefVar $INST_AktGina$
DefVar $INST_AllowReboot$
@@ -556,6 +570,28 @@
Set $OLB_LoginBlockerStart$ = GetValueFromInifile($INST_custom_Cfgini$, "opsiLoginBlocker", "LoginBlockerStart", $OLB_LoginBlockerStart$)
Set $OLB_LoginBlockerTimeoutConnect$ = GetValueFromInifile($INST_custom_Cfgini$, "opsiLoginBlocker", "LoginBlockerTimeoutConnect", $OLB_LoginBlockerTimeoutConnect$)
+
+;*************************************
+; <boris.synak@zobelsoft.de>
+;*************************************
+if contains( $OCD_config_service.url$, "," )
+
+ Set $OCD_POSSIBLE_config_service.urls$ = splitString( $OCD_config_service.url$, "," )
+
+ for %possible_config_service_url% in $OCD_POSSIBLE_config_service.urls$ do sub_test_config_service_url
+
+ Set $OCD_config_service.url$ = $OCD_WORKING_config_service.url$
+
+endif
+;*************************************
+; <boris.synak@zobelsoft.de>
+;*************************************
+
+
+
+
+
+
; change value given by config.ini only if property present
if GetProductProperty ("LoginBlockerStart","") = "on"
Set $OLB_LoginBlockerStart$ = "1"
@@ -661,6 +697,12 @@
if errorsOccuredSinceMark > 0
comment "was not authenticated -> retry scripted login by client ID and hostkey"
comment "Try to open new network connection"
+
+
+
+
+
+
markErrorNumber
SetLogLevel=$INST_PasswdLogLevel$
opsiservicecall_authenticated /username $INST_ClientId$ /password $SHI_pckey$ /serviceurl $OCD_config_service.url$
@@ -941,6 +983,23 @@
; *** Get active service url ***
Set $INST_ServiceResult$ = getReturnListFromSection('opsiservicecall_getNetworkconfig_hash')
set $OCD_config_service.url$ = takestring(1, splitString(takeFirstStringContaining($INST_ServiceResult$,"nextBootServiceURL"), '='))
+
+;*************************************
+; <boris.synak@zobelsoft.de>
+;*************************************
+if contains( $OCD_config_service.url$, "," )
+
+ Set $OCD_POSSIBLE_config_service.urls$ = splitString( $OCD_config_service.url$, "," )
+
+ for %possible_config_service_url% in $OCD_POSSIBLE_config_service.urls$ do sub_test_config_service_url
+
+ Set $OCD_config_service.url$ = $OCD_WORKING_config_service.url$
+
+endif
+;*************************************
+; <boris.synak@zobelsoft.de>
+;*************************************
+
if $OCD_config_service.url$ = ""
comment "Getting values from from config file"
Set $OCD_config_service.url$ = GetvalueFromInifile($INST_cfgini$, "opsiclientd", "config_service.url", "")
@@ -948,6 +1007,22 @@
Set $OCD_config_service.url$ = GetvalueFromInifile($INST_custom_Cfgini$, "opsiclientd", "config_service.url", $OCD_config_service.url$)
endif
+;*************************************
+; <boris.synak@zobelsoft.de>
+;*************************************
+if contains( $OCD_config_service.url$, "," )
+
+ Set $OCD_POSSIBLE_config_service.urls$ = splitString( $OCD_config_service.url$, "," )
+
+ for %possible_config_service_url% in $OCD_POSSIBLE_config_service.urls$ do sub_test_config_service_url
+
+ Set $OCD_config_service.url$ = $OCD_WORKING_config_service.url$
+
+endif
+;*************************************
+; <boris.synak@zobelsoft.de>
+;*************************************
+
; uncommented for experimental 4.0.4.2-1 :
;; *** Get hostkey1 ***
; SetLogLevel=$INST_PasswdLogLevel$
@@ -1129,7 +1204,21 @@
comment "lock c:\opsi.org -> for administrators only"
DosInAnIcon_lock_c_opsiorg
+
+;*************************************
+; <boris.synak@zobelsoft.de>
+;*************************************
+opsiservicecall_setGeneralConfigValue_clientconfig_configserver_url
+Set $OCD_config_service.url$ = stringReplace( $OCD_config_service.url$, "/rpc", "" )
+comment "$OCD_config_service.url$ = " + $OCD_config_service.url$
+;*************************************
+; </boris.synak@zobelsoft.de>
+;*************************************
+
+
+
Patches_opsiclientd_conf_rest $INST_OpsiclientdConf$
+
if not (($SHI_pckey$ = "") or ($SHI_pckey$ = "#@PCKEY#"))
comment "dont log the pckey"
SetLogLevel=$INST_PasswdLogLevel$
@@ -2400,3 +2489,44 @@
;**************************************************
;**************************************************
+
+
+
+
+
+
+
+
+;*************************************
+; <boris.synak@zobelsoft.de>
+;*************************************
+
+
+[opsiservicecall_setGeneralConfigValue_clientconfig_configserver_url]
+"method": "setGeneralConfigValue"
+"params": [
+ "clientconfig.configserver.url",
+ "$OCD_config_service.url$"
+ "$INST_ClientId$"
+ ]
+
+
+[sub_test_config_service_url]
+comment "testing " + trim("%possible_config_service_url%")
+Set $OCD_TEST_URL_IP$ = stringReplace( trim( takeString(1, splitString( trim("%possible_config_service_url%"), ":") ) ), "/", "" )
+comment "IP to check:" + $OCD_TEST_URL_IP$
+dosinanicon_ping_test_url
+set $OCD_PING_RESULT$ = getLastExitCode
+if $OCD_PING_RESULT$ = "0"
+ Set $OCD_WORKING_config_service.url$ = trim("%possible_config_service_url%")
+endif
+
+
+[dosinanicon_ping_test_url]
+ping -4 -n 3 $OCD_TEST_URL_IP$
+
+
+
+;*************************************
+; </boris.synak@zobelsoft.de>
+;*************************************
boris
look, he's crawling up my wall
black and hairy, very small
now he's up above my head
hanging by a little thread
black and hairy, very small
now he's up above my head
hanging by a little thread
Re: multi-homed opsi-server
Hi,
danke für den Patch.
Wir haben im Moment leider keine Zeit Ihn zu testet (opsi 4.0.5 muß fertig werden).
Damit er nicht vergessen wird habe ich ein internes Ticket aufgemacht.
Dieses wir bei der nächsten tieferen Bearbeitung des client-agent dann abgearbeitet.
gruß
d.oertel
danke für den Patch.
Wir haben im Moment leider keine Zeit Ihn zu testet (opsi 4.0.5 muß fertig werden).
Damit er nicht vergessen wird habe ich ein internes Ticket aufgemacht.
Dieses wir bei der nächsten tieferen Bearbeitung des client-agent dann abgearbeitet.
gruß
d.oertel
Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.
Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.
uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de
Re: multi-homed opsi-server
Gibt es hier schon etwas neues?! 
Ich werde in ein paar Wochen das gleiche Problem angehen müssen
Ich werde in ein paar Wochen das gleiche Problem angehen müssen
Re: multi-homed opsi-server
Ich habe jetzt genau das gleich Problem...
Wir haben zwei Netze 192.168.0.x (SuperNeting) und 192.168.14.x
Der OPSI steht mit Depot und Configed im 192.168.0.x.
Bei allen Clients in diesem Netz funktioniert alles einwandfrei.
Bei dem Testclient im 14er Netz, kann ich diesen OnDemand runterfahren...ergo scheint die Verdbingung vom Server aus zum Client zu funktionieren.
Nur Produkte die ich auf "setup" setze können beim Start des Clients nicht ausgeführt werden weil ich eine Fehlermeldung bekomme
Dann bin ich mal den Infos aus dem Thread hier gefolgt:
1) Unter "clientconfig.configserver.url" habe ich beide Adressen eingetragen (im Configed) Webinterface
2) Ein opsi-admin -d method getGeneralConfigValue "clientconfig.configserver.url" "opsiserver0.domain.de"
gibt mir "https://opsiserver0.domain:4447/rpc,htt ... n:4447/rpc" zurück.
Beim Start des Clients (14er) Netz wird aber immer opsiserver0 angesprochen.
Wie ich gesehen habe habt ihr im opsi-client-agent den Patch von Boris mit dem (automatischen) wählen des zu erreichenden configservers schon eingebaut? Aber funktionieren tut das bei mir irgendwie nicht.
Was mache ich falsch?
Wir haben zwei Netze 192.168.0.x (SuperNeting) und 192.168.14.x
Der OPSI steht mit Depot und Configed im 192.168.0.x.
Bei allen Clients in diesem Netz funktioniert alles einwandfrei.
Bei dem Testclient im 14er Netz, kann ich diesen OnDemand runterfahren...ergo scheint die Verdbingung vom Server aus zum Client zu funktionieren.
Nur Produkte die ich auf "setup" setze können beim Start des Clients nicht ausgeführt werden weil ich eine Fehlermeldung bekomme
Code: Alles auswählen
[Errno 11004] getaddrinfo failed
1) Unter "clientconfig.configserver.url" habe ich beide Adressen eingetragen (im Configed) Webinterface
2) Ein opsi-admin -d method getGeneralConfigValue "clientconfig.configserver.url" "opsiserver0.domain.de"
gibt mir "https://opsiserver0.domain:4447/rpc,htt ... n:4447/rpc" zurück.
Beim Start des Clients (14er) Netz wird aber immer opsiserver0 angesprochen.
Wie ich gesehen habe habt ihr im opsi-client-agent den Patch von Boris mit dem (automatischen) wählen des zu erreichenden configservers schon eingebaut? Aber funktionieren tut das bei mir irgendwie nicht.
Was mache ich falsch?
-
n.wenselowski
- Ex-uib-Team
- Beiträge: 3194
- Registriert: 04 Apr 2013, 12:15
Re: multi-homed opsi-server
Hi,
da scheint ja ein Problem mit dem Auflösen einer Adresse vorhanden zu sein.
Wo kommt die Fehlermeldung?
Bei sowas ist es natürlich interessant auch ein wenig mehr zu sehen, damit man den Context sieht
Gruß
Niko
da scheint ja ein Problem mit dem Auflösen einer Adresse vorhanden zu sein.
Wo kommt die Fehlermeldung?
Bei sowas ist es natürlich interessant auch ein wenig mehr zu sehen, damit man den Context sieht
Gruß
Niko
Code: Alles auswählen
import OPSIRe: multi-homed opsi-server
Wenn ich am Client angemeldet bin, dann kann ich opsiserver14 pingen. Das funktioniert.
Die Meldung kommt, wenn der Client nach dem Start versucht das auf Setup gesetzte Softwareprodukt zu installieren.
Die Logs vom Client sehen so aus:
Darin sehe ich, dass er immer auf opsiserver0 zugreifen will. Obwohl ich ihm im clientconfig.configserver.url beide angegeben habe.
Ich dachte das der Patch von Boris (wenn zwei angegeben sind) den als client.configserver nimmt, den er erreichen kann?
Die Meldung kommt, wenn der Client nach dem Start versucht das auf Setup gesetzte Softwareprodukt zu installieren.
Die Logs vom Client sehen so aus:
Code: Alles auswählen
[6] [Nov 04 10:19:25] [ event generator wait_for_gui ] Starting FireEventThread for listeners: [<ocdlib.Opsiclientd.WaitForGUI object at 0x02621B50>] (Events.pyo|465)
[6] [Nov 04 10:19:25] [ event generator wait_for_gui ] Event generator '<GUIStartupEventGenerator wait_for_gui>' now deactivated after 1 event occurrences (Events.pyo|487)
[6] [Nov 04 10:19:25] [ event generator wait_for_gui ] Event generator '<GUIStartupEventGenerator wait_for_gui>' exiting (Events.pyo|498)
[6] [Nov 04 10:19:25] [ event generator wait_for_gui ] Calling processEvent on listener <ocdlib.Opsiclientd.WaitForGUI object at 0x02621B50> (Events.pyo|460)
[6] [Nov 04 10:19:25] [ event generator wait_for_gui ] GUI started (Opsiclientd.pyo|168)
[6] [Nov 04 10:19:25] [ event processing gui_startup ] Session id set to 1 (EventProcessing.pyo|173)
[5] [Nov 04 10:19:25] [ event processing gui_startup ] ============= EventProcessingThread for occurrcence of event 'gui_startup' started ============= (EventProcessing.pyo|1097)
[5] [Nov 04 10:19:25] [ event processing gui_startup ] Starting notification server on port 44003 (EventProcessing.pyo|194)
[6] [Nov 04 10:19:25] [ opsiclientd ] Notification server starting (Message.pyo|598)
[5] [Nov 04 10:19:25] [ opsiclientd ] Done waiting for GUI (Opsiclientd.pyo|314)
[6] [Nov 04 10:19:26] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:26] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:26] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:26] [ control pipe ] Got result (JsonRpc.pyo|133)
[5] [Nov 04 10:19:26] [ event processing gui_startup ] Notification server started (EventProcessing.pyo|221)
[6] [Nov 04 10:19:26] [ event processing gui_startup ] Action processor name 'opsi-script', version '4.11.5.14' (EventProcessing.pyo|351)
[5] [Nov 04 10:19:26] [ opsiclientd ] Block login now set to 'True' (Opsiclientd.pyo|109)
[5] [Nov 04 10:19:26] [ event processing gui_startup ] Starting notifier application in session '1' (EventProcessing.pyo|322)
[6] [Nov 04 10:19:26] [ opsiclientd ] Searching pids of process name winlogon.exe (session id: 1) (Windows.pyo|1400)
[6] [Nov 04 10:19:26] [ opsiclientd ] Found process winlogon.exe with matching name (pid 564, session 1) (Windows.pyo|1423)
[5] [Nov 04 10:19:26] [ opsiclientd ] Executing: 'C:\Program Files (x86)\opsi.org\opsi-client-agent\\opsiclientd_rpc.exe "bgfa470.domain.de" "*** confidential ***" "4441" "setCurrentActiveDesktopName("1", System.getActiveDesktopName())"' in session '1' on desktop 'winsta0\winlogon' (Windows.pyo|1587)
[6] [Nov 04 10:19:26] [ opsiclientd ] Process startet, pid: 1376 (Windows.pyo|1590)
[6] [Nov 04 10:19:26] [ opsiclientd ] Waiting for process ending: 1376 (timeout: 60 seconds) (Windows.pyo|1593)
[6] [Nov 04 10:19:27] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:27] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:27] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:27] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:28] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:28] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:28] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:28] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:29] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:29] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:29] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:29] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:30] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:30] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:30] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:30] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:30] [ control server ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x024395F8> started processing (Worker.pyo|249)
[5] [Nov 04 10:19:30] [ control server ] New session created (Session.pyo|179)
[5] [Nov 04 10:19:30] [ control server ] Authorization request from bgfa470.domain.de@127.0.0.1 (application: opsi jsonrpc module version 4.0.5) (ControlServer.pyo|162)
[5] [Nov 04 10:19:30] [ opsiclientd ] -----> Executing: backend_getInterface() (JsonRpc.pyo|125)
[6] [Nov 04 10:19:30] [ opsiclientd ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:30] [ control server ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x02439260> started processing (Worker.pyo|249)
[6] [Nov 04 10:19:30] [ control server ] Reusing session for client '127.0.0.1', application 'opsi jsonrpc module version 4.0.5' (Worker.pyo|390)
[5] [Nov 04 10:19:30] [ control server ] Authorization request from bgfa470.domain.de@127.0.0.1 (application: opsi jsonrpc module version 4.0.5) (ControlServer.pyo|162)
[5] [Nov 04 10:19:30] [ opsiclientd ] -----> Executing: setCurrentActiveDesktopName(1, u'Winlogon') (JsonRpc.pyo|125)
[5] [Nov 04 10:19:30] [ opsiclientd ] rpc setCurrentActiveDesktopName: current active desktop name for session 1 set to 'Winlogon' (ControlServer.pyo|564)
[6] [Nov 04 10:19:30] [ opsiclientd ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:30] [ control server ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x02447198> started processing (Worker.pyo|249)
[6] [Nov 04 10:19:30] [ control server ] Reusing session for client '127.0.0.1', application 'opsi jsonrpc module version 4.0.5' (Worker.pyo|390)
[5] [Nov 04 10:19:30] [ control server ] Authorization request from bgfa470.domain.de@127.0.0.1 (application: opsi jsonrpc module version 4.0.5) (ControlServer.pyo|162)
[5] [Nov 04 10:19:30] [ opsiclientd ] -----> Executing: backend_exit() (JsonRpc.pyo|125)
[6] [Nov 04 10:19:30] [ opsiclientd ] Got result (JsonRpc.pyo|133)
[5] [Nov 04 10:19:30] [ opsiclientd ] Process 1376 ended with exit code 0 (Windows.pyo|1603)
[6] [Nov 04 10:19:30] [ event processing gui_startup ] Running command C:\Program Files (x86)\opsi.org\opsi-client-agent\\notifier.exe -p 44003 -i event -s notifier\\event.ini in session '1' on desktop 'winlogon' (EventProcessing.pyo|298)
[6] [Nov 04 10:19:30] [ event processing gui_startup ] Searching pids of process name winlogon.exe (session id: 1) (Windows.pyo|1400)
[6] [Nov 04 10:19:30] [ event processing gui_startup ] Found process winlogon.exe with matching name (pid 564, session 1) (Windows.pyo|1423)
[5] [Nov 04 10:19:30] [ event processing gui_startup ] Executing: 'C:\Program Files (x86)\opsi.org\opsi-client-agent\\notifier.exe -p 44003 -i event -s notifier\\event.ini' in session '1' on desktop 'winsta0\winlogon' (Windows.pyo|1587)
[6] [Nov 04 10:19:30] [ event processing gui_startup ] Process startet, pid: 2464 (Windows.pyo|1590)
[6] [Nov 04 10:19:30] [ event processing gui_startup ] Session id set to 1 (EventProcessing.pyo|173)
[6] [Nov 04 10:19:31] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:31] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:31] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:31] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:31] [ event generator wait_for_gui ] client connection made (Message.pyo|447)
[6] [Nov 04 10:19:32] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:32] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:32] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:32] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:33] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:33] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:33] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:33] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:33] [ event processing gui_startup ] User is allowed to cancel connection after 30 seconds (EventProcessing.pyo|131)
[6] [Nov 04 10:19:33] [ event processing gui_startup ] Starting ServiceConnectionThread, timeout is 30 seconds (OpsiService.pyo|160)
[5] [Nov 04 10:19:33] [ service connection ] Connecting to config server 'https://opsiserver0.domain.de:4447/rpc' #1 (OpsiService.pyo|313)
[6] [Nov 04 10:19:34] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:34] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:34] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:34] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:35] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:35] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:35] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:35] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:36] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:36] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:36] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:36] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:37] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:37] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:37] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:37] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:38] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:38] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:38] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:38] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:39] [ opsiclientd ] Traceback: (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 115 in 'process' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 674 in '_request' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 475 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 910 in 'request' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 947 in '_send_request' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 904 in 'endheaders' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 776 in '_send_output' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 735 in 'send' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 1108 in 'connect' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] line 500 in 'create_connection' in file 'socket.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:39] [ opsiclientd ] ==>>> Failed to process method 'backend_getInterface': [Errno 11004] getaddrinfo failed (JSONRPC.pyo|119)
[3] [Nov 04 10:19:39] [ service connection ] Failed to connect to config server 'https://opsiserver0.domain.de:4447/rpc': [Errno 11004] getaddrinfo failed (OpsiService.pyo|345)
[6] [Nov 04 10:19:39] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:39] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:39] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:39] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:40] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:40] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:40] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:40] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:41] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:41] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:41] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:41] [ control pipe ] Got result (JsonRpc.pyo|133)
[5] [Nov 04 10:19:42] [ service connection ] Connecting to config server 'https://opsiserver0.domain.de:4447/rpc' #2 (OpsiService.pyo|313)
[6] [Nov 04 10:19:42] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:42] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:42] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:42] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:43] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:43] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:43] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:43] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:44] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:44] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:44] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:44] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:45] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:45] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:45] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:45] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:46] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:46] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:46] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:46] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:47] [ control pipe ] Traceback: (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 115 in 'process' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 674 in '_request' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 475 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 910 in 'request' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 947 in '_send_request' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 904 in 'endheaders' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 776 in '_send_output' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 735 in 'send' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 1108 in 'connect' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] line 500 in 'create_connection' in file 'socket.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:47] [ control pipe ] ==>>> Failed to process method 'backend_getInterface': [Errno 11004] getaddrinfo failed (JSONRPC.pyo|119)
[3] [Nov 04 10:19:47] [ service connection ] Failed to connect to config server 'https://opsiserver0.domain.de:4447/rpc': [Errno 11004] getaddrinfo failed (OpsiService.pyo|345)
[6] [Nov 04 10:19:47] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:47] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:47] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:47] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:48] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:48] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:48] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:48] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:49] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:49] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:49] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:49] [ control pipe ] Got result (JsonRpc.pyo|133)
[5] [Nov 04 10:19:50] [ service connection ] Connecting to config server 'https://opsiserver0.domain.de:4447/rpc' #3 (OpsiService.pyo|313)
[5] [Nov 04 10:19:50] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:50] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:50] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:50] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[6] [Nov 04 10:19:51] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:51] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:51] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:51] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:52] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:52] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:52] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:52] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:53] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:53] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:53] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:53] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:54] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:54] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:54] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:54] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:55] [ control pipe ] Traceback: (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 115 in 'process' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 674 in '_request' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 475 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 910 in 'request' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 947 in '_send_request' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 904 in 'endheaders' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 776 in '_send_output' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 735 in 'send' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 1108 in 'connect' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] line 500 in 'create_connection' in file 'socket.pyo' (Logger.pyo|767)
[6] [Nov 04 10:19:55] [ control pipe ] ==>>> Failed to process method 'backend_getInterface': [Errno 11004] getaddrinfo failed (JSONRPC.pyo|119)
[3] [Nov 04 10:19:55] [ service connection ] Failed to connect to config server 'https://opsiserver0.domain.de:4447/rpc': [Errno 11004] getaddrinfo failed (OpsiService.pyo|345)
[6] [Nov 04 10:19:55] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:55] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:55] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:55] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:56] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:56] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:56] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:56] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:57] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:57] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:57] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:57] [ control pipe ] Got result (JsonRpc.pyo|133)
[5] [Nov 04 10:19:58] [ service connection ] Connecting to config server 'https://opsiserver0.domain.de:4447/rpc' #4 (OpsiService.pyo|313)
[6] [Nov 04 10:19:58] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:58] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:58] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:58] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:19:59] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:19:59] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:19:59] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:19:59] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:20:00] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:20:00] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:20:00] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:20:00] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:20:01] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:20:01] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:20:01] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:20:01] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:20:02] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:20:02] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:20:02] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:20:02] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:20:03] [ control pipe ] Traceback: (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 115 in 'process' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 674 in '_request' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 547 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 475 in 'urlopen' in file 'OPSI\Util\HTTP.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 910 in 'request' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 947 in '_send_request' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 904 in 'endheaders' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 776 in '_send_output' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 735 in 'send' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 1108 in 'connect' in file 'httplib.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] line 500 in 'create_connection' in file 'socket.pyo' (Logger.pyo|767)
[6] [Nov 04 10:20:03] [ control pipe ] ==>>> Failed to process method 'backend_getInterface': [Errno 11004] getaddrinfo failed (JSONRPC.pyo|119)
[3] [Nov 04 10:20:03] [ service connection ] Failed to connect to config server 'https://opsiserver0.domain.de:4447/rpc': [Errno 11004] getaddrinfo failed (OpsiService.pyo|345)
[6] [Nov 04 10:20:03] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:20:03] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:20:03] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:20:03] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:20:04] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:20:04] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:20:04] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:20:04] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:20:05] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:20:05] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:20:05] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'True' (ControlPipe.pyo|428)
[6] [Nov 04 10:20:05] [ control pipe ] Got result (JsonRpc.pyo|133)
[3] [Nov 04 10:20:06] [ event processing gui_startup ] Failed to connect to config service 'https://opsiserver0.domain.de:4447/rpc': timed out after 30 seconds (OpsiService.pyo|103)
[5] [Nov 04 10:20:06] [ event processing gui_startup ] Writing log to service (EventProcessing.pyo|257)
[4] [Nov 04 10:20:06] [ event processing gui_startup ] Cannot write log to service: not connected (EventProcessing.pyo|260)
[6] [Nov 04 10:20:06] [ opsiclientd ] shutdownRequested: 0 (Windows.pyo|335)
[6] [Nov 04 10:20:06] [ opsiclientd ] rebootRequested: 0 (Windows.pyo|321)
[5] [Nov 04 10:20:06] [ opsiclientd ] Block login now set to 'False' (Opsiclientd.pyo|109)
[6] [Nov 04 10:20:06] [ opsiclientd ] Terminating block login notifier app (pid 2036) (Opsiclientd.pyo|146)
[6] [Nov 04 10:20:06] [ event processing gui_startup ] Stopping notification server (EventProcessing.pyo|235)
[6] [Nov 04 10:20:06] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Nov 04 10:20:06] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|125)
[5] [Nov 04 10:20:06] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'False' (ControlPipe.pyo|428)
[6] [Nov 04 10:20:06] [ control pipe ] Got result (JsonRpc.pyo|133)
[6] [Nov 04 10:20:08] [ event generator wait_for_gui ] client connection lost (Message.pyo|452)
[6] [Nov 04 10:20:08] [ event processing gui_startup ] Notification server stopped (Message.pyo|640)
[3] [Nov 04 10:20:11] [ event processing gui_startup ] Failed to process event <ocdlib.Events.GUIStartupEvent object at 0x02609D50>: Failed to connect to config service 'https://opsiserver0.domain.de:4447/rpc': timed out after 30 seconds (EventProcessing.pyo|1247)
[2] [Nov 04 10:20:11] [ event processing gui_startup ] Traceback: (Logger.pyo|767)
[2] [Nov 04 10:20:11] [ event processing gui_startup ] line 1181 in 'run' in file 'ocdlib\EventProcessing.pyo' (Logger.pyo|767)
[2] [Nov 04 10:20:11] [ event processing gui_startup ] line 184 in 'connectConfigService' in file 'ocdlib\OpsiService.pyo' (Logger.pyo|767)
[2] [Nov 04 10:20:11] [ event processing gui_startup ] line 156 in 'connectionTimedOut' in file 'ocdlib\EventProcessing.pyo' (Logger.pyo|767)
[2] [Nov 04 10:20:11] [ event processing gui_startup ] line 104 in 'connectionTimedOut' in file 'ocdlib\OpsiService.pyo' (Logger.pyo|767)
[2] [Nov 04 10:20:11] [ event processing gui_startup ] ==>>> Failed to connect to config service 'https://opsiserver0.domain.de:4447/rpc': timed out after 30 seconds (EventProcessing.pyo|1248)
[5] [Nov 04 10:20:11] [ opsiclientd ] Block login now set to 'False' (Opsiclientd.pyo|109)
[5] [Nov 04 10:20:11] [ event processing gui_startup ] ============= EventProcessingThread for event 'gui_startup' ended ============= (EventProcessing.pyo|1257)
[5] [Nov 04 10:20:11] [ opsiclientd ] Done processing event '<ocdlib.Events.GUIStartupEvent object at 0x02609D50>' (Opsiclientd.pyo|419)
Ich dachte das der Patch von Boris (wenn zwei angegeben sind) den als client.configserver nimmt, den er erreichen kann?