LinuxQuestions.org - MythTv: Frontend can not properly open recordings: File path error to the master

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - MythTv: Frontend can not properly open recordings: File path error to the master (https://www.linuxquestions.org/questions/linux-software-2/mythtv-frontend-can-not-properly-open-recordings-file-path-error-to-the-master-558066/)

MythTv: Frontend can not properly open recordings: File path error to the master

Hi,

I've been using mythtv for a while now. I have been running the frontend/backend on the same server for a while. Well I wanted to run another server upstairs and use it as a standalone front end.

I have configured the backend such that it is no longer using a local loopback (127.0.0.1) as its address and configured the standalone front to point to the master back end. I can sucessfully see upcoming showing, see what is recorded, ect fron the standalone frontend.

However, on playback of a recording I get the following.

2007-05-31 14:18:41.225 RingBuffer::RingBuffer(): Failed to open remote file (myth://:/2040_20070531140000.mpg)

The closest thread I could google and find with the same problem was as follows:
http://www.avsforum.com/avs-vb/archi.../t-711243.html. The person at the end however did not indicate where the missing port/dir information is being pulled from and what the configuration should look like.

Has anyone else seen this problem or would know where to look for the missing information as shown where it tries to open the file.

Thanks in advance.

You may need to run mythtv-setup again on your frontend. The fact that you can see upcoming episodes indicates that you have successful access to the database, but doesn't necessarily imply you have successful access to the backend (which may or may not be on the same machine). Because these two "applications" can be physically separated, they are separate entries in the database and on the frontend machine. Try running mythtv-setup again on the frontend and redefining the backend location.

Good luck!

Cool

I ended up discovering that there were settings related to the masterbackend server not being populated in the database on the frontend side (Ran mythfront end in debug mode to see what database queries were being executed for tv playback 'mythfrontend -v all'). 'eagle' is the masterbackend not residing on the same box. After adding the below SQL statements, everything works (until I probaly find something else).

Code:

INSERT INTO settings (value, data, hostname) VALUES ('BackendServerIP', '192.168.1.129', 'eagle' );



INSERT INTO settings (value, data, hostname) VALUES ('BackendServerPort', '6543', 'eagle');



INSERT INTO settings (value, data, hostname) VALUES ('RecordFilePrefix', '/mythtv', 'eagle');

Thanks
J

That's very odd. One would think that rerunning mythtv-setup from both/either machine should update those tables to the correct (above) settings.

Nice job on figuring it out though.

Cool