Readingsgroup führt zu fhem server restarts group mit Timestamp

Begonnen von riker1, 12 Februar 2019, 21:03:04

Vorheriges Thema - Nächstes Thema

riker1

Hallo

habe diverse server restarts bei fhem.

restart Counter  geht hoch.

im Log finde ich keine Fehlermeldungen die ich richtig interpretieren kann.

aktuell versuche ich gerade Readingsgroup und structure zu implementieren.

Dies hängt da wohl irgendwie mit zusammen.

logeintrag:
2019.02.12 20:55:58.373 1: checkFritzMACpresent (FB3390_32): mac_FC_53_9E_A6_BB_B1 nicht gefunden, abwesend.
2019.02.12 20:55:59.819 4: Connection closed for WEB8086_192.168.0.10_57958: EOF
2019.02.12 20:56:04.950 4: WEB8086_192.168.0.10_57946 POST /fhem?cmd.attrWZ_Licht_state%3Dattr%20WZ_Licht_state%20comment%20problem%3A%20%E2%90%A4state%20zur%C3%BCcksetzen%20nach%20on-for-timer%20%E2%90%A4%E2%90%A4-%3E%20neue%20notifys%3F%E2%90%A4%E2%90%A4-%3E%20check%20structure%3F&XHR=1&fw_id=12451; BUFLEN:0
2019.02.12 20:56:04.952 4: authorize WEB8086/cmd/attr: allowed returned dont care
2019.02.12 20:56:04.952 4: authorize WEB8086/devicename/WZ_Licht_state: allowed returned dont care
2019.02.12 20:56:04.990 4: WEB8086: /fhem?cmd.attrWZ_Licht_state%3Dattr%20WZ_Licht_state%20comment%20problem%3A%20%E2%90%A4state%20zur%C3%BCcksetzen%20nach%20on-for-timer%20%E2%90%A4%E2%90%A4-%3E%20neue%20notifys%3F%E2%90%A4%E2%90%A4-%3E%20check%20structure%3F&XHR=1&fw_id=12451 / RL:20 / text/plain; charset=UTF-8 / Content-Encoding: gzip
/ Cache-Control: no-cache, no-store, must-revalidate

2019.02.12 20:56:05.011 4: WEB8086_192.168.0.10_57946 GET /fhem?detail=WZ_Licht_state; BUFLEN:0
2019.02.12 20:56:05.104 4: WEB8086: /fhem?detail=WZ_Licht_state / RL:6754 / text/html; charset=UTF-8 / Content-Encoding: gzip
/ Cache-Control: no-cache, no-store, must-revalidate

2019.02.12 20:56:05.125 4: Connection closed for WEB8086_192.168.0.10_57954: EOF
2019.02.12 20:56:05.221 4: WEB8086_192.168.0.10_57946 GET /fhem?cmd=%7BAttrVal(%22WZ_Licht_state%22%2C%22room%22%2C%22%22)%7D&XHR=1; BUFLEN:0
2019.02.12 20:56:05.222 4: authorize WEB8086/cmd/perl: allowed returned dont care
2019.02.12 20:56:05.223 4: WEB8086: /fhem?cmd=%7BAttrVal(%22WZ_Licht_state%22%2C%22room%22%2C%22%22)%7D&XHR=1 / RL:64 / text/plain; charset=UTF-8 / Content-Encoding: gzip
/ Cache-Control: no-cache, no-store, must-revalidate

