Re: Eisxen stürzt nach Reboot von Eis1 ab
Carsten Weisky <[email protected]>
| Newsgroups | spline.eisxen |
|---|---|
| Organization | spline |
| Message-ID | <[email protected]> |
Am 22.07.2010 15:36, schrieb Michael Sauer: > ## Nachricht vom [email protected]· > ## Ursprung : /spline/eisxen· > >> fli4l, eis1, und eis2 als Domu's >> wenn ich den fli4l oder den Eis1 neu starte, dann hängt sich Eixxen >> auf und muss manuell aus und wieder eingeschaltet werden. Wie kann >> ich mit der Fehlersuche beginnen. > > Steht was verwertbares auf dem Monitor am Xen? > > Cu ..... > > ******************Michael************************* Nach erneutem Ansturz ein Neustart und dann stehen diese Meldungen in den betreffenden Dateien. Vielleicht könnt Ihr damit was anfangen: Auf dem Eisxen: errors: Aug 2 00:00:02 eisxen fcron[7314]: Can't find "/usr/sbin/sendmail". Trying a execlp("sendmail"): No such file or directory Aug 2 00:00:02 eisxen fcron[7314]: Can't exec /usr/sbin/sendmail: No such file or directory Aug 2 10:58:46 eisxen kernel: [ 0.452422] failed to set up cpufreq notifier │ Aug 2 10:58:46 eisxen kernel: [ 0.098852] Successfully initialized TPM backend driver. │ Aug 2 10:58:46 eisxen kernel: [ 5.608996] intel_rng: FWH not detected Aug 2 10:58:47 eisxen xenstored: Checking store ... Aug 2 10:58:47 eisxen xenstored: Checking store complete. Aug 2 10:58:49 eisxen kernel: [ 14.481617] tmpbridge: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature. │ Aug 2 10:59:03 eisxen usbmount[2958]: cannot read from /dev/sdd Aug 2 10:59:03 eisxen usbmount[2959]: cannot read from /dev/sdc Aug 2 10:59:03 eisxen usbmount[2955]: cannot read from /dev/sde Aug 2 10:59:03 eisxen usbmount[2957]: cannot read from /dev/sdf messages: was sagen mir diese Meldungen Aug 2 10:59:54 eisxen kernel: [ 79.533085] PCI: Setting latency timer of device 0000:00:1d.0 to 64 Aug 2 10:59:54 eisxen kernel: [ 79.533226] pciback 0000:00:1d.0: Driver tried to write to a read-only configuration space field at offset 0xc0, size 2. This may be harmless, but if you have problems wit▒ Aug 2 10:59:54 eisxen kernel: [ 79.533228] 1) see permissive attribute in sysfs Aug 2 10:59:54 eisxen kernel: [ 79.533229] 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci. ▒ │Aug 2 10:59:55 eisxen kernel: [ 79.635631] PCI: Enabling device 0000:00:1d.1 (0000 -> 0001) Aug 2 10:59:55 eisxen kernel: [ 79.635643] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19 Aug 2 10:59:55 eisxen kernel: [ 79.635697] PCI: Setting latency timer of device 0000:00:1d.1 to 64 Aug 2 10:59:55 eisxen kernel: [ 79.635785] pciback 0000:00:1d.1: Driver tried to write to a read-only configuration space field at offset 0xc0, size 2. This may be harmless, but if you have problems wit▒ Aug 2 10:59:55 eisxen kernel: [ 79.635787] 1) see permissive attribute in sysfs Aug 2 10:59:55 eisxen kernel: [ 79.635788] 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci. ▒ Aug 2 10:59:55 eisxen kernel: [ 79.739641] PCI: Enabling device 0000:00:1d.2 (0000 -> 0001) Aug 2 10:59:55 eisxen kernel: [ 79.739652] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 20 Aug 2 10:59:55 eisxen kernel: [ 79.739976] PCI: Setting latency timer of device 0000:00:1d.2 to 64 Aug 2 10:59:55 eisxen kernel: [ 79.740074] pciback 0000:00:1d.2: Driver tried to write to a read-only configuration space field at offset 0xc0, size 2. This may be harmless, but if you have problems wit▒ Aug 2 10:59:55 eisxen kernel: [ 79.740076] 1) see permissive attribute in sysfs Aug 2 10:59:55 eisxen kernel: [ 79.740077] 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci. ▒ Aug 2 10:59:55 eisxen kernel: [ 79.843576] PCI: Enabling device 0000:00:1d.3 (0000 -> 0001) Aug 2 10:59:55 eisxen kernel: [ 79.843585] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 16 Aug 2 10:59:55 eisxen kernel: [ 79.843639] PCI: Setting latency timer of device 0000:00:1d.3 to 64 Aug 2 10:59:55 eisxen kernel: [ 79.843719] pciback 0000:00:1d.3: Driver tried to write to a read-only configuration space field at offset 0xc0, size 2. This may be harmless, but if you have problems wit▒ Aug 2 10:59:55 eisxen kernel: [ 79.843721] 1) see permissive attribute in sysfs Aug 2 10:59:55 eisxen kernel: [ 79.843721] 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci. ▒ Aug 2 10:59:55 eisxen kernel: [ 79.947742] PCI: Enabling device 0000:00:1d.7 (0000 -> 0002) Aug 2 10:59:55 eisxen kernel: [ 79.947750] ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 18 Aug 2 10:59:55 eisxen kernel: [ 79.947812] PCI: Setting latency timer of device 0000:00:1d.7 to 64 auf den Eis2: errors│Aug 2 11:00:07 server kernel: [ 0.174604] failed to set up cpufreq notifier Aug 2 11:00:07 server kernel: [ 0.195309] PCI: Fatal: No config space access function found Aug 2 11:00:07 server kernel: [ 0.263890] Successfully initialized TPM backend driver. Aug 2 11:00:07 server kernel: [ 0.291764] rtc: IRQ 8 is not free. Aug 2 11:00:07 server kernel: [ 0.293154] i8042.c: No controller found. Aug 2 11:00:07 server kernel: [ 1.841228] Aug 2 11:00:07 server kernel: [ 1.841230] *************************************************************** Aug 2 11:00:07 server kernel: [ 1.841231] *************************************************************** Aug 2 11:00:07 server kernel: [ 1.841233] ** WARNING: Currently emulating unsupported memory accesses ** Aug 2 11:00:07 server kernel: [ 1.841234] ** in /lib/tls glibc libraries. The emulation is ** Aug 2 11:00:07 server kernel: [ 1.841235] ** slow. To ensure full performance you should ** Aug 2 11:00:07 server kernel: [ 1.841237] ** install a 'xen-friendly' (nosegneg) version of ** Aug 2 11:00:07 server kernel: [ 1.841238] ** the library, or disable tls support by executing ** Aug 2 11:00:07 server kernel: [ 1.841239] ** the following as root: ** Aug 2 11:00:07 server kernel: [ 1.841240] ** mv /lib/tls /lib/tls.disabled ** Aug 2 11:00:07 server kernel: [ 1.841242] ** Offending process: init (pid=883) ** Aug 2 11:00:07 server kernel: [ 1.841243] *************************************************************** Aug 2 11:00:07 server kernel: [ 1.841245] *************************************************************** Aug 2 11:00:07 server kernel: [ 1.841246] Aug 2 11:00:18 server mini_httpd[2903]: bind 0.0.0.0 - Address already in use Aug 2 11:00:25 server fcrontab[3277]: user "root.tmp" is not in passwd file. Aborting.: Success Aug 2 11:00:29 server usbmount[2425]: cannot read from /dev/sdd Aug 2 11:00:29 server usbmount[2424]: cannot read from /dev/sda Aug 2 11:00:30 server usbmount[2429]: cannot read from /dev/sdc Aug 2 11:00:30 server usbmount[2423]: cannot read from /dev/sdb