Re: Rygel stops working with fedora 21

[John Obaterspok <john obaterspok gmail com>]

Hello,

It might be dhcp related since after enable more logging in rygel I noticed the following:

13:58:21 dhclient[1347]: DHCPREQUEST on p33p1 to 192.168.0.1 port 67 (xid=0x85dbe073)

13:58:21 dhclient[1347]: DHCPACK from 192.168.0.1 (xid=0x85dbe073)

13:58:23 rygel: (rygel:12099): Rygel-DEBUG: rygel-main.vala:182: Network 192.168.0.0 (p33p1) context now unavailable. IP: 192.168.0.103

13:58:23 rygel: ** (rygel:12099): WARNING **: GUPnPContext: Unable to listen on 192.168.0.103:53434 Kan inte lyssna på adress 192.168.0.103, port 53434

13:58:23 rygel: (rygel:12099): Rygel-DEBUG: rygel-main.vala:149: New network 192.168.0.0 (p33p1) context available. IP: 192.168.0.103

13:58:23 rygel: (rygel:12099): Rygel-DEBUG: rygel-root-device-factory.vala:180: No icon provided by plugin 'MediaExport'. Using Rygel logo.

13:58:23 rygel: (rygel:12099): libsoup-CRITICAL **: soup_uri_copy: assertion 'uri != NULL' failed

13:58:23 rygel: (rygel:12099): libsoup-CRITICAL **: soup_uri_set_path: assertion 'uri != NULL' failed

13:58:23 rygel: (rygel:12099): libsoup-CRITICAL **: soup_uri_to_string_internal: assertion 'uri != NULL' failed

13:58:23 rygel: (rygel:12099): libsoup-CRITICAL **: soup_uri_free: assertion 'uri != NULL' failed

13:58:23 rygel: (rygel:12099): libsoup-WARNING **: (soup-uri.c:604):soup_uri_copy: runtime check failed: (SOUP_URI_IS_VALID (uri))

13:58:23 rygel: (rygel:12099): libsoup-WARNING **: (soup-uri.c:604):soup_uri_copy: runtime check failed: (SOUP_URI_IS_VALID (uri))

13:58:23 rygel: (rygel:12099): libsoup-WARNING **: (soup-uri.c:604):soup_uri_copy: runtime check failed: (SOUP_URI_IS_VALID (uri))

13:58:23 rygel: ** (rygel:12099): CRITICAL **: gupnp_resource_factory_create_service: assertion 'location != NULL' failed

13:58:23 rygel: ** (rygel:12099): CRITICAL **: gupnp_resource_factory_create_service: assertion 'location != NULL' failed

13:58:23 rygel: ** (rygel:12099): CRITICAL **: gupnp_resource_factory_create_service: assertion 'location != NULL' failed

13:58:23 dhclient[1347]: bound to 192.168.0.103 -- renewal in 36044 seconds.

I need to check if I rygel disappears at the same time a DHCP renewal happens

-- john

2015-03-24 11:27 GMT+01:00 John Obaterspok <john obaterspok gmail com>:

2015-03-24 9:55 GMT+01:00 Jens Georg <mail jensge org>:

Weird. Is Rygel running on a network interface using DHCP?

DHCP Yes, but with a reserved/fixed IP

 

Does the time after Rygel stopps being discoverable roughly match up
with the lease time?

I can check.

Two things happened in my setup before/after problems started to appear

1) F20 -> F21 update

2) Router upgrade to AC87U

Another thing as well:

With F19 & F20 I normally just started rygel by logging in via ssh and executed the rygel command as a normal user, then logged out again. With F21 I believe I had problems where rygel became undiscoverable when I logged out of ssh. That's why I switched to running rygel as systemd service instead.

-- john