98_WOL: Probleme mit Ping und UDP

Begonnen von vbs, 10 Januar 2015, 13:56:01

Vorheriges Thema - Nächstes Thema

vbs

Hm Ok, aber das wussten wir ja schon, oder? Meinst du etwas bestimmtes?

Dietmar63

eingecheckt.

nun mit BlockingCall()

und

attr <name> interval <seconds>
defines the time between two checks by a ping if state of <name> is on. By using 0 as parameter for interval you can switch off checking the device.
attr <name> useUdpBroadcast <>
When using UDP then the magic packet can be send to one of the broardcastAdresses (x.x.x.255, x.x.255.255, x.255.255.255) instead of the target host address. Try using this, when you are trying to wake up a machine in your own subnet and the wakekup with the target adress is instable or doesn't work.
Gruß Dietmar
FB7390, CUL, 2 FHT, FS20
modules: 98_WOL.pm, 98_Heating_Control.pm,   98_WeekdayTimer.pm, 98_RandomTimer.pm, 59_Twilight.pm

Simon74

Seit meinem letzten Update habe ich Logeinträge von WOL:
2015.01.21 14:24:25 1: Timeout for WOL_Ping reached, terminated process 15915
2015.01.21 14:24:25 3: BlockingCall for t5.wol.pc1 was aborted
2015.01.21 14:40:48 1: Timeout for WOL_Ping reached, terminated process 16735
2015.01.21 14:40:48 3: BlockingCall for t5.wol.pc2 was aborted
2015.01.21 14:51:53 1: Timeout for WOL_Ping reached, terminated process 17324
2015.01.21 14:51:53 3: BlockingCall for t5.wol.pc1 was aborted
2015.01.21 15:18:48 1: Timeout for WOL_Ping reached, terminated process 18729
2015.01.21 15:18:48 3: BlockingCall for t5.wol.pc1 was aborted


Was muss ich an meiner (Standard) Konfig ändern um im Log Ruhe zu haben ?
define computer1 WOL 72:11:AC:4D:37:13 192.168.0.24 EW

Dietmar63

#33
Setze mal verbose auf 5 und Poste den Output.
Als Hardware verwendest du einen Cubietruck?

Nutzt du das Weathermodul? Es hat auch BlockingCall () im Bauch. Wenn du es nicht verwendest kannst du es Testweise einbauen?

Mit attr interval 0 kannst du die pings abschalten. 

prüf bitte mal, ob auf dem Cubi folgender Befehl funktioniert:
ping -c 1 -w 2 192.1.168.xxx
mal mit einer Adresse, dei es in deinem Netzwerk gibt und einmal mit einer Adresse, die es nicht gibt.
Gruß Dietmar
FB7390, CUL, 2 FHT, FS20
modules: 98_WOL.pm, 98_Heating_Control.pm,   98_WeekdayTimer.pm, 98_RandomTimer.pm, 59_Twilight.pm

Simon74

#34
Cubietruck, Ja
Weathermodul, Ja
Ping:
root@haus ~ > ping -c 1 -w 2 192.168.0.50
PING 192.168.0.50 (192.168.0.50) 56(84) bytes of data.

--- 192.168.0.50 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1009ms


verbose 5:
2015.01.21 22:03:17 5: [t5.wol.pc2] executing: ping -c 1 -w 2 192.168.0.105
2015.01.21 22:03:17 5: [t5.wol.pc2] ping not succesful - state = off
2015.01.21 22:03:17 5: [t5.wol.pc2] WOL_SetNextTimer to 30
2015.01.21 22:03:17 5: [t5.wol.pc2] removing Timer: t5.wol.pc2_ping
2015.01.21 22:03:17 5: [t5.wol.pc2] setting  Timer: t5.wol.pc2_ping 21.01.2015  22:03:47
2015.01.21 22:03:49 5: [t5.wol.pc2] executing: ping -c 1 -w 2 192.168.0.105
2015.01.21 22:03:49 5: [t5.wol.pc2] ping not succesful - state = off
2015.01.21 22:03:49 5: [t5.wol.pc2] WOL_SetNextTimer to 30
2015.01.21 22:03:49 5: [t5.wol.pc2] removing Timer: t5.wol.pc2_ping
2015.01.21 22:03:49 5: [t5.wol.pc2] setting  Timer: t5.wol.pc2_ping 21.01.2015  22:04:19
2015.01.21 22:04:21 5: [t5.wol.pc2] executing: ping -c 1 -w 2 192.168.0.105
2015.01.21 22:04:21 5: [t5.wol.pc2] ping not succesful - state = off
2015.01.21 22:04:21 5: [t5.wol.pc2] WOL_SetNextTimer to 30
2015.01.21 22:04:21 5: [t5.wol.pc2] removing Timer: t5.wol.pc2_ping
2015.01.21 22:04:21 5: [t5.wol.pc2] setting  Timer: t5.wol.pc2_ping 21.01.2015  22:04:51

Dietmar63

sind diese Meldungen nun verschwunden, oder kommen sie sporadisch?
2015.01.21 14:24:25 1: Timeout for WOL_Ping reached, terminated process 15915
2015.01.21 14:24:25 3: BlockingCall for t5.wol.pc1 was aborted
Gruß Dietmar
FB7390, CUL, 2 FHT, FS20
modules: 98_WOL.pm, 98_Heating_Control.pm,   98_WeekdayTimer.pm, 98_RandomTimer.pm, 59_Twilight.pm

