Könnte das bitte jemand übersetzen?

[Ebbi]

Moin,

es geht um Solaris 10 U5.

Die Kiste fährt hoch, dann tut sich eine Zeit lang nichts mehr. ssh funktioniert, aber man kann nur den Benutzernamen eingeben.
Irgendwann kommt die Passwortabfrage und ab da geht alles wie gewohnt.

# dmesg

Code: [Auswählen]

May 21 11:11:57 fire280r eri: [ID 786680 kern.notice] SUNW,eri0 : 100 Mbps full duplex link up
May 21 11:12:50 fire280r svc.startd[7]: [ID 122153 daemon.warning] svc:/system/power:default: Method or service exit timed out.  Killing contract 27.
May 21 11:12:50 fire280r svc.startd[7]: [ID 636263 daemon.warning] svc:/system/power:default: Method "/lib/svc/method/svc-power start" failed due to signal KILL.
May 21 11:13:50 fire280r svc.startd[7]: [ID 122153 daemon.warning] svc:/system/power:default: Method or service exit timed out.  Killing contract 67.
May 21 11:13:50 fire280r svc.startd[7]: [ID 636263 daemon.warning] svc:/system/power:default: Method "/lib/svc/method/svc-power start" failed due to signal KILL.
May 21 11:14:51 fire280r svc.startd[7]: [ID 122153 daemon.warning] svc:/system/power:default: Method or service exit timed out.  Killing contract 69.
May 21 11:16:56 fire280r last message repeated 124 times
May 21 11:16:57 fire280r svc.startd[7]: [ID 636263 daemon.warning] svc:/system/power:default: Method "/lib/svc/method/svc-power start" failed due to signal KILL.
May 21 11:16:57 fire280r svc.startd[7]: [ID 748625 daemon.error] system/power:default failed: transitioned to maintenance (see 'svcs -xv' for details)


[Ebbi]

Von wegen alles wie gewohnt...

Alles geht unsäglich langsam, die Kiste steht seit 20 Minuten im Bootvorgang und nichts passiert:

Code: [Auswählen]

Rebooting with command: boot
Boot device: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@w2100002037421c83,0:a  File and args:
SunOS Release 5.10 Version Generic_127127-11 64-bit
Copyright 1983-2008 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
TSI: gfxp0 is GFX8P @ 1152x900
WARNING: /pci@8,700000/QLGC,qla@3/fp@0,0/ssd@w500805f300025d11,4 (ssd3):
        Corrupt label; wrong magic number

Hostname: kackspecht
Configuring devices.
SUNW,eri0 : 100 Mbps full duplex link up

Wenn ich mich dann endlich einloggen kann, dauern viele Befehle ewig, z.B. devfsadm -C oder format.

[stiefkind]

Die Kiste fährt hoch, dann tut sich eine Zeit lang nichts mehr. ssh funktioniert, aber man kann nur den Benutzernamen eingeben.
Irgendwann kommt die Passwortabfrage und ab da geht alles wie gewohnt.

Spontan hätte ich gesagt: DNS-Problem. SSH will die IP auflösen, von der du kommst, kann das aber nicht und läuft deswegen in DNS Timeouts.

Wenn ich mich dann endlich einloggen kann, dauern viele Befehle ewig, z.B. devfsadm -C oder format.

Das wiederum klingt eher nach Plattenproblem. Schonmal geschaut, was im /var/adm/messages so drin steht?

wolfgang

[Ebbi]

Spontan hätte ich gesagt: DNS-Problem. SSH will die IP auflösen, von der du kommst, kann das aber nicht und läuft deswegen in DNS Timeouts.

Niemals! Der wird von mir persönlich von Hand gepflegt.

Das wiederum klingt eher nach Plattenproblem. Schonmal geschaut, was im /var/adm/messages so drin steht?

Ja - nichts, bzw. das selbe wie bei dmesg kommt.



Aber IM MOMENT sieht es eher so aus, dass dieses Problem zumindest weg ist.
Ich habe nämlich die Intel Gigabit Karte e1000g ausgebaut und die Kiste ist zügig hochgefahren und führt auch die Befehle wieder ohne Wartezeit aus.

Allerdings erscheint mit fmadm faulty und auf der Console ab und zu der Fehler aus diesem Thread:
http://www.sonnenblen.de/sun_sparc/bisher_unbekannter_hardwarefehler-t5284.0.html

Code: [Auswählen]

SUNW-MSG-ID: PCIEX-8000-5Y, TYPE: Fault, VER: 1, SEVERITY: Critical
EVENT-TIME: Mon May 19 14:57:54 CEST 2008
PLATFORM: SUNW,Sun-Fire-280R, CSN: -, HOSTNAME: fire280r
SOURCE: eft, REV: 1.16
EVENT-ID: 1a988d32-b3bd-4ac2-ccac-b787873962dd
DESC: The transmitting device sent an invalid request.
  Refer to http://sun.com/msg/PCIEX-8000-5Y for more information.
