Not sure what is going on here, I can't see anything obvious that is causing it in the logs.
One strange thing is the size of the logs, they are over 200MB fully extracted for only a few seconds.
They normally should not be large enough that they cannot be uploaded to the forum.
I don't see any error messages besides the prolog and there is not enough of them to make the logs that big.
I do see the same message being constantly spammed and this will be the cause of the file size.
Code: Select all
ServerSentEvents send message: {"id":3,"name":"APTV_9","address":"192.168.20.9","uuid":"898f9738-d930-4db4-a3cf-d80f99888515","icon":"wmp.png","iconOverlays":"","playing":" ","time":" ","progressPercent":0,"userId":-1,"state":{"playback":0,"mute":false,"volume":50,"buffer":0,"name":" "},"isActive":true,"isAllowed":true,"isAuthenticated":false,"controls":3,"action":"renderer_update"}
This is part of the data that is sent to the webUI for UMS to update the status of renderers but something is triggering it every few milliseconds.
I think this is the request received as it appears just as often. It seems to be reporting the current volume on the TV.
Code: Select all
Received a request from 192.168.20.9:
============================= UPNP HTTP SERVER REQUEST BEGIN ================================
NOTIFY /dev/898f9738-d930-4db4-a3cf-d80f99888515/svc/upnp-org/RenderingControl/event/cb HTTP/1.1
HEADER:
...
CONTENT:
<e:propertyset xmlns:e="urn:schemas-upnp-org:event-1-0">
<e:property>
<LastChange><Event xmlns="urn:schemas-upnp-org:metadata-1-0/RCS/"><InstanceID val="0"><Volume Channel="Master" val="50"/><Mute Channel="Master" val="0"/><PresetNameList val="FactoryDefaults"/><VolumeDB Channel="Master" val="0"/></InstanceID></Event></LastChange>
</e:property>
</e:propertyset>
============================= UPNP HTTP SERVER REQUEST END ==================================
I searched for what "Reference is not allowed in prolog" and found an
instance about escaping XML like <> to <> for data like it does here and this might not be working right if UMS cannot keep up.
This APTV_9 is confusing me as it is the same IP as the Sony TV so maybe there is an app on the TV that is spamming requests to UMS and maybe it is overwhelming it and causes that error. This will be the cause of high CPU too.
I could not find any info on APTV_9 but it also has in the manufacturer tag as being from WaxRain which is some Airplay screen mirroring app.
Do you have something like this installed on the TV? If so try disabling it and see if stops doing this.
