<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Telegram Adapter gelb]]></title><description><![CDATA[<p dir="auto">Hallo Freunde seit heute morgen ist der Telegrammadapter gelb. Wer hat noch Probleme?</p>
<pre><code>elegram.0	2021-09-10 21:34:32.280	info	(6020) terminating
telegram.0	2021-09-10 21:34:31.744	error	(6020) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
telegram.0	2021-09-10 21:34:31.743	error	(6020) RequestError: Error: getaddrinfo EAI_AGAIN api.telegram.org at new RequestError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/opt/
telegram.0	2021-09-10 21:34:31.743	error	(6020) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
telegram.0	2021-09-10 21:34:31.741	error	(6020) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
telegram.0	2021-09-10 21:34:26.720	error	(6020) getMe Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
telegram.0	2021-09-10 21:34:10.660	info	(6020) starting. Version 1.9.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v12.22.2, js-controller: 3.2.16
telegram.0	2021-09-10 21:33:49.292	warn	(5009) Terminated (UNCAUGHT_EXCEPTION): Without reason
telegram.0	2021-09-10 21:33:49.288	info	(5009) terminating
telegram.0	2021-09-10 21:33:48.751	error	(5009) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
telegram.0	2021-09-10 21:33:48.750	error	at processTicksAndRejections (internal/process/task_queues.js:84:21)
telegram.0	2021-09-10 21:33:48.750	error	at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
telegram.0	2021-09-10 21:33:48.750	error	at emitErrorNT (internal/streams/destroy.js:92:8)
telegram.0	2021-09-10 21:33:48.750	error	at TLSSocket.emit (events.js:314:20)
telegram.0	2021-09-10 21:33:48.750	error	at TLSSocket.socketErrorListener (_http_client.js:427:9)
telegram.0	2021-09-10 21:33:48.750	error	at ClientRequest.emit (events.js:314:20)
telegram.0	2021-09-10 21:33:48.750	error	at Request.onRequestError (/opt/iobroker/node_modules/request/request.js:877:8)
telegram.0	2021-09-10 21:33:48.750	error	at Request.emit (events.js:314:20)
telegram.0	2021-09-10 21:33:48.750	error	at self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
telegram.0	2021-09-10 21:33:48.750	error	at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
telegram.0	2021-09-10 21:33:48.750	error	at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:87:29)
telegram.0	2021-09-10 21:33:48.750	error	at new RequestError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:14:15)
telegram.0	2021-09-10 21:33:48.750	error	(5009) RequestError: Error: getaddrinfo EAI_AGAIN api.telegram.org
telegram.0	2021-09-10 21:33:48.749	error	(5009) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
telegram.0	2021-09-10 21:33:48.747	error	(5009) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
telegram.0	2021-09-10 21:33:43.732	error	(5009) getMe Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
</code></pre>
]]></description><link>https://forum.iobroker.net/topic/47684/telegram-adapter-gelb</link><generator>RSS for Node</generator><lastBuildDate>Wed, 27 May 2026 19:26:03 GMT</lastBuildDate><atom:link href="https://forum.iobroker.net/topic/47684.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 10 Sep 2021 19:38:00 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Telegram Adapter gelb on Fri, 10 Sep 2021 20:29:18 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/glasfaser" aria-label="Profile: glasfaser">@<bdi>glasfaser</bdi></a> stimmt es wurde aber nichts geändert Ich habe Pihole aufgerufen und da stand DNS Server nicht gestartet. dann habe ich den PI neu gestartet und jetzt alles grün. Nun hoffe ich das es das war. Dann brauche ich das nächste mal nur den Pi neu starten. auf sowas muss man erst mal kommen.<br />
Danke</p>
]]></description><link>https://forum.iobroker.net/post/675844</link><guid isPermaLink="true">https://forum.iobroker.net/post/675844</guid><dc:creator><![CDATA[ostseereiter]]></dc:creator><pubDate>Fri, 10 Sep 2021 20:29:18 GMT</pubDate></item><item><title><![CDATA[Reply to Telegram Adapter gelb on Fri, 10 Sep 2021 19:43:46 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ostseereiter" aria-label="Profile: ostseereiter">@<bdi>ostseereiter</bdi></a> sagte in <a href="/post/675817">Telegram Adapter gelb</a>:</p>
<blockquote>
<p dir="auto">RequestError: Error: getaddrinfo EAI_AGAIN <a href="http://api.telegram.org" rel="nofollow ugc">api.telegram.org</a></p>
</blockquote>
<p dir="auto">Gleicher Fehler , wei beim letzten mal :</p>
<p dir="auto"><a href="https://forum.iobroker.net/topic/44571/gel%C3%B6st-telegram">https://forum.iobroker.net/topic/44571/gelöst-telegram</a></p>
]]></description><link>https://forum.iobroker.net/post/675820</link><guid isPermaLink="true">https://forum.iobroker.net/post/675820</guid><dc:creator><![CDATA[Glasfaser]]></dc:creator><pubDate>Fri, 10 Sep 2021 19:43:46 GMT</pubDate></item></channel></rss>