Autor Thema: OWX kann FHEM abschiessen ?!?  (Gelesen 48633 mal)

Offline hexenmeister

  • Developer
  • Hero Member
  • ****
  • Beiträge: 4699
    • tech_LogBuch
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #75 am: 06 Mai 2014, 16:47:36 »

Irgendwie wurde Deine 99_myUtils ganz zerschossen...

hier:

# Liefert aktueller Zeitstempel
sub
CurrentTime()
{
return strftime("%H:%M:%S", localtime());
}
Maintainer: MQTT_GENERIC_BRIDGE, SYSMON, SMARTMON, systemd_watchdog, MQTT, MQTT_DEVICE, MQTT_BRIDGE
Contrib: dev_proxy

Offline Spezialtrick

  • Hero Member
  • *****
  • Beiträge: 1027
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #76 am: 06 Mai 2014, 21:20:01 »
Ich habe meine zerschossene 99_myUtils durch eine andere aus einem meiner Backups ausgetauscht. Die Meldungen im Log sind tatsächlich verschwunden. :)

Aber der Watchdog schafft es immer noch ab und an FHEM zu beenden. Hier ein Auszug aus der watchdog.log:

2014-05-06_19:00:36 fhem_server MSG: no FHEM Server process found
2014-05-06_19:03:37 fhem_server V: 37 S: alive MSG: FHEM Server alive
2014-05-06_19:04:37 fhem_server V: 37 S: alive MSG: FHEM Server alive
2014-05-06_19:05:37 fhem_server MSG: no FHEM Server process found
2014-05-06_19:08:38 fhem_server V: 38 S: alive MSG: FHEM Server alive
2014-05-06_19:09:38 fhem_server MSG: no FHEM Server process found
2014-05-06_19:12:39 fhem_server V: 39 S: alive MSG: FHEM Server alive
2014-05-06_19:13:39 fhem_server V: 39 S: alive MSG: FHEM Server alive
2014-05-06_19:14:39 fhem_server MSG: no FHEM Server process found
2014-05-06_19:17:40 fhem_server MSG: no FHEM Server process found
2014-05-06_19:20:41 fhem_server V: 41 S: alive MSG: FHEM Server alive
2014-05-06_19:21:41 fhem_server V: 41 S: alive MSG: FHEM Server alive
2014-05-06_19:22:41 fhem_server MSG: no FHEM Server process found
2014-05-06_19:25:42 fhem_server MSG: no FHEM Server process found
2014-05-06_19:28:43 fhem_server V: 43 S: alive MSG: FHEM Server alive
2014-05-06_19:29:43 fhem_server V: 43 S: alive MSG: FHEM Server alive
2014-05-06_19:30:43 fhem_server MSG: no FHEM Server process found
2014-05-06_19:33:44 fhem_server MSG: no FHEM Server process found
2014-05-06_19:36:44 fhem_server MSG: no FHEM Server process found
2014-05-06_19:39:45 fhem_server V: 45 S: alive MSG: FHEM Server alive
2014-05-06_19:40:45 fhem_server V: 45 S: alive MSG: FHEM Server alive
2014-05-06_19:41:46 fhem_server MSG: no FHEM Server process found
2014-05-06_19:44:46 fhem_server MSG: no FHEM Server process found
2014-05-06_19:47:47 fhem_server V: 47 S: alive MSG: FHEM Server alive
2014-05-06_19:48:47 fhem_server V: 47 S: alive MSG: FHEM Server alive
2014-05-06_19:49:47 fhem_server MSG: no FHEM Server process found
2014-05-06_19:52:48 fhem_server MSG: no FHEM Server process found
2014-05-06_19:55:49 fhem_server V: 48 S: alive MSG: FHEM Server alive
2014-05-06_19:56:49 fhem_server V: 49 S: alive MSG: FHEM Server alive
2014-05-06_19:57:49 fhem_server MSG: no FHEM Server process found
2014-05-06_20:00:50 fhem_server MSG: no FHEM Server process found
2014-05-06_20:03:50 fhem_server V: 50 S: alive MSG: FHEM Server alive
2014-05-06_20:04:51 fhem_server MSG: no FHEM Server process found
2014-05-06_20:07:51 fhem_server MSG: no FHEM Server process found
2014-05-06_20:10:51 fhem_server MSG: no FHEM Server process found
2014-05-06_20:13:52 fhem_server V: 52 S: alive MSG: FHEM Server alive
2014-05-06_20:14:52 fhem_server MSG: no FHEM Server process found
2014-05-06_20:17:53 fhem_server V: 53 S: alive MSG: FHEM Server alive
2014-05-06_20:18:53 fhem_server MSG: no FHEM Server process found
2014-05-06_20:21:54 fhem_server MSG: no FHEM Server process found
2014-05-06_20:24:54 fhem_server MSG: no FHEM Server process found
2014-05-06_20:27:55 fhem_server V: 55 S: alive MSG: FHEM Server alive
2014-05-06_20:28:55 fhem_server V: 55 S: alive MSG: FHEM Server alive
2014-05-06_20:29:55 fhem_server MSG: no FHEM Server process found
2014-05-06_20:32:56 fhem_server V: 56 S: alive MSG: FHEM Server alive
2014-05-06_20:33:56 fhem_server V: 56 S: alive MSG: FHEM Server alive
2014-05-06_20:34:56 fhem_server V: 56 S: alive MSG: FHEM Server alive
2014-05-06_20:35:57 fhem_server V: 57 S: alive MSG: FHEM Server alive
2014-05-06_20:36:57 fhem_server V: 57 S: alive MSG: FHEM Server alive
2014-05-06_20:37:57 fhem_server MSG: no FHEM Server process found
2014-05-06_20:40:58 fhem_server V: 58 S: alive MSG: FHEM Server alive
2014-05-06_20:41:58 fhem_server V: 58 S: alive MSG: FHEM Server alive
2014-05-06_20:42:59 fhem_server V: 59 S: alive MSG: FHEM Server alive
2014-05-06_20:43:59 fhem_server MSG: no FHEM Server process found
2014-05-06_20:43:59 fhem_server MSG: killing FHEM PID:  2100
2014-05-06_20:47:03 fhem_server MSG: no FHEM Server process found
2014-05-06_20:50:03 fhem_server V: 3 S: alive MSG: FHEM Server alive
2014-05-06_20:51:04 fhem_server V: 4 S: alive MSG: FHEM Server alive
2014-05-06_20:52:04 fhem_server V: 4 S: alive MSG: FHEM Server alive
2014-05-06_20:53:04 fhem_server V: 4 S: alive MSG: FHEM Server alive
2014-05-06_20:54:05 fhem_server MSG: no FHEM Server process found
2014-05-06_20:57:05 fhem_server V: 5 S: alive MSG: FHEM Server alive
2014-05-06_20:58:06 fhem_server V: 6 S: alive MSG: FHEM Server alive
2014-05-06_20:59:06 fhem_server V: 6 S: alive MSG: FHEM Server alive
2014-05-06_21:00:06 fhem_server MSG: no FHEM Server process found
2014-05-06_21:03:07 fhem_server MSG: no FHEM Server process found
2014-05-06_21:06:07 fhem_server V: 7 S: alive MSG: FHEM Server alive
2014-05-06_21:07:08 fhem_server V: 8 S: alive MSG: FHEM Server alive
2014-05-06_21:08:08 fhem_server V: 8 S: alive MSG: FHEM Server alive

