Hallo Gemeinde,
ich habe heute ein Problem bekommen, nach dem ich einen Festplattenfehler hatte.
Soweit laüft wieder alles, bis auf die Netboot-Produkte.Das Bootimage wird gezogen und
geladen. Die Netzwerkadresse wird zugewiesen,dann bleibt er hängen (opsi config server : /prc).
Danach läuft er in einen Timeout (no Connection to /rpc).Wenn ich von CD boot funktioniert es und
beim Screen steht jetzt die IP vom Server (opsi config server: 192.168.1.1).Ich habe leider nicht darauf
geachtet, ob früher beim booten über das Netzwerk auch die " IP" stand.
Hat jemand auch das Problem schon mal gehabt?
Wie gesagt, es ist kein Fehler von der Opsi-Software.Die funktionierte bis zum Ausfall Super.
Gruss Thomas
[gelöst] Problem mit Netboot-Produkten
-
- Beiträge: 67
- Registriert: 06 Jul 2008, 10:10
[gelöst] Problem mit Netboot-Produkten
Zuletzt geändert von thomask3006 am 06 Jun 2011, 13:25, insgesamt 1-mal geändert.
Re: Problem mit Netboot-Produkten
Hi,
evtl das bootimage Paket neu installieren.
Wenn das nicht hilft das log des bootimages posten.
(Im zweifelsfall im opsi-Handbuch nachlesen wo es zufinden ist....)
gruss
d.oertel
evtl das bootimage Paket neu installieren.
Wenn das nicht hilft das log des bootimages posten.
(Im zweifelsfall im opsi-Handbuch nachlesen wo es zufinden ist....)
gruss
d.oertel
opsi support - uib gmbh
For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org
For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org
-
- Beiträge: 67
- Registriert: 06 Jul 2008, 10:10
Re: Problem mit Netboot-Produkten
Hallo Herr Oertel,
ich habe das Bootimage neu installiert, leider ohne Erfolg. ("Connection to service '/rpc' failed: Opsi timeout error:
Timed out after 30 seconds ([Errno 1031] Software caused connection abort)" ).Das Netboot_produkt "memtest86" funktioniert. Leider gibt es keine Logdatei nach den 27.05.2011 mehr im "/var/log/opsi/bootimage".Die
Netboot-Produkte habe ich auch neu installiert, ohne Erfolg.
Gruß Thomas
ich habe das Bootimage neu installiert, leider ohne Erfolg. ("Connection to service '/rpc' failed: Opsi timeout error:
Timed out after 30 seconds ([Errno 1031] Software caused connection abort)" ).Das Netboot_produkt "memtest86" funktioniert. Leider gibt es keine Logdatei nach den 27.05.2011 mehr im "/var/log/opsi/bootimage".Die
Netboot-Produkte habe ich auch neu installiert, ohne Erfolg.
Gruß Thomas
Re: Problem mit Netboot-Produkten
Hi,
log direkt vom bootimage holen wie im Handbuch beschrieben....
gruss
d.oertel
log direkt vom bootimage holen wie im Handbuch beschrieben....
gruss
d.oertel
opsi support - uib gmbh
For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org
For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org
-
- Beiträge: 67
- Registriert: 06 Jul 2008, 10:10
Re: Problem mit Netboot-Produkten
Hallo Herr Oertel,
anbei ein Auszug der Logdatei vom Client.Ich hoffe, das ist so in Ordnung.
6] [Mai 31 14:41:43] DHCP result for device eth0:
{
"domain" : "edu.de",
"network" : "10.65.179.0",
"nameservers" : "10.64.1.50",
"ip" : "10.65.179.73",
"netmask" : "255.255.255.128",
"broadcast" : "10.65.179.127",
"nextserver" : "10.65.179.14",
"bootfile" : "/tftpboot/linux/pxelinux.0",
"gateways" : "10.65.179.1",
"renewaltime" : "Wed",
"expirationtime" : "Wed",
"bootserver" : "10.65.179.7"
} (master.py|719)
[6] [Mai 31 14:41:43] Executing: /sbin/ifconfig eth0 (Posix.py|610)
[6] [Mai 31 14:41:43] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mai 31 14:41:43] >>> eth0 Link encap:Ethernet HWaddr 00:1d:09:07:2a:bb (Posix.py|688)
[7] [Mai 31 14:41:43] >>> inet addr:10.65.179.73 Bcast:10.65.179.127 Mask:255.255.255.128 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> collisions:0 txqueuelen:1000 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) (Posix.py|688)
[7] [Mai 31 14:41:43] >>> Interrupt:16 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> (Posix.py|688)
[7] [Mai 31 14:41:43] Exit code: 0 (Posix.py|695)
[6] [Mai 31 14:41:43] Executing: /sbin/ip route (Posix.py|610)
[6] [Mai 31 14:41:43] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mai 31 14:41:43] >>> 10.65.179.0/25 dev eth0 proto kernel scope link src 10.65.179.73 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> default via 10.65.179.1 dev eth0 (Posix.py|688)
[7] [Mai 31 14:41:43] Exit code: 0 (Posix.py|695)
[6] [Mai 31 14:41:43] Current network config: (master.py|751)
[6] [Mai 31 14:41:43] device : eth0 (master.py|752)
[6] [Mai 31 14:41:43] hardwareAddress : 00:1d:09:07:2a:bb (master.py|753)
[6] [Mai 31 14:41:43] ipaddress : 10.65.179.73 (master.py|754)
[6] [Mai 31 14:41:43] netmask : 255.255.255.128 (master.py|755)
[6] [Mai 31 14:41:43] gateway : 10.65.179.1 (master.py|756)
[6] [Mai 31 14:41:43] nameserver : 10.64.1.50 (master.py|757)
[6] [Mai 31 14:41:43] hostname : test (master.py|758)
[6] [Mai 31 14:41:43] domain : edu.de (master.py|759)
[6] [Mai 31 14:41:43] nextserver : /rpc (master.py|760) <<<<<<<<<<<<<<-----------------------------?????
[6] [Mai 31 14:41:43] Found ethernet device: 'eth0' (Posix.py|349)
[6] [Mai 31 14:41:43] Executing: /sbin/ifconfig eth0 (Posix.py|610)
[6] [Mai 31 14:41:43] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mai 31 14:41:43] >>> eth0 Link encap:Ethernet HWaddr 00:1d:09:07:2a:bb (Posix.py|688)
[7] [Mai 31 14:41:43] >>> inet addr:10.65.179.73 Bcast:10.65.179.127 Mask:255.255.255.128 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> collisions:0 txqueuelen:1000 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) (Posix.py|688)
[7] [Mai 31 14:41:43] >>> Interrupt:16 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> (Posix.py|688)
[7] [Mai 31 14:41:43] Exit code: 0 (Posix.py|695)
[6] [Mai 31 14:41:43] Executing: /sbin/ip route (Posix.py|610)
[6] [Mai 31 14:41:43] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mai 31 14:41:43] >>> 10.65.179.0/25 dev eth0 proto kernel scope link src 10.65.179.73 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> default via 10.65.179.1 dev eth0 (Posix.py|688)
[7] [Mai 31 14:41:43] Exit code: 0 (Posix.py|695)
[6] [Mai 31 14:41:43] Default network interface found: eth0 (Posix.py|424)
[6] [Mai 31 14:41:43] Executing: /sbin/ifconfig eth0 (Posix.py|610)
[6] [Mai 31 14:41:43] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mai 31 14:41:43] >>> eth0 Link encap:Ethernet HWaddr 00:1d:09:07:2a:bb (Posix.py|688)
[7] [Mai 31 14:41:43] >>> inet addr:10.65.179.73 Bcast:10.65.179.127 Mask:255.255.255.128 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> collisions:0 txqueuelen:1000 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) (Posix.py|688)
[7] [Mai 31 14:41:43] >>> Interrupt:16 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> (Posix.py|688)
[7] [Mai 31 14:41:43] Exit code: 0 (Posix.py|695)
[6] [Mai 31 14:41:43] Executing: /sbin/ip route (Posix.py|610)
[6] [Mai 31 14:41:43] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mai 31 14:41:43] >>> 10.65.179.0/25 dev eth0 proto kernel scope link src 10.65.179.73 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> default via 10.65.179.1 dev eth0 (Posix.py|688)
[7] [Mai 31 14:41:43] Exit code: 0 (Posix.py|695)
[6] [Mai 31 14:41:43] Using FQDN 'test.edu.de' (master.py|957)
[6] [Mai 31 14:41:43] Creating JSONRPCBackend instance (try #1) (master.py|998)
[7] [Mai 31 14:41:43] Executing jsonrpc method 'backend_getInterface' on host (JSONRPC.py|103)
[6] [Mai 31 14:41:43] Starting new HTTPS connection (0) to :4447 (HTTP.py|418)
[7] [Mai 31 14:41:43] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:44] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:44] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:45] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:45] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:46] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:46] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:47] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:47] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:48] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:48] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:49] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:49] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:50] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:50] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:51] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:51] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:52] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:52] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:53] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:53] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:54] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:54] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:55] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:55] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:56] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:56] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:57] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:57] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:58] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:58] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:59] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:59] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:00] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:00] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:01] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:01] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:02] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:03] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:03] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:04] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:04] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:05] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:05] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:06] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:06] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:07] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:07] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:08] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:08] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:09] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:09] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:10] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:10] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:11] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:11] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:12] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:12] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:13] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:13] [Errno 103] Software caused connection abort (HTTP.py|76)
[6] [Mai 31 14:42:14] Traceback: (Logger.py|721)
[6] [Mai 31 14:42:14] line 107 in 'process' in file '/usr/lib/pymodules/python2.6/OPSI/Backend/JSONRPC.py' (Logger.py|721)
[6] [Mai 31 14:42:14] line 610 in '_request' in file '/usr/lib/pymodules/python2.6/OPSI/Backend/JSONRPC.py' (Logger.py|721)
[6] [Mai 31 14:42:14] line 326 in 'urlopen' in file '/usr/lib/pymodules/python2.6/OPSI/Util/HTTP.py' (Logger.py|721)
[6] [Mai 31 14:42:14] line 251 in '_get_conn' in file '/usr/lib/pymodules/python2.6/OPSI/Util/HTTP.py' (Logger.py|721)
[6] [Mai 31 14:42:14] line 420 in '_new_conn' in file '/usr/lib/pymodules/python2.6/OPSI/Util/HTTP.py' (Logger.py|721)
[6] [Mai 31 14:42:14] line 87 in 'non_blocking_connect_https' in file '/usr/lib/pymodules/python2.6/OPSI/Util/HTTP.py' (Logger.py|721)
[6] [Mai 31 14:42:14] line 72 in 'non_blocking_connect_http' in file '/usr/lib/pymodules/python2.6/OPSI/Util/HTTP.py' (Logger.py|721)
[6] [Mai 31 14:42:14] ==>>> Failed to process method 'backend_getInterface': Opsi timeout error: Timed out after 30 seconds ([Errno 103] Software caused connection abort) (JSONRPC.py|111)
[3] [Mai 31 14:42:14] Connection to service '/rpc' failed: Opsi timeout error: Timed out after 30 seconds ([Errno 103] Software caused connection abort) (master.py|1010)
[6] [Mai 31 14:42:16] Creating JSONRPCBackend instance (try #2) (master.py|998)
[7] [Mai 31 14:42:16] Executing jsonrpc method 'backend_getInterface' on host (JSONRPC.py|103)
[6] [Mai 31 14:42:16] Starting new HTTPS connection (-1) to :4447 (HTTP.py|418)
[7] [Mai 31 14:42:16] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:16] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:17] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:17] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:18] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:18] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:19] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:19] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:20] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:20] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:21] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:21] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:22] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:22] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:23] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:23] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:24] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:24] [Errno 103] Software caused connection abort (HTTP.py|76)
Was mich wundert, ist warum bei Nextserver: /rpc steht und keine IP?
Gruß Thomas
anbei ein Auszug der Logdatei vom Client.Ich hoffe, das ist so in Ordnung.
6] [Mai 31 14:41:43] DHCP result for device eth0:
{
"domain" : "edu.de",
"network" : "10.65.179.0",
"nameservers" : "10.64.1.50",
"ip" : "10.65.179.73",
"netmask" : "255.255.255.128",
"broadcast" : "10.65.179.127",
"nextserver" : "10.65.179.14",
"bootfile" : "/tftpboot/linux/pxelinux.0",
"gateways" : "10.65.179.1",
"renewaltime" : "Wed",
"expirationtime" : "Wed",
"bootserver" : "10.65.179.7"
} (master.py|719)
[6] [Mai 31 14:41:43] Executing: /sbin/ifconfig eth0 (Posix.py|610)
[6] [Mai 31 14:41:43] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mai 31 14:41:43] >>> eth0 Link encap:Ethernet HWaddr 00:1d:09:07:2a:bb (Posix.py|688)
[7] [Mai 31 14:41:43] >>> inet addr:10.65.179.73 Bcast:10.65.179.127 Mask:255.255.255.128 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> collisions:0 txqueuelen:1000 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) (Posix.py|688)
[7] [Mai 31 14:41:43] >>> Interrupt:16 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> (Posix.py|688)
[7] [Mai 31 14:41:43] Exit code: 0 (Posix.py|695)
[6] [Mai 31 14:41:43] Executing: /sbin/ip route (Posix.py|610)
[6] [Mai 31 14:41:43] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mai 31 14:41:43] >>> 10.65.179.0/25 dev eth0 proto kernel scope link src 10.65.179.73 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> default via 10.65.179.1 dev eth0 (Posix.py|688)
[7] [Mai 31 14:41:43] Exit code: 0 (Posix.py|695)
[6] [Mai 31 14:41:43] Current network config: (master.py|751)
[6] [Mai 31 14:41:43] device : eth0 (master.py|752)
[6] [Mai 31 14:41:43] hardwareAddress : 00:1d:09:07:2a:bb (master.py|753)
[6] [Mai 31 14:41:43] ipaddress : 10.65.179.73 (master.py|754)
[6] [Mai 31 14:41:43] netmask : 255.255.255.128 (master.py|755)
[6] [Mai 31 14:41:43] gateway : 10.65.179.1 (master.py|756)
[6] [Mai 31 14:41:43] nameserver : 10.64.1.50 (master.py|757)
[6] [Mai 31 14:41:43] hostname : test (master.py|758)
[6] [Mai 31 14:41:43] domain : edu.de (master.py|759)
[6] [Mai 31 14:41:43] nextserver : /rpc (master.py|760) <<<<<<<<<<<<<<-----------------------------?????
[6] [Mai 31 14:41:43] Found ethernet device: 'eth0' (Posix.py|349)
[6] [Mai 31 14:41:43] Executing: /sbin/ifconfig eth0 (Posix.py|610)
[6] [Mai 31 14:41:43] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mai 31 14:41:43] >>> eth0 Link encap:Ethernet HWaddr 00:1d:09:07:2a:bb (Posix.py|688)
[7] [Mai 31 14:41:43] >>> inet addr:10.65.179.73 Bcast:10.65.179.127 Mask:255.255.255.128 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> collisions:0 txqueuelen:1000 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) (Posix.py|688)
[7] [Mai 31 14:41:43] >>> Interrupt:16 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> (Posix.py|688)
[7] [Mai 31 14:41:43] Exit code: 0 (Posix.py|695)
[6] [Mai 31 14:41:43] Executing: /sbin/ip route (Posix.py|610)
[6] [Mai 31 14:41:43] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mai 31 14:41:43] >>> 10.65.179.0/25 dev eth0 proto kernel scope link src 10.65.179.73 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> default via 10.65.179.1 dev eth0 (Posix.py|688)
[7] [Mai 31 14:41:43] Exit code: 0 (Posix.py|695)
[6] [Mai 31 14:41:43] Default network interface found: eth0 (Posix.py|424)
[6] [Mai 31 14:41:43] Executing: /sbin/ifconfig eth0 (Posix.py|610)
[6] [Mai 31 14:41:43] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mai 31 14:41:43] >>> eth0 Link encap:Ethernet HWaddr 00:1d:09:07:2a:bb (Posix.py|688)
[7] [Mai 31 14:41:43] >>> inet addr:10.65.179.73 Bcast:10.65.179.127 Mask:255.255.255.128 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> collisions:0 txqueuelen:1000 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) (Posix.py|688)
[7] [Mai 31 14:41:43] >>> Interrupt:16 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> (Posix.py|688)
[7] [Mai 31 14:41:43] Exit code: 0 (Posix.py|695)
[6] [Mai 31 14:41:43] Executing: /sbin/ip route (Posix.py|610)
[6] [Mai 31 14:41:43] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mai 31 14:41:43] >>> 10.65.179.0/25 dev eth0 proto kernel scope link src 10.65.179.73 (Posix.py|688)
[7] [Mai 31 14:41:43] >>> default via 10.65.179.1 dev eth0 (Posix.py|688)
[7] [Mai 31 14:41:43] Exit code: 0 (Posix.py|695)
[6] [Mai 31 14:41:43] Using FQDN 'test.edu.de' (master.py|957)
[6] [Mai 31 14:41:43] Creating JSONRPCBackend instance (try #1) (master.py|998)
[7] [Mai 31 14:41:43] Executing jsonrpc method 'backend_getInterface' on host (JSONRPC.py|103)
[6] [Mai 31 14:41:43] Starting new HTTPS connection (0) to :4447 (HTTP.py|418)
[7] [Mai 31 14:41:43] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:44] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:44] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:45] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:45] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:46] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:46] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:47] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:47] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:48] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:48] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:49] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:49] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:50] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:50] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:51] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:51] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:52] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:52] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:53] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:53] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:54] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:54] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:55] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:55] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:56] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:56] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:57] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:57] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:58] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:58] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:41:59] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:41:59] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:00] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:00] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:01] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:01] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:02] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:03] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:03] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:04] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:04] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:05] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:05] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:06] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:06] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:07] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:07] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:08] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:08] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:09] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:09] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:10] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:10] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:11] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:11] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:12] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:12] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:13] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:13] [Errno 103] Software caused connection abort (HTTP.py|76)
[6] [Mai 31 14:42:14] Traceback: (Logger.py|721)
[6] [Mai 31 14:42:14] line 107 in 'process' in file '/usr/lib/pymodules/python2.6/OPSI/Backend/JSONRPC.py' (Logger.py|721)
[6] [Mai 31 14:42:14] line 610 in '_request' in file '/usr/lib/pymodules/python2.6/OPSI/Backend/JSONRPC.py' (Logger.py|721)
[6] [Mai 31 14:42:14] line 326 in 'urlopen' in file '/usr/lib/pymodules/python2.6/OPSI/Util/HTTP.py' (Logger.py|721)
[6] [Mai 31 14:42:14] line 251 in '_get_conn' in file '/usr/lib/pymodules/python2.6/OPSI/Util/HTTP.py' (Logger.py|721)
[6] [Mai 31 14:42:14] line 420 in '_new_conn' in file '/usr/lib/pymodules/python2.6/OPSI/Util/HTTP.py' (Logger.py|721)
[6] [Mai 31 14:42:14] line 87 in 'non_blocking_connect_https' in file '/usr/lib/pymodules/python2.6/OPSI/Util/HTTP.py' (Logger.py|721)
[6] [Mai 31 14:42:14] line 72 in 'non_blocking_connect_http' in file '/usr/lib/pymodules/python2.6/OPSI/Util/HTTP.py' (Logger.py|721)
[6] [Mai 31 14:42:14] ==>>> Failed to process method 'backend_getInterface': Opsi timeout error: Timed out after 30 seconds ([Errno 103] Software caused connection abort) (JSONRPC.py|111)
[3] [Mai 31 14:42:14] Connection to service '/rpc' failed: Opsi timeout error: Timed out after 30 seconds ([Errno 103] Software caused connection abort) (master.py|1010)
[6] [Mai 31 14:42:16] Creating JSONRPCBackend instance (try #2) (master.py|998)
[7] [Mai 31 14:42:16] Executing jsonrpc method 'backend_getInterface' on host (JSONRPC.py|103)
[6] [Mai 31 14:42:16] Starting new HTTPS connection (-1) to :4447 (HTTP.py|418)
[7] [Mai 31 14:42:16] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:16] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:17] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:17] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:18] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:18] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:19] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:19] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:20] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:20] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:21] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:21] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:22] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:22] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:23] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:23] [Errno 103] Software caused connection abort (HTTP.py|76)
[7] [Mai 31 14:42:24] [Errno 111] Connection refused (HTTP.py|76)
[7] [Mai 31 14:42:24] [Errno 103] Software caused connection abort (HTTP.py|76)
Was mich wundert, ist warum bei Nextserver: /rpc steht und keine IP?
Gruß Thomas
-
- Beiträge: 67
- Registriert: 06 Jul 2008, 10:10
Re: Problem mit Netboot-Produkten
Moin,
hat keiner einen Tipp?
Gruss Thomas
hat keiner einen Tipp?
Gruss Thomas
Re: Problem mit Netboot-Produkten
Hi,
mal im configed / Serverkonfiguration
nach dem Parameter
clientconfig.configserver.url
schauen
da sollte sowas drinstehen wie
https://10.65.179.14:4447/rpc
sonst gehts nicht
gruss
d.oertel
mal im configed / Serverkonfiguration
nach dem Parameter
clientconfig.configserver.url
schauen
da sollte sowas drinstehen wie
https://10.65.179.14:4447/rpc
sonst gehts nicht
gruss
d.oertel
opsi support - uib gmbh
For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org
For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org
-
- Beiträge: 67
- Registriert: 06 Jul 2008, 10:10
[gelöst] Problem mit Netboot-Produkten
Hallo ,
in der config.ini fehlten die Einträge. Ich habe die Config.ini aus der Sicherung gzurückgesichert und nun
funktioniert der Opsi wieder. Danke für den Tipp.
Gruss Thomas
in der config.ini fehlten die Einträge. Ich habe die Config.ini aus der Sicherung gzurückgesichert und nun
funktioniert der Opsi wieder. Danke für den Tipp.
Gruss Thomas