Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Rygel is sending SSDP packets all over the network

Description

May 17 14:47:41 raspberrypi3 rygel[692]: Rygel-Message: rygel-acl.vala:143: No ACL fallback policy found. Using "allow" May 17 14:47:41 raspberrypi3 rygel[692]: Rygel-Message: Rygel v0.28.2 starting? May 17 14:47:41 raspberrypi3 rygel[692]: RygelCore-Message: New plugin 'LMS' available May 17 14:53:50 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.24: Error sending message: Invalid argument May 17 14:53:52 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.24: Error sending message: Invalid argument May 17 14:53:53 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.24: Error sending message: Invalid argument May 17 14:53:56 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.24: Error sending message: Invalid argument May 17 14:53:58 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.24: Error sending message: Invalid argument May 17 14:54:01 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.24: Error sending message: Invalid argument May 17 14:55:25 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.105: Error sending message: Invalid argument May 17 14:55:27 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.105: Error sending message: Invalid argument May 17 14:55:31 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.105: Error sending message: Invalid argument May 17 15:01:48 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:01:52 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:01:54 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:06:51 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:06:54 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:06:58 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:14:04 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:14:08 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:14:10 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:40:29 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:40:30 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:40:32 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:40:33 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:40:34 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:40:38 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:51:55 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:52:00 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 15:52:03 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.51: Error sending message: Invalid argument May 17 16:08:01 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.105: Error sending message: Invalid argument May 17 16:08:06 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.105: Error sending message: Invalid argument May 17 16:08:09 raspberrypi3 rygel[692]: ** (rygel:692): WARNING **: Error sending SSDP packet to 192.168.1.105: Error sending message: Invalid argument

Environment

Raspberry Pi 3, connected to ethernet

Activity

Matt Ranostay 
June 5, 2017 at 6:32 PM

Patchset to disable Rygel user service merged. https://gerrit.automotivelinux.org/gerrit/#/c/9557/

Matt Porter 
May 24, 2017 at 6:35 PM

Are we sure there aren't any out-of-tree users? If there are out-of-tree users then we could just preset the rygel unit to disabled as suggested offline by and then leave it in the build...problem solved. That allows a system integrator to turn it on if they've got a demo that uses it to do something like serve video to an independent seatback display. Much speculation, indeed.

Jan-Simon Moeller 
May 24, 2017 at 6:18 PM

: iirc the openivi was added by you. Do you know if rygel is in use there ?

Jan-Simon Moeller 
May 24, 2017 at 6:17 PM

meta-agl/meta-agl/recipes-ivi/packagegroups/packagegroup-agl-ivi-connectivity.bb: rygel \ meta-agl/meta-agl/recipes-ivi/packagegroups/packagegroup-agl-ivi-connectivity.bb: rygel-plugin-media-export \ meta-agl/meta-agl/recipes-ivi/packagegroups/packagegroup-agl-ivi-connectivity.bb: rygel-plugin-lms \

So there seems to be rygel in the packagegroup and also the lightmediascanner plugin is there.
I don't know if it is actually working (might be now winking face as lms is working ).

At least the

meta-agl-demo/recipes-openivi/openivi-html5/openivi-html5/openivi-html5.service:After=dbus.service lightmediascanner.service rygel.service weston.service

seems to have it at least this in the service file.

Matt Ranostay 
May 24, 2017 at 6:07 PM

Maybe and  has more input.   

But I don't think anything is using it in AGL, this is mostly based no recipe has it in it's DEPENDS

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Priority

Created May 23, 2017 at 7:54 PM
Updated July 24, 2017 at 11:45 PM
Resolved June 5, 2017 at 6:32 PM

Flag notifications