AUTO-RESPONSE: One or more device instances may be disabled

IMPACT: Loss of services provided by the device instances associated with this fault

REC-ACTION: Ensure that the latest drivers and patches are installed. Otherwise schedule a repair procedure to replace the affected device(s).  Use fmdump -v -u <EVENT_ID> to identify the devices or contact Sun for support.


[Ebbi]

Der Hardwarefehler ist weg, aber dieses Problem werde ich nicht los.
Was bedeutet das denn?

Code: [Auswählen]

Jul 21 13:51:26 fire280r svc.startd[7]: [ID 122153 daemon.warning] svc:/system/power:default: Method or service exit timed out.  Killing contract 26.
Jul 21 13:51:26 fire280r svc.startd[7]: [ID 636263 daemon.warning] svc:/system/power:default: Method "/lib/svc/method/svc-power start" failed due to signal KILL.
Jul 21 13:52:27 fire280r svc.startd[7]: [ID 122153 daemon.warning] svc:/system/power:default: Method or service exit timed out.  Killing contract 39.
Jul 21 13:52:27 fire280r svc.startd[7]: [ID 636263 daemon.warning] svc:/system/power:default: Method "/lib/svc/method/svc-power start" failed due to signal KILL.
Jul 21 13:53:27 fire280r svc.startd[7]: [ID 122153 daemon.warning] svc:/system/power:default: Method or service exit timed out.  Killing contract 41.
Jul 21 13:53:27 fire280r svc.startd[7]: [ID 636263 daemon.warning] svc:/system/power:default: Method "/lib/svc/method/svc-power start" failed due to signal KILL.
Jul 21 13:53:27 fire280r svc.startd[7]: [ID 748625 daemon.error] system/power:default failed: transitioned to maintenance (see 'svcs -xv' for details)


[linuxdomination]

Code: [Auswählen]

Jul 21 13:51:26 fire280r svc.startd[7]: [ID 122153 daemon.warning] svc:/system/power:default: Method or service exit timed out.  Killing contract 26.
Jul 21 13:51:26 fire280r svc.startd[7]: [ID 636263 daemon.warning] svc:/system/power:default: Method "/lib/svc/method/svc-power start" failed due to signal KILL.
Jul 21 13:52:27 fire280r svc.startd[7]: [ID 122153 daemon.warning] svc:/system/power:default: Method or service exit timed out.  Killing contract 39.
Jul 21 13:52:27 fire280r svc.startd[7]: [ID 636263 daemon.warning] svc:/system/power:default: Method "/lib/svc/method/svc-power start" failed due to signal KILL.
Jul 21 13:53:27 fire280r svc.startd[7]: [ID 122153 daemon.warning] svc:/system/power:default: Method or service exit timed out.  Killing contract 41.
Jul 21 13:53:27 fire280r svc.startd[7]: [ID 636263 daemon.warning] svc:/system/power:default: Method "/lib/svc/method/svc-power start" failed due to signal KILL.
Jul 21 13:53:27 fire280r svc.startd[7]: [ID 748625 daemon.error] system/power:default failed: transitioned to maintenance (see 'svcs -xv' for details)

ist nur powermanagement, wahrscheinlich kann deine kiste das nicht wirklich, bei nen server allerdings auich nicht so interessant.

[Ebbi]

ist nur powermanagement, wahrscheinlich kann deine kiste das nicht wirklich, bei nen server allerdings auich nicht so interessant.

Jo, das habe ich mir auch gedacht und das einfach mal mit svcadm disable /system/power:default deaktiviert. Mal sehen was beim nächsten Neustart passiert.

[Drusus]

Moin,

das bedeuted, dass der Power-Management Service nicht richtig starten konnte (Timeout). SMF versucht das dann dreimal bevor es aufgibt uns den Service in den Status "maintenance" setzt. Da muss halt der Admin dann mal selber schauen warum das nicht starten mag.

Mittels "svcs -l <service>" bekommst du mehr Informationen zu den Services - insbesondere die Logdatei mit dem Output. Schau also in deinem Fall mal in die Datei /var/svc/log/system-power:default.log ob dort mehr Informationen zu dem Fehler zu finden sind (warum Power-Management bei dir nicht mag).

Tschau,
  Drusus.

[Ebbi]

Vielen Dank! Viel steht in der Datei ja nicht drin:

Code: [Auswählen]