2019.02.12 20:56:05.276 4: Connection accepted from WEB8086_192.168.0.10_57990
2019.02.12 20:56:06.049 4: Connection accepted from WEB8086_192.168.0.10_57992
2019.02.12 20:56:08.728 1: checkFritzMACpresent (FB3390_32): mac_FC_53_9E_A6_BB_B1 nicht gefunden, abwesend.
2019.02.12 20:56:09.775 4: Connection closed for WEB8086_192.168.0.10_57964: EOF
2019.02.12 20:56:15.762 4: Connection accepted from WEB8086_192.168.0.10_57996
2019.02.12 20:56:19.046 1: checkFritzMACpresent (FB3390_32): mac_FC_53_9E_A6_BB_B1 nicht gefunden, abwesend.
2019.02.12 20:56:20.764 4: Connection closed for WEB8086_192.168.0.10_57966: EOF
2019.02.12 20:56:26.653 4: WEB8086_192.168.0.10_57946 POST /fhem?cmd.modifyWKD_Licht_SW_DIM%3Dmodify%20WKD_Licht_SW_DIM%20KWD_Lichter_S_Type1%20%20model%3DHM-LC-.*%3AFILTER%3Droom%3D1_%5BWKD%5D.*Licht&XHR=1&fw_id=12280; BUFLEN:0
2019.02.12 20:56:26.654 4: authorize WEB8086/cmd/modify: allowed returned dont care
2019.02.12 20:56:27.495 5: SET: Unknown argument ?, choose one of assignHmKey:noArg clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all deviceRename down fwUpdate getConfig:noArg getDevInfo:noArg getRegRaw getSerial:noArg getVersion:noArg inhibit:on,off off:noArg old:noArg on-for-timer on-till on:noArg pair:noArg pct:slider,0,1,100 peerBulk peerIODev press raw regBulk regSet reset:noArg sign:on,off statusRequest:noArg stop:noArg templateDel toggle:noArg unpair:noArg up
Unknown argument ?, choose one of assignHmKey:noArg clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all deviceRename fwUpdate getConfig:noArg getDevInfo:noArg getRegRaw getSerial:noArg getVersion:noArg inhibit:on,off off:noArg on-for-timer on-till on:noArg pair:noArg peerBulk peerIODev press raw regBulk regSet reset:noArg sign:on,off statusRequest:noArg templateDel toggle:noArg unpair:noArg
Unknown argument ?, choose one of clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all down getConfig:noArg getRegRaw inhibit:on,off off:noArg old:noArg on-for-timer on-till on:noArg pct:slider,0,1,100 peerBulk peerIODev press regBulk regSet sign:on,off statusRequest:noArg stop:noArg templateDel toggle:noArg up
Unknown argument ?, choose one of assignHmKey:noArg clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all deviceRename fwUpdate getConfig:noArg getDevInfo:noArg getRegRaw getSerial:noArg getVersion:noArg inhibit:on,off off:noArg on-for-timer on-till on:noArg pair:noArg peerBulk peerIODev press raw regBulk regSet reset:noArg sign:on,off statusRequest:noArg templateDel toggle:noArg unpair:noArg
Unknown argument ?, choose one of assignHmKey:noArg clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all deviceRename fwUpdate getConfig:noArg getDevInfo:noArg getRegRaw getSerial:noArg getVersion:noArg inhibit:on,off off:noArg on-for-timer on-till on:noArg pair:noArg peerBulk peerIODev press raw regBulk regSet reset:noArg sign:on,off statusRequest:noArg templateDel toggle:noArg unpair:noArg
Unknown argument ?, choose one of assignHmKey:noArg clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all deviceRename eventL eventS fwUpdate getConfig:noArg getDevInfo:noArg getRegRaw getSerial:noArg getVersion:noArg inhibit:on,off off:noArg on-for-timer on-till on:noArg pair:noArg peerBulk peerIODev press pressS:self01 pressL:self01 raw regBulk regSet reset:noArg sign:on,off statusRequest:noArg templateDel toggle:noArg unpair:noArg  tplSet_self01:SwCondAbove_long,SwCondAbove_short,SwCondBelow_long,SwCondBelow_short,SwOff_long,SwOff_short,SwOnCond_long,SwOnCond_short,SwOn_long,SwOn_short,SwToggle_long,SwToggle_short,autoOff_long,autoOff_short,motionOnSw_long,motionOnSw_short
Unknown argument ?, choose one of assignHmKey:noArg clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all deviceRename fwUpdate getConfig:noArg getDevInfo:noArg getRegRaw getSerial:noArg getVersion:noArg inhibit:on,off off:noArg on-for-timer on-till on:noArg pair:noArg peerBulk peerIODev press raw regBulk regSet reset:noArg sign:on,off statusRequest:noArg templateDel toggle:noArg unpair:noArg
2019.02.12 20:56:27.502 4: WEB8086: /fhem?cmd.modifyWKD_Licht_SW_DIM%3Dmodify%20WKD_Licht_SW_DIM%20KWD_Lichter_S_Type1%20%20model%3DHM-LC-.*%3AFILTER%3Droom%3D1_%5BWKD%5D.*Licht&XHR=1&fw_id=12280 / RL:20 / text/plain; charset=UTF-8 / Content-Encoding: gzip
/ Cache-Control: no-cache, no-store, must-revalidate

