MythTV Official Community Forum

Yes! It appears that the problem was %STARTTIMEUTC%. I made the change and successfully ran the user job from the "Watch Recordings" pop-up (thanks for the hint). Indeed, mythlink.pl fails silently. The log now shows: Link destination directory: /home/mythtv/links /home/mythtv/links/The Co...

I captured the output mythlink runs as a user job with verbose set (--verbose). This is the only thing sent to stdout and stderr: Link destination directory: /home/mythtv/links This is the correct destinaiton directory, but no symlink is created in that directory or anywhere else on the computer. Th...

Thanks for the suggestion. It looks link mythlink.pl logs to standard out when --verbose is specified. I added this to the user job command and redirected to a log file owned by mythtv. I'll see what happens when the next scheduled program is recorded.

Myth has extensive logging available - see "mythfrontend -v help" Try: mythfrontend -v general, database, network --loglevel debug on the frontend to check that it is configured correctly and doing what you expect. And you can get detailed MySQL logs by adjusting your my.cnf. Maybe they w...

MythTV Andriod Frontend (and likely others) access the backend using the Services API. It does not connect to mysql. The Services API running in the backend accesses the DB as needed. Thanks for the information. I kind of thought it was something like that. That method seems to he a lot less troubl...

All that data looks good, except the ipv4 address is 192.168.0.120, not .119. Connecting to the backend server from a remote is pretty simple. All you need to do is make sure the ports are open, it listens for the addresses that try to connect to it, and you have the correct user name and password....

Not a MythTV usability issue, a packagers usability issue. Contact your packager, or change to a different packager, or do your own packaging. The project (itself) does not ship a package that overwrites your configurations. This is clearly a packaging proble and no criticism of MythTV was implied....

Any idea why I'm getting the localhost errors in the remote frontend log: I MythCoreContext: Connecting to backend server: localhost:6543 (try 1 of 1) E Unable to connect to database! and No address defined for host: localhost It's as if the frontend is trying to connect to a local backend, which d...

The Ubuntu "mythtv-database" package installs/overwrites /etc/mysql/conf.d/mythtv.cnf. There's probabaly a good reason, but it's a symptom of MythTV's usability problem. Common things like accessing a remote frontend accessing the backend should "just work" and not turn into comp...

Yea, that was a typo. You're right about overwrighting config files. It's sloppy packaging. In my experience MythTV in general is a handfull. Before MythTV I used the commercial package SageTV. It did about the same thing as MythTV but was much easier to manage. MythTV is a terrific product, but I w...

forget the ipv6 thing. That was another problem. Every time you upgrade mythtv, mythtv.cnf gets overwritten and the bind address will be commented out. Just comment out the bind-address in my.cnf and mythtv.cnf and try that. That is supposed to open up all ports to both ipv4 and ipv6 addresses. And...

Did you try commenting out the bind-address directive? Also just noticed your ipv6 address. It didn't work right with my right ipv6 address either. had to change it in mythtv-setup to ::1 Do you have a firewall set? That's all I can think of at the moment. Do you mean to comment-out bind-address in...

Tried bind-address = 0.0.0.0 in conf.d with bind-address in my.cnf set to its original value of 127.0.0.1. Got the same result. The frontend still can't contact the server.

In mythtv-setup, you define the address of the master backend. The first time you run mythtv-setup or mythfrontend, it lets you specify the address of the database, and subsequently stores that in config.xml. It sounds like you have a bad value in your config.xml. That's what I thought at first. Bu...

It looks like you specified your local IP address as the address of your MySQL server. That's what I thought when I saw it, but I defintely specify the IP of the backend (192.168.0.101) in setup. My suspsion is that there's a config flie somewhere that's not getting updated, but I can't find it. To...