Pimatic process gets killed every night - causing bei Telegram plugin?

OrTiN

Hi all,
I have a problem with the pimatic system of my neighbor. Since this week the pimatic process gets killed every night. The last I can find in the log is following:

.
.
.
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.713 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.823 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.798 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
.
.
.

I think that this is causing the killing of pimatic process at the end. Am I right?

My system is also equipped with the Telegram plugin and I haven’t such a problem. Has someone an idea how to fix it? Simply reinstall plugin and maybe get a new apitoken?

Gleno0h

@OrTiN the host is unreachable for the telegram bot.

Did you define the host somewhere? Could you post that here?

OrTiN

Do you mean the host within the telegram plugin?
The host there is:

"host": "api.telegram.org",

As long as pimatic is running telegram in working and sends messages if necessary (triggered by rule)

Gleno0h

@OrTiN no, your neighbor is using a telegram bot.

Something wants to connect to 149.154.167.199:443

Which is https://core.telegram.org/bots

Could be that that ip address reboots their system at night. Are the crash times always the same?

OrTiN

Unfortunately I can’t see the the time of the crash. The log entries of the bot are not added with the related time. But it seems to be always between 5:00am and 7:00am.

I checked the source of the ip address as you. See here.

All the IP’s of the log can be found there:
-149.154.167.197
-149.154.167.198
-149.154.167.199

I have no idea why it is not reachable for his system.

The first error in the log starts yesterday a round about 7:00pm. After restart this morning at 7:20am the errors are still the same.

There is as well a reconnection so the IP should be reachable. But why it is disconnecting? Have no idea