Und einer aus dem Log:

2014.05.06 19:00:50 3: Watchdog watchdogiPhoneMiroBluetoothAbwesend triggered
2014.05.06 19:00:50 2: ROOMMATE set rr_Miro absent
2014.05.06 19:11:38 1: FHEMduino_KW9010 77 Skipping override due to too large timedifference
2014.05.06 19:31:22 1: FHEMduino_KW9010 77 Skipping override due to too large timedifference
2014.05.06 19:36:42 1: FHEMduino_KW9010 77 Skipping override due to too large timedifference
2014.05.06 20:17:14 1: FHEMduino_KW9010 77 Skipping override due to too large timedifference
2014.05.06 20:32:10 1: FHEMduino_KW9010 77 Skipping override due to too large timedifference
2014.05.06 20:32:11 3: Unautorisierter_Zutritt_Haustuer_Pushover return value: OK
2014.05.06 20:32:36 2: ROOMMATE set rr_Miro home
2014.05.06 20:44:00 0: Server shutdown
2014.05.06 20:44:05 1: Including fhem.cfg
2014.05.06 20:44:06 3: WEB: port 8083 opened
2014.05.06 20:44:06 3: WEBphone: port 8084 opened
2014.05.06 20:44:06 3: WEBtablet: port 8085 opened
2014.05.06 20:44:06 3: telnetPort: port 7072 opened
2014.05.06 20:44:08 2: eventTypes: loaded 766 events from ./log/eventTypes.txt
2014.05.06 20:44:08 3: Opening FHEMduino device /dev/ttyUSB0
2014.05.06 20:44:08 3: Setting FHEMduino baudrate to 9600
2014.05.06 20:44:08 3: FHEMduino device opened
2014.05.06 20:44:11 3: FHEMduino: Possible commands: VisRq
2014.05.06 20:44:12 3: Opening CUL_0 device /dev/ttyAMA0
2014.05.06 20:44:12 3: Setting CUL_0 baudrate to 38400
2014.05.06 20:44:12 3: CUL_0 device opened
2014.05.06 20:44:12 3: CUL_0: Possible commands: mBCFAIZOGMRTVWXefltux
2014.05.06 20:44:12 2: Switched CUL_0 rfmode to MAX
2014.05.06 20:44:12 2: Switched IR_Dev irReceive to ON_NR
2014.05.06 20:44:13 1: OWX: COC/CUNO device CUL_0 defined
2014.05.06 20:44:18 3: OWTHERM: Device OWX_28_13C458050000 defined.
2014.05.06 20:44:18 3: OWTHERM: Device OWX_28_589C58050000 defined.
2014.05.06 20:44:20 1: Including ./log/fhem.save
2014.05.06 20:44:20 1: statefile: Undefined value undef
2014.05.06 20:44:20 3: No I/O device found for FHEMduino_KW9010_35
2014.05.06 20:44:20 3: No I/O device found for LCD_Backlight
2014.05.06 20:44:20 3: No I/O device found for FHEMduino_KW9010_B5
2014.05.06 20:44:20 3: No I/O device found for FHEMduino_KW9010_77
2014.05.06 20:44:20 3: Airquality: filed to find CO20 device
2014.05.06 20:44:22 1: OWX: 1-Wire bus OWio: interface DS2482 / COC detected in CUL_0 with response R:F6000005589C5828
R:D000000558C41328
D: 2
OK
V 1.58 CSM868

