Homeserver geht ständig von alleine an...

[hoagie]

Hallo!

Ich habe das Problem, daß mein Homeserver immer nach ca. 10 Minuten aus dem Ruhezustand wieder aufwacht, egal ob ein Client-PC läuft oder nicht.

Hier ein Auszug aus dem Lightsout-Logfile, um 22:09 ist er "einfach so" wieder angegangen...

2010-05-21 21:50:25:375 [ 17] DEBUG Action: wait for lock
2010-05-21 21:50:25:375 [ 17] DEBUG Reading known services from C:\Programme\Windows Home Server\LightsOut.KnownServices.txt
2010-05-21 21:50:25:390 [ 17] DEBUG Read 9 known services
2010-05-21 21:50:25:390 [ 17] DEBUG Found service Routing und RAS [RemoteAccess], state Stopped
2010-05-21 21:50:25:390 [ 17] DEBUG Found service Druckwarteschlange [Spooler], state Running
2010-05-21 21:50:25:390 [ 17] DEBUG >>>> Hibernate
2010-05-21 21:50:25:406 [ 17] DEBUG WHSClientMonitor: suspended
2010-05-21 21:50:25:406 [ 17] DEBUG BackupMonitor: suspended
2010-05-21 21:50:25:421 [ 17] DEBUG IPDeviceMonitor: suspended
2010-05-21 21:50:25:421 [ 17] DEBUG NetworkMonitor: suspended
2010-05-21 21:50:25:437 [ 17] DEBUG HandleServices: DriveExtenderMigrator Status=Running
2010-05-21 21:50:25:437 [ 17] DEBUG stopping DriveExtenderMigrator
2010-05-21 21:50:27:515 [ 17] DEBUG service DriveExtenderMigrator Status Stopped
2010-05-21 21:50:27:515 [ 17] DEBUG HandleServices: jdownloader Status=Running
2010-05-21 21:50:27:515 [ 17] DEBUG stopping jdownloader
2010-05-21 21:50:27:515 [ 17] DEBUG service jdownloader Status Stopped
2010-05-21 21:50:27:515 [ 17] DEBUG HandleServices: Spooler Status=Running
2010-05-21 21:50:27:531 [ 17] DEBUG stopping Spooler
2010-05-21 21:50:27:859 [ 17] DEBUG service Spooler Status Stopped
2010-05-21 21:50:27:859 [ 17] DEBUG last event recorded: InitiatedHibernation
2010-05-21 21:50:28:437 [ 4] DEBUG Power event: QuerySuspend
2010-05-21 21:50:28:656 [ 4] DEBUG Power event: Suspend
2010-05-21 21:50:28:656 [ 4] DEBUG BackupMonitor: suspended
2010-05-21 21:50:28:656 [ 4] DEBUG last event recorded: Suspend
2010-05-21 21:50:29:343 [ 4] DEBUG -------------------------


