NEWS
Modbus Adapter: Poll error count e3dc S10
-
Muss hier nochmal nachfragen.
Diese Poll error count hat niemand??
Mein Modbus, ist kontinuierlich am flackern grün gelb im Admin unter instanzen und das log hat soviele warnings Poll error count
Danke für Eure Hilfe
Zippolighter
-
Ichh abe den Fehler auch - der Adapter liefert ordentliche Werte, aber er müllt auch das log zu:
host.iobroker-deb 2018-03-27 14:28:13.637 info Restart adapter system.adapter.modbus.0 because enabled host.iobroker-deb 2018-03-27 14:28:13.637 error instance system.adapter.modbus.0 terminated with code 0 (OK) modbus.0 2018-03-27 14:28:13.629 info terminating modbus.0 2018-03-27 14:28:13.623 error at Timer.listOnTimeout (timers.js:92:15) modbus.0 2018-03-27 14:28:13.623 error at null._onTimeout (/opt/iobroker/node_modules/iobroker.modbus/main.js:2231:18) modbus.0 2018-03-27 14:28:13.623 error at Object.main.pollResult (/opt/iobroker/node_modules/iobroker.modbus/main.js:2203:23) modbus.0 2018-03-27 14:28:13.623 error Error: Reconnect did not help, restart adapter modbus.0 2018-03-27 14:28:13.621 error uncaught exception: Reconnect did not help, restart adapter modbus.0 2018-03-27 14:28:13.619 warn Poll error count: 19 code: "App Timeout" modbus.0 2018-03-27 14:28:13.609 warn Poll error count: 18 code: "App Timeout" modbus.0 2018-03-27 14:28:13.568 warn Poll error count: 17 code: "App Timeout" modbus.0 2018-03-27 14:28:13.561 warn Poll error count: 16 code: "App Timeout" modbus.0 2018-03-27 14:28:13.381 warn Poll error count: 15 code: "App Timeout" modbus.0 2018-03-27 14:28:13.370 warn Poll error count: 14 code: "App Timeout" modbus.0 2018-03-27 14:28:13.247 warn Poll error count: 13 code: "App Timeout" modbus.0 2018-03-27 14:28:12.985 warn Poll error count: 12 code: "App Timeout" modbus.0 2018-03-27 14:28:12.915 warn Poll error count: 11 code: "App Timeout" modbus.0 2018-03-27 14:28:11.126 warn Poll error count: 10 code: "App Timeout" modbus.0 2018-03-27 14:28:09.508 warn Poll error count: 9 code: "App Timeout" modbus.0 2018-03-27 14:28:09.404 warn Poll error count: 8 code: "App Timeout" modbus.0 2018-03-27 14:28:08.103 warn Poll error count: 7 code: "App Timeout" modbus.0 2018-03-27 14:28:08.087 warn On error: {} modbus.0 2018-03-27 14:28:08.077 info Disconnected from slave 192.168.50.136 modbus.0 2018-03-27 14:28:08.076 warn Poll error count: 6 code: "App Timeout" modbus.0 2018-03-27 14:28:07.845 warn Poll error count: 5 code: "App Timeout" modbus.0 2018-03-27 14:28:07.835 warn Poll error count: 4 code: "App Timeout" modbus.0 2018-03-27 14:28:07.772 warn Poll error count: 3 code: "App Timeout" modbus.0 2018-03-27 14:28:07.750 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:28:05.875 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:28:02.667 warn Poll error count: 3 code: "App Timeout" modbus.0 2018-03-27 14:28:02.632 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:28:02.608 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:28:02.542 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:28:02.531 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:28:00.783 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:28:00.713 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:57.326 warn Poll error count: 3 code: "App Timeout" modbus.0 2018-03-27 14:27:57.306 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:27:57.297 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:55.571 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:27:55.546 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:52.098 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:50.340 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:27:50.328 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:45.128 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:27:45.125 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:39.901 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:27:39.894 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:25.452 info Connected to slave 192.168.50.136 modbus.0 2018-03-27 14:26:31.444 warn Poll error count: 18 code: "App Timeout" modbus.0 2018-03-27 14:26:30.435 warn Poll error count: 17 code: "App Timeout" modbus.0 2018-03-27 14:26:27.870 warn Poll error count: 16 code: "App Timeout" modbus.0 2018-03-27 14:26:26.617 warn Poll error count: 15 code: "App Timeout" modbus.0 2018-03-27 14:26:26.451 warn Poll error count: 14 code: "App Timeout" modbus.0 2018-03-27 14:26:26.391 warn Poll error count: 13 code: "App Timeout" modbus.0 2018-03-27 14:26:26.292 warn Poll error count: 12 code: "App Timeout" modbus.0 2018-03-27 14:26:25.851 warn Poll error count: 11 code: "App Timeout" modbus.0 2018-03-27 14:26:25.751 warn Poll error count: 10 code: "App Timeout" modbus.0 2018-03-27 14:26:25.703 warn Poll error count: 9 code: "App Timeout" modbus.0 2018-03-27 14:26:25.274 warn Poll error count: 8 code: "App Timeout" modbus.0 2018-03-27 14:26:25.268 warn Poll error count: 7 code: "App Timeout" modbus.0 2018-03-27 14:26:25.258 info Disconnected from slave 192.168.50.136 modbus.0 2018-03-27 14:26:25.257 warn Poll error count: 6 code: "App Timeout" modbus.0 2018-03-27 14:26:25.054 warn Poll error count: 5 code: "App Timeout" modbus.0 2018-03-27 14:26:20.548 warn Poll error count: 4 code: "App Timeout" modbus.0 2018-03-27 14:26:19.522 warn Poll error count: 3 code: "App Timeout" modbus.0 2018-03-27 14:26:19.241 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:26:18.232 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:26:14.250 warn Poll error count: 3 code: "App Timeout" modbus.0 2018-03-27 14:26:14.189 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:26:14.090 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:26:06.031 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:26:04.156 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:26:02.048 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:25:39.590 warn Poll error count: 3 code: "App Timeout" modbus.0 2018-03-27 14:25:38.131 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:25:37.046 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:25:25.928 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:24:39.733 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:21:06.361 info Connected to slave 192.168.50.136 modbus.0 2018-03-27 14:21:06.147 info starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.modbus, node: v4.8.7 host.iobroker-deb 2018-03-27 14:21:05.688 info instance system.adapter.modbus.0 started with pid 4026 host.iobroker-deb 2018-03-27 14:21:03.194 info instance system.adapter.modbus.0 terminated with code 0 (OK) -
Ichh abe den Fehler auch - der Adapter liefert ordentliche Werte, aber er müllt auch das log zu:
host.iobroker-deb 2018-03-27 14:28:13.637 info Restart adapter system.adapter.modbus.0 because enabled host.iobroker-deb 2018-03-27 14:28:13.637 error instance system.adapter.modbus.0 terminated with code 0 (OK) modbus.0 2018-03-27 14:28:13.629 info terminating modbus.0 2018-03-27 14:28:13.623 error at Timer.listOnTimeout (timers.js:92:15) modbus.0 2018-03-27 14:28:13.623 error at null._onTimeout (/opt/iobroker/node_modules/iobroker.modbus/main.js:2231:18) modbus.0 2018-03-27 14:28:13.623 error at Object.main.pollResult (/opt/iobroker/node_modules/iobroker.modbus/main.js:2203:23) modbus.0 2018-03-27 14:28:13.623 error Error: Reconnect did not help, restart adapter modbus.0 2018-03-27 14:28:13.621 error uncaught exception: Reconnect did not help, restart adapter modbus.0 2018-03-27 14:28:13.619 warn Poll error count: 19 code: "App Timeout" modbus.0 2018-03-27 14:28:13.609 warn Poll error count: 18 code: "App Timeout" modbus.0 2018-03-27 14:28:13.568 warn Poll error count: 17 code: "App Timeout" modbus.0 2018-03-27 14:28:13.561 warn Poll error count: 16 code: "App Timeout" modbus.0 2018-03-27 14:28:13.381 warn Poll error count: 15 code: "App Timeout" modbus.0 2018-03-27 14:28:13.370 warn Poll error count: 14 code: "App Timeout" modbus.0 2018-03-27 14:28:13.247 warn Poll error count: 13 code: "App Timeout" modbus.0 2018-03-27 14:28:12.985 warn Poll error count: 12 code: "App Timeout" modbus.0 2018-03-27 14:28:12.915 warn Poll error count: 11 code: "App Timeout" modbus.0 2018-03-27 14:28:11.126 warn Poll error count: 10 code: "App Timeout" modbus.0 2018-03-27 14:28:09.508 warn Poll error count: 9 code: "App Timeout" modbus.0 2018-03-27 14:28:09.404 warn Poll error count: 8 code: "App Timeout" modbus.0 2018-03-27 14:28:08.103 warn Poll error count: 7 code: "App Timeout" modbus.0 2018-03-27 14:28:08.087 warn On error: {} modbus.0 2018-03-27 14:28:08.077 info Disconnected from slave 192.168.50.136 modbus.0 2018-03-27 14:28:08.076 warn Poll error count: 6 code: "App Timeout" modbus.0 2018-03-27 14:28:07.845 warn Poll error count: 5 code: "App Timeout" modbus.0 2018-03-27 14:28:07.835 warn Poll error count: 4 code: "App Timeout" modbus.0 2018-03-27 14:28:07.772 warn Poll error count: 3 code: "App Timeout" modbus.0 2018-03-27 14:28:07.750 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:28:05.875 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:28:02.667 warn Poll error count: 3 code: "App Timeout" modbus.0 2018-03-27 14:28:02.632 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:28:02.608 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:28:02.542 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:28:02.531 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:28:00.783 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:28:00.713 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:57.326 warn Poll error count: 3 code: "App Timeout" modbus.0 2018-03-27 14:27:57.306 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:27:57.297 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:55.571 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:27:55.546 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:52.098 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:50.340 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:27:50.328 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:45.128 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:27:45.125 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:39.901 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:27:39.894 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:27:25.452 info Connected to slave 192.168.50.136 modbus.0 2018-03-27 14:26:31.444 warn Poll error count: 18 code: "App Timeout" modbus.0 2018-03-27 14:26:30.435 warn Poll error count: 17 code: "App Timeout" modbus.0 2018-03-27 14:26:27.870 warn Poll error count: 16 code: "App Timeout" modbus.0 2018-03-27 14:26:26.617 warn Poll error count: 15 code: "App Timeout" modbus.0 2018-03-27 14:26:26.451 warn Poll error count: 14 code: "App Timeout" modbus.0 2018-03-27 14:26:26.391 warn Poll error count: 13 code: "App Timeout" modbus.0 2018-03-27 14:26:26.292 warn Poll error count: 12 code: "App Timeout" modbus.0 2018-03-27 14:26:25.851 warn Poll error count: 11 code: "App Timeout" modbus.0 2018-03-27 14:26:25.751 warn Poll error count: 10 code: "App Timeout" modbus.0 2018-03-27 14:26:25.703 warn Poll error count: 9 code: "App Timeout" modbus.0 2018-03-27 14:26:25.274 warn Poll error count: 8 code: "App Timeout" modbus.0 2018-03-27 14:26:25.268 warn Poll error count: 7 code: "App Timeout" modbus.0 2018-03-27 14:26:25.258 info Disconnected from slave 192.168.50.136 modbus.0 2018-03-27 14:26:25.257 warn Poll error count: 6 code: "App Timeout" modbus.0 2018-03-27 14:26:25.054 warn Poll error count: 5 code: "App Timeout" modbus.0 2018-03-27 14:26:20.548 warn Poll error count: 4 code: "App Timeout" modbus.0 2018-03-27 14:26:19.522 warn Poll error count: 3 code: "App Timeout" modbus.0 2018-03-27 14:26:19.241 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:26:18.232 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:26:14.250 warn Poll error count: 3 code: "App Timeout" modbus.0 2018-03-27 14:26:14.189 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:26:14.090 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:26:06.031 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:26:04.156 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:26:02.048 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:25:39.590 warn Poll error count: 3 code: "App Timeout" modbus.0 2018-03-27 14:25:38.131 warn Poll error count: 2 code: "App Timeout" modbus.0 2018-03-27 14:25:37.046 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:25:25.928 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:24:39.733 warn Poll error count: 1 code: "App Timeout" modbus.0 2018-03-27 14:21:06.361 info Connected to slave 192.168.50.136 modbus.0 2018-03-27 14:21:06.147 info starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.modbus, node: v4.8.7 host.iobroker-deb 2018-03-27 14:21:05.688 info instance system.adapter.modbus.0 started with pid 4026 host.iobroker-deb 2018-03-27 14:21:03.194 info instance system.adapter.modbus.0 terminated with code 0 (OK)@meisterf said in Modbus Adapter: Poll error count e3dc S10:
Ichh abe den Fehler auch - der Adapter liefert ordentliche Werte, aber er müllt auch das log zu:
-
-
Mal das PE11 oder was auch immer genau die Gegenstelle zum Modbus Adapter ist neu gestartet?
Mal einen PING auf das Device gemacht und die Zeiten angeschaut?
Hatten letztens den Fall mit SMA WR. Da lag es am WR, nach einem kompletten Neustart des WR war das Problem weg.
Konnte man an den Antwortzeiten des Ping sehen.
-
Mal das PE11 oder was auch immer genau die Gegenstelle zum Modbus Adapter ist neu gestartet?
Mal einen PING auf das Device gemacht und die Zeiten angeschaut?
Hatten letztens den Fall mit SMA WR. Da lag es am WR, nach einem kompletten Neustart des WR war das Problem weg.
Konnte man an den Antwortzeiten des Ping sehen.
Neustart habe ich schon öfter gemacht.
Ich hoffe das ich die Pingzeiten richt darstelle.
Last login: Sun Mar 13 17:39:00 on ttys000 achimpassiep@Mac-mini-von-Achim ~ % ping 192.168.8.44 PING 192.168.8.44 (192.168.8.44): 56 data bytes 64 bytes from 192.168.8.44: icmp_seq=0 ttl=255 time=7.551 ms 64 bytes from 192.168.8.44: icmp_seq=1 ttl=255 time=12.303 ms 64 bytes from 192.168.8.44: icmp_seq=2 ttl=255 time=7.255 ms 64 bytes from 192.168.8.44: icmp_seq=3 ttl=255 time=111.964 ms 64 bytes from 192.168.8.44: icmp_seq=4 ttl=255 time=7.291 ms 64 bytes from 192.168.8.44: icmp_seq=5 ttl=255 time=9.604 ms 64 bytes from 192.168.8.44: icmp_seq=6 ttl=255 time=4.741 ms 64 bytes from 192.168.8.44: icmp_seq=7 ttl=255 time=7.498 ms 64 bytes from 192.168.8.44: icmp_seq=8 ttl=255 time=6.295 ms 64 bytes from 192.168.8.44: icmp_seq=9 ttl=255 time=6.520 ms 64 bytes from 192.168.8.44: icmp_seq=10 ttl=255 time=6.082 ms 64 bytes from 192.168.8.44: icmp_seq=11 ttl=255 time=9.055 ms 64 bytes from 192.168.8.44: icmp_seq=12 ttl=255 time=7.106 ms 64 bytes from 192.168.8.44: icmp_seq=13 ttl=255 time=6.613 ms 64 bytes from 192.168.8.44: icmp_seq=14 ttl=255 time=27.431 ms 64 bytes from 192.168.8.44: icmp_seq=15 ttl=255 time=7.738 ms 64 bytes from 192.168.8.44: icmp_seq=16 ttl=255 time=6.470 ms 64 bytes from 192.168.8.44: icmp_seq=17 ttl=255 time=18.053 ms 64 bytes from 192.168.8.44: icmp_seq=18 ttl=255 time=44.237 ms 64 bytes from 192.168.8.44: icmp_seq=19 ttl=255 time=8.979 ms 64 bytes from 192.168.8.44: icmp_seq=20 ttl=255 time=7.036 ms 64 bytes from 192.168.8.44: icmp_seq=21 ttl=255 time=9.036 ms 64 bytes from 192.168.8.44: icmp_seq=22 ttl=255 time=6.447 ms 64 bytes from 192.168.8.44: icmp_seq=23 ttl=255 time=13.222 ms 64 bytes from 192.168.8.44: icmp_seq=24 ttl=255 time=7.086 msMOD Edit: Log in Code Tags
-
Neustart habe ich schon öfter gemacht.
Ich hoffe das ich die Pingzeiten richt darstelle.
Last login: Sun Mar 13 17:39:00 on ttys000 achimpassiep@Mac-mini-von-Achim ~ % ping 192.168.8.44 PING 192.168.8.44 (192.168.8.44): 56 data bytes 64 bytes from 192.168.8.44: icmp_seq=0 ttl=255 time=7.551 ms 64 bytes from 192.168.8.44: icmp_seq=1 ttl=255 time=12.303 ms 64 bytes from 192.168.8.44: icmp_seq=2 ttl=255 time=7.255 ms 64 bytes from 192.168.8.44: icmp_seq=3 ttl=255 time=111.964 ms 64 bytes from 192.168.8.44: icmp_seq=4 ttl=255 time=7.291 ms 64 bytes from 192.168.8.44: icmp_seq=5 ttl=255 time=9.604 ms 64 bytes from 192.168.8.44: icmp_seq=6 ttl=255 time=4.741 ms 64 bytes from 192.168.8.44: icmp_seq=7 ttl=255 time=7.498 ms 64 bytes from 192.168.8.44: icmp_seq=8 ttl=255 time=6.295 ms 64 bytes from 192.168.8.44: icmp_seq=9 ttl=255 time=6.520 ms 64 bytes from 192.168.8.44: icmp_seq=10 ttl=255 time=6.082 ms 64 bytes from 192.168.8.44: icmp_seq=11 ttl=255 time=9.055 ms 64 bytes from 192.168.8.44: icmp_seq=12 ttl=255 time=7.106 ms 64 bytes from 192.168.8.44: icmp_seq=13 ttl=255 time=6.613 ms 64 bytes from 192.168.8.44: icmp_seq=14 ttl=255 time=27.431 ms 64 bytes from 192.168.8.44: icmp_seq=15 ttl=255 time=7.738 ms 64 bytes from 192.168.8.44: icmp_seq=16 ttl=255 time=6.470 ms 64 bytes from 192.168.8.44: icmp_seq=17 ttl=255 time=18.053 ms 64 bytes from 192.168.8.44: icmp_seq=18 ttl=255 time=44.237 ms 64 bytes from 192.168.8.44: icmp_seq=19 ttl=255 time=8.979 ms 64 bytes from 192.168.8.44: icmp_seq=20 ttl=255 time=7.036 ms 64 bytes from 192.168.8.44: icmp_seq=21 ttl=255 time=9.036 ms 64 bytes from 192.168.8.44: icmp_seq=22 ttl=255 time=6.447 ms 64 bytes from 192.168.8.44: icmp_seq=23 ttl=255 time=13.222 ms 64 bytes from 192.168.8.44: icmp_seq=24 ttl=255 time=7.086 msMOD Edit: Log in Code Tags
@koenigpils läuft iobroker auf dem MAC ?
Du musst mal Ping vom iobroker Rechner aus machen
Wobei die Antwort Zeiten schon teilweise „hoch“ sind und stark schwanken.
-
@koenigpils läuft iobroker auf dem MAC ?
Du musst mal Ping vom iobroker Rechner aus machen
Wobei die Antwort Zeiten schon teilweise „hoch“ sind und stark schwanken.
@wendy2702
Komme nicht mehr auf meinen PaspyThe fingerprint for the ED25519 key sent by the remote host is SHA256:otCrXLnicRgAwbenAvIfyWvrpov7E6eEK7VZNBjXiJM. Please contact your system administrator. Add correct host key in /Users/achimpassiep/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /Users/achimpassiep/.ssh/known_hosts:3 Host key for 192.168.8.35 has changed and you have requested strict checking. Host key verification failed. achimpassiep@Mac-mini-von-Achim ~ % Last login: Sun Mar 13 17:56:00 on ttys000 achimpassiep@Mac-mini-von-Achim ~ % ssh pi@192.168.8.35 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ED25519 key sent by the remote host is SHA256:otCrXLnicRgAwbenAvIfyWvrpov7E6eEK7VZNBjXiJM. Please contact your system administrator. Add correct host key in /Users/achimpassiep/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /Users/achimpassiep/.ssh/known_hosts:3 Host key for 192.168.8.35 has changed and you have requested strict checking. Host key verification failed. achimpassiep@Mac-mini-von-Achim ~ %MOD Edit: Log in Code Tags
-
@wendy2702
Komme nicht mehr auf meinen PaspyThe fingerprint for the ED25519 key sent by the remote host is SHA256:otCrXLnicRgAwbenAvIfyWvrpov7E6eEK7VZNBjXiJM. Please contact your system administrator. Add correct host key in /Users/achimpassiep/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /Users/achimpassiep/.ssh/known_hosts:3 Host key for 192.168.8.35 has changed and you have requested strict checking. Host key verification failed. achimpassiep@Mac-mini-von-Achim ~ % Last login: Sun Mar 13 17:56:00 on ttys000 achimpassiep@Mac-mini-von-Achim ~ % ssh pi@192.168.8.35 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ED25519 key sent by the remote host is SHA256:otCrXLnicRgAwbenAvIfyWvrpov7E6eEK7VZNBjXiJM. Please contact your system administrator. Add correct host key in /Users/achimpassiep/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /Users/achimpassiep/.ssh/known_hosts:3 Host key for 192.168.8.35 has changed and you have requested strict checking. Host key verification failed. achimpassiep@Mac-mini-von-Achim ~ %MOD Edit: Log in Code Tags
@koenigpils was steht in dem erwähnten known Hosts File?
-
@koenigpils was steht in dem erwähnten known Hosts File?
@wendy2702
habe den Mac erst seit kurzen, ich weiss nicht wie ich da hinkomme. -
@wendy2702
habe den Mac erst seit kurzen, ich weiss nicht wie ich da hinkomme. -
@wendy2702
Geht wieder ,tausend Dank64 bytes from 192.168.8.44: icmp_seq=1 ttl=255 time=3.90 ms 64 bytes from 192.168.8.44: icmp_seq=2 ttl=255 time=5.49 ms 64 bytes from 192.168.8.44: icmp_seq=3 ttl=255 time=4.07 ms 64 bytes from 192.168.8.44: icmp_seq=4 ttl=255 time=4.13 ms 64 bytes from 192.168.8.44: icmp_seq=5 ttl=255 time=3.16 ms 64 bytes from 192.168.8.44: icmp_seq=6 ttl=255 time=2.89 ms 64 bytes from 192.168.8.44: icmp_seq=7 ttl=255 time=13.9 ms 64 bytes from 192.168.8.44: icmp_seq=8 ttl=255 time=3.43 ms 64 bytes from 192.168.8.44: icmp_seq=9 ttl=255 time=3.79 ms 64 bytes from 192.168.8.44: icmp_seq=10 ttl=255 time=3.56 ms 64 bytes from 192.168.8.44: icmp_seq=11 ttl=255 time=4.80 ms 64 bytes from 192.168.8.44: icmp_seq=12 ttl=255 time=8.21 ms 64 bytes from 192.168.8.44: icmp_seq=13 ttl=255 time=3.36 ms 64 bytes from 192.168.8.44: icmp_seq=14 ttl=255 time=4.06 ms 64 bytes from 192.168.8.44: icmp_seq=15 ttl=255 time=9.30 ms 64 bytes from 192.168.8.44: icmp_seq=16 ttl=255 time=3.81 ms 64 bytes from 192.168.8.44: icmp_seq=17 ttl=255 time=3.49 ms 64 bytes from 192.168.8.44: icmp_seq=18 ttl=255 time=4.31 ms 64 bytes from 192.168.8.44: icmp_seq=19 ttl=255 time=4.69 ms 64 bytes from 192.168.8.44: icmp_seq=20 ttl=255 time=3.88 ms 64 bytes from 192.168.8.44: icmp_seq=21 ttl=255 time=6.50 ms 64 bytes from 192.168.8.44: icmp_seq=22 ttl=255 time=5.00 ms 64 bytes from 192.168.8.44: icmp_seq=23 ttl=255 time=18.5 ms 64 bytes from 192.168.8.44: icmp_seq=24 ttl=255 time=4.39 ms 64 bytes from 192.168.8.44: icmp_seq=25 ttl=255 time=6.01 ms 64 bytes from 192.168.8.44: icmp_seq=26 ttl=255 time=48.7 ms 64 bytes from 192.168.8.44: icmp_seq=27 ttl=255 time=3.15 ms 64 bytes from 192.168.8.44: icmp_seq=28 ttl=255 time=4.83 ms 64 bytes from 192.168.8.44: icmp_seq=29 ttl=255 time=4.71 ms 64 bytes from 192.168.8.44: icmp_seq=30 ttl=255 time=3.19 ms 64 bytes from 192.168.8.44: icmp_seq=31 ttl=255 time=5.28 ms 64 bytes from 192.168.8.44: icmp_seq=32 ttl=255 time=3.74 ms 64 bytes from 192.168.8.44: icmp_seq=33 ttl=255 time=18.8 msMOD Edit: Log in Code Tags
-
@wendy2702
Geht wieder ,tausend Dank64 bytes from 192.168.8.44: icmp_seq=1 ttl=255 time=3.90 ms 64 bytes from 192.168.8.44: icmp_seq=2 ttl=255 time=5.49 ms 64 bytes from 192.168.8.44: icmp_seq=3 ttl=255 time=4.07 ms 64 bytes from 192.168.8.44: icmp_seq=4 ttl=255 time=4.13 ms 64 bytes from 192.168.8.44: icmp_seq=5 ttl=255 time=3.16 ms 64 bytes from 192.168.8.44: icmp_seq=6 ttl=255 time=2.89 ms 64 bytes from 192.168.8.44: icmp_seq=7 ttl=255 time=13.9 ms 64 bytes from 192.168.8.44: icmp_seq=8 ttl=255 time=3.43 ms 64 bytes from 192.168.8.44: icmp_seq=9 ttl=255 time=3.79 ms 64 bytes from 192.168.8.44: icmp_seq=10 ttl=255 time=3.56 ms 64 bytes from 192.168.8.44: icmp_seq=11 ttl=255 time=4.80 ms 64 bytes from 192.168.8.44: icmp_seq=12 ttl=255 time=8.21 ms 64 bytes from 192.168.8.44: icmp_seq=13 ttl=255 time=3.36 ms 64 bytes from 192.168.8.44: icmp_seq=14 ttl=255 time=4.06 ms 64 bytes from 192.168.8.44: icmp_seq=15 ttl=255 time=9.30 ms 64 bytes from 192.168.8.44: icmp_seq=16 ttl=255 time=3.81 ms 64 bytes from 192.168.8.44: icmp_seq=17 ttl=255 time=3.49 ms 64 bytes from 192.168.8.44: icmp_seq=18 ttl=255 time=4.31 ms 64 bytes from 192.168.8.44: icmp_seq=19 ttl=255 time=4.69 ms 64 bytes from 192.168.8.44: icmp_seq=20 ttl=255 time=3.88 ms 64 bytes from 192.168.8.44: icmp_seq=21 ttl=255 time=6.50 ms 64 bytes from 192.168.8.44: icmp_seq=22 ttl=255 time=5.00 ms 64 bytes from 192.168.8.44: icmp_seq=23 ttl=255 time=18.5 ms 64 bytes from 192.168.8.44: icmp_seq=24 ttl=255 time=4.39 ms 64 bytes from 192.168.8.44: icmp_seq=25 ttl=255 time=6.01 ms 64 bytes from 192.168.8.44: icmp_seq=26 ttl=255 time=48.7 ms 64 bytes from 192.168.8.44: icmp_seq=27 ttl=255 time=3.15 ms 64 bytes from 192.168.8.44: icmp_seq=28 ttl=255 time=4.83 ms 64 bytes from 192.168.8.44: icmp_seq=29 ttl=255 time=4.71 ms 64 bytes from 192.168.8.44: icmp_seq=30 ttl=255 time=3.19 ms 64 bytes from 192.168.8.44: icmp_seq=31 ttl=255 time=5.28 ms 64 bytes from 192.168.8.44: icmp_seq=32 ttl=255 time=3.74 ms 64 bytes from 192.168.8.44: icmp_seq=33 ttl=255 time=18.8 msMOD Edit: Log in Code Tags
@koenigpils
Hallo WendyHabe es hinbekommen
Pollzeit 60000msVielen Dank für deine Unterstützung. :+1:
887
Online32.6k
Benutzer81.9k
Themen1.3m
Beiträge