I'm on OSX 10.11.6. Xcode 8.0.
I did do all the steps on that page. Is there something different with XCode 8? I know it is brand new.
Thanks,
Shredder83
MacPorts and Myth 0.28
Re: MacPorts and Myth 0.28
Just to be sure, you did install the Command Line Tools with 'xcode-select --install', right?
I haven't put XCode 8 on any of my machines. I'll try to get to that in the next couple of days.
Craig
I haven't put XCode 8 on any of my machines. I'll try to get to that in the next couple of days.
Craig
Formerly the MacPorts guy.
-
shredder83
- Newcomer
- Posts: 7
- Joined: Mon Aug 10, 2015 8:26 pm
Re: MacPorts and Myth 0.28
Yes I did. I even tried it again just to be sure and it said it was installed. 
Thanks for helping out with this.
Shredder83
Thanks for helping out with this.
Shredder83
Re: MacPorts and Myth 0.28
I migrated by building through MacPorts from 0.27 to 0.28 and seem to be successful with limited testing so far.
Procedure:
1) Backed up mythtv database with /opt/local/share/mythtv/mythconverg_backup.pl -directory ~/Desktop --mysqldump /opt/local/lib/mariadb/bin/mysqldump --verbose
1 ) Stopped Mythtv backend 0.27 by using the script Myth_Stop_Start to shut down 0.27 backend
2) Optional: I updated macports to the latest versions with
sudo port self update
sudo port upgrade outdated
2 ) Deactivated mythweb by sudo port deactivate mythweb.27
3) Deactivated mythtv 0.27 by sudo port deactivate mythtv-core.27
4) Installed mythtv 0.28 by sudo port install mythtv-core.28 +mariadb+mariadb55+python27+perl5_24
5) Installed mythweb 0.28 by sudo port install mythweb.28
6) Restarted mythtv backend 0.27 by using the script Myth_Stop_Start to start 0.28 backend
I then tested mythtv frontends and Kodi and the items that I tried seemed to be functional for both on the master and on slaves.
I tried Mythweb 0.28 and that seemed to work as expected
I tried Mythweb fronted http://localhost:6544 and that seemed to work as well.
Procedure:
1) Backed up mythtv database with /opt/local/share/mythtv/mythconverg_backup.pl -directory ~/Desktop --mysqldump /opt/local/lib/mariadb/bin/mysqldump --verbose
1 ) Stopped Mythtv backend 0.27 by using the script Myth_Stop_Start to shut down 0.27 backend
2) Optional: I updated macports to the latest versions with
sudo port self update
sudo port upgrade outdated
2 ) Deactivated mythweb by sudo port deactivate mythweb.27
3) Deactivated mythtv 0.27 by sudo port deactivate mythtv-core.27
4) Installed mythtv 0.28 by sudo port install mythtv-core.28 +mariadb+mariadb55+python27+perl5_24
5) Installed mythweb 0.28 by sudo port install mythweb.28
6) Restarted mythtv backend 0.27 by using the script Myth_Stop_Start to start 0.28 backend
I then tested mythtv frontends and Kodi and the items that I tried seemed to be functional for both on the master and on slaves.
I tried Mythweb 0.28 and that seemed to work as expected
I tried Mythweb fronted http://localhost:6544 and that seemed to work as well.
Re: MacPorts and Myth 0.28
Thanks very much for the detailed report. Glad that it is working for you.gsulshski wrote:I migrated by building through MacPorts from 0.27 to 0.28 and seem to be successful with limited testing so far.
Procedure:
1) Backed up mythtv database with /opt/local/share/mythtv/mythconverg_backup.pl -directory ~/Desktop --mysqldump /opt/local/lib/mariadb/bin/mysqldump --verbose
1 ) Stopped Mythtv backend 0.27 by using the script Myth_Stop_Start to shut down 0.27 backend
2) Optional: I updated macports to the latest versions with
sudo port self update
sudo port upgrade outdated
2 ) Deactivated mythweb by sudo port deactivate mythweb.27
3) Deactivated mythtv 0.27 by sudo port deactivate mythtv-core.27
4) Installed mythtv 0.28 by sudo port install mythtv-core.28 +mariadb+mariadb55+python27+perl5_24
5) Installed mythweb 0.28 by sudo port install mythweb.28
6) Restarted mythtv backend 0.27 by using the script Myth_Stop_Start to start 0.28 backend
I then tested mythtv frontends and Kodi and the items that I tried seemed to be functional for both on the master and on slaves.
I tried Mythweb 0.28 and that seemed to work as expected
I tried Mythweb fronted http://localhost:6544 and that seemed to work as well.
One small clarification:
http://localhost:6544 Is the new Web Frontend
http://localhost/MythWeb Is the old MythWeb
Craig
Formerly the MacPorts guy.
Re: MacPorts and Myth 0.28
I upgraded my macports build to use mythtv 0.28 from mythtv 0.27 and have been successful.
1) I backed up my mythtv database with
/opt/local/share/mythtv/mythconverg_backup.pl -directory ~/Desktop --mysqldump /opt/local/lib/mariadb/bin/mysqldump --verbose
2) I stopped the mythtv backend by running the script
Myth_Stop_Start to shut down 0.27 backend
3) Optional: I updated my macports with the following
sudo port self update
sudo port upgrade outdated
4) I deactivated 0.27 since it can't be active with 0.28. I use mythweb so I have to deactivate that first
sudo port deactivate mythweb.27
sudo port deactivate mythtv-core.27
5) I built 0.28 with
sudo port install mythtv-core.28 +mariadb+mariadb55+python27+perl5_24
sudo port install mythweb.28
6) I I started the mythtv backend by running the script
Myth_Stop_Start to start 0.28 backend
I tested mythtv 0.28 on the master, slave and with Kodi as a slave and it works fine so far.
I tried mythweb and webfrontend and they both seem to work so far.
1) I backed up my mythtv database with
/opt/local/share/mythtv/mythconverg_backup.pl -directory ~/Desktop --mysqldump /opt/local/lib/mariadb/bin/mysqldump --verbose
2) I stopped the mythtv backend by running the script
Myth_Stop_Start to shut down 0.27 backend
3) Optional: I updated my macports with the following
sudo port self update
sudo port upgrade outdated
4) I deactivated 0.27 since it can't be active with 0.28. I use mythweb so I have to deactivate that first
sudo port deactivate mythweb.27
sudo port deactivate mythtv-core.27
5) I built 0.28 with
sudo port install mythtv-core.28 +mariadb+mariadb55+python27+perl5_24
sudo port install mythweb.28
6) I I started the mythtv backend by running the script
Myth_Stop_Start to start 0.28 backend
I tested mythtv 0.28 on the master, slave and with Kodi as a slave and it works fine so far.
I tried mythweb and webfrontend and they both seem to work so far.
-
shredder83
- Newcomer
- Posts: 7
- Joined: Mon Aug 10, 2015 8:26 pm
Re: MacPorts and Myth 0.28
I found this bug report on macports
Looks like there is a problem building qt5 on Xcode 8. Guess I'll need to watch the ticket to see if it gets fixed.
Thanks,
Shredder83
Code: Select all
https://trac.macports.org/ticket/52200Thanks,
Shredder83
Re: MacPorts and Myth 0.28
Further feedback with my build with MacPorts and Myth 0.28:
I have moved to macOS Sierra 10.12 on my 2012 Mac Mini and 2013 iMac since my original build which was done in El Capitan. I have a homerun prime with 3 tuners.
I use Kodi as my frontend on the Mac Mini and a FireTV to access Mythtv backend. I occasionally use Mythtv frontend when I want to have PiP for multiple football games along with Kodi full screen.
Mythtv Backend (0.28)
Operation wise: I haven't noticed any specific issues with the recordings or the operation of mythtv backend by itself
Differences:
I have two user jobs that I use that remove the commercials (cut list) and then I use handbrake to encode them (h264) so that I can watch them on any apple device and then I fetch the metadata (tvdb) so that I can name them with Show - sxxeyy - subtitle.m4v and place them in a TV scrapper friendly folder structure Show -> Season X -> Show - sxxeyy - subtitle.m4v
1) The recordings are named Channel_Starttime.ts vs Channel_Starttime.mpg : I had to modify the scripts with the new file extension but the content is still mpeg stream
2) For some reason, mythtranscode (what I use to remove the commercials) operates differently in 0.28 and I had to change the mythtv setup - general - job queue (general) - check save original files after transcoding (globally) or my job would fail (recording was removed after I transcoded to remove the commercials).
3) For some reason, when I was using tvdb.py to look up the season and episode, it was always returning a empty xml file. I debugged it and found that script was trying to access a api file in my directories that had root access and would fail. I updated the script with sudo $PATH/tvdb.py vs $PATH/tvdb.py it worked. Not sure what this has to do with 0.28 but I didn't have this issue with 0.27.
MythWeb 0.28
Operation wise: It isn't very stable from my perspective.
Most of the time I get
Fatal error: Call to a member function query_col() on a non-object in /opt/local/apache2/htdocs/MythWeb/modules/backend_log/init.php on line 15
I find that I can refresh and Mythweb will work every 2nd or 3rd time which is annoying. It seems to be more forgiving when I do the tv/listing but the recordings, upcoming recordings and backend are less friendly.
Webfrontend:
I have been using it for the last couple of weeks.
I don't have any specific issues running the Webfrontend. Not all features are meant to be working and there is some function that isn't available that I like to use with Mythweb.
Kodi 16.x and 17.x beta:
I have been using 17.x beta on the mac mini and 16.x on the fire tv and I haven't noticed any mythtv interaction issues that is the same as 0.27
I have moved to macOS Sierra 10.12 on my 2012 Mac Mini and 2013 iMac since my original build which was done in El Capitan. I have a homerun prime with 3 tuners.
I use Kodi as my frontend on the Mac Mini and a FireTV to access Mythtv backend. I occasionally use Mythtv frontend when I want to have PiP for multiple football games along with Kodi full screen.
Mythtv Backend (0.28)
Operation wise: I haven't noticed any specific issues with the recordings or the operation of mythtv backend by itself
Differences:
I have two user jobs that I use that remove the commercials (cut list) and then I use handbrake to encode them (h264) so that I can watch them on any apple device and then I fetch the metadata (tvdb) so that I can name them with Show - sxxeyy - subtitle.m4v and place them in a TV scrapper friendly folder structure Show -> Season X -> Show - sxxeyy - subtitle.m4v
1) The recordings are named Channel_Starttime.ts vs Channel_Starttime.mpg : I had to modify the scripts with the new file extension but the content is still mpeg stream
2) For some reason, mythtranscode (what I use to remove the commercials) operates differently in 0.28 and I had to change the mythtv setup - general - job queue (general) - check save original files after transcoding (globally) or my job would fail (recording was removed after I transcoded to remove the commercials).
3) For some reason, when I was using tvdb.py to look up the season and episode, it was always returning a empty xml file. I debugged it and found that script was trying to access a api file in my directories that had root access and would fail. I updated the script with sudo $PATH/tvdb.py vs $PATH/tvdb.py it worked. Not sure what this has to do with 0.28 but I didn't have this issue with 0.27.
MythWeb 0.28
Operation wise: It isn't very stable from my perspective.
Most of the time I get
Fatal error: Call to a member function query_col() on a non-object in /opt/local/apache2/htdocs/MythWeb/modules/backend_log/init.php on line 15
I find that I can refresh and Mythweb will work every 2nd or 3rd time which is annoying. It seems to be more forgiving when I do the tv/listing but the recordings, upcoming recordings and backend are less friendly.
Webfrontend:
I have been using it for the last couple of weeks.
I don't have any specific issues running the Webfrontend. Not all features are meant to be working and there is some function that isn't available that I like to use with Mythweb.
Kodi 16.x and 17.x beta:
I have been using 17.x beta on the mac mini and 16.x on the fire tv and I haven't noticed any mythtv interaction issues that is the same as 0.27
Re: MacPorts and Myth 0.28
You are a risk taker if moving to Sierra already!
For MythWeb, do you happen to have a non default mythconverg database location, user or password? Have you checked the mariadb logs to see if perhaps mariadb is having issues of some sort? What I found with the query_col error was that meant there is no connection to mariadb. It appears myth error checking is missing a check somewhere.
For MythWeb, do you happen to have a non default mythconverg database location, user or password? Have you checked the mariadb logs to see if perhaps mariadb is having issues of some sort? What I found with the query_col error was that meant there is no connection to mariadb. It appears myth error checking is missing a check somewhere.
Re: MacPorts and Myth 0.28
Yes, i guess I am a risk taker... i went from mythtv 0.27 to 0.28 , Kodi prod to a beta and then I decided to go for it and add macOS Sierra on top of that. I have to get nfs working so I have to undo the security process and update a nfs plilst and then redo the security process.
mythconverg db should be in the default location with default userid and password. I suppose that I could log in to the database and do sql queries and see if I see connection issues.
Remember, MythWeb works many of the times..just not always.
I didn't find any logs for mariadb. I see I have a directory but it is empty. How do I enable logging for mariadb ?
I did check my mythbackend logs and I did notice some strange messages (anyway I didn't see these in my 0.27 backend logs). I noticed a disconnect message....
ProcessRequest mainserver.cpp:1698 (HandleAnnounce) - MainServer: MainServer::ANN Monitor
15:05:36.635765 I [1574/1202819] ProcessRequest mainserver.cpp:1703 (HandleAnnounce) - MainServer: adding: Ulsh-HTPC.local(7fb1f80acc10) as a client (events: 0)
15:05:42.475296 I [1574/1209071] MythSocketThread(87) mainserver.cpp:7629 (connectionClosed) - Monitor sock(7fb1f80acc10) 'XXXX-HTPC.local' disconnected
15:15:00.988797 I [1574/1212331] ProcessRequest mainserver.cpp:1698 (HandleAnnounce) - MainServer: MainServer::ANN Monitor
15:15:00.988811 I [1574/1212331] ProcessRequest mainserver.cpp:1703 (HandleAnnounce) - MainServer: adding: XXXX-HTPC.local(7fb1f854ee50) as a client (events: 0)
15:15:01.153417 I [1574/1212331] ProcessRequest mainserver.cpp:1698 (HandleAnnounce) - MainServer: MainServer::ANN Monitor
15:15:01.153433 I [1574/1212331] ProcessRequest mainserver.cpp:1703 (HandleAnnounce) - MainServer: adding: XXXX-HTPC.local(7fb1fa7e41e0) as a client (events: 0)
15:15:04.140002 I [1574/1204467] MythSocketThread(108) mainserver.cpp:7629 (connectionClosed) - Monitor sock(7fb1f854ee50) 'XXXX-HTPC.local' disconnected
15:15:04.153726 I [1574/1211271] MythSocketThread(152) mainserver.cpp:7629 (connectionClosed) - Monitor sock(7fb1fa7e41e0) 'XXXX-HTPC.local' disconnected
15:15:24.491921 I [1574/1212331] ProcessRequest mainserver.cpp:1698 (HandleAnnounce) - MainServer: MainServer::ANN Monitor
15:15:24.491935 I [1574/1212331] ProcessRequest mainserver.cpp:1703 (HandleAnnounce) - MainServer: adding: XXXX-HTPC.local(7fb1fa6f83a0) as a client (events: 0)
15:15:27.787302 I [1574/1213491] MythSocketThread(65) mainserver.cpp:7629 (connectionClosed) - Monitor sock(7fb1fa6f83a0) 'Ulsh-HTPC.local' disconnected
mythconverg db should be in the default location with default userid and password. I suppose that I could log in to the database and do sql queries and see if I see connection issues.
Remember, MythWeb works many of the times..just not always.
I didn't find any logs for mariadb. I see I have a directory but it is empty. How do I enable logging for mariadb ?
I did check my mythbackend logs and I did notice some strange messages (anyway I didn't see these in my 0.27 backend logs). I noticed a disconnect message....
ProcessRequest mainserver.cpp:1698 (HandleAnnounce) - MainServer: MainServer::ANN Monitor
15:05:36.635765 I [1574/1202819] ProcessRequest mainserver.cpp:1703 (HandleAnnounce) - MainServer: adding: Ulsh-HTPC.local(7fb1f80acc10) as a client (events: 0)
15:05:42.475296 I [1574/1209071] MythSocketThread(87) mainserver.cpp:7629 (connectionClosed) - Monitor sock(7fb1f80acc10) 'XXXX-HTPC.local' disconnected
15:15:00.988797 I [1574/1212331] ProcessRequest mainserver.cpp:1698 (HandleAnnounce) - MainServer: MainServer::ANN Monitor
15:15:00.988811 I [1574/1212331] ProcessRequest mainserver.cpp:1703 (HandleAnnounce) - MainServer: adding: XXXX-HTPC.local(7fb1f854ee50) as a client (events: 0)
15:15:01.153417 I [1574/1212331] ProcessRequest mainserver.cpp:1698 (HandleAnnounce) - MainServer: MainServer::ANN Monitor
15:15:01.153433 I [1574/1212331] ProcessRequest mainserver.cpp:1703 (HandleAnnounce) - MainServer: adding: XXXX-HTPC.local(7fb1fa7e41e0) as a client (events: 0)
15:15:04.140002 I [1574/1204467] MythSocketThread(108) mainserver.cpp:7629 (connectionClosed) - Monitor sock(7fb1f854ee50) 'XXXX-HTPC.local' disconnected
15:15:04.153726 I [1574/1211271] MythSocketThread(152) mainserver.cpp:7629 (connectionClosed) - Monitor sock(7fb1fa7e41e0) 'XXXX-HTPC.local' disconnected
15:15:24.491921 I [1574/1212331] ProcessRequest mainserver.cpp:1698 (HandleAnnounce) - MainServer: MainServer::ANN Monitor
15:15:24.491935 I [1574/1212331] ProcessRequest mainserver.cpp:1703 (HandleAnnounce) - MainServer: adding: XXXX-HTPC.local(7fb1fa6f83a0) as a client (events: 0)
15:15:27.787302 I [1574/1213491] MythSocketThread(65) mainserver.cpp:7629 (connectionClosed) - Monitor sock(7fb1fa6f83a0) 'Ulsh-HTPC.local' disconnected
Re: MacPorts and Myth 0.28
In /opt/local/etc/mariadb/my.cnf, you can specify where you want any log files. I don't know if there is a default (mine is always custom), if there was, I would expect it to be in /opt/local/var/log and possibly under mariadb there. Looking at the macports defailts, it might actually be /opt/local/var/db/mariadb/localhost.err? It sounds sort of like mariadb might be having issues and stopping now and then which would then give you the errors. The log file would show any issues. You sure you didn't also change mariadb versions (major ones), and if you did, you do need to run the upgrade on the database. Or, you may also have crashed tables or other odd issues. The log would tell you. Since you say it connects sometimes, it should not have anything to do with user or passwords.
-
blackarrow
- Newcomer
- Posts: 9
- Joined: Thu May 12, 2016 12:33 am
Re: MacPorts and Myth 0.28
Hi,
I'm attempting to move from the 0.27 all in one installer to 0.28 macports build.
I'm also on Sierra and Xcode 8.
I got past the Qt build issue which was fixed yesterday.
Now during mythtv-core.28 build I'm getting this error (copied lines out of main.log which contain mythwikiscripts only):
:info:build copying and adjusting scripts/mythwikiscripts -> build/scripts-2.7
:info:build changing mode of build/scripts-2.7/mythwikiscripts from 644 to 755
:info:destroot copying build/scripts-2.7/mythwikiscripts -> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_mythtv.28/mythtv-core.28/work/destroot/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin
:info:destroot changing mode of /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_mythtv.28/mythtv-core.28/work/destroot/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/mythwikiscripts to 755
:debug:destroot ... for mythwikiscripts
:error:destroot org.macports.destroot for port mythtv-core.28 returned: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump: '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_mythtv.28/mythtv-core.28/work/destroot/opt/local/bin/mythwikiscripts': The file was not recognized as a valid object file.
:debug:destroot Backtrace: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump: '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_mythtv.28/mythtv-core.28/work/destroot/opt/local/bin/mythwikiscripts': The file was not recognized as a valid object file.
Any ideas?
I'm attempting to move from the 0.27 all in one installer to 0.28 macports build.
I'm also on Sierra and Xcode 8.
I got past the Qt build issue which was fixed yesterday.
Now during mythtv-core.28 build I'm getting this error (copied lines out of main.log which contain mythwikiscripts only):
:info:build copying and adjusting scripts/mythwikiscripts -> build/scripts-2.7
:info:build changing mode of build/scripts-2.7/mythwikiscripts from 644 to 755
:info:destroot copying build/scripts-2.7/mythwikiscripts -> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_mythtv.28/mythtv-core.28/work/destroot/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin
:info:destroot changing mode of /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_mythtv.28/mythtv-core.28/work/destroot/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/mythwikiscripts to 755
:debug:destroot ... for mythwikiscripts
:error:destroot org.macports.destroot for port mythtv-core.28 returned: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump: '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_mythtv.28/mythtv-core.28/work/destroot/opt/local/bin/mythwikiscripts': The file was not recognized as a valid object file.
:debug:destroot Backtrace: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump: '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_mythtv.28/mythtv-core.28/work/destroot/opt/local/bin/mythwikiscripts': The file was not recognized as a valid object file.
Any ideas?
Re: MacPorts and Myth 0.28
1) Yes, the filename extension was changed in 0.28.gsulshski wrote:...
1) The recordings are named Channel_Starttime.ts vs Channel_Starttime.mpg : I had to modify the scripts with the new file extension but the content is still mpeg stream
2) For some reason, mythtranscode (what I use to remove the commercials) operates differently in 0.28 and I had to change the mythtv setup - general - job queue (general) - check save original files after transcoding (globally) or my job would fail (recording was removed after I transcoded to remove the commercials).
3) For some reason, when I was using tvdb.py to look up the season and episode, it was always returning a empty xml file. I debugged it and found that script was trying to access a api file in my directories that had root access and would fail. I updated the script with sudo $PATH/tvdb.py vs $PATH/tvdb.py it worked. Not sure what this has to do with 0.28 but I didn't have this issue with 0.27.
MythWeb 0.28
Operation wise: It isn't very stable from my perspective.
Most of the time I get
Fatal error: Call to a member function query_col() on a non-object in /opt/local/apache2/htdocs/MythWeb/modules/backend_log/init.php on line 15
...
2) AIUI, you just need to change a setting. See:
http://www.gossamer-threads.com/lists/m ... 103#602103
3) This is new to me. I'll have a look when I get a chance.
MythWeb -- I haven't experienced this issue. I wonder if some caching is going on? Which browser are you using? Does it also occur with other browsers?
Craig
Formerly the MacPorts guy.
Re: MacPorts and Myth 0.28
Re mariadb logs, the current default install doesn't produce logs. I've pointed this out to the maintainer of the mariadb port and we're working out a fix. To get mariadb logs now, edit /opt/local/etc/mariadb/my.cnf to include:gsulshski wrote:...
I didn't find any logs for mariadb. I see I have a directory but it is empty. How do I enable logging for mariadb ?
I did check my mythbackend logs and I did notice some strange messages (anyway I didn't see these in my 0.27 backend logs). I noticed a disconnect message....
ProcessRequest mainserver.cpp:1698 (HandleAnnounce) - MainServer: MainServer::ANN Monitor
15:05:36.635765 I [1574/1202819] ProcessRequest mainserver.cpp:1703 (HandleAnnounce) - MainServer: adding: Ulsh-HTPC.local(7fb1f80acc10) as a client (events: 0)
15:05:42.475296 I [1574/1209071] MythSocketThread(87) mainserver.cpp:7629 (connectionClosed) - Monitor sock(7fb1f80acc10) 'XXXX-HTPC.local' disconnected
15:15:00.988797 I [1574/1212331] ProcessRequest mainserver.cpp:1698 (HandleAnnounce) - MainServer: MainServer::ANN Monitor
15:15:00.988811 I [1574/1212331] ProcessRequest mainserver.cpp:1703 (HandleAnnounce) - MainServer: adding: XXXX-HTPC.local(7fb1f854ee50) as a client (events: 0)
15:15:01.153417 I [1574/1212331] ProcessRequest mainserver.cpp:1698 (HandleAnnounce) - MainServer: MainServer::ANN Monitor
15:15:01.153433 I [1574/1212331] ProcessRequest mainserver.cpp:1703 (HandleAnnounce) - MainServer: adding: XXXX-HTPC.local(7fb1fa7e41e0) as a client (events: 0)
15:15:04.140002 I [1574/1204467] MythSocketThread(108) mainserver.cpp:7629 (connectionClosed) - Monitor sock(7fb1f854ee50) 'XXXX-HTPC.local' disconnected
15:15:04.153726 I [1574/1211271] MythSocketThread(152) mainserver.cpp:7629 (connectionClosed) - Monitor sock(7fb1fa7e41e0) 'XXXX-HTPC.local' disconnected
15:15:24.491921 I [1574/1212331] ProcessRequest mainserver.cpp:1698 (HandleAnnounce) - MainServer: MainServer::ANN Monitor
15:15:24.491935 I [1574/1212331] ProcessRequest mainserver.cpp:1703 (HandleAnnounce) - MainServer: adding: XXXX-HTPC.local(7fb1fa6f83a0) as a client (events: 0)
15:15:27.787302 I [1574/1213491] MythSocketThread(65) mainserver.cpp:7629 (connectionClosed) - Monitor sock(7fb1fa6f83a0) 'Ulsh-HTPC.local' disconnected
Code: Select all
log-error=/opt/local/var/log/mariadb/localhost.log
Craig
Formerly the MacPorts guy.
Re: MacPorts and Myth 0.28
Ideas? Wait for the 0.28 all-in-one installer? I really hope to have it out in the next 2 weeks or so.blackarrow wrote:I'm attempting to move from the 0.27 all in one installer to 0.28 macports build.
I'm also on Sierra and Xcode 8.
I got past the Qt build issue which was fixed yesterday.
Now during mythtv-core.28 build I'm getting this error (copied lines out of main.log which contain mythwikiscripts only):
...
Any ideas?
If you want to proceed with building your own 0.28, clean and try again. If it fails, please post the entire main.log somewhere and supply a link.
Also, keep in mind that you are going to have to backup and restore your database. Make sure that all the 0.27 background processes are shut down before you start up the 0.28 versions. Otherwise you're going to get "interesting" results.
Craig
Formerly the MacPorts guy.