Sehr viele LogFile einträge "at ./FHEM/98_DLNARenderer.pm"

Begonnen von Marlen, 19 Juli 2017, 06:54:34

Vorheriges Thema - Nächstes Thema

Marlen

Guten Morgen,

meine Logfile wird gerade zugepflaster und ich weiß nicht warum!

2017.07.19 02:42:28 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 02:42:31 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 02:45:48 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 02:45:51 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 02:49:08 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 02:49:11 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 02:52:28 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 02:52:31 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 02:55:48 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 02:55:51 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 02:59:07 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 02:59:10 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 03:02:28 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 03:02:31 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 03:05:48 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 03:05:51 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 03:09:07 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 03:09:10 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 03:12:28 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 03:12:31 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 03:15:48 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 03:15:51 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 03:19:08 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 03:19:11 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 03:22:28 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 03:22:31 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 03:25:47 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 03:25:50 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.
2017.07.19 03:29:07 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1264.
2017.07.19 03:29:10 1: PERL WARNING: Renewal of subscription failed with error: 500 Can't connect to 192.168.178.26:7676 at ./FHEM/98_DLNARenderer.pm line 1271.

bugster_de

Dein DLNA / UPNP Server ist nicht erreichbar oder der entsprechende Port nicht offen
Zitat192.168.178.26:7676
Das ist dein Server und das FHEM Modul 98_DLNARenderer.pm versucht alle paar Sekunden den zu erreichen. Da er das nicht kann macht er einen Eintrag im Logfile. Schau mal ob der Server Down ist.


Marlen

Was ist denn ein DLNA / UPNP Server, wo oder was soll das sein!

Meinst du das Device:
Internals:
   CFGFN
   NAME       dlnadevices
   NR         9692
   STATE      initialized
   TYPE       DLNARenderer
   UDN        0
   VERSION    v2.0.5
   READINGS:
     2017-07-19 13:54:03   state           initialized
   helper:
     caskeid    0
     caskeidClients


Beta-User

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

Marlen

Ich hab jetzt mal alle gelösche...hab ich zumindest gedacht, aber da kommen trotzdem noch welche!

DLNASocket-dlnadevices-45
DLNASocket-dlnadevices-46
DLNASocket-dlnadevices-47
DLNASocket-dlnadevices-54
DLNASocket-dlnadevices-55
DLNASocket-dlnadevices-56

Beta-User

...dann solltest Du die vermutlich auch löschen, wenn Du nicht weist, was das soll/ist (=>commandref)...

Eventuell hast Du irgend einen Automatismus, der Dir diese devices anlegt?
Server: HP-elitedesk@Debian 12, aktuelles FHEM@ConfigDB | CUL_HM (VCCU) | MQTT2: ZigBee2mqtt, MiLight@ESP-GW, BT@OpenMQTTGw | ZWave | SIGNALduino | MapleCUN | RHASSPY
svn: u.a Weekday-&RandomTimer, Twilight,  div. attrTemplate-files, MySensors