I've been using myth for quite some time, but I run into snags any time I upgrade the OS or allow any changes. I'm afraid I'm just making things worse.
Here is my config.xml file that I think it's using:
I have tested the mysql connection and I can connect to it with the above configuration. Upon running mythbackend I get errors along the lines of 'failed listening on TCP 127.0.0.1:6544 error 8 the bound address is already in use.
Please help - I'll try to answer any questions posed.
Thanks
Last edited by Coolmike99 on Tue May 22, 2018 4:04 am, edited 1 time in total.
The "bound address..." message says that there is already an instance of the
backend running, no need to start it again.
Be sure to mention your OS and version if additional help is needed.
No need to guess which config.xml is in use. just look at the backend log for a line
similar to: Using configuration directory = /home/mythtv/.mythtv. The file lives under
that directory. See: https://www.mythtv.org/wiki/Config.xml#Troubleshooting
The log lives in /var/log/mythtv (usually.) If it's not there, see what: ls -ld /var/log/mythtv
says. The backend (run as user mythtv) need write permission on the directory.)
You can also use: journalctl. man journalctl will explain its options.
To see if the backend is running, the command is: systemctl status mythtv-backend
sudo systemctl stop (and start) mythtv-backend do the obvious.
Thanks for the help thus far. If I stop it and try to restart, it tells me: Failed listening on TCP 127.0.0.1:3306 - Error 8 The bound address is already in use. What should I try now please?
3306 is the port used by mysql, not MythTV. Check the output of the status command above your
last post. When commands fail, it's good to include the command line too.
You didn't start the backend directly with: mythbackend ... rather than with systemctl did you?
If that's the case, ps ax|grep mythbackend will show if it's running and you have to kill it (pkill mythbackend.)
I had killed the backend with sudo systemctl stop mythtv-backend. I then attempted to restart by mythbackend. I got the aforementioned response. Do I have a port setting wrong? Where would I change that?
Good to hear. When you've finished testing (and it's working), please edit your the 1st post in this thread
and prepend [Solved] to the Subject. Thanks.