Fehlermeldung: 'ascii' codec can't decode byte 0xfc in pos.

Antworten
eer
Beiträge: 1
Registriert: 13 Sep 2011, 11:31

Fehlermeldung: 'ascii' codec can't decode byte 0xfc in pos.

Beitrag von eer »

Hallo zusammen,

ich bekomme beim Hochfahren des Rechners folgende Fehlermeldung während der opsi-client-agent sich mit dem Server verbinden will:

'ascii' codec can't decode byte 0xfc in position 61: ordinal not in range(128)
Ein Socketvorgang bezog sich auf ein nicht verf\xfcgbares Netzwerk'


Daraufhin startet der Agent einen weiteren Verbindungsversuch, der wieder scheitert.
Erst der 3. oder 4. Verbindungsversuch ist erfolgreich.


Die Logfile spuckt folgende Informationen aus:

Code: Alles auswählen


[5] [Nov 23 10:38:57] [ service connection            ] Connecting to config server 'https://192.168.30.18:4447/rpc' #1   (OpsiService.pyo|298)
[6] [Nov 23 10:39:02] [ opsiclientd                   ] Traceback:   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 108 in 'process' in file 'OPSI\Backend\JSONRPC.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 635 in '_request' in file 'OPSI\Backend\JSONRPC.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:02] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:03] [ opsiclientd                   ]      line 474 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:03] [ opsiclientd                   ]      line 402 in 'urlopen' in file 'OPSI\Util\HTTP.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:03] [ opsiclientd                   ]      line 910 in 'request' in file 'httplib.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:03] [ opsiclientd                   ]      line 947 in '_send_request' in file 'httplib.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:03] [ opsiclientd                   ]      line 904 in 'endheaders' in file 'httplib.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:03] [ opsiclientd                   ]      line 776 in '_send_output' in file 'httplib.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:03] [ opsiclientd                   ]      line 735 in 'send' in file 'httplib.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:03] [ opsiclientd                   ]      line 1108 in 'connect' in file 'httplib.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:03] [ opsiclientd                   ]      line 514 in 'create_connection' in file 'socket.pyo'   (Logger.pyo|742)
[6] [Nov 23 10:39:03] [ opsiclientd                   ]      ==>>> Failed to process method 'backend_getInterface': error(10051, 'Ein Socketvorgang bezog sich auf ein nicht verf\xfcgbares Netzwerk')   (JSONRPC.pyo|112)
[3] [Nov 23 10:39:03] [ service connection            ] Failed to connect to config server 'https://192.168.30.18:4447/rpc': 'ascii' codec can't decode byte 0xfc in position 61: ordinal not in range(128)   (OpsiService.pyo|330)

Versionen der OPSI-Pakete:

Code: Alles auswählen

root@OPSI01:/home/support# dpkg -l | grep opsi
ii  opsi-atftpd                           0.7.dfsg-1.4                                    advanced TFTP server - opsi version with pcre, fifo and max-blks
ii  opsi-configed                         4.0.1.16-1                                      OPSI config editor
ii  opsi-depotserver                      4.0.1.10-1                                      opsi depotserver configuration package
ii  opsi-linux-bootimage                  20110926-1                                      opsi linux bootimage
ii  opsi-utils                            4.0.1.14-1                                      opsi utils
ii  opsiconfd                             4.0.1.9-4                                       opsi configuration service
ii  opsipxeconfd                          4.0.1.4-1                                       opsi pxe configuration daemon
ii  python-opsi                           4.0.1.32-1                                      opsi python library

Der Server ist ein Xubuntu 10.04

Da die Installation nach dem 3. bzw. 4. Verbindungsversuch normal durchlaufen, ist es kein kritisches aber lästiges Problem.
Komischerweise tritt dieses Problem nicht auf allen Clients auf.
Die meisten Clients (ca. 25 Stk.) laufen ohne Probleme.

Vielleicht hatte schon jemand ein ähnliches Problem und kann mir einen Lösungsansatz bieten.
Ich bin für jeden Tipp dankbar :)
marconb
Beiträge: 1
Registriert: 16 Jun 2014, 10:13

Re: Fehlermeldung: 'ascii' codec can't decode byte 0xfc in p

Beitrag von marconb »

Guten Morgen.


Konntest du eine Lösung für dein Problem finden? Steh vor dem gleichen Problem.
Benutzeravatar
ueluekmen
uib-Team
Beiträge: 1940
Registriert: 28 Mai 2008, 10:53

Re: Fehlermeldung: 'ascii' codec can't decode byte 0xfc in p

Beitrag von ueluekmen »

Hi,

hier laufen einige Dinge zusammen.

1.) Der ascii Fehler kommt von der eigentlichen Fehlermeldung. Diese ist in deutsch lokalisiert und enthält ein ü, was nicht sauber abgefangen wird. Microsoft lokalisiert alles, da sind die sehr gründlich.
2.) Der eigentliche Fehler ist entscheidend: Ein Socketvorgang bezog sich auf ein nicht verfügbares Netzwerk. Deutet auf ein Netzwerkproblem hin. Der Fehlercode der migeliefert wird besagt: Network is unreachable.
3.) Du nutzt eine veraltete opsi-Version und solltest mal updaten.


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


Antworten