# more /var/svc/log/system-power:default.log
[ May 29 12:01:16 Disabled. ]
[ May 29 12:01:16 Rereading configuration. ]
[ May 29 12:01:59 Enabled. ]
[ May 29 12:01:59 Executing start method ("/lib/svc/method/svc-power start") ]
[ May 29 12:02:00 Method "start" exited with status 0 ]
[ May 29 12:33:46 Stopping because service disabled. ]
[ May 29 12:33:46 Executing stop method ("/lib/svc/method/svc-power stop") ]
[ May 29 12:33:46 Method "stop" exited with status 0 ]
[ May 29 12:35:38 Executing start method ("/lib/svc/method/svc-power start") ]
[ May 29 12:35:39 Method "start" exited with status 0 ]
[ May 29 12:50:26 Stopping because service disabled. ]
[ May 29 12:50:26 Executing stop method ("/lib/svc/method/svc-power stop") ]
[ May 29 12:50:26 Method "stop" exited with status 0 ]
[ May 30 11:07:01 Executing start method ("/lib/svc/method/svc-power start") ]
[ May 30 11:07:02 Method "start" exited with status 0 ]
[ Jul 14 17:08:47 Method "start" exited with status 0 ]
[ Jul 14 17:37:10 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 14 17:37:10 Method "start" exited with status 0 ]
[ Jul 14 17:42:42 Stopping because service disabled. ]
[ Jul 14 17:42:42 Executing stop method ("/lib/svc/method/svc-power stop") ]
[ Jul 14 17:42:43 Method "stop" exited with status 0 ]
[ Jul 15 12:01:45 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 15 12:01:46 Method "start" exited with status 0 ]
[ Jul 15 12:06:23 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 15 12:06:24 Method "start" exited with status 0 ]
[ Jul 15 14:51:23 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 15 14:51:24 Method "start" exited with status 0 ]
[ Jul 16 07:51:16 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 16 07:51:17 Method "start" exited with status 0 ]
[ Jul 16 09:15:41 Stopping because service disabled. ]
[ Jul 16 09:15:41 Executing stop method ("/lib/svc/method/svc-power stop") ]
[ Jul 16 09:15:41 Method "stop" exited with status 0 ]
[ Jul 16 09:45:40 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 16 09:45:41 Method "start" exited with status 0 ]
[ Jul 16 13:16:09 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 16 13:16:10 Method "start" exited with status 0 ]
[ Jul 16 14:43:15 Stopping because service disabled. ]
[ Jul 16 14:43:16 Executing stop method ("/lib/svc/method/svc-power stop") ]
[ Jul 16 14:43:16 Method "stop" exited with status 0 ]
[ Jul 17 12:52:27 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 17 12:52:28 Method "start" exited with status 0 ]
[ Jul 17 13:08:48 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 17 13:08:48 Method "start" exited with status 0 ]
[ Jul 17 13:16:55 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 17 13:16:56 Method "start" exited with status 0 ]
[ Jul 17 13:56:47 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 17 13:56:49 Method "start" exited with status 0 ]
[ Jul 17 14:46:58 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 17 14:46:58 Method "start" exited with status 0 ]
[ Jul 17 16:24:10 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 17 16:24:11 Method "start" exited with status 0 ]
[ Jul 17 16:35:41 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 17 16:36:41 Method or service exit timed out.  Killing contract 24 ]
[ Jul 17 16:36:41 Method "start" failed due to signal KILL ]
[ Jul 17 16:36:41 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 17 16:37:42 Method or service exit timed out.  Killing contract 37 ]
[ Jul 17 16:37:42 Method "start" failed due to signal KILL ]
[ Jul 17 16:37:42 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 17 16:38:42 Method or service exit timed out.  Killing contract 39 ]
[ Jul 17 16:38:42 Method "start" failed due to signal KILL ]
[ Jul 18 13:56:52 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 18 13:56:53 Method "start" exited with status 0 ]
[ Jul 21 13:50:26 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 21 13:51:26 Method or service exit timed out.  Killing contract 26 ]
[ Jul 21 13:51:26 Method "start" failed due to signal KILL ]
[ Jul 21 13:51:26 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 21 13:52:27 Method or service exit timed out.  Killing contract 39 ]
[ Jul 21 13:52:27 Method "start" failed due to signal KILL ]
[ Jul 21 13:52:27 Executing start method ("/lib/svc/method/svc-power start") ]
[ Jul 21 13:53:27 Method or service exit timed out.  Killing contract 41 ]
[ Jul 21 13:53:27 Method "start" failed due to signal KILL ]
[ Jul 21 14:07:22 Leaving maintenance because disable requested. ]
[ Jul 21 14:07:22 Disabled. ]

Aber wozu braucht der Server denn Power Management?
Ich hatte es deaktiviert, dann "bremst" es beim Starten nicht:

Code: [Auswählen]

# svcs -l svc:/system/power:default
fmri         svc:/system/power:default
name         power management
enabled      false
state        disabled
next_state   none
state_time   Wed Jul 23 14:17:31 2008
restarter    svc:/system/svc/restarter:default
dependency   require_all/none svc:/system/filesystem/minimal (online)