Closed alfureu closed 4 years ago
What do you mean in point 3 by link it with an epg grabber? Enabling the external grabber and restarting the tvheadend container does not convert the xmlt.sock into a folder here. Please provide exact steps to reproduce the error. As of now it's missing the part where you send something to the xmltv.sock.
You do know that you have both a xmltv file grabber and webgrab++ file grabber you can use to get the epg data into tvheadend?
Closing this as I can't reproduce the issue and no reply.
Ticket can remain closed, but FWIW: I just observed the same thing but can't reproduce it anymore once I deleted the erroneous folder. I think it was related to my migration of the config dir from the non-dockerized tvheadend.
Expected Behavior
Whenever I recreate/update the container, the socket under
config/epggrab/xmltv.sock
should be recreated to receive connection from tvheadend and other epg grabbers that support itCurrent Behavior
Whenever I restart/recreate/update the container, the
xmltv.sock
becomes a folder somehow, and other epg grabbers cannot connectSteps to Reproduce
xmltv.sock
anymore, and it appears under linux as a folderEnvironment
OS: Linux
CPU architecture: x86_64
How docker service was installed:
Does not matter.
My guess is that in the docker creation script additional lines need to be introduced, which check for the presence of
xmltv.sock
and if it throws TRUE, it should be deleted and a file should be recreated