2010-05-21 22:09:53:687 [ 14] DEBUG Power event: ResumeSuspend
2010-05-21 22:09:53:781 [ 17] DEBUG Power event: ResumeAutomatic
2010-05-21 22:09:54:515 [ 17] DEBUG last event recorded: Resume
2010-05-21 22:09:54:687 [ 17] DEBUG HandleServices: DriveExtenderMigrator Status=Stopped
2010-05-21 22:09:54:718 [ 17] DEBUG starting DriveExtenderMigrator
2010-05-21 22:10:14:921 [ 17] DEBUG service DriveExtenderMigrator Status Running
2010-05-21 22:10:14:921 [ 17] DEBUG HandleServices: jdownloader Status=Stopped
2010-05-21 22:10:16:218 [ 17] DEBUG HandleServices: Spooler Status=Stopped
2010-05-21 22:10:16:312 [ 17] DEBUG starting Spooler
2010-05-21 22:10:23:046 [ 17] DEBUG service Spooler Status Running
2010-05-21 22:10:23:046 [ 17] DEBUG Run:
2010-05-21 22:10:23:046 [ 17] DEBUG WHSClientMonitor: resumed
2010-05-21 22:10:23:046 [ 17] DEBUG BackupMonitor: resumed
2010-05-21 22:10:23:046 [ 17] DEBUG IPDeviceMonitor: resumed
2010-05-21 22:10:23:046 [ 17] DEBUG NetworkMonitor: resumed
2010-05-21 22:10:23:046 [ 17] DEBUG Licensee Trial 26
2010-05-21 22:10:33:046 [ 23] DEBUG >> Global wait timer enabled, Action Hibernate, Interval 10 minutes
2010-05-21 22:16:27:671 [ 20] DEBUG Adding LAPTOP DoNothing to queue
2010-05-21 22:16:29:796 [ 23] DEBUG SendSettings LAPTOP False
2010-05-21 22:16:29:875 [ 8] DEBUG IPDeviceMonitor List saved, 9 entries
2010-05-21 22:16:29:875 [ 14] DEBUG ClientCommunication List updated, 9 entries
2010-05-21 22:16:30:000 [ 14] DEBUG Request version info from LAPTOP, result False
2010-05-21 22:16:33:046 [ 17] DEBUG + WHSClientMonitor, active clients : LAPTOP
2010-05-21 22:16:33:046 [ 17] DEBUG + WHSClientMonitor: activity, clients are running (LAPTOP)
2010-05-21 22:16:33:046 [ 17] DEBUG ACTIVITY SIGNALED BY: WHSClient, action=Hibernate
2010-05-21 22:16:33:046 [ 17] DEBUG -- Global wait timer stopped
2010-05-21 22:18:53:125 [ 17] DEBUG Check every 01:00:00 triggered
2010-05-21 22:18:53:125 [ 17] DEBUG ACTIVITY SIGNALED BY: WHSClient, action=Hibernate
2010-05-21 22:19:03:125 [ 17] DEBUG Check every 00:30:00 triggered
2010-05-21 22:19:03:125 [ 17] DEBUG IPDeviceMonitor is active
2010-05-21 22:19:03:125 [ 17] DEBUG Added server 759e91a5-12dd-4636-9ba9-900e2e85ca31, SERVER 00-24-8C-7A-C5-2D, list not changed
2010-05-21 22:19:03:125 [ 17] DEBUG Scanning from address 192.168.2.1, 255 items with 8 threads, server mac 00-24-8C-7A-C5-2D
2010-05-21 22:19:03:125 [ 17] DEBUG Using 8 threads for scanning
2010-05-21 22:19:03:125 [ 14] DEBUG Starting 8 threads
2010-05-21 22:19:03:125 [ 17] DEBUG IPDeviceMonitor: >> Running update scan on network 192.168.2.1 with 8 threads
2010-05-21 22:19:03:140 [ 16] DEBUG Found device: name speedport, IP 192.168.2.1, mac 00-24-FE-0E-29-DC, key 00-24-FE-0E-29-DC
2010-05-21 22:19:03:140 [ 16] DEBUG Old device with same key exists: name speedport, IP 192.168.2.1, mac 00-24-FE-0E-29-DC, key 00-24-FE-0E-29-DC
2010-05-21 22:19:03:140 [ 16] DEBUG Existing device updated
2010-05-21 22:19:07:640 [ 16] DEBUG Found device: name 192.168.2.2, IP 192.168.2.2, mac 00-15-0C-CF-63-AE, key 00-15-0C-CF-63-AE
2010-05-21 22:19:07:640 [ 16] DEBUG Old device with same key exists: name 192.168.2.2, IP 192.168.2.2, mac 00-15-0C-CF-63-AE, key 00-15-0C-CF-63-AE
2010-05-21 22:19:07:640 [ 16] DEBUG Existing device updated
2010-05-21 22:19:09:781 [ 15] WARN 192.168.2.134: Der angegebene Host ist unbekannt
2010-05-21 22:19:09:781 [ 15] DEBUG Found device: name 192.168.2.134, IP 192.168.2.134, mac 00-09-34-1C-37-BF, key 00-09-34-1C-37-BF
2010-05-21 22:19:09:781 [ 15] DEBUG Old device with same key exists: name 192.168.2.134, IP 192.168.2.134, mac 00-09-34-1C-37-BF, key 00-09-34-1C-37-BF
2010-05-21 22:19:09:781 [ 15] DEBUG Existing device updated
2010-05-21 22:19:10:531 [ 15] DEBUG Found device: name LAPTOP, IP 192.168.2.136, mac 00-21-6A-71-73-B8, key 00-21-6A-71-73-B8
2010-05-21 22:19:10:531 [ 15] DEBUG Old device with same mac exists: name LAPTOP, IP 192.168.2.136, mac 00-21-6A-71-73-B8, key 00-21-6A-71-73-B8
2010-05-21 22:19:10:531 [ 15] DEBUG Existing device updated

Darüber hinaus sehe ich, daß ja einige Fehlermeldungen drin auftauchen. - Sind die schlimm?

Freue mich über Hilfe!

Schonmal danke im Voraus

[nexusle]

Wie ist denn der WOL Modus an der Netzwerkkarte eingestellt?? "Magic Packet", "Pattern Match" oder beides??

Beim Betrieb von LightsOut sollte NUR "Magic Packet" eingestellt sein. Das Phänomen, dass der Server bei "Pattern Match" immer wieder aufwacht, ist normal und liegt am Router. Der sendet nämlich ständig Anfragen an die Adresse des Servers um herauszufinden, ob er noch da ist...

Einstellen kann man die Modi im Gerätemanager unter den Eigenschaften der Netzwerkkarte...

[larry]

nexusle hat eigentlich alles gesagt.
Hier gibt es dies mit Screenshots:
http://www.axonet.de/whs/webhelp/de/00005.htm

Gruß
Larry

[hoagie]

Na danke für die fixe Antwort! Bin heute nicht zu hause, werde es aber dann umgehend testen und berichten, ob's geklappt hat...seltsam nur, daß es mir monatelang nicht so extrem aufgefallen ist...

[hoagie]

Alles klar!

"Wake on pattern" hieß die Funktion bei mir - und war aktiviert. Die habe ich jetzt deaktiviert - hoffe mal, daß das jetzt läuft.

Danke nochmals!