2019.02.12 20:56:30.715 4: Connection accepted from WEB8086_192.168.0.10_57998
2019.02.12 20:56:31.510 4: WEB8086_192.168.0.10_57946 GET /fhem?room=02_structure; BUFLEN:0
2019.02.12 20:56:31.867 5: SET: Unknown argument ?, choose one of assignHmKey:noArg clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all deviceRename down fwUpdate getConfig:noArg getDevInfo:noArg getRegRaw getSerial:noArg getVersion:noArg inhibit:on,off off:noArg old:noArg on-for-timer on-till on:noArg pair:noArg pct:slider,0,1,100 peerBulk peerIODev press raw regBulk regSet reset:noArg sign:on,off statusRequest:noArg stop:noArg templateDel toggle:noArg unpair:noArg up
Unknown argument ?, choose one of assignHmKey:noArg clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all deviceRename fwUpdate getConfig:noArg getDevInfo:noArg getRegRaw getSerial:noArg getVersion:noArg inhibit:on,off off:noArg on-for-timer on-till on:noArg pair:noArg peerBulk peerIODev press raw regBulk regSet reset:noArg sign:on,off statusRequest:noArg templateDel toggle:noArg unpair:noArg
Unknown argument ?, choose one of clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all down getConfig:noArg getRegRaw inhibit:on,off off:noArg old:noArg on-for-timer on-till on:noArg pct:slider,0,1,100 peerBulk peerIODev press regBulk regSet sign:on,off statusRequest:noArg stop:noArg templateDel toggle:noArg up
Unknown argument ?, choose one of assignHmKey:noArg clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all deviceRename fwUpdate getConfig:noArg getDevInfo:noArg getRegRaw getSerial:noArg getVersion:noArg inhibit:on,off off:noArg on-for-timer on-till on:noArg pair:noArg peerBulk peerIODev press raw regBulk regSet reset:noArg sign:on,off statusRequest:noArg templateDel toggle:noArg unpair:noArg
Unknown argument ?, choose one of assignHmKey:noArg clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all deviceRename fwUpdate getConfig:noArg getDevInfo:noArg getRegRaw getSerial:noArg getVersion:noArg inhibit:on,off off:noArg on-for-timer on-till on:noArg pair:noArg peerBulk peerIODev press raw regBulk regSet reset:noArg sign:on,off statusRequest:noArg templateDel toggle:noArg unpair:noArg
Unknown argument ?, choose one of assignHmKey:noArg clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all deviceRename eventL eventS fwUpdate getConfig:noArg getDevInfo:noArg getRegRaw getSerial:noArg getVersion:noArg inhibit:on,off off:noArg on-for-timer on-till on:noArg pair:noArg peerBulk peerIODev press pressS:self01 pressL:self01 raw regBulk regSet reset:noArg sign:on,off statusRequest:noArg templateDel toggle:noArg unpair:noArg  tplSet_self01:SwCondAbove_long,SwCondAbove_short,SwCondBelow_long,SwCondBelow_short,SwOff_long,SwOff_short,SwOnCond_long,SwOnCond_short,SwOn_long,SwOn_short,SwToggle_long,SwToggle_short,autoOff_long,autoOff_short,motionOnSw_long,motionOnSw_short
Unknown argument ?, choose one of assignHmKey:noArg clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all deviceRename fwUpdate getConfig:noArg getDevInfo:noArg getRegRaw getSerial:noArg getVersion:noArg inhibit:on,off off:noArg on-for-timer on-till on:noArg pair:noArg peerBulk peerIODev press raw regBulk regSet reset:noArg sign:on,off statusRequest:noArg templateDel toggle:noArg unpair:noArg
2019.02.12 20:56:31.988 4: WEB8086: /fhem?room=02_structure / RL:6633 / text/html; charset=UTF-8 / Content-Encoding: gzip
/ Cache-Control: no-cache, no-store, must-revalidate

2019.02.12 20:56:32.040 1: checkFritzMACpresent (FB3390_32): mac_FC_53_9E_A6_BB_B1 nicht gefunden, abwesend.
2019.02.12 20:56:35.562 4: Connection closed for WEB8086_192.168.0.10_57972: EOF
2019.02.12 20:56:38.963 4: Connection accepted from WEB8086_192.168.0.10_58004
2019.02.12 20:56:39.671 4: Connection accepted from WEB8086_192.168.0.10_58006
2019.02.12 20:56:40.359 4: WEB8086_192.168.0.10_57946 GET /fhem?detail=WKD_Licht_Alle; BUFLEN:0
2019.02.12 20:56:40.458 4: WEB8086: /fhem?detail=WKD_Licht_Alle / RL:5935 / text/html; charset=UTF-8 / Content-Encoding: gzip
/ Cache-Control: no-cache, no-store, must-revalidate