[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.197:443
...
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.835 seconds

Maybe it is a problem to take an existing config and adapt is simply. I did it this way. Took my config, copied it to the system of my neighbor and adapt the api only.
I will uninstall the telegram plugin and will reinstall it. Maybe it will fix the problem.

Gleno0h

@OrTiN yeah it it strange behaviour. Indeed try to reinstall the plugin.

Also, could there be a firewall on your neighbors pi? Or maybe there is a firewall enabled in the router?

Normally it shouldnt matter but it could be some ports are blocked (433) which wouldnt make sense but maybe just check it?

Or simply put the pi in the DMZ to test it.

OrTiN

Now I check my log. It has as well the connection problems, but my system is running. Maybe telegram if filling the log, but the process kill occures for an other reason. I’m lost!

Gleno0h

@OrTiN Maybe you could post the crash from pimatic-daemon.log?

OrTiN

Problem is that no crash is logged. The deamon simply stopped.
sudo pimatic.js status returned “PID exists, but process is dead”. So I start is with sudo pimatic.js start. Since this morning the system is running…

18:53:51.048 2017-09-19 Tuesday
18:54:00.653 [pimatic] info: Starting pimatic version 0.9.42
18:54:12.458 [pimatic, ppm] info: 2.15.12
18:54:12.537 [pimatic] info: Loading plugin: "pimatic-cron" (0.8.8)
18:54:13.110 [pimatic] info: Loading plugin: "pimatic-mobile-frontend" (0.9.12)
18:54:14.016 [pimatic] info: Loading plugin: "pimatic-iframe" (0.3.1)
18:54:14.071 [pimatic] info: Loading plugin: "pimatic-openweather" (0.9.4)
18:54:14.152 [pimatic] info: Loading plugin: "pimatic-sunrise" (0.8.7)
18:54:14.190 [pimatic] info: Loading plugin: "pimatic-sysinfo" (0.9.4)
18:54:14.383 [pimatic] info: Loading plugin: "pimatic-gpio" (0.9.0)
18:54:14.474 [pimatic] info: Loading plugin: "pimatic-ping" (0.9.5)
18:54:14.545 [pimatic] info: Loading plugin: "pimatic-shell-execute" (0.9.11)
18:54:14.603 [pimatic] info: Loading plugin: "pimatic-filebrowser" (0.9.0)
18:54:14.794 [pimatic] info: Loading plugin: "pimatic-homeduino" (0.9.11)
18:54:15.626 [pimatic] info: Loading plugin: "pimatic-mqtt" (0.9.7)
18:54:16.184 [pimatic] info: Loading plugin: "pimatic-links" (0.8.6)
18:54:16.212 [pimatic] info: Loading plugin: "pimatic-log-reader" (0.9.1)
18:54:16.253 [pimatic] info: Loading plugin: "pimatic-telegram" (1.1.6)
18:54:17.536 [pimatic-cron] info: the time is: Tue Sep 19 2017 18:54:17 GMT+0200 (CEST)
18:54:17.784 [pimatic-sunrise] info: Your location is set to lat: 52.1411497, long: 10.5416876
18:54:18.972 [pimatic-mqtt] debug: Registering device class MqttSwitch
18:54:19.270 [pimatic-mqtt] info: Successfully connected to MQTT Broker default
18:54:19.438 [pimatic] info: New device "Einfahrt"...
18:54:19.484 [pimatic] info: New device "Lüften"...
18:54:19.521 [pimatic] info: New device "Temperaturfühler-Bad nativ"...
18:54:19.605 [pimatic] info: New device "OpenWeather aktuell"...
18:54:19.642 [pimatic] info: New device "Temperaturfühler Adrian nativ"...
18:54:19.674 [pimatic] info: New device "Temperaturfühler Wohnzimmer nativ"...
18:54:19.702 [pimatic] info: New device "Temperaturfühler Kühlschrank nativ"...
18:54:19.749 [pimatic] info: New device "Sonnensensor"...
18:54:19.782 [pimatic] info: New device "System"...
18:54:19.828 [pimatic] info: New device "Systemzeit"...
18:54:19.867 [pimatic] info: New device "Systemlaufzeit"...
18:54:19.892 [pimatic] info: New device "CPU"...
18:54:19.921 [pimatic] info: New device "Systemspeicher"...
18:54:19.946 [pimatic] info: New device "Festplattenspeicher"...
18:54:20.066 [pimatic] info: New device "pimatic Version"...
18:54:20.106 [pimatic] info: New device "Pimatic Version Abfrage"...
18:54:20.135 [pimatic] info: New device "pimatic Update Info"...
18:54:20.152 [pimatic] info: New device "Einfahrt"...
18:54:20.198 [pimatic] info: New device "Küchentürkontakt"...
18:54:20.216 [pimatic] info: New device "Sonnenschutz 50%"...
18:54:20.235 [pimatic] info: New device "Sonnenschutz 75%"...
18:54:20.253 [pimatic] info: New device "Sonnenschutz Schlaf & Kinderzimmer"...
18:54:20.271 [pimatic] info: New device "Sonnenschutz Osten"...
18:54:20.295 [pimatic] info: New device "Sonnenschutz Westen"...
18:54:20.310 [pimatic] info: New device "Sonnenschutzautomatik"...
18:54:20.338 [pimatic] info: New device "Sonnenschutz manuell"...
18:54:20.372 [pimatic] info: New device "Einfahrt Aufzeichungsgröße"...
18:54:20.398 [pimatic] info: New device "Außenbedingungen"...
18:54:20.441 [pimatic] info: New device "Sonnenverlauf"...
18:54:21.213 [pimatic] info: New device "Temperaturfühler Schlafzimmer nativ"...
18:54:21.234 [pimatic] info: New device "Terrassenlicht"...
18:54:21.261 [pimatic] info: New device "Terrasse DummyDimmer"...
18:54:21.295 [pimatic] info: New device "Stromverbrauch"...
18:54:21.317 [pimatic] info: New device "Klingeltaster"...
18:54:21.337 [pimatic] info: New device "Sonnenschutz Süd+"...
18:54:21.351 [pimatic] info: New device "Garagentor"...
18:54:21.371 [pimatic] info: New device "Temperaturfühler Wohnzimmer"...
18:54:21.390 [pimatic] info: New device "Temperaturfühler Adrian"...
18:54:21.410 [pimatic] info: New device "Temperaturfühler Schlafzimmer"...
18:54:21.429 [pimatic] info: New device "Temperaturfühler Bad"...
18:54:21.448 [pimatic] info: New device "Temperaturfühler Kühlschrank"...
18:54:21.466 [pimatic] info: New device "Dimmerstatus"...
18:54:21.490 [pimatic] info: New device "VZLogger Strom"...
18:54:21.531 [pimatic] info: New device "Beleuchtung Vorgarten"...
18:54:21.565 [pimatic] info: New device "Systemzeit kurz"...
18:54:21.581 [pimatic] info: New device "Küchentür offen (manuell) "...
18:54:21.595 [pimatic] info: New device "Jemand DA?"...
18:54:21.608 [pimatic] info: New device "Klingelsperre"...
18:54:21.621 [pimatic] info: New device "Klingel"...
18:54:21.647 [pimatic] info: New device "Klingelstatus"...
18:54:21.664 [pimatic] info: New device "BT Klingel"...
18:54:21.677 [pimatic] info: New device "sonstiges"...
18:54:21.702 [pimatic] info: New device "Jalousiemodul Küche"...
18:54:21.729 [pimatic] info: New device "Jalousiemodul Terrasse"...
18:54:21.750 [pimatic] info: New device "Jalousiemodul WC"...
18:54:21.779 [pimatic] info: New device "Jalousiemodul Bad"...
18:54:21.807 [pimatic] info: New device "Jalousiemodul Schlafzimmer"...
18:54:21.830 [pimatic] info: New device "Jalousiemodule Osten"...
18:54:21.859 [pimatic] info: New device "Jalousiemodule Westen"...
18:54:21.879 [pimatic] info: New device "Jalousiemodule außer Schlaf- & Kinderzimmer"...
18:54:21.902 [pimatic] info: New device "Alle Jalousiemodule"...
18:54:21.918 [pimatic] info: New device "Sonnenschutz 50% anwesend"...
18:54:21.936 [pimatic] info: New device "Sonnenschutz 50% abwesend"...
18:54:21.949 [pimatic] info: New device "Sonnenschutz 75%"...
18:54:21.962 [pimatic] info: New device "Sonnenschutz Süd+"...
18:54:21.989 [pimatic] info: New device "Garagentor"...
18:54:22.014 [pimatic] info: New device "Sonnensensor Differenzwert"...
18:54:22.048 [pimatic] info: New device "Jalousienzeit morgens (Wochenende)"...
18:54:22.068 [pimatic] info: New device "Klingellautstärke"...
18:54:22.085 [pimatic] info: New device "Klingel auf 'normal' stellen um"...
18:54:22.103 [pimatic] info: New device "Klingel auf 'leise' stellen um"...
18:54:22.115 [pimatic] info: New device "Klingel deaktivieren um"...
18:54:22.132 [pimatic] info: New device "Abend Lux Trigger"...
18:54:22.151 [pimatic-telegram] info: Starting Telegram listener
18:54:22.188 [pimatic] info: New device "HomationBot "Telegram" Empfänger"...
18:54:22.226 [pimatic] info: New device "Jalousiemodul Stube Kamin"...
18:54:22.270 [pimatic] info: New device "Jalousiemodul-Stube-Sofa"...
18:54:22.293 [pimatic] info: New device "Jalousiemodul-Luke"...
18:54:22.314 [pimatic] info: New device "Jalousiemodul-Gästezimmer"...
18:54:22.346 [pimatic] info: New device "Jalousiemodul-Lea"...
18:54:22.373 [pimatic] info: New device "Jalousiemodul-Flur"...
18:54:22.394 [pimatic] info: New device "Jalousiemodul-HWR"...
18:54:22.415 [pimatic] info: New device "Jalousiemodule-außer-Küche"...
18:54:22.436 [pimatic] info: New device "Jalousiemodule außer Küche, Schlaf- & Kinderzimmer"...
18:54:22.449 [pimatic] info: New device "Jalousienzeit morgens (Werktags)"...
18:54:22.487 [pimatic] info: New device "OpenSenseMap Temperatur (Sonne)"...
18:54:22.521 [pimatic] info: New device "OpenSenseMap Helligkeit"...
18:54:22.562 [pimatic] info: New device "OpenSenseMap Temperatur (Referenz)"...
18:54:22.578 [pimatic] info: New device "Morgens Lux Trigger"...
18:54:22.602 [pimatic] info: New device "Treppenlicht"...
18:54:22.637 [pimatic] info: New device "Darth"...
18:54:22.720 [pimatic] info: New device "Vader"...
18:54:22.831 [pimatic] info: New device "Luke"...
18:55:03.445 [pimatic-telegram] info: Listener enabled ruleset command: ' Alles gut? '
18:55:05.441 [pimatic-mobile-frontend] info: packing static assets
18:55:06.521 [pimatic-mobile-frontend] info: packing static assets finished
18:55:06.528 [pimatic-mobile-frontend] info: rendering html
18:55:09.114 [pimatic-homeduino] info: Connected to homeduino device.
[bot.info] bot started
18:55:13.459 [pimatic-mobile-frontend] info: rendering html finished
18:55:13.592 [pimatic] info: Listening for HTTP-request on port 80...
18:55:14.645 [pimatic-telegram] info: [Message] Sending Telegram "Homation erfolgreich gestartet Di. 19. Sep. 18:55:13" to Darth: success
18:58:16.702 [pimatic] info: Recreating "Jalousiemodul Flur"...
18:58:27.262 [pimatic] info: Recreating "Jalousiemodul HWR"...
18:58:36.666 [pimatic] info: Recreating "Jalousiemodul Luke"...
18:58:46.065 [pimatic] info: Recreating "Jalousiemodul Lea"...
18:58:58.589 [pimatic] info: Recreating "Jalousiemodule außer Küche"...
18:59:14.022 [pimatic] info: Recreating "Jalousiemodul Stube Sofa"...
18:59:24.097 [pimatic] info: Recreating "Jalousiemodul Gästezimmer"...
19:32:52.592 [pimatic-telegram] info: [Message] Sending Telegram "Jalousien fahren gleich runter - Abend." to Darth: success
19:32:52.621 [pimatic-telegram] info: [Message] Sending Telegram "Jalousien fahren gleich runter - Abend." to Vader: success
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.807 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.197:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.838 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.197:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.846 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.197:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.815 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.88 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.903 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.894 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 6.058 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 6.016 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.915 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.821 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.817 seconds
22:40:00.454 [pimatic-telegram] info: [Message] Sending Telegram "Jalousien fahren in 5 Minuten herunter - Nacht. Zum verhindern 'Lüften' aktivieren!" to Darth: success
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.713 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.823 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.798 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.835 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.200:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.815 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.200:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.823 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.197:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.798 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.197:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.857 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.898 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.847 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.712 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.794 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.835 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.815 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.819 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.826 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.851 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.875 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 6.175 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.825 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.811 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.817 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.843 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.819 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.197:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.816 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.199:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.831 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.874 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.764 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.198:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.904 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.200:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.836 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.200:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.805 seconds
[bot.error.update] Error: connect EHOSTUNREACH 149.154.167.197:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...
[bot.info.update] reconnected after 5.841 seconds
[bot.error.update] Error: connect ENETUNREACH 149.154.167.197:443
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
[bot.info.update] reconnecting in 5 seconds...

Restart this morging

07:18:57.777 2017-09-20 Wednesday
07:19:06.783 [pimatic] info: Starting pimatic version 0.9.42
07:19:11.724 [pimatic, ppm] info: 2.15.12
.
.
.

mwittig

@OrTiN said in Pimatic process gets killed every night - causing bei Telegram plugin?:

I am wondering why 149.154.167.199 is unreachable.

Do you switch off your internet / wifi at night?
Does the “unreachable” error starts to occur at about the same time each night?

Appart from this, I agree with you, the telegram plugin (or the underlying lib) might be guilty as it seems to trial reconnects in a tight 5s loop. This may cause the system to run out of file descriptor, but generally it should not kill your pimatic process unless the call loop causes an stack overflow. Which Raspi model and power supply are you using?

OrTiN

The raspberry, it’s a 3rd generation model, is always online. The power supply is the 2.5A original power adapter. All the pimatic data are located to a 2.5" HDD. The power LED is steady illuminated, no flicking.

The connection problems start short after starting the system. Crazy is that there are connection problems logged, but telegram sends messages to the same time. See 22:40h. When I’m back at home I will go to my neighbor and check the latest logs.
As I wrote in my last post from today morning I have the same messages in my log. Till now my system works. Will see what happens this night with it…

OrTiN

I check the log of my neighbor and mine. Both shows the same errors. His pimatic daemon was stopped once more, and once more without a error in the log. My system is still running.
Now I added a rule to my neighbors config which writes a log entry every minute to see the time when pimatic stops working. Will see in the next days what will be the result.
BTW the log entries are correct. Telegram is not reachable on the announced IP’s (https):
149.154.167.198:443
149.154.167.199:443
149.154.167.200:443

but here:
149.154.167.198
149.154.167.199
149.154.167.200

Is here anybody else who’s using telegram with the same log entries?

Gleno0h

@OrTiN

PING 149.154.167.198 (149.154.167.198) 56(84) bytes of data. ---
64 bytes from 149.154.167.198: icmp_seq=1 ttl=57 time=11.2 ms
64 bytes from 149.154.167.198: icmp_seq=2 ttl=57 time=11.0 ms
64 bytes from 149.154.167.198: icmp_seq=3 ttl=57 time=11.0 ms
64 bytes from 149.154.167.198: icmp_seq=4 ttl=57 time=11.0 ms


--- 149.154.167.198 ping statistics ---

					
packets transmitted 	4
received 	4
packet loss 	0 %
time 	3003 ms

149.154.167.198:443 port is open

Seems okay to me.

Maybe a certificate issue?
Maybe you could post a issue on the pimatic-telegram github?

OrTiN

Hmm, but you send your ping to the ip only (that should be port 80, am I right) not to the https port 443. Up to my knowledge it is not possible to send a ping to a specific ip:port kombi. Maybe I wrong.
Sure I can post it on git, but I could be only an temporary problem. I use telegram since some weeks and the problem occurs from yesterday. Therefore it would be nice to compare my finding this an other user who is also using telegram.

Gleno0h

@OrTiN yes you are right. But as you can see, the ip address is available, and after that i did a port scan that reports it is open. 1+1=2

I also noticed you send two messages at the same time?

19:32:52.592 [pimatic-telegram] info: [Message] Sending Telegram "Jalousien fahren gleich runter - Abend." to Darth: success
19:32:52.621 [pimatic-telegram] info: [Message] Sending Telegram "Jalousien fahren gleich runter - Abend." to Vader: success

Could you try and set a 5 seconds delay between person 1 and 2?

I also think it is a temporary issue. So anyone else has these problems with this plugin?

OrTiN

Okay understand, I was wondering how you could see the port 443 was open with the ping only. When you scanned the port in an other step its clear. Thx for you investigation.

To send more than one message is a function of the telegram plugin. I moved from pushbullet due to this. It would be possible to send the message in two steps with a gap of 1 or 2 secs, but it should work like it is.

First info from my neighbor from tonight. His system is still running after I uninstall it from his system. Have no idea why it work for me without removing it from my system.

mwittig

@OrTiN Possibly the guilty is the default device configuration which sets the retry timout to 5000ms. Try to set set the retryTimeout as part of the device configuration to 20000 for a start. May be it helps (if it is not stack overflow).

https://github.com/SenTzu01/pimatic-telegram/blob/master/telegram-device-config-schema.coffee#L39-L42

OrTiN

Adapted the timeout this morning. Now there are less errors in the log. Will see if this lets the system of my neighbor living peacely :D.

mwittig

@OrTiN As a follow-up on the chat communication we had I think we need @Dan took into the issue. As far as I can see he is using a fork of “telebot” which seems to be outdated (100 commits behind parent). Maybe the fork needs to be updated to match up with the latest version of the Telegram APIs.

https://github.com/SenTzu01/pimatic-telegram/issues/30

OrTiN

Hi all,
have some news for this. The pimatic daemon kill is not related to telegram as seems. I uninstalled the plugin and the daemon is still killed for known reason. The daemon lives ~20-21h now. With telegram it was only ~8-10h. It seems really to be a kind of stack overflow.
Could it be an idea to delete all plugin folders and let the system recreate it, what you think? Raspian itself works fine as I can see - SMB, pureFTP… are running without any problems.