Guten Tag,
ich habe das FHEM auf einem CentOS Server nach folgender Anleitung installiert:
http://blog.teddy-net.de/heimautomatisierungsserver-fhem-installieren-und-als-systemd-service-einrichten
Laut Status läuft FHEM auch und in der Firewall wurden die Ports 8083-8085 Freigegeben, nur leider erreiche ich das FHEM nicht über den Browser, dort zeigt er mir einen Seiten Ladefehler an. Was mich stutzig macht ist, das weder bei der Installation diverser Module die man benötigt noch beim starten von FHEM Fehlermeldungen auftreten alles ist okay.
Ich freue mich wenn mir jemand bei diesem bestimmt einfachen Problem behilflich sein kann.
Vielen Dank.
Willkommen im Forum!
Vorab: Portforwarding ist keine gute Idee, und ohne passendes allowed wird alles abgewehrt, was nicht im lokalen Netz ist. Besser eine andere Lösung wählen (vpn z.B.).
Ansonsten: Was steht im Log?
Gibt es weitere Services, die evtl. die Ports belegen?
Vielleicht hilfreich:
https://wiki.fhem.de/wiki/FHEM_startet_nicht_-_Tipps_zur_Fehlersuche
Ansonsten noch (zu CentOS gibt es wohl nichts passendes, aber grundsätzlich): https://wiki.fhem.de/wiki/Dokumentationsstruktur
(Will heißen: Blogs sollte man sehr mir Vorsicht genießen, lieber erst die FHEM-Quellen zu Rate ziehen).
Gruß,
Beta-User
Hallo,
Zitat von: vtruckers_dehabe das FHEM auf einem CentOS Server
Läuft bei mir auch ohne Probleme auf einer CentOS-VM
Zitat von: vtruckers_deLaut Status läuft FHEM auch und in der Firewall wurden die Ports 8083-8085 Freigegeben
Von welcher Firewall reden wir denn hier ?
-NAT
-IPtables
-SELinux
Was ergibt denn ein:
netstat -4tulpenWerden da die erwarteten Ports gelistet ?
Gruß,
JudgeDredd
ZitatVon welcher Firewall reden wir denn hier ?
-NAT
-IPtables
-SELinux
FirewallD
ZitatWas ergibt denn ein:
Code: [Auswählen]
netstat -4tulpen
Werden da die erwarteten Ports gelistet ?
Ergebniss:
Aktive Internetverbindungen (Nur Server)
Proto Recv-Q Send-Q Local Address Foreign Address State Benutzer Inode PID/Program name
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 0 29504 2911/dovecot
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 0 29532 2911/dovecot
tcp 0 0 212.83.56.21:80 0.0.0.0:* LISTEN 0 31470 3121/nginx: master
tcp 0 0 0.0.0.0:8880 0.0.0.0:* LISTEN 0 30974 2973/sw-cp-server:
tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 0 33411 3570/master
tcp 0 0 0.0.0.0:8083 0.0.0.0:* LISTEN 0 845207 10556/perl
tcp 0 0 172.17.0.1:53 0.0.0.0:* LISTEN 25 33906 2942/named
tcp 0 0 212.83.56.21:53 0.0.0.0:* LISTEN 25 30968 2942/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 25 30966 2942/named
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 30856 2908/sshd
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 0 33328 876/smtpd
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 25 31137 2942/named
tcp 0 0 127.0.0.1:12346 0.0.0.0:* LISTEN 0 33399 3570/master
tcp 0 0 212.83.56.21:443 0.0.0.0:* LISTEN 0 31468 3121/nginx: master
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 0 30973 2973/sw-cp-server:
tcp 0 0 0.0.0.0:4190 0.0.0.0:* LISTEN 0 29489 2911/dovecot
tcp 0 0 127.0.0.1:12768 0.0.0.0:* LISTEN 89 29361 2907/psa-pc-remote
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 0 29534 2911/dovecot
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 0 29506 2911/dovecot
udp 0 0 172.17.0.1:53 0.0.0.0:* 25 33905 2942/named
udp 0 0 212.83.56.21:53 0.0.0.0:* 25 30967 2942/named
udp 0 0 127.0.0.1:53 0.0.0.0:* 25 30964 2942/named
udp 0 0 127.0.0.1:323 0.0.0.0:* 0 25039 2488/chronyd
ZitatGibt es weitere Services, die evtl. die Ports belegen?
Port 8443 wird von Plesk belegt, sonst nichts.
Folgende Meldungen erhalte ich wenn ich FHEM zum laufen bringen möchte:
Zitatsystemctl status fhem.service
● fhem.service - FHEM
Loaded: loaded (/etc/systemd/system/fhem.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sa 2019-05-11 12:07:18 CEST; 5min ago
Process: 3052 ExecStart=/usr/bin/perl /srv/fhem/fhem.pl /srv/fhem/fhem.cfg (code=exited, status=1/FAILURE)
Main PID: 3157 (code=exited, status=0/SUCCESS)
Mai 11 12:07:18 webdata.vtruckers.de systemd[1]: Starting FHEM...
Mai 11 12:07:18 webdata.vtruckers.de perl[3052]: 2019.05.11 12:07:18.542 1: Including /srv/fhem/fhem.cfg
Mai 11 12:07:18 webdata.vtruckers.de perl[3052]: 2019.05.11 12:07:18.632 1: WEB: Can't open server port at 8083: Die Adresse wird bereits verwendet. Exiting.
Mai 11 12:07:18 webdata.vtruckers.de systemd[1]: fhem.service: control process exited, code=exited status=1
Mai 11 12:07:18 webdata.vtruckers.de systemd[1]: Failed to start FHEM.
Mai 11 12:07:18 webdata.vtruckers.de systemd[1]: Unit fhem.service entered failed state.
Mai 11 12:07:18 webdata.vtruckers.de systemd[1]: fhem.service failed.
systemctl start fhem
Job for fhem.service failed because the control process exited with error code. See "systemctl status fhem.service" and "journalctl -xe" for details.
Wenn ich das Perl Script ausführe erscheint:
perl fhem.pl fhem.cfg
2019.05.11 12:18:59.760 1: Including fhem.cfg
2019.05.11 12:18:59.826 1: WEB: Can't open server port at 8083: Die Adresse wird bereits verwendet. Exiting.
Hallo,
Zitat von: vtruckers_deFirewallD
und SELinux ist deaktiviert ?
Zitat von: vtruckers_desystemctl start fhem
mit "systemctl restart fhem" kannst Du den Dienst neu starten, dann sollte es auch keine Fehlermeldung bzgl. eines bereits laufenden Prozesses geben.
tcp 0 0 0.0.0.0:8083 0.0.0.0:* LISTEN 0 845207 10556/perlWie Du siehst, ist der FHEM-Service auf Port 8083 am laufen.
Sofern Deine Aussage bezüglich der erfolgten Firewall-Einstellung stimmt, sollte es funktionieren.
Wie @Beta-User schon schreibt. Was ist mit dem "allowfrom"-Attribut im FHEMWEB Device ?
Gruß,
JudgeDredd
FHEM ist nicht aufrufbar und läuft auch nicht.
Zitat
● fhem.service - FHEM
Loaded: loaded (/etc/systemd/system/fhem.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sa 2019-05-11 13:22:03 CEST; 3s ago
Process: 10026 ExecStart=/usr/bin/perl /srv/fhem/fhem.pl /srv/fhem/fhem.cfg (code=exited, status=0/SUCCESS)
Main PID: 10027 (code=exited, status=1/FAILURE)
Mai 11 13:22:03 webdata.vtruckers.de systemd[1]: Starting FHEM...
Mai 11 13:22:03 webdata.vtruckers.de systemd[1]: Started FHEM.
Mai 11 13:22:03 webdata.vtruckers.de systemd[1]: fhem.service: main process exited, code=exited, status=1/FAILURE
Mai 11 13:22:03 webdata.vtruckers.de systemd[1]: Unit fhem.service entered failed state.
Mai 11 13:22:03 webdata.vtruckers.de systemd[1]: fhem.service failed.
Aufrufen über 8083 logischerweise dann ja nicht möglich, hat aber auch nicht geklappt wo FHEM Vorgestern noch lief.
Zitatund SELinux ist deaktiviert ?
Ja
Zitat von: vtruckers_deFHEM ist nicht aufrufbar und läuft auch nicht.
Was sagt das FHEM-Log ?
Gibt es mehr Infos, wenn Du den Prozess beendest und FHEM direkt startest mit:
/usr/bin/perl /srv/fhem/fhem.pl /srv/fhem/fhem.cfgWas ist mit der Frage zum "allowfrom"-Attribut ?
Firewalld klingt nach einem Service. Beende den mal
systemctl stop firewalld
Oder ähnlich. Musst mal schauen. Oder konfiguriere die firewall entsprechend.
Und die Aussage "FHEM läuft" ist seeeehr pauschal. Gib uns zusätzlich bitte mal die Ausgabe von:
ps aux | grep [f]hem
ZitatWas ist mit der Frage zum "allowfrom"-Attribut ?
Finde ich wo? ;)
ZitatUnd die Aussage "FHEM läuft" ist seeeehr pauschal. Gib uns zusätzlich bitte mal die Ausgabe von:
Code: [Auswählen]
ps aux | grep [f]hem
Passiert nichts, es erscheint nur eine neue Leere Zeile.
ZitatFirewalld klingt nach einem Service. Beende den mal
Erledigt, ich habe auch alle Einträge nochmals gelöscht und wieder über die entsprechende Zone eingetragen, dennoch kann ich auch in der "public" Zone nicht auf den Port Zugreifen.
ZitatGibt es mehr Infos, wenn Du den Prozess beendest und FHEM direkt startest mit:
Code: [Auswählen]
/usr/bin/perl /srv/fhem/fhem.pl /srv/fhem/fhem.cfg
Passiert auch nichts, es erscheint nur eine neue Leere Zeile wo ich wieder einen Befehl eingeben kann.
ZitatWas sagt das FHEM-Log ?
Wie komme ich am besten an die Log?
Vielen Dank für eure Antworten. :) ;)
Lies mal den QuickStart im wiki WG. allowed.
Dann scheint noch was anderes Port 8083 zu belegen. Also: einen der services weg v. diesem Port, ggf. fhem.xdg ausnahmsweise editieren...
Steht aber vermutlich im log. Danach war schon gefragt gewesen...
Das ist meine .log
Zitat2019.05.09 16:38:04 1: Including /srv/fhem/fhem.cfg
2019.05.09 16:38:05 3: WEB: port 8083 opened
2019.05.09 16:38:05 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2019.05.09 16:38:05 1: usb create starting
2019.05.09 16:38:05 1: PERL WARNING: Can't exec "lsusb": Datei oder Verzeichnis nicht gefunden at ./FHEM/98_autocreate.pm line 537.
2019.05.09 16:38:05 3: Probing CUL device /dev/ttyS0
2019.05.09 16:38:05 1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:38:05 1: CUL: Can't connect to /dev/ttyS0: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:38:05 3: Probing CUL device /dev/ttyS1
2019.05.09 16:38:05 1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:38:05 1: CUL: Can't connect to /dev/ttyS1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:38:05 3: Probing CUL device /dev/ttyS2
2019.05.09 16:38:05 1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:38:05 1: CUL: Can't connect to /dev/ttyS2: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:38:05 3: Probing CUL device /dev/ttyS3
2019.05.09 16:38:05 1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:38:05 1: CUL: Can't connect to /dev/ttyS3: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:38:05 1: usb create end
2019.05.09 16:38:05 0: Featurelevel: 5.8
2019.05.09 16:38:05 0: Server started with 6 defined entities (fhem.pl:17329/2018-09-12 perl:5.016003 os:linux user:root pid:12521)
2019.05.09 16:38:39 1: Connection refused from the non-local address 93.206.247.138:62118, as there is no working allowed instance defined for it
2019.05.09 16:38:39 1: Connection refused from the non-local address 93.206.247.138:62119, as there is no working allowed instance defined for it
2019.05.09 16:38:39 1: Connection refused from the non-local address 93.206.247.138:62120, as there is no working allowed instance defined for it
2019.05.09 16:38:39 1: Connection refused from the non-local address 93.206.247.138:62121, as there is no working allowed instance defined for it
2019.05.09 16:38:39 1: Connection refused from the non-local address 93.206.247.138:62122, as there is no working allowed instance defined for it
2019.05.09 16:38:39 1: Connection refused from the non-local address 93.206.247.138:62123, as there is no working allowed instance defined for it
2019.05.09 16:38:39 1: Connection refused from the non-local address 93.206.247.138:62124, as there is no working allowed instance defined for it
2019.05.09 16:38:39 1: Connection refused from the non-local address 93.206.247.138:62125, as there is no working allowed instance defined for it
2019.05.09 16:38:39 1: Connection refused from the non-local address 93.206.247.138:62126, as there is no working allowed instance defined for it
2019.05.09 16:38:39 1: Connection refused from the non-local address 93.206.247.138:62127, as there is no working allowed instance defined for it
2019.05.09 16:39:15 1: Connection refused from the non-local address 93.206.247.138:62131, as there is no working allowed instance defined for it
2019.05.09 16:39:15 1: Connection refused from the non-local address 93.206.247.138:62132, as there is no working allowed instance defined for it
2019.05.09 16:39:15 1: Connection refused from the non-local address 93.206.247.138:62133, as there is no working allowed instance defined for it
2019.05.09 16:39:15 1: Connection refused from the non-local address 93.206.247.138:62134, as there is no working allowed instance defined for it
2019.05.09 16:39:15 1: Connection refused from the non-local address 93.206.247.138:62135, as there is no working allowed instance defined for it
2019.05.09 16:39:15 1: Connection refused from the non-local address 93.206.247.138:62136, as there is no working allowed instance defined for it
2019.05.09 16:39:15 1: Connection refused from the non-local address 93.206.247.138:62137, as there is no working allowed instance defined for it
2019.05.09 16:39:15 1: Connection refused from the non-local address 93.206.247.138:62138, as there is no working allowed instance defined for it
2019.05.09 16:39:15 1: Connection refused from the non-local address 93.206.247.138:62139, as there is no working allowed instance defined for it
2019.05.09 16:39:15 1: Connection refused from the non-local address 93.206.247.138:62140, as there is no working allowed instance defined for it
2019.05.09 16:40:10 1: Connection refused from the non-local address 93.206.247.138:62144, as there is no working allowed instance defined for it
2019.05.09 16:40:10 1: Connection refused from the non-local address 93.206.247.138:62145, as there is no working allowed instance defined for it
2019.05.09 16:40:10 1: Connection refused from the non-local address 93.206.247.138:62146, as there is no working allowed instance defined for it
2019.05.09 16:40:10 1: Connection refused from the non-local address 93.206.247.138:62147, as there is no working allowed instance defined for it
2019.05.09 16:40:10 1: Connection refused from the non-local address 93.206.247.138:62148, as there is no working allowed instance defined for it
2019.05.09 16:40:10 1: Connection refused from the non-local address 93.206.247.138:62149, as there is no working allowed instance defined for it
2019.05.09 16:40:10 1: Connection refused from the non-local address 93.206.247.138:62150, as there is no working allowed instance defined for it
2019.05.09 16:40:10 1: Connection refused from the non-local address 93.206.247.138:62151, as there is no working allowed instance defined for it
2019.05.09 16:40:11 1: Connection refused from the non-local address 93.206.247.138:62152, as there is no working allowed instance defined for it
2019.05.09 16:40:11 1: Connection refused from the non-local address 93.206.247.138:62153, as there is no working allowed instance defined for it
2019.05.09 16:51:12 1: Connection refused from the non-local address 93.206.247.138:62206, as there is no working allowed instance defined for it
2019.05.09 16:51:12 1: Connection refused from the non-local address 93.206.247.138:62207, as there is no working allowed instance defined for it
2019.05.09 16:51:12 1: Connection refused from the non-local address 93.206.247.138:62208, as there is no working allowed instance defined for it
2019.05.09 16:51:12 1: Connection refused from the non-local address 93.206.247.138:62209, as there is no working allowed instance defined for it
2019.05.09 16:51:13 1: Connection refused from the non-local address 93.206.247.138:62210, as there is no working allowed instance defined for it
2019.05.09 16:51:13 1: Connection refused from the non-local address 93.206.247.138:62211, as there is no working allowed instance defined for it
2019.05.09 16:51:13 1: Connection refused from the non-local address 93.206.247.138:62212, as there is no working allowed instance defined for it
2019.05.09 16:51:13 1: Connection refused from the non-local address 93.206.247.138:62213, as there is no working allowed instance defined for it
2019.05.09 16:51:13 1: Connection refused from the non-local address 93.206.247.138:62214, as there is no working allowed instance defined for it
2019.05.09 16:51:13 1: Connection refused from the non-local address 93.206.247.138:62215, as there is no working allowed instance defined for it
2019.05.09 16:55:27 1: Connection refused from the non-local address 93.206.247.138:62309, as there is no working allowed instance defined for it
2019.05.09 16:55:27 1: Connection refused from the non-local address 93.206.247.138:62310, as there is no working allowed instance defined for it
2019.05.09 16:55:27 1: Connection refused from the non-local address 93.206.247.138:62311, as there is no working allowed instance defined for it
2019.05.09 16:55:27 1: Connection refused from the non-local address 93.206.247.138:62312, as there is no working allowed instance defined for it
2019.05.09 16:55:28 1: Connection refused from the non-local address 93.206.247.138:62313, as there is no working allowed instance defined for it
2019.05.09 16:55:28 1: Connection refused from the non-local address 93.206.247.138:62314, as there is no working allowed instance defined for it
2019.05.09 16:55:28 1: Connection refused from the non-local address 93.206.247.138:62315, as there is no working allowed instance defined for it
2019.05.09 16:55:28 1: Connection refused from the non-local address 93.206.247.138:62316, as there is no working allowed instance defined for it
2019.05.09 16:55:28 1: Connection refused from the non-local address 93.206.247.138:62317, as there is no working allowed instance defined for it
2019.05.09 16:55:28 1: Connection refused from the non-local address 93.206.247.138:62318, as there is no working allowed instance defined for it
2019.05.09 16:58:39 0: Server shutdown
2019.05.09 16:58:39 1: Including /srv/fhem/fhem.cfg
2019.05.09 16:58:39 3: WEB: port 8083 opened
2019.05.09 16:58:39 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2019.05.09 16:58:39 1: Including ./log/fhem.save
2019.05.09 16:58:39 1: usb create starting
2019.05.09 16:58:39 1: PERL WARNING: Can't exec "lsusb": Datei oder Verzeichnis nicht gefunden at ./FHEM/98_autocreate.pm line 537.
2019.05.09 16:58:39 3: Probing CUL device /dev/ttyS0
2019.05.09 16:58:39 1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:58:39 1: CUL: Can't connect to /dev/ttyS0: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:58:39 3: Probing CUL device /dev/ttyS1
2019.05.09 16:58:39 1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:58:39 1: CUL: Can't connect to /dev/ttyS1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:58:39 3: Probing CUL device /dev/ttyS2
2019.05.09 16:58:39 1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:58:39 1: CUL: Can't connect to /dev/ttyS2: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:58:39 3: Probing CUL device /dev/ttyS3
2019.05.09 16:58:39 1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:58:39 1: CUL: Can't connect to /dev/ttyS3: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 16:58:39 1: usb create end
2019.05.09 16:58:39 0: Featurelevel: 5.8
2019.05.09 16:58:39 0: Server started with 6 defined entities (fhem.pl:17329/2018-09-12 perl:5.016003 os:linux user:root pid:15038)
2019.05.09 16:58:51 1: Connection refused from the non-local address 93.206.247.138:62370, as there is no working allowed instance defined for it
2019.05.09 16:58:51 1: Connection refused from the non-local address 93.206.247.138:62371, as there is no working allowed instance defined for it
2019.05.09 16:58:51 1: Connection refused from the non-local address 93.206.247.138:62372, as there is no working allowed instance defined for it
2019.05.09 16:58:51 1: Connection refused from the non-local address 93.206.247.138:62373, as there is no working allowed instance defined for it
2019.05.09 16:58:51 1: Connection refused from the non-local address 93.206.247.138:62374, as there is no working allowed instance defined for it
2019.05.09 16:58:51 1: Connection refused from the non-local address 93.206.247.138:62375, as there is no working allowed instance defined for it
2019.05.09 16:58:51 1: Connection refused from the non-local address 93.206.247.138:62376, as there is no working allowed instance defined for it
2019.05.09 16:58:52 1: Connection refused from the non-local address 93.206.247.138:62377, as there is no working allowed instance defined for it
2019.05.09 16:58:52 1: Connection refused from the non-local address 93.206.247.138:62378, as there is no working allowed instance defined for it
2019.05.09 16:58:52 1: Connection refused from the non-local address 93.206.247.138:62379, as there is no working allowed instance defined for it
2019.05.09 17:01:50 0: Server shutdown
2019.05.09 17:04:11 1: Including /srv/fhem/fhem.cfg
2019.05.09 17:04:11 3: WEB: port 8083 opened
2019.05.09 17:04:11 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2019.05.09 17:04:11 1: Including ./log/fhem.save
2019.05.09 17:04:11 1: usb create starting
2019.05.09 17:04:11 1: PERL WARNING: Can't exec "lsusb": Datei oder Verzeichnis nicht gefunden at ./FHEM/98_autocreate.pm line 537.
2019.05.09 17:04:11 3: Probing CUL device /dev/ttyS0
2019.05.09 17:04:11 1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 17:04:11 1: CUL: Can't connect to /dev/ttyS0: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 17:04:11 3: Probing CUL device /dev/ttyS1
2019.05.09 17:04:11 1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 17:04:11 1: CUL: Can't connect to /dev/ttyS1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 17:04:11 3: Probing CUL device /dev/ttyS2
2019.05.09 17:04:11 1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 17:04:11 1: CUL: Can't connect to /dev/ttyS2: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 17:04:11 3: Probing CUL device /dev/ttyS3
2019.05.09 17:04:11 1: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 17:04:11 1: CUL: Can't connect to /dev/ttyS3: Can't locate Device/SerialPort.pm in @INC (@INC contains: . /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 ./FHEM) at ./FHEM/DevIo.pm line 418.
2019.05.09 17:04:11 1: usb create end
2019.05.09 17:04:11 0: Featurelevel: 5.8
2019.05.09 17:04:11 0: Server started with 6 defined entities (fhem.pl:17329/2018-09-12 perl:5.016003 os:linux user:root pid:16010)
2019.05.09 17:04:49 1: Connection refused from the non-local address 93.206.247.138:62541, as there is no working allowed instance defined for it
2019.05.09 17:04:49 1: Connection refused from the non-local address 93.206.247.138:62542, as there is no working allowed instance defined for it
2019.05.09 17:04:49 1: Connection refused from the non-local address 93.206.247.138:62543, as there is no working allowed instance defined for it
2019.05.09 17:04:49 1: Connection refused from the non-local address 93.206.247.138:62544, as there is no working allowed instance defined for it
2019.05.09 17:04:49 1: Connection refused from the non-local address 93.206.247.138:62545, as there is no working allowed instance defined for it
2019.05.09 17:04:49 1: Connection refused from the non-local address 93.206.247.138:62546, as there is no working allowed instance defined for it
2019.05.09 17:04:49 1: Connection refused from the non-local address 93.206.247.138:62547, as there is no working allowed instance defined for it
2019.05.09 17:04:49 1: Connection refused from the non-local address 93.206.247.138:62548, as there is no working allowed instance defined for it
2019.05.09 17:04:49 1: Connection refused from the non-local address 93.206.247.138:62549, as there is no working allowed instance defined for it
2019.05.09 17:04:49 1: Connection refused from the non-local address 93.206.247.138:62550, as there is no working allowed instance defined for it
2019.05.09 17:06:02 1: Connection refused from the non-local address 93.206.247.138:62582, as there is no working allowed instance defined for it
2019.05.09 17:06:02 1: Connection refused from the non-local address 93.206.247.138:62583, as there is no working allowed instance defined for it
2019.05.09 17:06:02 1: Connection refused from the non-local address 93.206.247.138:62584, as there is no working allowed instance defined for it
2019.05.09 17:06:02 1: Connection refused from the non-local address 93.206.247.138:62585, as there is no working allowed instance defined for it
2019.05.09 17:06:02 1: Connection refused from the non-local address 93.206.247.138:62586, as there is no working allowed instance defined for it
2019.05.09 17:06:02 1: Connection refused from the non-local address 93.206.247.138:62587, as there is no working allowed instance defined for it
2019.05.09 17:06:02 1: Connection refused from the non-local address 93.206.247.138:62588, as there is no working allowed instance defined for it
2019.05.09 17:06:02 1: Connection refused from the non-local address 93.206.247.138:62589, as there is no working allowed instance defined for it
2019.05.09 17:06:02 1: Connection refused from the non-local address 93.206.247.138:62590, as there is no working allowed instance defined for it
2019.05.09 17:06:02 1: Connection refused from the non-local address 93.206.247.138:62591, as there is no working allowed instance defined for it
2019.05.09 17:08:42 1: Connection refused from the non-local address 93.206.247.138:62648, as there is no working allowed instance defined for it
2019.05.09 17:08:42 1: Connection refused from the non-local address 93.206.247.138:62649, as there is no working allowed instance defined for it
2019.05.09 17:08:42 1: Connection refused from the non-local address 93.206.247.138:62650, as there is no working allowed instance defined for it
2019.05.09 17:08:42 1: Connection refused from the non-local address 93.206.247.138:62651, as there is no working allowed instance defined for it
2019.05.09 17:08:42 1: Connection refused from the non-local address 93.206.247.138:62652, as there is no working allowed instance defined for it
2019.05.09 17:08:42 1: Connection refused from the non-local address 93.206.247.138:62653, as there is no working allowed instance defined for it
2019.05.09 17:08:42 1: Connection refused from the non-local address 93.206.247.138:62654, as there is no working allowed instance defined for it
2019.05.09 17:08:42 1: Connection refused from the non-local address 93.206.247.138:62655, as there is no working allowed instance defined for it
2019.05.09 17:08:42 1: Connection refused from the non-local address 93.206.247.138:62656, as there is no working allowed instance defined for it
2019.05.09 17:08:42 1: Connection refused from the non-local address 93.206.247.138:62657, as there is no working allowed instance defined for it
2019.05.09 17:15:30 1: Connection refused from the non-local address 93.206.247.138:62720, as there is no working allowed instance defined for it
2019.05.09 17:15:30 1: Connection refused from the non-local address 93.206.247.138:62721, as there is no working allowed instance defined for it
2019.05.09 17:15:30 1: Connection refused from the non-local address 93.206.247.138:62722, as there is no working allowed instance defined for it
2019.05.09 17:15:30 1: Connection refused from the non-local address 93.206.247.138:62723, as there is no working allowed instance defined for it
2019.05.09 17:15:31 1: Connection refused from the non-local address 93.206.247.138:62724, as there is no working allowed instance defined for it
2019.05.09 17:15:31 1: Connection refused from the non-local address 93.206.247.138:62725, as there is no working allowed instance defined for it
2019.05.09 17:15:31 1: Connection refused from the non-local address 93.206.247.138:62726, as there is no working allowed instance defined for it
2019.05.09 17:15:31 1: Connection refused from the non-local address 93.206.247.138:62727, as there is no working allowed instance defined for it
2019.05.09 17:15:31 1: Connection refused from the non-local address 93.206.247.138:62728, as there is no working allowed instance defined for it
2019.05.09 17:15:31 1: Connection refused from the non-local address 93.206.247.138:62729, as there is no working allowed instance defined for it
2019.05.09 17:40:53 0: Server shutdown
2019.05.09 17:54:44 1: Including /srv/fhem/fhem.cfg
2019.05.09 17:54:45 3: WEB: port 8083 opened
2019.05.09 17:54:45 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2019.05.09 17:54:45 1: Including ./log/fhem.save
2019.05.09 17:54:45 1: usb create starting
2019.05.09 17:54:45 1: PERL WARNING: Can't exec "lsusb": Datei oder Verzeichnis nicht gefunden at ./FHEM/98_autocreate.pm line 537.
2019.05.09 17:54:45 3: Probing CUL device /dev/ttyS0
2019.05.09 17:54:45 1: PERL WARNING: can't getattr: Eingabe-/Ausgabefehler at ./FHEM/DevIo.pm line 419.
2019.05.09 17:54:45 1: CUL: Can't open /dev/ttyS0: Eingabe-/Ausgabefehler
2019.05.09 17:54:45 3: Probing CUL device /dev/ttyS1
2019.05.09 17:54:45 1: CUL: Can't open /dev/ttyS1: Eingabe-/Ausgabefehler
2019.05.09 17:54:45 3: Probing CUL device /dev/ttyS2
2019.05.09 17:54:45 1: CUL: Can't open /dev/ttyS2: Eingabe-/Ausgabefehler
2019.05.09 17:54:45 3: Probing CUL device /dev/ttyS3
2019.05.09 17:54:45 1: CUL: Can't open /dev/ttyS3: Eingabe-/Ausgabefehler
2019.05.09 17:54:45 1: usb create end
2019.05.09 17:54:45 0: Featurelevel: 5.8
2019.05.09 17:54:45 0: Server started with 6 defined entities (fhem.pl:17329/2018-09-12 perl:5.016003 os:linux user:root pid:2982)
2019.05.09 17:54:56 1: Connection refused from the non-local address 93.206.247.138:63711, as there is no working allowed instance defined for it
2019.05.09 17:54:56 1: Connection refused from the non-local address 93.206.247.138:63712, as there is no working allowed instance defined for it
2019.05.09 17:54:56 1: Connection refused from the non-local address 93.206.247.138:63713, as there is no working allowed instance defined for it
2019.05.09 17:54:58 1: Connection refused from the non-local address 93.206.247.138:63714, as there is no working allowed instance defined for it
2019.05.09 17:54:58 1: Connection refused from the non-local address 93.206.247.138:63715, as there is no working allowed instance defined for it
2019.05.09 17:54:58 1: Connection refused from the non-local address 93.206.247.138:63716, as there is no working allowed instance defined for it
2019.05.09 17:54:58 1: Connection refused from the non-local address 93.206.247.138:63718, as there is no working allowed instance defined for it
2019.05.09 17:54:59 1: Connection refused from the non-local address 93.206.247.138:63719, as there is no working allowed instance defined for it
2019.05.09 17:54:59 1: Connection refused from the non-local address 93.206.247.138:63720, as there is no working allowed instance defined for it
2019.05.09 17:54:59 1: Connection refused from the non-local address 93.206.247.138:63721, as there is no working allowed instance defined for it
2019.05.09 17:55:23 1: Connection refused from the non-local address 93.206.247.138:63728, as there is no working allowed instance defined for it
2019.05.09 17:55:23 1: Connection refused from the non-local address 93.206.247.138:63729, as there is no working allowed instance defined for it
2019.05.09 17:55:23 1: Connection refused from the non-local address 93.206.247.138:63731, as there is no working allowed instance defined for it
2019.05.09 17:55:23 1: Connection refused from the non-local address 93.206.247.138:63732, as there is no working allowed instance defined for it
2019.05.09 17:55:23 1: Connection refused from the non-local address 93.206.247.138:63733, as there is no working allowed instance defined for it
2019.05.09 17:55:24 1: Connection refused from the non-local address 93.206.247.138:63734, as there is no working allowed instance defined for it
2019.05.09 17:55:24 1: Connection refused from the non-local address 93.206.247.138:63735, as there is no working allowed instance defined for it
2019.05.09 17:55:24 1: Connection refused from the non-local address 93.206.247.138:63736, as there is no working allowed instance defined for it
2019.05.09 17:55:24 1: Connection refused from the non-local address 93.206.247.138:63737, as there is no working allowed instance defined for it
2019.05.09 17:55:25 1: Connection refused from the non-local address 93.206.247.138:63739, as there is no working allowed instance defined for it
2019.05.09 17:55:25 1: Connection refused from the non-local address 93.206.247.138:63742, as there is no working allowed instance defined for it
2019.05.09 17:55:30 1: Connection refused from the non-local address 93.206.247.138:63745, as there is no working allowed instance defined for it
2019.05.09 17:55:30 1: Connection refused from the non-local address 93.206.247.138:63746, as there is no working allowed instance defined for it
2019.05.09 17:55:31 1: Connection refused from the non-local address 93.206.247.138:63747, as there is no working allowed instance defined for it
2019.05.09 17:55:31 1: Connection refused from the non-local address 93.206.247.138:63748, as there is no working allowed instance defined for it
2019.05.09 17:55:31 1: Connection refused from the non-local address 93.206.247.138:63749, as there is no working allowed instance defined for it
2019.05.09 17:55:32 1: Connection refused from the non-local address 93.206.247.138:63750, as there is no working allowed instance defined for it
2019.05.09 17:55:32 1: Connection refused from the non-local address 93.206.247.138:63751, as there is no working allowed instance defined for it
2019.05.09 17:55:32 1: Connection refused from the non-local address 93.206.247.138:63752, as there is no working allowed instance defined for it
2019.05.09 17:55:33 1: Connection refused from the non-local address 93.206.247.138:63753, as there is no working allowed instance defined for it
2019.05.09 17:55:34 1: Connection refused from the non-local address 93.206.247.138:63754, as there is no working allowed instance defined for it
2019.05.09 17:55:34 1: Connection refused from the non-local address 93.206.247.138:63755, as there is no working allowed instance defined for it
2019.05.09 17:56:22 1: Connection refused from the non-local address 93.206.247.138:63777, as there is no working allowed instance defined for it
2019.05.09 17:56:22 1: Connection refused from the non-local address 93.206.247.138:63778, as there is no working allowed instance defined for it
2019.05.09 17:56:23 1: Connection refused from the non-local address 93.206.247.138:63779, as there is no working allowed instance defined for it
2019.05.09 17:56:23 1: Connection refused from the non-local address 93.206.247.138:63780, as there is no working allowed instance defined for it
2019.05.09 17:56:24 1: Connection refused from the non-local address 93.206.247.138:63781, as there is no working allowed instance defined for it
2019.05.09 17:56:24 1: Connection refused from the non-local address 93.206.247.138:63782, as there is no working allowed instance defined for it
2019.05.09 17:56:24 1: Connection refused from the non-local address 93.206.247.138:63783, as there is no working allowed instance defined for it
2019.05.09 17:56:25 1: Connection refused from the non-local address 93.206.247.138:63784, as there is no working allowed instance defined for it
2019.05.09 17:56:25 1: Connection refused from the non-local address 93.206.247.138:63785, as there is no working allowed instance defined for it
2019.05.09 17:56:25 1: Connection refused from the non-local address 93.206.247.138:63786, as there is no working allowed instance defined for it
2019.05.09 17:56:25 1: Connection refused from the non-local address 93.206.247.138:63787, as there is no working allowed instance defined for it
2019.05.09 18:02:02 1: Connection refused from the non-local address 93.206.247.138:63873, as there is no working allowed instance defined for it
2019.05.09 18:02:02 1: Connection refused from the non-local address 93.206.247.138:63874, as there is no working allowed instance defined for it
2019.05.09 18:02:02 1: Connection refused from the non-local address 93.206.247.138:63875, as there is no working allowed instance defined for it
2019.05.09 18:02:03 1: Connection refused from the non-local address 93.206.247.138:63876, as there is no working allowed instance defined for it
2019.05.09 18:02:03 1: Connection refused from the non-local address 93.206.247.138:63877, as there is no working allowed instance defined for it
2019.05.09 18:02:04 1: Connection refused from the non-local address 93.206.247.138:63878, as there is no working allowed instance defined for it
2019.05.09 18:02:04 1: Connection refused from the non-local address 93.206.247.138:63879, as there is no working allowed instance defined for it
2019.05.09 18:02:05 1: Connection refused from the non-local address 93.206.247.138:63880, as there is no working allowed instance defined for it
2019.05.09 18:02:05 1: Connection refused from the non-local address 93.206.247.138:63881, as there is no working allowed instance defined for it
2019.05.09 18:02:06 1: Connection refused from the non-local address 93.206.247.138:63882, as there is no working allowed instance defined for it
2019.05.09 18:02:07 1: Connection refused from the non-local address 93.206.247.138:63884, as there is no working allowed instance defined for it
2019.05.09 18:02:07 1: Connection refused from the non-local address 93.206.247.138:63885, as there is no working allowed instance defined for it
2019.05.09 18:02:07 1: Connection refused from the non-local address 93.206.247.138:63886, as there is no working allowed instance defined for it
2019.05.09 18:02:08 1: Connection refused from the non-local address 93.206.247.138:63887, as there is no working allowed instance defined for it
2019.05.09 18:02:08 1: Connection refused from the non-local address 93.206.247.138:63888, as there is no working allowed instance defined for it
2019.05.09 18:02:08 1: Connection refused from the non-local address 93.206.247.138:63889, as there is no working allowed instance defined for it
2019.05.09 18:02:08 1: Connection refused from the non-local address 93.206.247.138:63890, as there is no working allowed instance defined for it
2019.05.09 18:02:09 1: Connection refused from the non-local address 93.206.247.138:63891, as there is no working allowed instance defined for it
2019.05.09 18:02:09 1: Connection refused from the non-local address 93.206.247.138:63892, as there is no working allowed instance defined for it
2019.05.09 18:02:09 1: Connection refused from the non-local address 93.206.247.138:63893, as there is no working allowed instance defined for it
2019.05.09 18:03:21 1: Connection refused from the non-local address 93.206.247.138:63935, as there is no working allowed instance defined for it
2019.05.09 18:03:21 1: Connection refused from the non-local address 93.206.247.138:63936, as there is no working allowed instance defined for it
2019.05.09 18:03:21 1: Connection refused from the non-local address 93.206.247.138:63937, as there is no working allowed instance defined for it
2019.05.09 18:03:22 1: Connection refused from the non-local address 93.206.247.138:63938, as there is no working allowed instance defined for it
2019.05.09 18:03:22 1: Connection refused from the non-local address 93.206.247.138:63939, as there is no working allowed instance defined for it
2019.05.09 18:03:22 1: Connection refused from the non-local address 93.206.247.138:63940, as there is no working allowed instance defined for it
2019.05.09 18:03:23 1: Connection refused from the non-local address 93.206.247.138:63941, as there is no working allowed instance defined for it
2019.05.09 18:03:23 1: Connection refused from the non-local address 93.206.247.138:63942, as there is no working allowed instance defined for it
2019.05.09 18:03:23 1: Connection refused from the non-local address 93.206.247.138:63943, as there is no working allowed instance defined for it
2019.05.09 18:03:23 1: Connection refused from the non-local address 93.206.247.138:63944, as there is no working allowed instance defined for it
2019.05.09 18:03:24 1: Connection refused from the non-local address 93.206.247.138:63945, as there is no working allowed instance defined for it
2019.05.09 18:03:24 1: Connection refused from the non-local address 93.206.247.138:63946, as there is no working allowed instance defined for it
2019.05.09 18:04:35 0: Server shutdown
2019.05.09 18:14:35 1: Including /srv/fhem/fhem.cfg
2019.05.09 18:14:35 3: WEB: port 8083 opened
2019.05.09 18:14:35 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2019.05.09 18:14:35 1: Including ./log/fhem.save
2019.05.09 18:14:35 1: usb create starting
2019.05.09 18:14:35 1: PERL WARNING: Can't exec "lsusb": Datei oder Verzeichnis nicht gefunden at ./FHEM/98_autocreate.pm line 537.
2019.05.09 18:14:35 3: Probing CUL device /dev/ttyS0
2019.05.09 18:14:35 1: PERL WARNING: can't getattr: Eingabe-/Ausgabefehler at ./FHEM/DevIo.pm line 419.
2019.05.09 18:14:35 1: CUL: Can't open /dev/ttyS0: Eingabe-/Ausgabefehler
2019.05.09 18:14:35 3: Probing CUL device /dev/ttyS1
2019.05.09 18:14:35 1: CUL: Can't open /dev/ttyS1: Eingabe-/Ausgabefehler
2019.05.09 18:14:35 3: Probing CUL device /dev/ttyS2
2019.05.09 18:14:35 1: CUL: Can't open /dev/ttyS2: Eingabe-/Ausgabefehler
2019.05.09 18:14:35 3: Probing CUL device /dev/ttyS3
2019.05.09 18:14:35 1: CUL: Can't open /dev/ttyS3: Eingabe-/Ausgabefehler
2019.05.09 18:14:35 1: usb create end
2019.05.09 18:14:35 0: Featurelevel: 5.8
2019.05.09 18:14:35 0: Server started with 6 defined entities (fhem.pl:17329/2018-09-12 perl:5.016003 os:linux user:root pid:5040)
2019.05.09 18:15:06 0: Server shutdown
2019.05.09 18:15:06 1: Including /srv/fhem/fhem.cfg
2019.05.09 18:15:06 3: WEB: port 8083 opened
2019.05.09 18:15:06 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2019.05.09 18:15:06 1: Including ./log/fhem.save
2019.05.09 18:15:06 1: usb create starting
2019.05.09 18:15:06 1: PERL WARNING: Can't exec "lsusb": Datei oder Verzeichnis nicht gefunden at ./FHEM/98_autocreate.pm line 537.
2019.05.09 18:15:06 3: Probing CUL device /dev/ttyS0
2019.05.09 18:15:06 1: PERL WARNING: can't getattr: Eingabe-/Ausgabefehler at ./FHEM/DevIo.pm line 419.
2019.05.09 18:15:06 1: CUL: Can't open /dev/ttyS0: Eingabe-/Ausgabefehler
2019.05.09 18:15:06 3: Probing CUL device /dev/ttyS1
2019.05.09 18:15:06 1: CUL: Can't open /dev/ttyS1: Eingabe-/Ausgabefehler
2019.05.09 18:15:06 3: Probing CUL device /dev/ttyS2
2019.05.09 18:15:06 1: CUL: Can't open /dev/ttyS2: Eingabe-/Ausgabefehler
2019.05.09 18:15:06 3: Probing CUL device /dev/ttyS3
2019.05.09 18:15:06 1: CUL: Can't open /dev/ttyS3: Eingabe-/Ausgabefehler
2019.05.09 18:15:06 1: usb create end
2019.05.09 18:15:06 0: Featurelevel: 5.8
2019.05.09 18:15:06 0: Server started with 6 defined entities (fhem.pl:17329/2018-09-12 perl:5.016003 os:linux user:root pid:5105)
2019.05.09 18:15:10 1: Connection refused from the non-local address 93.206.247.138:64294, as there is no working allowed instance defined for it
2019.05.09 18:15:11 1: Connection refused from the non-local address 93.206.247.138:64295, as there is no working allowed instance defined for it
2019.05.09 18:15:11 1: Connection refused from the non-local address 93.206.247.138:64296, as there is no working allowed instance defined for it
2019.05.09 18:15:11 1: Connection refused from the non-local address 93.206.247.138:64297, as there is no working allowed instance defined for it
2019.05.09 18:15:12 1: Connection refused from the non-local address 93.206.247.138:64298, as there is no working allowed instance defined for it
2019.05.09 18:15:12 1: Connection refused from the non-local address 93.206.247.138:64300, as there is no working allowed instance defined for it
2019.05.09 18:15:12 1: Connection refused from the non-local address 93.206.247.138:64301, as there is no working allowed instance defined for it
2019.05.09 18:15:12 1: Connection refused from the non-local address 93.206.247.138:64302, as there is no working allowed instance defined for it
2019.05.09 18:15:13 1: Connection refused from the non-local address 93.206.247.138:64303, as there is no working allowed instance defined for it
2019.05.09 18:15:13 1: Connection refused from the non-local address 93.206.247.138:64304, as there is no working allowed instance defined for it
2019.05.09 18:15:35 1: Connection refused from the non-local address 93.206.247.138:64309, as there is no working allowed instance defined for it
2019.05.09 18:15:35 1: Connection refused from the non-local address 93.206.247.138:64310, as there is no working allowed instance defined for it
2019.05.09 18:15:35 1: Connection refused from the non-local address 93.206.247.138:64311, as there is no working allowed instance defined for it
2019.05.09 18:15:36 1: Connection refused from the non-local address 93.206.247.138:64312, as there is no working allowed instance defined for it
2019.05.09 18:15:36 1: Connection refused from the non-local address 93.206.247.138:64313, as there is no working allowed instance defined for it
2019.05.09 18:15:36 1: Connection refused from the non-local address 93.206.247.138:64314, as there is no working allowed instance defined for it
2019.05.09 18:15:37 1: Connection refused from the non-local address 93.206.247.138:64315, as there is no working allowed instance defined for it
2019.05.09 18:15:37 1: Connection refused from the non-local address 93.206.247.138:64316, as there is no working allowed instance defined for it
2019.05.09 18:15:37 1: Connection refused from the non-local address 93.206.247.138:64317, as there is no working allowed instance defined for it
2019.05.09 18:15:37 1: Connection refused from the non-local address 93.206.247.138:64318, as there is no working allowed instance defined for it
2019.05.09 18:15:37 1: Connection refused from the non-local address 93.206.247.138:64319, as there is no working allowed instance defined for it
2019.05.09 18:15:37 1: Connection refused from the non-local address 93.206.247.138:64320, as there is no working allowed instance defined for it
2019.05.09 18:16:05 1: Connection refused from the non-local address 93.206.247.138:64329, as there is no working allowed instance defined for it
2019.05.09 18:16:05 1: Connection refused from the non-local address 93.206.247.138:64330, as there is no working allowed instance defined for it
2019.05.09 18:16:06 1: Connection refused from the non-local address 93.206.247.138:64332, as there is no working allowed instance defined for it
2019.05.09 18:16:06 1: Connection refused from the non-local address 93.206.247.138:64333, as there is no working allowed instance defined for it
2019.05.09 18:16:06 1: Connection refused from the non-local address 93.206.247.138:64334, as there is no working allowed instance defined for it
2019.05.09 18:16:06 1: Connection refused from the non-local address 93.206.247.138:64335, as there is no working allowed instance defined for it
2019.05.09 18:16:07 1: Connection refused from the non-local address 93.206.247.138:64336, as there is no working allowed instance defined for it
2019.05.09 18:16:07 1: Connection refused from the non-local address 93.206.247.138:64337, as there is no working allowed instance defined for it
2019.05.09 18:16:07 1: Connection refused from the non-local address 93.206.247.138:64338, as there is no working allowed instance defined for it
2019.05.09 18:16:07 1: Connection refused from the non-local address 93.206.247.138:64339, as there is no working allowed instance defined for it
2019.05.09 18:19:36 0: Server shutdown
2019.05.09 18:21:00 1: Including /srv/fhem/fhem.cfg
2019.05.09 18:21:00 3: WEB: port 8083 opened
2019.05.09 18:21:00 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2019.05.09 18:21:00 1: Including ./log/fhem.save
2019.05.09 18:21:00 1: usb create starting
2019.05.09 18:21:00 1: PERL WARNING: Can't exec "lsusb": Datei oder Verzeichnis nicht gefunden at ./FHEM/98_autocreate.pm line 537.
2019.05.09 18:21:00 3: Probing CUL device /dev/ttyS0
2019.05.09 18:21:00 1: PERL WARNING: can't getattr: Eingabe-/Ausgabefehler at ./FHEM/DevIo.pm line 419.
2019.05.09 18:21:00 1: CUL: Can't open /dev/ttyS0: Eingabe-/Ausgabefehler
2019.05.09 18:21:00 3: Probing CUL device /dev/ttyS1
2019.05.09 18:21:00 1: CUL: Can't open /dev/ttyS1: Eingabe-/Ausgabefehler
2019.05.09 18:21:00 3: Probing CUL device /dev/ttyS2
2019.05.09 18:21:00 1: CUL: Can't open /dev/ttyS2: Eingabe-/Ausgabefehler
2019.05.09 18:21:00 3: Probing CUL device /dev/ttyS3
2019.05.09 18:21:00 1: CUL: Can't open /dev/ttyS3: Eingabe-/Ausgabefehler
2019.05.09 18:21:00 1: usb create end
2019.05.09 18:21:00 0: Featurelevel: 5.8
2019.05.09 18:21:00 0: Server started with 6 defined entities (fhem.pl:17329/2018-09-12 perl:5.016003 os:linux user:root pid:5439)
2019.05.09 18:21:11 1: Connection refused from the non-local address 93.206.247.138:64388, as there is no working allowed instance defined for it
2019.05.09 18:21:11 1: Connection refused from the non-local address 93.206.247.138:64389, as there is no working allowed instance defined for it
2019.05.09 18:21:11 1: Connection refused from the non-local address 93.206.247.138:64390, as there is no working allowed instance defined for it
2019.05.09 18:21:11 1: Connection refused from the non-local address 93.206.247.138:64391, as there is no working allowed instance defined for it
2019.05.09 18:21:11 1: Connection refused from the non-local address 93.206.247.138:64392, as there is no working allowed instance defined for it
2019.05.09 18:21:11 1: Connection refused from the non-local address 93.206.247.138:64393, as there is no working allowed instance defined for it
2019.05.09 18:21:11 1: Connection refused from the non-local address 93.206.247.138:64394, as there is no working allowed instance defined for it
2019.05.09 18:21:11 1: Connection refused from the non-local address 93.206.247.138:64395, as there is no working allowed instance defined for it
2019.05.09 18:21:11 1: Connection refused from the non-local address 93.206.247.138:64396, as there is no working allowed instance defined for it
2019.05.09 18:21:11 1: Connection refused from the non-local address 93.206.247.138:64397, as there is no working allowed instance defined for it
2019.05.09 18:21:14 1: Connection refused from the non-local address 93.206.247.138:64399, as there is no working allowed instance defined for it
2019.05.09 18:21:14 1: Connection refused from the non-local address 93.206.247.138:64400, as there is no working allowed instance defined for it
2019.05.09 18:21:14 1: Connection refused from the non-local address 93.206.247.138:64401, as there is no working allowed instance defined for it
2019.05.09 18:21:14 1: Connection refused from the non-local address 93.206.247.138:64402, as there is no working allowed instance defined for it
2019.05.09 18:21:14 1: Connection refused from the non-local address 93.206.247.138:64403, as there is no working allowed instance defined for it
2019.05.09 18:21:14 1: Connection refused from the non-local address 93.206.247.138:64404, as there is no working allowed instance defined for it
2019.05.09 18:21:14 1: Connection refused from the non-local address 93.206.247.138:64405, as there is no working allowed instance defined for it
2019.05.09 18:21:14 1: Connection refused from the non-local address 93.206.247.138:64406, as there is no working allowed instance defined for it
2019.05.09 18:21:14 1: Connection refused from the non-local address 93.206.247.138:64407, as there is no working allowed instance defined for it
2019.05.09 18:21:14 1: Connection refused from the non-local address 93.206.247.138:64408, as there is no working allowed instance defined for it
2019.05.09 18:21:18 1: Connection refused from the non-local address 93.206.247.138:64409, as there is no working allowed instance defined for it
2019.05.09 18:21:18 1: Connection refused from the non-local address 93.206.247.138:64410, as there is no working allowed instance defined for it
2019.05.09 18:21:18 1: Connection refused from the non-local address 93.206.247.138:64411, as there is no working allowed instance defined for it
2019.05.09 18:21:18 1: Connection refused from the non-local address 93.206.247.138:64412, as there is no working allowed instance defined for it
2019.05.09 18:21:18 1: Connection refused from the non-local address 93.206.247.138:64413, as there is no working allowed instance defined for it
2019.05.09 18:21:18 1: Connection refused from the non-local address 93.206.247.138:64414, as there is no working allowed instance defined for it
2019.05.09 18:21:18 1: Connection refused from the non-local address 93.206.247.138:64415, as there is no working allowed instance defined for it
2019.05.09 18:21:18 1: Connection refused from the non-local address 93.206.247.138:64416, as there is no working allowed instance defined for it
2019.05.09 18:21:18 1: Connection refused from the non-local address 93.206.247.138:64417, as there is no working allowed instance defined for it
2019.05.09 18:21:19 1: Connection refused from the non-local address 93.206.247.138:64418, as there is no working allowed instance defined for it
2019.05.09 18:21:50 1: Connection refused from the non-local address 93.206.247.138:64432, as there is no working allowed instance defined for it
2019.05.09 18:21:50 1: Connection refused from the non-local address 93.206.247.138:64433, as there is no working allowed instance defined for it
2019.05.09 18:21:51 1: Connection refused from the non-local address 93.206.247.138:64434, as there is no working allowed instance defined for it
2019.05.09 18:21:51 1: Connection refused from the non-local address 93.206.247.138:64435, as there is no working allowed instance defined for it
2019.05.09 18:21:51 1: Connection refused from the non-local address 93.206.247.138:64436, as there is no working allowed instance defined for it
2019.05.09 18:21:51 1: Connection refused from the non-local address 93.206.247.138:64437, as there is no working allowed instance defined for it
2019.05.09 18:21:51 1: Connection refused from the non-local address 93.206.247.138:64438, as there is no working allowed instance defined for it
2019.05.09 18:21:51 1: Connection refused from the non-local address 93.206.247.138:64439, as there is no working allowed instance defined for it
2019.05.09 18:21:51 1: Connection refused from the non-local address 93.206.247.138:64440, as there is no working allowed instance defined for it
2019.05.09 18:21:51 1: Connection refused from the non-local address 93.206.247.138:64441, as there is no working allowed instance defined for it
2019.05.09 18:22:18 0: Server shutdown
2019.05.09 18:22:39 1: Including /srv/fhem/fhem.cfg
2019.05.09 18:22:39 3: WEB: port 8083 opened
2019.05.09 18:22:39 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2019.05.09 18:22:39 1: Including ./log/fhem.save
2019.05.09 18:22:39 1: usb create starting
2019.05.09 18:22:39 1: PERL WARNING: Can't exec "lsusb": Datei oder Verzeichnis nicht gefunden at ./FHEM/98_autocreate.pm line 537.
2019.05.09 18:22:39 3: Probing CUL device /dev/ttyS0
2019.05.09 18:22:39 1: PERL WARNING: can't getattr: Eingabe-/Ausgabefehler at ./FHEM/DevIo.pm line 419.
2019.05.09 18:22:39 1: CUL: Can't open /dev/ttyS0: Eingabe-/Ausgabefehler
2019.05.09 18:22:39 3: Probing CUL device /dev/ttyS1
2019.05.09 18:22:39 1: CUL: Can't open /dev/ttyS1: Eingabe-/Ausgabefehler
2019.05.09 18:22:39 3: Probing CUL device /dev/ttyS2
2019.05.09 18:22:39 1: CUL: Can't open /dev/ttyS2: Eingabe-/Ausgabefehler
2019.05.09 18:22:39 3: Probing CUL device /dev/ttyS3
2019.05.09 18:22:39 1: CUL: Can't open /dev/ttyS3: Eingabe-/Ausgabefehler
2019.05.09 18:22:39 1: usb create end
2019.05.09 18:22:39 0: Featurelevel: 5.8
2019.05.09 18:22:39 0: Server started with 6 defined entities (fhem.pl:17329/2018-09-12 perl:5.016003 os:linux user:root pid:3037)
2019.05.09 18:26:23 0: Server shutdown
2019.05.09 18:26:43 1: Including /srv/fhem/fhem.cfg
2019.05.09 18:26:43 3: WEB: port 8083 opened
2019.05.09 18:26:43 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2019.05.09 18:26:43 1: Including ./log/fhem.save
2019.05.09 18:26:43 1: usb create starting
2019.05.09 18:26:43 1: PERL WARNING: Can't exec "lsusb": Datei oder Verzeichnis nicht gefunden at ./FHEM/98_autocreate.pm line 537.
2019.05.09 18:26:44 3: Probing CUL device /dev/ttyS0
2019.05.09 18:26:44 1: PERL WARNING: can't getattr: Eingabe-/Ausgabefehler at ./FHEM/DevIo.pm line 419.
2019.05.09 18:26:44 1: CUL: Can't open /dev/ttyS0: Eingabe-/Ausgabefehler
2019.05.09 18:26:44 3: Probing CUL device /dev/ttyS1
2019.05.09 18:26:44 1: CUL: Can't open /dev/ttyS1: Eingabe-/Ausgabefehler
2019.05.09 18:26:44 3: Probing CUL device /dev/ttyS2
2019.05.09 18:26:44 1: CUL: Can't open /dev/ttyS2: Eingabe-/Ausgabefehler
2019.05.09 18:26:44 3: Probing CUL device /dev/ttyS3
2019.05.09 18:26:44 1: CUL: Can't open /dev/ttyS3: Eingabe-/Ausgabefehler
2019.05.09 18:26:44 1: usb create end
2019.05.09 18:26:44 0: Featurelevel: 5.8
2019.05.09 18:26:44 0: Server started with 6 defined entities (fhem.pl:17329/2018-09-12 perl:5.016003 os:linux user:root pid:3089)
2019.05.09 18:27:12 1: Connection refused from the non-local address 93.206.247.138:64541, as there is no working allowed instance defined for it
2019.05.09 18:27:12 1: Connection refused from the non-local address 93.206.247.138:64542, as there is no working allowed instance defined for it
2019.05.09 18:27:12 1: Connection refused from the non-local address 93.206.247.138:64543, as there is no working allowed instance defined for it
2019.05.09 18:27:12 1: Connection refused from the non-local address 93.206.247.138:64545, as there is no working allowed instance defined for it
2019.05.09 18:27:12 1: Connection refused from the non-local address 93.206.247.138:64546, as there is no working allowed instance defined for it
2019.05.09 18:27:12 1: Connection refused from the non-local address 93.206.247.138:64547, as there is no working allowed instance defined for it
2019.05.09 18:27:12 1: Connection refused from the non-local address 93.206.247.138:64548, as there is no working allowed instance defined for it
2019.05.09 18:27:12 1: Connection refused from the non-local address 93.206.247.138:64549, as there is no working allowed instance defined for it
2019.05.09 18:27:12 1: Connection refused from the non-local address 93.206.247.138:64550, as there is no working allowed instance defined for it
2019.05.09 18:27:12 1: Connection refused from the non-local address 93.206.247.138:64551, as there is no working allowed instance defined for it
2019.05.09 18:27:34 1: Connection refused from the non-local address 93.206.247.138:64567, as there is no working allowed instance defined for it
2019.05.09 18:27:34 1: Connection refused from the non-local address 93.206.247.138:64568, as there is no working allowed instance defined for it
2019.05.09 18:27:34 1: Connection refused from the non-local address 93.206.247.138:64569, as there is no working allowed instance defined for it
2019.05.09 18:27:35 1: Connection refused from the non-local address 93.206.247.138:64570, as there is no working allowed instance defined for it
2019.05.09 18:27:35 1: Connection refused from the non-local address 93.206.247.138:64571, as there is no working allowed instance defined for it
2019.05.09 18:27:35 1: Connection refused from the non-local address 93.206.247.138:64572, as there is no working allowed instance defined for it
2019.05.09 18:27:35 1: Connection refused from the non-local address 93.206.247.138:64573, as there is no working allowed instance defined for it
2019.05.09 18:27:35 1: Connection refused from the non-local address 93.206.247.138:64574, as there is no working allowed instance defined for it
2019.05.09 18:27:35 1: Connection refused from the non-local address 93.206.247.138:64575, as there is no working allowed instance defined for it
2019.05.09 18:27:35 1: Connection refused from the non-local address 93.206.247.138:64576, as there is no working allowed instance defined for it
2019.05.09 18:28:06 1: Connection refused from the non-local address 93.206.247.138:64617, as there is no working allowed instance defined for it
2019.05.09 18:28:07 1: Connection refused from the non-local address 93.206.247.138:64618, as there is no working allowed instance defined for it
2019.05.09 18:28:07 1: Connection refused from the non-local address 93.206.247.138:64619, as there is no working allowed instance defined for it
2019.05.09 18:28:07 1: Connection refused from the non-local address 93.206.247.138:64620, as there is no working allowed instance defined for it
2019.05.09 18:28:07 1: Connection refused from the non-local address 93.206.247.138:64621, as there is no working allowed instance defined for it
2019.05.09 18:28:07 1: Connection refused from the non-local address 93.206.247.138:64622, as there is no working allowed instance defined for it
2019.05.09 18:28:07 1: Connection refused from the non-local address 93.206.247.138:64623, as there is no working allowed instance defined for it
2019.05.09 18:28:07 1: Connection refused from the non-local address 93.206.247.138:64624, as there is no working allowed instance defined for it
2019.05.09 18:28:07 1: Connection refused from the non-local address 93.206.247.138:64625, as there is no working allowed instance defined for it
2019.05.09 18:28:07 1: Connection refused from the non-local address 93.206.247.138:64626, as there is no working allowed instance defined for it
2019.05.09 19:16:55 1: Connection refused from the non-local address 93.206.247.138:65358, as there is no working allowed instance defined for it
2019.05.09 19:16:55 1: Connection refused from the non-local address 93.206.247.138:65359, as there is no working allowed instance defined for it
2019.05.09 19:16:55 1: Connection refused from the non-local address 93.206.247.138:65360, as there is no working allowed instance defined for it
2019.05.09 19:16:55 1: Connection refused from the non-local address 93.206.247.138:65361, as there is no working allowed instance defined for it
2019.05.09 19:16:55 1: Connection refused from the non-local address 93.206.247.138:65362, as there is no working allowed instance defined for it
2019.05.09 19:16:55 1: Connection refused from the non-local address 93.206.247.138:65363, as there is no working allowed instance defined for it
2019.05.09 19:16:55 1: Connection refused from the non-local address 93.206.247.138:65364, as there is no working allowed instance defined for it
2019.05.09 19:16:55 1: Connection refused from the non-local address 93.206.247.138:65365, as there is no working allowed instance defined for it
2019.05.09 19:16:55 1: Connection refused from the non-local address 93.206.247.138:65366, as there is no working allowed instance defined for it
2019.05.09 19:16:55 1: Connection refused from the non-local address 93.206.247.138:65367, as there is no working allowed instance defined for it
2019.05.09 19:18:28 1: Connection refused from the non-local address 93.206.247.138:65403, as there is no working allowed instance defined for it
2019.05.09 19:18:28 1: Connection refused from the non-local address 93.206.247.138:65404, as there is no working allowed instance defined for it
2019.05.09 19:18:28 1: Connection refused from the non-local address 93.206.247.138:65405, as there is no working allowed instance defined for it
2019.05.09 19:18:28 1: Connection refused from the non-local address 93.206.247.138:65406, as there is no working allowed instance defined for it
2019.05.09 19:18:28 1: Connection refused from the non-local address 93.206.247.138:65407, as there is no working allowed instance defined for it
2019.05.09 19:18:28 1: Connection refused from the non-local address 93.206.247.138:65408, as there is no working allowed instance defined for it
2019.05.09 19:18:29 1: Connection refused from the non-local address 93.206.247.138:65409, as there is no working allowed instance defined for it
2019.05.09 19:18:29 1: Connection refused from the non-local address 93.206.247.138:65410, as there is no working allowed instance defined for it
2019.05.09 19:18:29 1: Connection refused from the non-local address 93.206.247.138:65411, as there is no working allowed instance defined for it
2019.05.09 19:18:29 1: Connection refused from the non-local address 93.206.247.138:65412, as there is no working allowed instance defined for it
2019.05.09 19:22:19 1: Connection refused from the non-local address 93.206.247.138:65454, as there is no working allowed instance defined for it
2019.05.09 19:22:19 1: Connection refused from the non-local address 93.206.247.138:65455, as there is no working allowed instance defined for it
2019.05.09 19:22:19 1: Connection refused from the non-local address 93.206.247.138:65456, as there is no working allowed instance defined for it
2019.05.09 19:22:19 1: Connection refused from the non-local address 93.206.247.138:65457, as there is no working allowed instance defined for it
2019.05.09 19:22:19 1: Connection refused from the non-local address 93.206.247.138:65458, as there is no working allowed instance defined for it
2019.05.09 19:22:19 1: Connection refused from the non-local address 93.206.247.138:65459, as there is no working allowed instance defined for it
2019.05.09 19:22:19 1: Connection refused from the non-local address 93.206.247.138:65460, as there is no working allowed instance defined for it
2019.05.09 19:22:20 1: Connection refused from the non-local address 93.206.247.138:65461, as there is no working allowed instance defined for it
2019.05.09 19:22:20 1: Connection refused from the non-local address 93.206.247.138:65462, as there is no working allowed instance defined for it
2019.05.09 19:22:20 1: Connection refused from the non-local address 93.206.247.138:65463, as there is no working allowed instance defined for it
2019.05.09 19:23:09 1: Connection refused from the non-local address 93.206.247.138:65465, as there is no working allowed instance defined for it
2019.05.09 19:23:09 1: Connection refused from the non-local address 93.206.247.138:65466, as there is no working allowed instance defined for it
2019.05.09 19:23:09 1: Connection refused from the non-local address 93.206.247.138:65467, as there is no working allowed instance defined for it
2019.05.09 19:23:09 1: Connection refused from the non-local address 93.206.247.138:65468, as there is no working allowed instance defined for it
2019.05.09 19:23:09 1: Connection refused from the non-local address 93.206.247.138:65469, as there is no working allowed instance defined for it
2019.05.09 19:23:09 1: Connection refused from the non-local address 93.206.247.138:65470, as there is no working allowed instance defined for it
2019.05.09 19:23:09 1: Connection refused from the non-local address 93.206.247.138:65471
Zitat von: Beta-User am 10 Mai 2019, 17:08:42
[...] und ohne passendes allowed wird alles abgewehrt, was nicht im lokalen Netz ist. [...]
Genau das sagt dein log: Es gibt kein allowed, wenn du unbedingt diese Lösung so haben willst, mußt du eines definieren. Wie das geht, steht in der commandref zu allowed.
(Ob das mit dem Portforwarding unter Sicherheitsaspekten eine gute Idee ist mit dem gewählten setup ist eine zweite Frage! Besser zusätzlich mit vpn beschäftigen (aber allowed trotzdem einrichten!)).
Das müsste die Anleitung sein richtig: https://fhem.de/commandref_DE.html#allowed
Das sind aber doch Befehle die ich in der Weboberfläche von FHEM eintrage oder nicht? Diese kann ich aber ja nicht aufrufen :o.
Vielen Dank!
ZitatDiese kann ich aber ja nicht aufrufen
Doch, aus dem lokalen Netz wo der Fhem Server steht, sollte es kein Pb sein
localhost sollte auch funktionieren. (Also notfalls eben Tastatur + Bildschirm anschließen...)
Generell: Wenn du bei solchen Aufgaben schon Hilfe auf dem Niveau brauchst, ist evtl. das setup insgesamt zu überdenken.
Ist nicht böse gemeint, aber
just my2ct.
Um es mal Pauschal zu sagen:
Wenn Du einen Rechner ist Netz stellst, hast Du Potentiell 6 Millarden Angreifer (Ist doch die aktuelle zahl der I-Net-User .. oder ist sie schon höher?)
FHEM ist nicht in Bezug auf Sicherheit entwickelt (nicht böse gemeint) oder getestet. Entsprechend sollte man wirklich ein Schutz davor bauen.
Okay. Dann mache ich mal einen Hacken an das Thema FHEM, schade eigentlich aber okay - es gibt bestimmt noch die ein oder andere Software die den Verkehr ebenfalls auslesen kann. ;)
Trotzdem vielen Dank an alle!
Das ist kein problem von FHEM, sondern von Software. Die "Konkurenz" hat das gleiche problem ... und erst recht die "Kommerziellen Varianten" .. habe beruflich schon viel zu viel so etwas gesehen ...
Zitat von: vtruckers_de am 13 Mai 2019, 11:03:52
Okay. Dann mache ich mal einen Hacken an das Thema FHEM, schade eigentlich aber okay - es gibt bestimmt noch die ein oder andere Software die den Verkehr ebenfalls auslesen kann. ;)
Nun ja, du hast den Versuch unternommen, eine dir unbekannte Software in einem eher komplexen IT-Setup ohne das Handbuch und ohne Analyse des logs an's laufen zu bekommen.
Hut ab, sowas traut sich nicht jeder zu.
Bin mal gespannt, welche andere ähnlich flexible Lösung du findest, die das "besser" kann :) . Oder eine community, die genauso freundlich 3x nach den immer gleichen Dingen fragt ;D .
cu, hoffentlich dann nach Lektüre von ein paar Grundlagendokumenten.