2019.02.12 20:56:40.860 4: WEB8086_192.168.0.10_57946 GET /fhem?cmd=%7BReadingsVal(%22WKD_Licht_Alle%22%2C%22pct%22%2C%22%22)%7D&XHR=1; BUFLEN:0
2019.02.12 20:56:40.862 4: authorize WEB8086/cmd/perl: allowed returned dont care
2019.02.12 20:56:40.865 4: WEB8086: /fhem?cmd=%7BReadingsVal(%22WKD_Licht_Alle%22%2C%22pct%22%2C%22%22)%7D&XHR=1 / RL:21 / text/plain; charset=UTF-8 / Content-Encoding: gzip
/ Cache-Control: no-cache, no-store, must-revalidate

2019.02.12 20:56:40.881 4: Connection closed for WEB8086_192.168.0.10_58004: EOF
2019.02.12 20:56:40.882 4: WEB8086_192.168.0.10_57944 GET /fhem?cmd=%7BAttrVal(%22WKD_Licht_Alle%22%2C%22room%22%2C%22%22)%7D&XHR=1; BUFLEN:0
2019.02.12 20:56:40.883 4: authorize WEB8086/cmd/perl: allowed returned dont care
2019.02.12 20:56:40.887 4: WEB8086: /fhem?cmd=%7BAttrVal(%22WKD_Licht_Alle%22%2C%22room%22%2C%22%22)%7D&XHR=1 / RL:63 / text/plain; charset=UTF-8 / Content-Encoding: gzip
/ Cache-Control: no-cache, no-store, must-revalidate

