Announcement

Collapse
No announcement yet.

Minidlna server disconnects after awhile

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Minidlna server disconnects after awhile

    I got the idea from this page to run a local DLNA server and use the pictures from an IP-Cam to show as a toast message.
    https://forums.homeseer.com/forum/me...-remotes/page8

    I've installed minidlna server on my Debian server where HomeSeer is installed.
    However after a while the server shows up as Activated Offline.
    Code:
    UPnPDevice Aperture has been disconnected from the network in DeviceLostCallback
    - If I restart the minidlna daemon the mediacontroller pi still shows Activated Offline
    - if I restart the mediacontroller pi the server goes back Activated Online

    I don't have a clue from where to start troubleshooting. Could anyone push me in the right direction?
    Tags: None
    #2
    I've enabled super debug to get a little bit more logging and the I've captured the moment the mediaserver disconnects

    Code:
    2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MyUPnPDevice.Dispose called for for UDN =  and RemoveSelf = True
2019-07-19T11:49:43, Source=HomeSeer3, Type=MC, Message=SetHSMainState called for device - Aperture and Current HSRef = 882 and AdminStateActive = True and DeviceStatus = Offline
2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MySSDP.RemoveDevices called with UDN = uuid:4d696e69-444c-164e-9d41-000c2995c6cb
2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MyUPnPDevice.Disspose called for for UDN = uuid:4d696e69-444c-164e-9d41-000c2995c6cb and RemoveSelf = True
2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MyUPnPService.RemoveCallback called for ServiceID = http://172.16.148.13:8200/ConnectionMgr.xml
2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MyUPnPService.RemoveCallback called for ServiceID = http://172.16.148.13:8200/ContentDir.xml
2019-07-19T11:49:43, Source=HomeSeer3, Type=MC, Message=DestroyObjects called for UPnPDevice - Aperture with Full = Falsepose called for for UDN = uuid:4d696e69-444c-164e-9d41-000c2995c6cb and RemoveSelf = True
2019-07-19T11:49:43, Source=HomeSeer3, Type=MC Warning, Message=MyUPnPDevices.RemoveDevice removed UDN = uuid:4d696e69-444c-164e-9d41-000c2995c6cb successfully
2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MySSDP.RemoveDevices called with UDN = uuid:4d696e69-444c-164e-9d41-000c2995c6cb
2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MyUPnPDevice.Di
2019-07-19T11:49:43, Source=HomeSeer3, Type=MC, Message=DeviceTrigger called for device - Aperture with Trigger = Player Offline
2019-07-19T11:49:43, Source=HomeSeer3, Type=MC, Message=PlayChangeNotifyCallback called for device - Aperture with ChangeType = DeviceStatusChanged and Changevalue = Offline
2019-07-19T11:49:43, Source=HomeSeer3, Type=MC Warning, Message=UPnPDevice Aperture has been disconnected from the network in DeviceLostCallback.
2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MyUPnPService.Dispose called for ServiceID = http://172.16.148.13:8200/X_MS_MediaReceiverRegistrar.xml
2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MyUPnPService.SendCancelSubscription called for ServiceID = http://172.16.148.13:8200/ConnectionMgr.xml
2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MyUPnPService.Dispose called for ServiceID = http://172.16.148.13:8200/ConnectionMgr.xml
2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MyUPnPService.SendCancelSubscription called for ServiceID = http://172.16.148.13:8200/ContentDir.xml
2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MyUPnPService.Dispose called for ServiceID = http://172.16.148.13:8200/ContentDir.xml
2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MyUPnPServices.Dispose called
2019-07-19T11:49:43, Source=UPnP, Type=MC, Message=MyUPnPDevice.ReleaseDeviceServiceInfo for for UDN = uuid:4d696e69-444c-164e-9d41-000c2995c6cb
2019-07-19T11:49:43, Source=HomeSeer3, Type=MC Warning, Message=MyUPnPDevice.SomePartOfDeviceDied called for UDN = uuid:4d696e69-444c-164e-9d41-000c2995c6cb and IP = 172.16.148.13 and Name = Aperture and ChildFlag = False with ChildUDN = uuid:4d696e69-444c-164e-9d41-000c2995c6cb
2019-07-19T11:49:43, Source=HomeSeer3, Type=MC Warning, Message=MyUPnPDevice.MySubscribeRenewTimer_Elapsed called for UDN = uuid:4d696e69-444c-164e-9d41-000c2995c6cb and IP = 172.16.148.13 and Name = Aperture
2019-07-19T11:49:41, Source=HomeSeer3, Type=MC, Message=DoRediscover found UDN = uuid:4d696e69-444c-164e-9d41-000c2995c6cb, with location = http://172.16.148.13:8200/rootDesc.xml and Alive = True
2019-07-19T11:49:41, Source=HomeSeer3, Type=MC, Message=GetIniSection called with section = UPnP Devices to discover, FileName = MediaController.ini and # Result = 12
2019-07-19T11:49:41, Source=HomeSeer3, Type=MC, Message=DoRediscover called
    Still don't understand why only this Server had this problem and why restarted the PI solves it (instead of restarted the minidlna daemon).

    Comment

      #3
      What OS are you running the pi on? Does it have a firewall? Does the PI have proper allowance on that FW?

      Comment

        #4
        I found this post on miniDLNA, not sure this is what you use but look at the bottom of the page where it talks about opening port 1900 (SSDP) on the device where miniDLNA lives. The reason it disconnects is because the PI doesn't receive a periodic "ALIVE" SSDP message. This message is multicasted on port 1900 so if that port is not open, nothing will stay alive for more that 1 hour.

        Link : https://help.ubuntu.com/community/MiniDLNA

        Comment

          #5
          Hi dcorsus thank you for your reply. I run the MiniDLNA on the same pc as where HomeSeer is installed it's a Debian OS without a firewall.

          In the minidlna.config there is a line

          # Path to the MiniSSDPd socket, for MiniSSDPd support.
          #minissdpdsocket=/run/minissdpd.sock

          I've uncommented the last line and I'll see if this works.

          Comment

            #6
            Originally posted by alan_smithee View Post
            Hi dcorsus thank you for your reply. I run the MiniDLNA on the same pc as where HomeSeer is installed it's a Debian OS without a firewall.

            In the minidlna.config there is a line

            # Path to the MiniSSDPd socket, for MiniSSDPd support.
            #minissdpdsocket=/run/minissdpd.sock

            I've uncommented the last line and I'll see if this works.
            if that doesn't work try to run minidlna on a different device then homeseer, just as a test. I would think that the 2 applications communicate with each other through the loopback address, so this setting also caught my eye
            network_interface Network interface(s) to bind to (e.g. eth0), comma delimited. This option can be specified more than once. If unspecified or empty, minidlnad binds to all the valid network interfaces (except loopback).
            By default, minidlnad listens on all the network interfaces (except loopback) for clients. This behavior can be changed on the command-line using the -i option, or in the configuration file through the network_interface option (see minidlna.conf(5) for details).

            Comment

              #7
              You're to man!
              I should've known to also add the loopback.
              Changed the line to network_interface=ens192,lo and I didn't even have to restart the PI to get activated online again.

              PM me your address and I'll send you frikandellen or if you want anything else please let me know

              Comment

                #8
                Originally posted by alan_smithee View Post

                PM me your address and I'll send you frikandellen
                ah, now were talking!

                Glad it works,

                Dirk

                Comment

                Previous template Next
                Working...
                X