I stated in another post that MythTv wasn't work and I didn't know if the Sierra update to 10.12.4 was the cause. One suggestion but backend.log didn't show anything. So I decided to remove MythTv and reinstall. I deleted /opt/dvr and Applications/MacPort directories. I power cycled my computer to make sure mysql wasn't available anymore. I then installed the MacPort package for MythTv. I set up MythTv with the settings I had for the last one. I ran Myth_Filldatabase and then opened Myth_Stop_Start. I see that mysql is running but MythBackend isn't. So I select Start MythBackend. But it didn't start. I have found the Myth_FillDataBase log and it's showing an issue with connecting to Mythbackend. I need some help deciphering what I need to do or did MacPort not set something up correctly?
2017-04-07 20:55:38.161377 C [863/775] thread_unknown mythcommandlineparser.cpp:2599 (ConfigureLogging) - mythfilldatabase version: fixes/0.28 [v0.28.1-03f44039-MacPorts] www.mythtv.org
2017-04-07 20:55:38.161397 C [863/775] thread_unknown mythcommandlineparser.cpp:2601 (ConfigureLogging) - Qt version: compile: 5.6.2, runtime: 5.6.2
2017-04-07 20:55:38.161401 N [863/775] thread_unknown mythcommandlineparser.cpp:2603 (ConfigureLogging) - Enabled verbose msgs: general
2017-04-07 20:55:38.175072 W [863/775] CoreContext mythcorecontext.cpp:273 (Init) - This application expects to be running a locale that specifies a UTF-8 codeset, and many features may behave improperly with your current language settings. Please set the LC_ALL or LC_CTYPE, and LANG variable(s) in the environment in which this program is executed to include a UTF-8 codeset (such as 'en_US.UTF-8').
2017-04-07 20:55:38.275756 E [863/11011] MythSocketThread(-1) mythsocket.cpp:729 (ConnectToHostReal) - MythSocket(7fcd4f443db0:-1): Failed to connect to (127.0.0.1:6543) Connection refused
2017-04-07 20:55:38.275894 E [863/775] CoreContext mythcorecontext.cpp:506 (ConnectCommandSocket) - Connection to master server timed out.
Either the server is down or the master server settings
in mythtv-settings does not contain the proper IP address
2017-04-07 20:55:38.275924 W [863/775] CoreContext main.cpp:316 (main) - Failed to connect to master backend. MythFillDatabase will continue running but will be unable to prevent backend from shutting down, or triggering a reschedule when complete.
2017-04-07 20:56:04.867058 E [863/775] CoreContext main.cpp:432 (main) - Failed to fetch some program info
2017-04-07 20:56:05.569403 E [863/26323] MythSocketThread(-1) mythsocket.cpp:729 (ConnectToHostReal) - MythSocket(7fcd4f514cf0:-1): Failed to connect to (127.0.0.1:6543) Connection refused
2017-04-07 20:56:05.569477 E [863/775] CoreContext mythcorecontext.cpp:506 (ConnectCommandSocket) - Connection to master server timed out.
Either the server is down or the master server settings
in mythtv-settings does not contain the proper IP address
2017-04-07 20:56:05.569489 E [863/775] CoreContext scheduledrecording.cpp:27 (SendReschedule) - Error rescheduling MATCH 0 0 0 - MythFillDatabase in ScheduledRecording::SendReschedule
2017-04-07 20:56:05.569995 E [863/26883] MythSocketThread(-1) mythsocket.cpp:729 (ConnectToHostReal) - MythSocket(7fcd4f501e20:-1): Failed to connect to (127.0.0.1:6543) Connection refused
2017-04-07 20:56:05.570092 E [863/26323] SendMessage mythcorecontext.cpp:506 (ConnectCommandSocket) - Connection to master server timed out.
Either the server is down or the master server settings
in mythtv-settings does not contain the proper IP address
2017-04-07 20:56:05.570342 E [863/26883] MythSocketThread(-1) mythsocket.cpp:729 (ConnectToHostReal) - MythSocket(7fcd4f61d000:-1): Failed to connect to (127.0.0.1:6543) Connection refused
2017-04-07 20:56:05.570418 E [863/26699] SendMessage mythcorecontext.cpp:506 (ConnectCommandSocket) - Connection to master server timed out.
Either the server is down or the master server settings
in mythtv-settings does not contain the proper IP address
Last edited by rbmisc on Sun Apr 16, 2017 12:40 pm, edited 1 time in total.
The posted log just shows that mythbackend was not running at the time you ran mythfilldatabase. That is not a problem in and of itself; MFD can do it's thing without the BE.
Are you saying there is no log for mythbackend? When you clicked Start MythBackend, a log should have been created even if the program immediately aborted. Please confirm whether or not you have any mythbackend log files.
If you do not have any log files, please check if the launchd plist is present. In Terminal, please enter 'ls -l /Library/LaunchDaemons/' and paste the results here.
You're right I did. Here is what's in org.mythtv.mythbackend.plist As you can see local is set instead of dvr. I have changed these but I can't find python2.7. It's not in /opt/dvr/lib. I find python2.7 in /opt/dvr/bin. But the way it's shown here makes it look like a directory when it's a bin file.
And here is what I have changed. But backend still doesn't start after restarting the computer and waiting the 5 minutes and also trying with the Myth_Start_Stop app.
rbmisc wrote:You're right I did. Here is what's in org.mythtv.mythbackend.plist As you can see local is set instead of dvr. I have changed these but I can't find python2.7. It's not in /opt/dvr/lib. I find python2.7 in /opt/dvr/bin. But the way it's shown here makes it look like a directory when it's a bin file.
...
PICK AN INSTALL METHOD AND STICK TO IT.
If you want to screw around and install both with the all-in-one installer AND with the port command, it is up to you to deal with the conflicts. Which is exactly what you're experiencing.
I don't appreciate your comments about screwing around. I wasn't aware that I did that. I come here for help not criticism. Not all of us are experts as you are. I would like to get MythTv working again. So let me know which one is the best to use.
rbmisc wrote:I don't appreciate your comments about screwing around. I wasn't aware that I did that. I come here for help not criticism. Not all of us are experts as you are. I would like to get MythTv working again. So let me know which one is the best to use.
You may not appreciate my comments but then you're not paying for my time. Your problem is likely entirely self-inflicted. At least give a heads-up in your first post.
I had done all of this before posting with the Mythbackend issue. I was able to get mythbackend up and running before seeing your latest post. I realized after your comment that local was from the other one and each time I would try to set up backup, it was using this plist and not generating a new one. So I deleted this plist, deleted the all in one install again and re-installed. I configured my system after reinstalling. Saved the setting and started backend because it wasn't running.
Here is what I'm getting in the mythbackend. I have the same HDHomerun Dual tuners I have had in the past. I used the same setup that I have in the past. When I select Watch TV I get the message "All tuners are currently busy." So what's the next thing I need to see? Also, I did a search already on this and saw another post about this from you. I have backed up my database and have tried several times deleting and adding my tuners to setup but no success. I know the tumers are working because I have another app from Silicon Dust and am able to watch TV with it.
Other question. Can I remove /opt/local since it was installed by MacPort?
rbmisc wrote:I had done all of this before posting with the Mythbackend issue. I was able to get mythbackend up and running before seeing your latest post. I realized after your comment that local was from the other one and each time I would try to set up backup, it was using this plist and not generating a new one. So I deleted this plist, deleted the all in one install again and re-installed. I configured my system after reinstalling. Saved the setting and started backend because it wasn't running.
Here is what I'm getting in the mythbackend. I have the same HDHomerun Dual tuners I have had in the past. I used the same setup that I have in the past. When I select Watch TV I get the message "All tuners are currently busy." So what's the next thing I need to see? Also, I did a search already on this and saw another post about this from you. I have backed up my database and have tried several times deleting and adding my tuners to setup but no success. I know the tumers are working because I have another app from Silicon Dust and am able to watch TV with it.
Other question. Can I remove /opt/local since it was installed by MacPort?
I have an HDHomerun Dual (OTA) and I've just verified that LiveTV works OK. You are receiving via antenna, too, right? Please go back through mythtv-setup and double-check all the settings for your tuners. Have you set a proper starting channel for each tuner? The wiki page for the Dual is terse but I think it is still relevant:
You should not need to do a channel scan if the expected channels are in the Channel Editor.
Yes you can remove '/opt/local/...' but if you'd looked at the other thread I recommended using 'sudo port uninstall installed' since it cleans up '/Applications/MacPorts' AND '/Library/LaunchDaemons'. Too late to do that now.
I did use what you recommended in the previous post back when I tried backing out of that install. But it didn't remove the backend plist file.
I am receiving via antenna. I have verified that the tuners start on channel 14.1. Everytime I deleted and reinstalled the tuners, I did do a scan and the tuners detected the channels. I verified them in the Channel Editor.
My tuners in Input Connection are [HDHOMERUN:10511A5B-0] (MPEG2TS->Schedules Direct) & [HDHOMERUN:10511A5B-1] (MPEG2TS->Schedules Direct)
rbmisc wrote:I did use what you recommended in the previous post back when I tried backing out of that install. But it didn't remove the backend plist file.
I am receiving via antenna. I have verified that the tuners start on channel 14.1. Everytime I deleted and reinstalled the tuners, I did do a scan and the tuners detected the channels. I verified them in the Channel Editor.
My tuners in Input Connection are [HDHOMERUN:10511A5B-0] (MPEG2TS->Schedules Direct) & [HDHOMERUN:10511A5B-1] (MPEG2TS->Schedules Direct)
Stop the backend and start it again (to get a fresh log). Go to Live TV and let it try for a minute or two. If it still doesn't work, post the backend log.
Via Ethernet. No change from how it was in the past. 192.168.1.2 is the address. That's what's shown in setup when selecting the tuner name. I can also access tuner on browser with this address.