Simon74

Sporadisch. 1,2 mal in der Stunde.

Dietmar63

Dann lass mal laufen, und liefere den Output wenn der Fehler kommt.
Gruß Dietmar
FB7390, CUL, 2 FHT, FS20
modules: 98_WOL.pm, 98_Heating_Control.pm,   98_WeekdayTimer.pm, 98_RandomTimer.pm, 59_Twilight.pm

Simon74

Wieder im Log:
2015.01.22 15:08:50 1: Timeout for WOL_Ping reached, terminated process 15252
2015.01.22 15:08:50 3: BlockingCall for t5.wol.pc1 was aborted
2015.01.22 15:22:38 3: CUL_HM set t5.bz.di1_Sw 30 300 0
2015.01.22 15:33:17 1: Timeout for WOL_Ping reached, terminated process 16394
2015.01.22 15:33:17 3: BlockingCall for t5.wol.pc2 was aborted
2015.01.22 15:35:59 1: Timeout for WOL_Ping reached, terminated process 16502
2015.01.22 15:35:59 3: BlockingCall for t5.wol.pc2 was aborted
2015.01.22 15:42:42 1: Timeout for WOL_Ping reached, terminated process 16754
2015.01.22 15:42:42 3: BlockingCall for t5.wol.pc1 was aborted
2015.01.22 15:46:44 1: Timeout for WOL_Ping reached, terminated process 17016
2015.01.22 15:46:44 3: BlockingCall for t5.wol.pc2 was aborted
2015.01.22 16:10:53 3: CUL_HM set t5.bz.di1_Sw 30 300 0
2015.01.22 16:14:08 1: Timeout for WOL_Ping reached, terminated process 18164
2015.01.22 16:14:08 3: BlockingCall for t5.wol.pc2 was aborted
2015.01.22 16:27:45 1: Notify: LED On Wohnzimmer
2015.01.22 16:27:45 3: CUL_HM set t5.wz.sd2_Sw on-for-timer 1800
2015.01.22 16:27:46 1: Kamera-Alarm: Aus (Anwesend)
2015.01.22 16:27:46 3: CUL_HM set t5.ku.sd2_Sw on
2015.01.22 16:27:46 3: CUL_HM set t5.wz.sd2_Sw on
2015.01.22 16:27:46 1: DOIF: LED Ein
2015.01.22 16:27:46 3: CUL_HM set t5.fl.di1_Sw 25 25 0
2015.01.22 16:28:22 3: CUL_HM set t5.fl.di1_Sw 25 25 0
2015.01.22 16:42:26 1: Timeout for WOL_Ping reached, terminated process 19460
2015.01.22 16:42:26 3: BlockingCall for t5.wol.pc1 was aborted
2015.01.22 16:42:34 1: Timeout for WOL_Ping reached, terminated process 19468
2015.01.22 16:42:34 3: BlockingCall for t5.wol.pc2 was aborted
2015.01.22 16:55:28 1: Timeout for WOL_Ping reached, terminated process 20062
2015.01.22 16:55:28 3: BlockingCall for t5.wol.pc2 was aborted
2015.01.22 16:55:54 1: Timeout for WOL_Ping reached, terminated process 20072
2015.01.22 16:55:54 3: BlockingCall for t5.wol.pc1 was aborted
2015.01.22 17:01:18 1: Timeout for WOL_Ping reached, terminated process 20399
2015.01.22 17:01:18 3: BlockingCall for t5.wol.pc1 was aborted
2015.01.22 17:01:23 1: Timeout for WOL_Ping reached, terminated process 20402
2015.01.22 17:01:23 3: BlockingCall for t5.wol.pc2 was aborted
2015.01.22 17:06:11 3: CUL_HM set t5.fl.di1_Sw 25 25 0
2015.01.22 17:08:20 1: Kamera-Alarm: Aus (Terrasse wurde geöffnet)
2015.01.22 17:15:18 1: Timeout for WOL_Ping reached, terminated process 21041
2015.01.22 17:15:18 3: BlockingCall for t5.wol.pc1 was aborted
2015.01.22 17:20:12 1: Timeout for WOL_Ping reached, terminated process 21227
2015.01.22 17:20:12 3: BlockingCall for t5.wol.pc2 was aborted

Dietmar63

Ich habe ein kleine Veränderung vorgenommen, und eingecheckt.
Prüf bitte mal, ob  eine Besserung erkennbar ist.
Gruß Dietmar
FB7390, CUL, 2 FHT, FS20
modules: 98_WOL.pm, 98_Heating_Control.pm,   98_WeekdayTimer.pm, 98_RandomTimer.pm, 59_Twilight.pm

Simon74


Dietmar63

Gruß Dietmar
FB7390, CUL, 2 FHT, FS20
modules: 98_WOL.pm, 98_Heating_Control.pm,   98_WeekdayTimer.pm, 98_RandomTimer.pm, 59_Twilight.pm

Simon74

Sehr Gut, keine PING-Einträge mehr im Log. :-)

Dietmar63

Ok, Ich habe dem Blocking Modul eine Sekunde mehr Zeit eingeräumt.

Wenn du den Status des Gerätes nicht benötigst kannst du den Ping mit interval 0 komplett abschalten.
Gruß Dietmar
FB7390, CUL, 2 FHT, FS20
modules: 98_WOL.pm, 98_Heating_Control.pm,   98_WeekdayTimer.pm, 98_RandomTimer.pm, 59_Twilight.pm