2014.05.06 20:44:22 3: initialUsbCheck return value: Unknown command usb, try help.
2014.05.06 20:44:22 2: Error messages while initializing FHEM: statefile: Undefined value undef
2014.05.06 20:44:22 0: Server started with 110 defined entities (version $Id: fhem.pl 5728 2014-05-03 09:41:12Z rudolfkoenig $, os linux, user fhem, pid 16882)
2014.05.06 20:44:23 3: telnetForBlockingFn: port 57524 opened
2014.05.06 20:44:24 1: FHEMduino_KW9010 35 Skipping override due to too large timedifference
2014.05.06 20:44:26 1: FHEMduino_KW9010 B5 Skipping override due to too large timedifference
2014.05.06 20:44:33 3: OWX: Answer to CUL_0 device search is 1:F6000005589C5828
2:D000000558C41328

2014.05.06 20:44:33 1: OWX: 1-Wire devices found on bus OWio (OWX_28_589C58050000,OWX_28_13C458050000)
2014.05.06 20:45:31 3: Watchdog watchdogiPhoneAngieBluetoothAbwesend triggered
2014.05.06 20:45:31 2: ROOMMATE set rr_Angie absent
2014.05.06 21:11:06 1: FHEMduino_KW9010 77 Skipping override due to too large timedifference

Liegt das am Watchdog oder habe ich möglicherweise ein anderes Problem?  :-\
FHEM - Debmatic - Zigbee2MQTT - Homekit

Offline hexenmeister

  • Developer
  • Hero Member
  • ****
  • Beiträge: 4699
    • tech_LogBuch
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #77 am: 06 Mai 2014, 21:57:56 »
sieht sehr komisch aus...

Die Zeiten werden nicht überschritten, also 'hängt' FHEM nicht. Es sieht eher so aus, dass der Serverprozess einfach weg ist. Probiere mal watchdog abzuschalten. Läuft dann FHEM längere Zeit, oder geht auch kaputt?

Oder irgendwas funktioniert mit dem Befehl zun Suchen von PID nicht:

ps -ef | grep -v grep | grep fhem.pl | wc -l

und

ps -ef | grep -v grep | grep fhem.pl | cut -c10-14

Ich habe aber keine Idee, was hier passieren soll.

Landet was spannendes in watchdog_err.log?

War FHEM auch gekillt mit der 'kaputten' 99_myUtils nach den Eintragen von den zwei fehlenen Methoden? Evtl. hat diese Datei aus der Sicherung auch ein Problem?

Ich sehe auch ein Shutdown im Log. Hast Du FHEM da selbst neugestartet ?
  2014.05.06 20:44:00 0: Server shutdown
Davor war eine 12 minutige Pause, was auch komisch ist.

Maintainer: MQTT_GENERIC_BRIDGE, SYSMON, SMARTMON, systemd_watchdog, MQTT, MQTT_DEVICE, MQTT_BRIDGE
Contrib: dev_proxy

Offline Spezialtrick

  • Hero Member
  • *****
  • Beiträge: 1027
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #78 am: 07 Mai 2014, 11:22:36 »
Danke schon mal für deine ausführliche Hilfe!