2019.02.12 20:56:40.951 4: Connection accepted from WEB8086_192.168.0.10_58008
2019.02.12 20:56:46.044 4: Closing inactive connection WEB8086_192.168.0.10_57844
2019.02.12 20:56:46.046 4: Closing inactive connection WEB8086_192.168.0.10_57948
2019.02.12 20:56:46.047 4: Closing inactive connection WEB8086_192.168.0.10_57922
2019.02.12 20:56:46.048 4: Closing inactive connection WEB8086_192.168.0.10_57920
Unmatched ( in regex; marked by <-- HERE in m/^{(ReadingsTimestamp( <-- HERE $DEVICE$/ at ./FHEM/33_readingsGroup.pm line 1383.
2019.02.12 20:56:46 1: reload: Error:Modul 99_myJson deactivated:
Illegal declaration of subroutine main::myUtils_Initialize at ./FHEM/99_myJson.pm line 15.

2019.02.12 20:56:46 1: PERL WARNING: Subroutine myUtils_Initialize redefined at ./FHEM/99_myUtils.pm line 15.
2019.02.12 20:56:47.076 1: Including fhem.cfg
2019.02.12 20:56:47.099 1: PERL WARNING: Subroutine myUtils_Initialize redefined at ./FHEM/99_myHeizung.pm line 15, <$fh> line 17.
2019.02.12 20:56:47.105 1: reload: Error:Modul 99_myJson deactivated:
Illegal declaration of subroutine main::myUtils_Initialize at ./FHEM/99_myJson.pm line 15, <$fh> line 17.

2019.02.12 20:56:47.108 1: Including ./fhemtr/includes/Telegram_bot.cfg
2019.02.12 20:56:54.402 1: cul_ub10_ser2net: Can't connect to 192.168.0.10:2022: Connection refused
2019.02.12 20:56:54.675 1: nanoCul868: Can't open /dev/ttyUSB1: No such file or directory
2019.02.12 20:56:54.680 1: cul_nas_ser2net: Can't connect to 192.168.0.22:2022: Connection refused
2019.02.12 20:57:00.934 1: cul_HM_ser2net: Can't connect to 192.168.0.97:2022: Connection timed out
2019.02.12 20:57:05.143 1: PERL WARNING: Use of uninitialized value $evcode in concatenation (.) or string at ./FHEM/10_IT.pm line 775, <$fh> line 1990.
2019.02.12 20:57:08.377 1: cul_rpi_remote_ser2net_lan: Can't connect to 192.168.0.99:2022: Connection timed out
2019.02.12 20:57:11.385 1: cul_wohn_ser2net_rpi_wlan: Can't connect to 192.168.0.55:2022: Connection timed out
2019.02.12 20:57:14.393 1: cul_rpi_91_ser2net_lan: Can't connect to 192.168.0.91:2022: Connection timed out
2019.02.12 20:57:17.402 1: cul_LAPTOP_ser2net: Can't connect to 192.168.0.25:2022: Connection timed out
2019.02.12 20:57:19.752 1: PERL WARNING: Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/^Value("osmc_tagesschau").{ <-- HERE .*}$/ at ./FHEM/98_expandJSON.pm line 64, <$fh> line 7687.
2019.02.12 20:57:19.754 1: PERL WARNING: Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/^ReadingsVal("osmc_tagesschau","state","").{ <-- HERE .fil*}$/ at ./FHEM/98_expandJSON.pm line 64, <$fh> line 7689.
2019.02.12 20:57:20.742 1: PERL WARNING: can't getattr: Input/output error at FHEM/DevIo.pm line 420.
2019.02.12 20:57:20.743 1: NAD_T773SER: Can't open /dev/ttyS20: Input/output error
2019.02.12 20:57:21.641 1: PERL WARNING: Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/^OSMC95Wohn:jsonResponse:.{ <-- HERE .*}$/ at ./FHEM/98_expandJSON.pm line 64, <$fh> line 13033.
2019.02.12 20:57:21.660 1: Including ./fhem.save
2019.02.12 20:57:22.564 5: CUL_HM HM_29553A queue configRead, register incomplete
2019.02.12 20:57:22.843 5: Update structure 'WKD_Licht_Alle' to undefined because device HM_2E3200 has changed
2019.02.12 20:57:22.890 5: Update structure 'WKD_Licht_SW_DIM' to on because device HM_2E3200 has changed
2019.02.12 20:57:22.936 5: Update structure 'WKD_Licht_Stuct' to undefined because device HM_2E3200 has changed
2019.02.12 20:57:24.485 1: PERL WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE $/ at ./FHEM/33_readingsGroup.pm line 154.
2019.02.12 20:57:24.486 1: PERL WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE $/ at ./FHEM/33_readingsGroup.pm line 160.
2019.02.12 20:57:24.970 5: HM_Components: not on any display, ignoring notify
2019.02.12 20:57:25.170 5: HM_Components: not on any display, ignoring notify
2019.02.12 20:57:25.452 1: usb create starting


Danke fürs Schauen.

VG T
FHEM    5.26.1 Ubuntu 18, FHEM    5.26.1 RPI 3 , Actoren: IT ,Tasmota, ESPEasy,
MAX CUBE, MAX HT, MAX WT, Selbstbau nanoCULs, FS 20,Tasmota, Homematic, FTK, SW. DIM, Smoke,KODI,Squeezebox

Wuppi68

Mein Bauch sagt mir, dass Du als erstes einen Image Backup von der SD Karte machen solltest --> das Log schreit nach Bad Blocks oder (nach dem Backup) das Netzteil mal tauschen ...

scheint ein wenig undeterministisch zu sein
FHEM unter Proxmox als VM

riker1

Hallo
das ist kein Rapsberry
Ein normaler Rechner ubuntu 18 Server mit HDD.

Etwas betagtes Gerät zwar aber läuft auch nicht so viel drauf.
FHEM    5.26.1 Ubuntu 18, FHEM    5.26.1 RPI 3 , Actoren: IT ,Tasmota, ESPEasy,
MAX CUBE, MAX HT, MAX WT, Selbstbau nanoCULs, FS 20,Tasmota, Homematic, FTK, SW. DIM, Smoke,KODI,Squeezebox

riker1

Im jounalctl finde ich :

fhem.service: Main process exited, code=exited, status=255/n/a

12 20:19:51 ub9 sshd[18790]: pam_unix(sshd:session): session opened for user fhem by (uid=0)
Feb 12 20:19:51 ub9 systemd[1]: Started Session 364 of user fhem.
Feb 12 20:19:51 ub9 systemd-logind[1075]: New session 364 of user fhem.
Feb 12 20:20:58 ub9 sshd[18648]: pam_unix(sshd:session): session closed for user fhem
Feb 12 20:21:00 ub9 sshd[18790]: pam_unix(sshd:session): session closed for user fhem
Feb 12 20:27:18 ub9 sudo[19621]: zwh100 : TTY=pts/2 ; PWD=/home/zwh100 ; USER=root ; COMMAND=/bin/systemctl status -l fhem
Feb 12 20:29:27 ub9 sudo[19810]: zwh100 : TTY=pts/2 ; PWD=/home/zwh100 ; USER=root ; COMMAND=/bin/systemctl status -l fhem
Feb 12 20:33:02 ub9 sudo[20173]: zwh100 : TTY=pts/2 ; PWD=/home/zwh100 ; USER=root ; COMMAND=/bin/systemctl status -l fhem
Feb 12 20:49:31 ub9 sudo[21711]: zwh100 : TTY=pts/2 ; PWD=/home/zwh100 ; USER=root ; COMMAND=/bin/systemctl status -l fhem
Feb 12 20:51:04 ub9 sudo[21862]: zwh100 : TTY=pts/2 ; PWD=/home/zwh100 ; USER=root ; COMMAND=/bin/systemctl status -l fhem
Feb 12 20:51:08 ub9 sudo[21866]: zwh100 : TTY=pts/2 ; PWD=/home/zwh100 ; USER=root ; COMMAND=/bin/systemctl status -l fhem
Feb 12 20:56:46 ub9 systemd[1]: fhem.service: Main process exited, code=exited, status=255/n/a
Feb 12 20:56:46 ub9 systemd[1]: fhem.service: Failed with result 'exit-code'.
Feb 12 20:56:46 ub9 systemd[1]: fhem.service: Service hold-off time over, scheduling restart.
Feb 12 20:56:46 ub9 systemd[1]: fhem.service: Scheduled restart job, restart counter is at 3.
Feb 12 20:57:38 ub9 sudo[22482]: zwh100 : TTY=pts/2 ; PWD=/home/zwh100 ; USER=root ; COMMAND=/bin/systemctl status -l fhem
Feb 12 20:58:00 ub9 sshd[22486]: Accepted publickey for fhem from 192.168.0.10 port 46925 ssh2: RSA SHA256:xxx
Feb 12 20:58:00 ub9 sshd[22486]: pam_unix(sshd:session): session opened for user fhem by (uid=0)
Feb 12 20:58:00 ub9 systemd-logind[1075]: New session 365 of user fhem.
Feb 12 20:58:00 ub9 systemd[1]: Started Session 365 of user fhem.
Feb 12 20:59:07 ub9 sshd[22486]: pam_unix(sshd:session): session closed for user fhem
Feb 12 21:12:36 ub9 sudo[23872]: zwh100 : TTY=pts/2 ; PWD=/home/zwh100 ; USER=root ; COMMAND=/bin/systemctl status -l fhem
Feb 12 21:12:39 ub9 sudo[23891]: zwh100 : TTY=pts/2 ; PWD=/home/zwh100 ; USER=root ; COMMAND=/bin/systemctl status -l fhem
Feb 12 21:12:41 ub9 sudo[23902]: zwh100 : TTY=pts/2 ; PWD=/home/zwh100 ; USER=root ; COMMAND=/bin/systemctl status -l fhem
Feb 12 21:13:38 ub9 systemd[1]: fhem.service: Main process exited, code=exited, status=255/n/a
Feb 12 21:13:38 ub9 systemd[1]: fhem.service: Failed with result 'exit-code'.
Feb 12 21:13:38 ub9 systemd[1]: fhem.service: Service hold-off time over, scheduling restart.
Feb 12 21:13:38 ub9 systemd[1]: fhem.service: Scheduled restart job, restart counter is at 4.
Feb 12 21:13:48 ub9 sudo[24022]: zwh100 : TTY=pts/2 ; PWD=/home/zwh100 ; USER=root ; COMMAND=/bin/systemctl status -l fhem
FHEM    5.26.1 Ubuntu 18, FHEM    5.26.1 RPI 3 , Actoren: IT ,Tasmota, ESPEasy,
MAX CUBE, MAX HT, MAX WT, Selbstbau nanoCULs, FS 20,Tasmota, Homematic, FTK, SW. DIM, Smoke,KODI,Squeezebox

riker1

top fhem liefert:



op - 21:18:57 up 7 days,  3:20,  1 user,  load average: 1.30, 0.90, 0.84
Tasks: 141 total,   2 running,  98 sleeping,   0 stopped,   0 zombie
%Cpu(s): 20.2 us,  4.6 sy,  0.0 ni, 68.2 id,  6.6 wa,  0.0 hi,  0.3 si,  0.0 st
KiB Mem :  2040980 total,   628588 free,   861872 used,   550520 buff/cache
KiB Swap:  2097148 total,  1503484 free,   593664 used.  1003136 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND                                                                                                 
24287 fhem      20   0  225192 137052   8856 S 19.4  6.7   0:57.57 perl                                                                                                   
24511 fhem      20   0  225192 131412   3216 S  1.0  6.4   0:00.03 perl                                                                                                   
24512 fhem      20   0   15100   1068    960 S  0.3  0.1   0:00.01 ping                                                                                                   
10054 fhem      20   0   76768   6952   5916 S  0.0  0.3   0:00.08 systemd                                                                                                 
10055 fhem      20   0  272248   2680      0 S  0.0  0.1   0:00.00 (sd-pam)                                                                                               
10230 fhem      20   0  120576   3420   2344 S  0.0  0.2   0:00.01 sshd                                                                                                   
10231 fhem      20   0   13060   1956   1796 S  0.0  0.1   0:00.00 sftp-server
FHEM    5.26.1 Ubuntu 18, FHEM    5.26.1 RPI 3 , Actoren: IT ,Tasmota, ESPEasy,
MAX CUBE, MAX HT, MAX WT, Selbstbau nanoCULs, FS 20,Tasmota, Homematic, FTK, SW. DIM, Smoke,KODI,Squeezebox

Wuppi68

hast Du vorher Updates gemacht?
Sind noch Updates ausstehend?
Wann hast Du das letzte FHEM Update gemacht?
Irgendwelche Module zurück gehalten?
FHEM unter Proxmox als VM

riker1

#6
Hallo

update glaube ich letzte Woche.
checke gleich mal
zurückgehalten habe ich nur ein Modul das ich angepasst habe für Denon.

Wo sehe ich wann das letzte Update war?




Bin mir eigentlich ziemlich sicher das es mit der Structure zusammenhängt.

Habe hier eine mit Homematic Switches und Dimmern kombiniert.

Fast bei jedem update dieser Structure erfolgt ein restart

defmod WKD_Licht_SW_DIM structure KWD_Lichter_S_Type1  model=HM-LC-.*:FILTER=room=1_[WKD].*Licht
attr WKD_Licht_SW_DIM room 02_structure,0_test,1_Wohnzimmer,Z_Control
attr WKD_Licht_SW_DIM verbose 5


hier ist der Status oft undefined, glaube wegen dem Dimmer.
...

Bin hier am recherchieren und neu in readingsgroup und structure unterwegs..

Hilft das?

Danke

FHEM    5.26.1 Ubuntu 18, FHEM    5.26.1 RPI 3 , Actoren: IT ,Tasmota, ESPEasy,
MAX CUBE, MAX HT, MAX WT, Selbstbau nanoCULs, FS 20,Tasmota, Homematic, FTK, SW. DIM, Smoke,KODI,Squeezebox

riker1

Habe auch eine readingsgruppe zur Kontrolle der HM Geräte.

die structure mit den Dimmern ist undefined

defmod WKD_Licht_SW_DIM structure KWD_Lichter_S_Type1  model=HM-LC-.*:FILTER=room=1_[WKD].*Licht


Dimmer haben state 50 , wegen den pct. Werten


HM_Wo_Ku_Lichter
Gerät
State
Model
S/N
HM_DIM2_WZ_Sofa_Leselampe_HM_1DCC51_JEQ0193659
55
HM-LC-Dim1T-Pl-2
JEQ0193659
HM_SW_HM_29553A_LTK0038886_Küche_Schrank
on
HM-LC-SW1-PL2
LTK0038886
HM_2C5AA7_Dim_Lampe_TV_Channel0_DIMMER
chn:on phys:80
HM-LC-Dim1T-Pl-3
HM_SW_Lichterkette_klein_HM_2E3200_LTK0071739
on
HM-LC-SW1-PL2
LTK0071739
HM_SW_Lichterkette_lang_HM_4A29F9_NEQ0181196
on
HM-LC-SW1-PL2
NEQ0181196
HM_1_Küche-fkt_NEQ0179861_HM_4A2F49
on
HM-LC-SW1-PL2
NEQ0179861
HM_SW_SL-KLAVIER-_NEQ0179540_HM_4A3089
on
HM-LC-SW1-PL2
NEQ0179540



Macht das irgendwie Sinn in dem Kontext?
FHEM    5.26.1 Ubuntu 18, FHEM    5.26.1 RPI 3 , Actoren: IT ,Tasmota, ESPEasy,
MAX CUBE, MAX HT, MAX WT, Selbstbau nanoCULs, FS 20,Tasmota, Homematic, FTK, SW. DIM, Smoke,KODI,Squeezebox

Wuppi68

starte mal FHEM mache ein SAVE danach SHUTDOWN und noch einmal Starten
FHEM unter Proxmox als VM

riker1

Hallo

das habe ich schon mehrfach gemacht denke ich .

shutdown , save mache ich laufend -
Fhem started nach shutdown automatisch.


Habe aber auch den fhem process  mit stop start  re-gestarted

FHEM    5.26.1 Ubuntu 18, FHEM    5.26.1 RPI 3 , Actoren: IT ,Tasmota, ESPEasy,
MAX CUBE, MAX HT, MAX WT, Selbstbau nanoCULs, FS 20,Tasmota, Homematic, FTK, SW. DIM, Smoke,KODI,Squeezebox

Wuppi68

mach am besten erst einmal ein FHEM Update ... neSciherung sollte ja vorhanden sein
FHEM unter Proxmox als VM

riker1

FHEM    5.26.1 Ubuntu 18, FHEM    5.26.1 RPI 3 , Actoren: IT ,Tasmota, ESPEasy,
MAX CUBE, MAX HT, MAX WT, Selbstbau nanoCULs, FS 20,Tasmota, Homematic, FTK, SW. DIM, Smoke,KODI,Squeezebox

riker1

Hallo

so nun alles frisch.
werde das mal weiter beobachten.

Melde mich dann
FHEM    5.26.1 Ubuntu 18, FHEM    5.26.1 RPI 3 , Actoren: IT ,Tasmota, ESPEasy,
MAX CUBE, MAX HT, MAX WT, Selbstbau nanoCULs, FS 20,Tasmota, Homematic, FTK, SW. DIM, Smoke,KODI,Squeezebox

riker1

Hatte gerade wieder einen neustart


glaube es liegt hieran:

defmod MAX_Mode_Problem readingsGroup <Name>,<Temp>,<DesiredTemp>,<mode>,<t-time> MAX.*:temperature,state,mode,{(ReadingsTimestamp($DEVICE,'temperature',''))}
attr MAX_Mode_Problem mapping %ALIAS
attr MAX_Mode_Problem room 02_structure
attr MAX_Mode_Problem verbose 5


Im log dazu
2019.02.13 10:30:29.466 1: usb create end
2019.02.13 10:30:29.581 0: Featurelevel: 5.9
2019.02.13 10:30:29.581 0: Server started with 1253 defined entities (fhem.pl:18497/2019-02-05 perl:5.026001 os:linux user:fhem pid:2409)
MAX_Mode_Problem
2019.02.13 10:30:35.108 5: MAX_Mode_Problem: not on any display, ignoring notify

FHEM    5.26.1 Ubuntu 18, FHEM    5.26.1 RPI 3 , Actoren: IT ,Tasmota, ESPEasy,
MAX CUBE, MAX HT, MAX WT, Selbstbau nanoCULs, FS 20,Tasmota, Homematic, FTK, SW. DIM, Smoke,KODI,Squeezebox

Beta-User

Was sicher auch nicht optimal ist, sind die Fehlermeldungen bei der Initialisierung der diversen myUtils-Dateien.
Siehe dazu im Wiki:
ZitatDer Name der Programmdatei muss mit dem Namen der Initialize-Routine übereinstimmen. Wenn Sie Ihr Programm also 99_Werkzeugkasten.pm nennen, muss die im code dargestellte initialize-Routine sub Werkzeugkasten_Initialize heißen.

Ansonsten wird ein Haufen Zeug nicht gefunden, darf nicht gelesen werden usw.. Da solltest du dich erst mal kümmern. Wenn es keine funktionierenden IO's gibt, brauchst du dich nicht zu wundern, dass es auch keine auszuwertenden Daten der Devices gibt, die darüber reinkommen.

Und schalte das usb-Autocreate ab...
Server: HP-elitedesk@Debian 12, aktuelles FHEM@ConfigDB | CUL_HM (VCCU) | MQTT2: ZigBee2mqtt, MiLight@ESP-GW, BT@OpenMQTTGw | ZWave | SIGNALduino | MapleCUN | RHASSPY
svn: u.a Weekday-&RandomTimer, Twilight,  div. attrTemplate-files, MySensors