Ich habe FHEM kein einziges Mal neugestartet. Das macht es ganz von alleine. Bin gerade mal das Log von heute Nacht durch gegangen und musst feststellen, dass FHEM seit 0 Uhr bis jetzt 11 Mal ein "Server shutdown" durchgeführt hat. Die "watchdog_err.log" ist prall gefüllt. Hier mal ein Auszug:

Use of uninitialized value in numeric gt (>) at fhem.pl line 374.
./killfhem.sh: 37: kill: No such process

./startfhem: 17: ./startfhem: cannot create log/watchdog_err.log: Permission denied
./startfhem: 31: ./startfhem: cannot create log/watchdog_err.log: Permission denied
Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 225.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./startfhem: 17: ./startfhem: cannot create log/watchdog_err.log: Permission denied
./startfhem: 31: ./startfhem: cannot create log/watchdog_err.log: Permission denied
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
./watchdogloop.sh: 159: test: 2100: unexpected operator
./watchdogloop.sh: 66: test: 2100: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 16882: unexpected operator
./watchdogloop.sh: 159: test: 16882: unexpected operator
./watchdogloop.sh: 66: test: 16882: unexpected operator
./watchdogloop.sh: 159: test: 16882: unexpected operator
./watchdogloop.sh: 66: test: 16882: unexpected operator
./watchdogloop.sh: 159: test: 16882: unexpected operator
./watchdogloop.sh: 66: test: 16882: unexpected operator
./watchdogloop.sh: 159: test: 16882: unexpected operator
./watchdogloop.sh: 66: test: 16882: unexpected operator
./watchdogloop.sh: 159: test: 16882: unexpected operator
./watchdogloop.sh: 66: test: 16882: unexpected operator
./watchdogloop.sh: 159: test: 16882: unexpected operator
./watchdogloop.sh: 66: test: 16882: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 20092: unexpected operator
./watchdogloop.sh: 159: test: 20092: unexpected operator
./watchdogloop.sh: 66: test: 20092: unexpected operator
./watchdogloop.sh: 159: test: 20092: unexpected operator
./watchdogloop.sh: 66: test: 20092: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 21512: unexpected operator
./watchdogloop.sh: 159: test: 21512: unexpected operator
./watchdogloop.sh: 66: test: 21512: unexpected operator
./watchdogloop.sh: 159: test: 21512: unexpected operator
./watchdogloop.sh: 66: test: 21512: unexpected operator
./watchdogloop.sh: 159: test: 21512: unexpected operator
./watchdogloop.sh: 66: test: 21512: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 23480: unexpected operator
./watchdogloop.sh: 159: test: 23480: unexpected operator
./watchdogloop.sh: 66: test: 23480: unexpected operator
./watchdogloop.sh: 159: test: 23480: unexpected operator
./watchdogloop.sh: 66: test: 23480: unexpected operator
./watchdogloop.sh: 159: test: 23480: unexpected operator
./watchdogloop.sh: 66: test: 23480: unexpected operator
./watchdogloop.sh: 159: test: 23480: unexpected operator
./watchdogloop.sh: 66: test: 23480: unexpected operator
./watchdogloop.sh: 159: test: 23480: unexpected operator
./watchdogloop.sh: 66: test: 23480: unexpected operator
./watchdogloop.sh: 159: test: 23480: unexpected operator
./watchdogloop.sh: 66: test: 23480: unexpected operator
./watchdogloop.sh: 159: test: 23480: unexpected operator
./watchdogloop.sh: 66: test: 23480: unexpected operator
./watchdogloop.sh: 159: test: 23480: unexpected operator
./watchdogloop.sh: 66: test: 23480: unexpected operator
./watchdogloop.sh: 159: test: 23480: unexpected operator
./watchdogloop.sh: 66: test: 23480: unexpected operator
./watchdogloop.sh: 159: test: 23480: unexpected operator
./watchdogloop.sh: 66: test: 23480: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 30149: unexpected operator
./watchdogloop.sh: 159: test: 30149: unexpected operator
./watchdogloop.sh: 66: test: 30149: unexpected operator
./watchdogloop.sh: 159: test: 30149: unexpected operator
./watchdogloop.sh: 66: test: 30149: unexpected operator
./watchdogloop.sh: 159: test: 30149: unexpected operator
./watchdogloop.sh: 66: test: 30149: unexpected operator
./watchdogloop.sh: 159: test: 30149: unexpected operator
./watchdogloop.sh: 66: test: 30149: unexpected operator
./watchdogloop.sh: 159: test: 30149: unexpected operator
./watchdogloop.sh: 66: test: 357: unexpected operator
./watchdogloop.sh: 159: test: 357: unexpected operator
./watchdogloop.sh: 66: test: 988: unexpected operator
./watchdogloop.sh: 159: test: 988: unexpected operator
./watchdogloop.sh: 66: test: 1735: unexpected operator
./watchdogloop.sh: 159: test: 1735: unexpected operator
./watchdogloop.sh: 66: test: 2030: unexpected operator
./watchdogloop.sh: 159: test: 2030: unexpected operator
./watchdogloop.sh: 66: test: 2561: unexpected operator
./watchdogloop.sh: 159: test: 2561: unexpected operator
./watchdogloop.sh: 66: test: 2850: unexpected operator
./watchdogloop.sh: 159: test: 2850: unexpected operator
./watchdogloop.sh: 66: test: 3367: unexpected operator
./watchdogloop.sh: 159: test: 3367: unexpected operator
./watchdogloop.sh: 66: test: 3998: unexpected operator
./watchdogloop.sh: 159: test: 3998: unexpected operator
./watchdogloop.sh: 66: test: 4626: unexpected operator
./watchdogloop.sh: 159: test: 4626: unexpected operator
./watchdogloop.sh: 66: test: 5020: unexpected operator
./watchdogloop.sh: 159: test: 5020: unexpected operator
./watchdogloop.sh: 66: test: 5237: unexpected operator
./watchdogloop.sh: 159: test: 5237: unexpected operator
./watchdogloop.sh: 66: test: 5866: unexpected operator
./watchdogloop.sh: 159: test: 5866: unexpected operator
./watchdogloop.sh: 66: test: 6501: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 6548: unexpected operator
./watchdogloop.sh: 159: test: 6548: unexpected operator
./watchdogloop.sh: 66: test: 6548: unexpected operator
./watchdogloop.sh: 159: test: 6548: unexpected operator
./watchdogloop.sh: 66: test: 6548: unexpected operator
./watchdogloop.sh: 159: test: 6548: unexpected operator
./watchdogloop.sh: 66: test: 6548: unexpected operator
./watchdogloop.sh: 159: test: 6548: unexpected operator
./watchdogloop.sh: 66: test: 6548: unexpected operator
./watchdogloop.sh: 159: test: 6548: unexpected operator
./watchdogloop.sh: 66: test: 6548: unexpected operator
./watchdogloop.sh: 159: test: 6548: unexpected operator
./watchdogloop.sh: 66: test: 6548: unexpected operator
./watchdogloop.sh: 159: test: 6548: unexpected operator
./watchdogloop.sh: 66: test: 6548: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Use of uninitialized value $temperature in concatenation (.) or string at ./FHEM/59_Weather.pm line 359, <$fh> line 117.
Use of uninitialized value $humidity in concatenation (.) or string at ./FHEM/59_Weather.pm line 359, <$fh> line 117.
Use of uninitialized value $wind in concatenation (.) or string at ./FHEM/59_Weather.pm line 359, <$fh> line 117.
Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 10278: unexpected operator
./watchdogloop.sh: 159: test: 10278: unexpected operator
./watchdogloop.sh: 66: test: 10278: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
./watchdogloop.sh: 159: test: 11610: unexpected operator
./watchdogloop.sh: 66: test: 11610: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 22514: unexpected operator
./watchdogloop.sh: 159: test: 22514: unexpected operator
./watchdogloop.sh: 66: test: 690: unexpected operator
./watchdogloop.sh: 159: test: 690: unexpected operator
./watchdogloop.sh: 66: test: 1322: unexpected operator
./watchdogloop.sh: 159: test: 1322: unexpected operator
./watchdogloop.sh: 66: test: 2054: unexpected operator
./watchdogloop.sh: 159: test: 2054: unexpected operator
./watchdogloop.sh: 66: test: 2626: unexpected operator
./watchdogloop.sh: 159: test: 2626: unexpected operator
./watchdogloop.sh: 66: test: 2847: unexpected operator
./watchdogloop.sh: 159: test: 2847: unexpected operator
./watchdogloop.sh: 66: test: 3320: unexpected operator
./watchdogloop.sh: 159: test: 3320: unexpected operator
./watchdogloop.sh: 66: test: 3953: unexpected operator
./watchdogloop.sh: 159: test: 3953: unexpected operator
./watchdogloop.sh: 66: test: 4583: unexpected operator
./watchdogloop.sh: 159: test: 4583: unexpected operator
./watchdogloop.sh: 66: test: 5051: unexpected operator
./watchdogloop.sh: 159: test: 5051: unexpected operator
./watchdogloop.sh: 66: test: 5272: unexpected operator
./watchdogloop.sh: 159: test: 5272: unexpected operator
./watchdogloop.sh: 66: test: 5827: unexpected operator
./watchdogloop.sh: 159: test: 5827: unexpected operator
./watchdogloop.sh: 66: test: 6455: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 6502: unexpected operator
./watchdogloop.sh: 159: test: 6502: unexpected operator
./watchdogloop.sh: 66: test: 6502: unexpected operator
./watchdogloop.sh: 159: test: 6502: unexpected operator
./watchdogloop.sh: 66: test: 6502: unexpected operator
./watchdogloop.sh: 159: test: 6502: unexpected operator
./watchdogloop.sh: 66: test: 6502: unexpected operator
./watchdogloop.sh: 159: test: 6502: unexpected operator
./watchdogloop.sh: 66: test: 6502: unexpected operator
./watchdogloop.sh: 159: test: 6502: unexpected operator
./watchdogloop.sh: 66: test: 6502: unexpected operator
./watchdogloop.sh: 159: test: 6502: unexpected operator
./watchdogloop.sh: 66: test: 6502: unexpected operator
./watchdogloop.sh: 159: test: 6502: unexpected operator
./watchdogloop.sh: 66: test: 6502: unexpected operator
./watchdogloop.sh: 159: test: 6502: unexpected operator
./watchdogloop.sh: 66: test: 6502: unexpected operator
./watchdogloop.sh: 159: test: 6502: unexpected operator
./watchdogloop.sh: 66: test: 6502: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 12515: unexpected operator
./watchdogloop.sh: 159: test: 12515: unexpected operator
./watchdogloop.sh: 66: test: 12515: unexpected operator
./watchdogloop.sh: 159: test: 12515: unexpected operator
./watchdogloop.sh: 66: test: 12515: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 13913: unexpected operator
./watchdogloop.sh: 159: test: 13913: unexpected operator
./watchdogloop.sh: 66: test: 13913: unexpected operator
./watchdogloop.sh: 159: test: 13913: unexpected operator
./watchdogloop.sh: 66: test: 13913: unexpected operator
./watchdogloop.sh: 159: test: 13913: unexpected operator
./watchdogloop.sh: 66: test: 13913: unexpected operator
./watchdogloop.sh: 159: test: 13913: unexpected operator
./watchdogloop.sh: 66: test: 13913: unexpected operator
./watchdogloop.sh: 159: test: 13913: unexpected operator
./watchdogloop.sh: 66: test: 13913: unexpected operator
./watchdogloop.sh: 159: test: 13913: unexpected operator
./watchdogloop.sh: 66: test: 13913: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 17363: unexpected operator
./watchdogloop.sh: 159: test: 17363: unexpected operator
./watchdogloop.sh: 66: test: 17363: unexpected operator
./watchdogloop.sh: 159: test: 17363: unexpected operator
./watchdogloop.sh: 66: test: 17363: unexpected operator
./watchdogloop.sh: 159: test: 17363: unexpected operator
./watchdogloop.sh: 66: test: 17363: unexpected operator
./watchdogloop.sh: 159: test: 17363: unexpected operator
./watchdogloop.sh: 66: test: 17363: unexpected operator
Use of uninitialized value in concatenation (.) or string at ./FHEM/74_StreamRadio.pm line 163.
./watchdogloop.sh: 168: kill: No such process

Useless use of numeric eq (==) in void context at ./FHEM/74_StreamRadio.pm line 112, <$fh> line 224.
Use of uninitialized value in pattern match (m//) at ./FHEM/38_CO20.pm line 84.
./watchdogloop.sh: 66: test: 19967: unexpected operator
./watchdogloop.sh: 159: test: 19967: unexpected operator

Vllt. findest du ja da was interessantes. Habe den Watchdog nun mal beendet und werde schauen wie es sich bis heute Abend verhält.

Edit: Zudem steht nun diese Meldung auf der FHEM Hauptseite:  :-\

Error messages while initializing FHEM:
statefile: Undefined value undef
« Letzte Änderung: 07 Mai 2014, 11:32:44 von Spezialtrick »
FHEM - Debmatic - Zigbee2MQTT - Homekit

Offline hexenmeister

  • Developer
  • Hero Member
  • ****
  • Beiträge: 4699
    • tech_LogBuch
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #79 am: 07 Mai 2014, 17:44:30 »
Es scheint mir so, dass mit deinem System etwas ziemlich nicht in Ordnung ist. Die Suche/Test nach dem PID von FHEM-Prozess scheint schon mal nicht korrekt zu funktionieren. Mal klapt es, mal liefert es nichts (und dabei wird dann FHEM doch beendet). Mal geht auch das Beenden nicht (kill: No such process).
Probiere die Test-Befehle in der SHH-Console mit und ohne laufenden FHEM. Ist vielleicht auch die watchdogloop.sh irgendwie verändert worden? (Kartenfehler?) Was steht in den Zeilen 66 und 159?

Aus diesen Symptomen werde ich nicht schlau...
Maintainer: MQTT_GENERIC_BRIDGE, SYSMON, SMARTMON, systemd_watchdog, MQTT, MQTT_DEVICE, MQTT_BRIDGE
Contrib: dev_proxy

Offline Spezialtrick

  • Hero Member
  • *****
  • Beiträge: 1027
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #80 am: 07 Mai 2014, 21:00:43 »
Mit beendeten Watchdogs lief Fhem den ganzen Nachmittag problemlos. Grad eben habe ich den Watchdog wieder gestartet und prompt wurde Fhem erstmal neugestartet.

Der Befehl "ps -ef | grep -v grep | grep fhem.pl | wc -l" ergibt bei nicht laufendem Fhem eine 0. Das sollte ja soweit richtig sein. Bei laufendem Fhem ergibt es eine 1 manchmal aber auch eine 2.

Der Befehl "ps -ef | grep -v grep | grep fhem.pl | cut -c10-14" ergibt bei nicht laufendem Fhem gar keine Ausgabe und bei laufendem Fhem in der Regel eine PID, wie "24431", manchmal aber auch drei PIDs, wie "24431, 24450, 24451" Ist das möglicherweise das Problem?

Die "watchdogloop.sh" habe ich sicherhaltshalber durch eine aktuelle von der HP ausgetauscht.
FHEM - Debmatic - Zigbee2MQTT - Homekit

Offline hexenmeister

  • Developer
  • Hero Member
  • ****
  • Beiträge: 4699
    • tech_LogBuch
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #81 am: 07 Mai 2014, 22:44:36 »
Mehrere PIDs müsste ja bedeuten, dass mehrere FHEM-Instanzen gleichzeitig laufen. Das erscheint mir komisch.
Laufen die VErsionen von GitHub besser?
Meine habe ich seit sehr langen Zeit nicht mehr angefasst, es läuft problemlos.

Fällt mir gerade ein, ich habe in Deinen Logs die 'permission denied'-Meldungen gesehen. Das kann auch ein Problem sein. Prüfe bitte, ob die Zugriffsrechte auf die Log-Dateien korrekt sind.

Maintainer: MQTT_GENERIC_BRIDGE, SYSMON, SMARTMON, systemd_watchdog, MQTT, MQTT_DEVICE, MQTT_BRIDGE
Contrib: dev_proxy

Offline Spezialtrick

  • Hero Member
  • *****
  • Beiträge: 1027
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #82 am: 08 Mai 2014, 21:41:56 »
Mit den Github Versionen habe ich die gleichen Probleme wie vorher. Ich habe einfach deine Anleitung nochmals abgearbeitet. Am Ende stehe ich faktisch wieder am Anfang. Kann es sein, dass FHEM keinen Zugriff auf den LOG Ordner hat? Aktuell steht folgende in der "watchdog_err.log":

./startfhem: 17: ./startfhem: cannot create log/watchdog_err.log: Permission denied
./startfhem: 31: ./startfhem: cannot create log/watchdog_err.log: Permission denied
chmod: changing permissions of `./log/watchdog-2014-05.log': Operation not permitted
./startfhem: 17: ./startfhem: cannot create log/watchdog_err.log: Permission denied
./startfhem: 31: ./startfhem: cannot create log/watchdog_err.log: Permission denied
FHEM - Debmatic - Zigbee2MQTT - Homekit

Offline hexenmeister

  • Developer
  • Hero Member
  • ****
  • Beiträge: 4699
    • tech_LogBuch
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #83 am: 08 Mai 2014, 21:52:35 »
Hm... Sieht so aus. Das ist vermutlich genau das Problem. Watchdog kann nicht die log lesen und erkennt nicht, ob fhem noch lebenszeichen von sich gibt. Verpasse dem log ordner passende Rechte. 
ungefähr so, je nach dem wo fhem installiert ist.
sudo chmod a+rw /opt/fhem/log
Auch für die log Dateien...
Maintainer: MQTT_GENERIC_BRIDGE, SYSMON, SMARTMON, systemd_watchdog, MQTT, MQTT_DEVICE, MQTT_BRIDGE
Contrib: dev_proxy

Offline Spezialtrick

  • Hero Member
  • *****
  • Beiträge: 1027
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #84 am: 09 Mai 2014, 13:39:44 »
Hallo. Ich habe "sudo chmod a+rw /opt/fhem/log" ausgeführt, aber leider wieder das Problem nicht behoben. Fhem läuft ein paar Minuten. Dann wird es beendet und startet nun aber auch nicht mehr selbstständig. Ich glaube das Beste wäre, wenn ich den Pi einmal komplett neu aufsetze. Würde dann die Anleitung von deiner HP benutzen. Oder was meinst du?
FHEM - Debmatic - Zigbee2MQTT - Homekit

Offline hexenmeister

  • Developer
  • Hero Member
  • ****
  • Beiträge: 4699
    • tech_LogBuch
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #85 am: 09 Mai 2014, 20:32:08 »
Hi!

Dieses Befehl alleine reicht noch nicht, auch die Log-Dateien müssen angepasst werden. Probiere mal noch folgendes:

sudo chmod a+rwx /opt/fhem/log
sudo chmod a+rw -R /opt/fhem/log/

Grundsätzlich kann man schon auch alles neu aufsetzen. Ich würde in jedem Fall eine neue SD-Card nehmen, dann hast Du jetziges System als Fallback-Lösung noch am Laufen. Ansonsten müsste die Anleitng auf der HP funktionieren, wenn nicht, schauen wir das uns dann gemeinesam an.

Maintainer: MQTT_GENERIC_BRIDGE, SYSMON, SMARTMON, systemd_watchdog, MQTT, MQTT_DEVICE, MQTT_BRIDGE
Contrib: dev_proxy

Offline Spezialtrick

  • Hero Member
  • *****
  • Beiträge: 1027
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #86 am: 11 Mai 2014, 22:17:12 »
So ich habe mein System heute komplett aufgesetzt. Alles bis auf den Watchdog. Erstaunlicherweise ist der Pi/Fhem nun richtig schnell. Scheinbar hat vorher tatsächlich irgendwas nicht richtig funktioniert. Ich habe mir ein Backup Image erstellt und werde morgen früh mit Hilfe deiner Anleitung den Watchdog installieren. Diesmal hoffentlich erfolgreich. ^^
FHEM - Debmatic - Zigbee2MQTT - Homekit

Offline Ma_Bo

  • Hero Member
  • *****
  • Beiträge: 1282
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #87 am: 12 Mai 2014, 10:12:38 »
Hallo,
ich habe huete mal deinen Watchdog eingebaut und es funktioniert alles soweit super.

Jetzt habe ich in meiner watchdog_err.log Datei ein Problem:

Use of uninitialized value $a[1] in substitution (s///) at ./FHEM/98_SVG.pm line 994.
Use of uninitialized value in join or string at ./FHEM/98_SVG.pm line 994.

diese beiden Zeilen fügt er jedesmal hinzu, sobald ich über das WEB Interface zugreife oder im Browser aktualisiere.

Woran kann das liegen ?

Gruß Marcel
NUC mit FHEM, HM Heizungsthermostate, HM Wandthermostate, Intertechno Funksteckdosen, 10" Tablet als Wanddisplay, KeyMatic, Fensterkontakte, Fensterkontakte umgebaut als Wassermelder und Briefkastenmelder, Aussenthermostat, Anwesenheitssteuerung über Fritz Box, Google Home usw. usw.

Offline hexenmeister

  • Developer
  • Hero Member
  • ****
  • Beiträge: 4699
    • tech_LogBuch
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #88 am: 12 Mai 2014, 13:34:24 »
Hat mit Watchdog vermutlich nichts zu tun. In dieser Datei landet jetzt alles, was in FHEM auf error geloggt wird. Das ist irgendein Problem mit einer Diagramm oder gar mit dem SVG-Modul selbst.
Maintainer: MQTT_GENERIC_BRIDGE, SYSMON, SMARTMON, systemd_watchdog, MQTT, MQTT_DEVICE, MQTT_BRIDGE
Contrib: dev_proxy

Offline Ma_Bo

  • Hero Member
  • *****
  • Beiträge: 1282
Antw:OWX kann FHEM abschiessen ?!?
« Antwort #89 am: 12 Mai 2014, 14:01:58 »
Hey hexenmeister,
stimmt, habe durch probieren jetzt rausgefunden, dass wenn ich

define 0.wlHeartbeat SVG FileLog_NN_TE_DMST01.Server_Heartbeat:myServerHeartbeat:CURRENT

auskommentiere, kein Fehler mehr entsteht, aber warum ist das so ?

SVG hab ich schon neu geupdatet.
NUC mit FHEM, HM Heizungsthermostate, HM Wandthermostate, Intertechno Funksteckdosen, 10" Tablet als Wanddisplay, KeyMatic, Fensterkontakte, Fensterkontakte umgebaut als Wassermelder und Briefkastenmelder, Aussenthermostat, Anwesenheitssteuerung über Fritz Box, Google Home usw. usw.