View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 43 posts ] 
Go to page Previous  1, 2, 3

Print view Previous topic   Next topic  
Author Message
Search for:
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 8:12 pm 
Offline
Joined: Fri Mar 26, 2004 9:00 am
Posts: 239
The thought plickens...

I just noticed on another reboot attempt that during the blue post penguin screen (where it splits horizontally) that I get "Successful connection to mythbackend" at the top of the screen in yellow. Then it goes in to the setup part and failes attempting to connect to the master backend. So I'm guess the subtetly of those differences is a hint as to where to look or what is wrong?

Looks like mythfrontend can't talk to the backend at 192.168.2.141:

Note there is a reference to a server at 0.0.0.0 in there? Is that normal? Did I miss a setting somewhere?

Code:
[root@mythtv 2017-12-10]# clear; date; grep -A 2000 2017-12-10T18:10:21.708006-08:00 mythtv_mythfrontend.log
Sun Dec 10 18:16:12 PST 2017
2017-12-10T18:10:21.708006-08:00 mythfrontend[2758]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Interrupt handler
2017-12-10T18:10:21.708591-08:00 mythfrontend[2758]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Terminated handler
2017-12-10T18:10:21.708809-08:00 mythfrontend[2758]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Segmentation fault handler
2017-12-10T18:10:21.709013-08:00 mythfrontend[2758]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Aborted handler
2017-12-10T18:10:21.709125-08:00 mythfrontend[2758]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Bus error handler
2017-12-10T18:10:21.709244-08:00 mythfrontend[2758]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Floating point exception handler
2017-12-10T18:10:21.709307-08:00 mythfrontend[2758]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Illegal instruction handler
2017-12-10T18:10:21.709368-08:00 mythfrontend[2758]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Real-time signal 0 handler
2017-12-10T18:10:21.709450-08:00 mythfrontend[2758]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup User defined signal 1 handler
2017-12-10T18:10:21.709509-08:00 mythfrontend[2758]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup User defined signal 2 handler
2017-12-10T18:10:21.709568-08:00 mythfrontend[2758]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Hangup handler
2017-12-10T18:10:21.709659-08:00 mythfrontend[2758]: C thread_unknown mythcommandlineparser.cpp:2619 (ConfigureLogging) mythfrontend version: fixes/29 [v29.0-64-g39b2062] www.mythtv.org
2017-12-10T18:10:21.709826-08:00 mythfrontend[2758]: C thread_unknown mythcommandlineparser.cpp:2621 (ConfigureLogging) Qt version: compile: 5.5.1, runtime: 5.5.1
2017-12-10T18:10:21.709991-08:00 mythfrontend[2758]: N thread_unknown mythcommandlineparser.cpp:2623 (ConfigureLogging) Enabled verbose msgs:  general
2017-12-10T18:10:21.710151-08:00 mythfrontend[2758]: N thread_unknown logging.cpp:927 (logStart) Setting Log Level to LOG_INFO
2017-12-10T18:10:21.710330-08:00 mythfrontend[2758]: N thread_unknown mythdirs.cpp:195 (InitializeMythDirs) Using runtime prefix = /usr
2017-12-10T18:10:21.710489-08:00 mythfrontend[2758]: N thread_unknown mythdirs.cpp:197 (InitializeMythDirs) Using configuration directory = /home/mythtv/.mythtv
2017-12-10T18:10:21.710688-08:00 mythfrontend[2758]: I CoreContext mythcorecontext.cpp:271 (Init) Assumed character encoding: en_US.UTF-8
2017-12-10T18:10:21.710877-08:00 mythfrontend[2758]: N CoreContext mythcontext.cpp:599 (LoadDatabaseSettings) Empty LocalHostName.
2017-12-10T18:10:21.711064-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:607 (LoadDatabaseSettings) Using localhost value of mythtv.local
2017-12-10T18:10:21.711255-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 0, status dbAwake
2017-12-10T18:10:21.711449-08:00 mythfrontend[2758]: I Logger logging.cpp:313 (run) Added logging to the console
2017-12-10T18:10:21.711637-08:00 mythfrontend[2758]: I LogForward loggingserver.cpp:302 (SyslogLogger) Added syslogging
2017-12-10T18:10:30.319602-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 1, status beAwake
2017-12-10T18:10:30.419921-08:00 mythfrontend[2758]: I CoreContext mythtranslation.cpp:73 (load) Loading en_us translation for module mythfrontend
2017-12-10T18:10:30.720585-08:00 mythfrontend[2758]: I SystemSignalManager mythsystemunix.cpp:509 (run) Starting process signal handler
2017-12-10T18:10:30.721274-08:00 mythfrontend[2758]: I SystemManager mythsystemunix.cpp:276 (run) Starting process manager
2017-12-10T18:10:30.721635-08:00 mythfrontend[2758]: I SystemIOHandlerW mythsystemunix.cpp:92 (run) Starting IO manager (write)
2017-12-10T18:10:30.721969-08:00 mythfrontend[2758]: I SystemIOHandlerR mythsystemunix.cpp:92 (run) Starting IO manager (read)
2017-12-10T18:10:30.822654-08:00 mythfrontend[2758]: I CoreContext screensaver-x11.cpp:82 (ScreenSaverX11Private) ScreenSaverX11Private: DPMS is disabled.
2017-12-10T18:10:30.822848-08:00 mythfrontend[2758]: E CoreContext mythxdisplay.cpp:191 (GetRefreshRate) X11 ModeLine query returned zeroes
2017-12-10T18:10:30.823004-08:00 mythfrontend[2758]: N CoreContext DisplayRes.cpp:64 (Initialize) Desktop video mode: 1280x720 60.000 Hz
2017-12-10T18:10:30.923335-08:00 mythfrontend[2758]: I CoreContext lirc.cpp:322 (Init) LIRC: Successfully initialized '/var/run/lirc/lircd' using '/home/mythtv/.mythtv/lircrc' config
2017-12-10T18:10:30.923541-08:00 mythfrontend[2758]: I CoreContext jsmenu.cpp:153 (ReadConfig) No joystick configuration found, not enabling joystick control
2017-12-10T18:10:31.023823-08:00 mythfrontend[2758]: E CoreContext cecadapter.cpp:167 (Open) CECAdapter: Failed to find any CEC devices.
2017-12-10T18:10:31.524488-08:00 mythfrontend[2758]: I CoreContext cecadapter.cpp:241 (Close) CECAdapter: Closing down CEC.
2017-12-10T18:10:31.524781-08:00 mythfrontend[2758]: I CoreContext mythudplistener.cpp:32 (Enable) UDPListener: Enabling

2017-12-10T18:10:31.524974-08:00 mythfrontend[2758]: I CoreContext serverpool.cpp:546 (bind) Binding to UDP 0.0.0.0:6948
2017-12-10T18:10:31.525166-08:00 mythfrontend[2758]: I CoreContext serverpool.cpp:546 (bind) Binding to UDP [::]:6948

2017-12-10T18:10:31.525370-08:00 mythfrontend[2758]: I CoreContext mythmainwindow.cpp:1046 (Init) Using Frameless Window
2017-12-10T18:10:31.525566-08:00 mythfrontend[2758]: I CoreContext mythmainwindow.cpp:1057 (Init) Using Full Screen Window
2017-12-10T18:10:31.525793-08:00 mythfrontend[2758]: I CoreContext mythmainwindow.cpp:1084 (Init) UI Screen Resolution: 1280 x 720
2017-12-10T18:10:31.726403-08:00 mythfrontend[2758]: I CoreContext mythmainwindow.cpp:1190 (Init) Using the Qt painter
2017-12-10T18:10:32.631437-08:00 mythfrontend[2758]: I CoreContext mythuiwebbrowser.cpp:1091 (LoadUserStyleSheet) MythUIWebBrowser: Loading css from - file:///usr/share/mythtv/themes/default/htmls/mythbrowser.css
2017-12-10T18:10:32.631506-08:00 mythfrontend[2758]: I CoreContext mythuiwebbrowser.cpp:998 (Init) MythUIWebBrowser: enabling plugins
2017-12-10T18:10:37.735261-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 2, status beAwake
2017-12-10T18:10:42.738516-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 3, status beAwake
2017-12-10T18:10:47.741905-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 4, status beAwake
2017-12-10T18:10:50.143907-08:00 mythfrontend[2758]: C CoreContext signalhandling.cpp:305 (handleSignal) Received Terminated: Code 0, PID 2854, UID 0, Value 0x736e6967756c702f
2017-12-10T18:10:53.146124-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 5, status beAwake
2017-12-10T18:10:58.149387-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 6, status beAwake
2017-12-10T18:11:03.152736-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 7, status beAwake
2017-12-10T18:11:08.156185-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 8, status beAwake
2017-12-10T18:11:13.259551-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 9, status beAwake
2017-12-10T18:11:18.262940-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 10, status beAwake
2017-12-10T18:11:23.267428-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:971 (TestDBconnection) Start up failure. host 192.168.2.141, status beAwakeFail
2017-12-10T18:11:23.267685-08:00 mythfrontend[2758]: I SendMessage mythcorecontext.cpp:448 (ConnectCommandSocket) MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.2.141:6543 (try 1 of 1)
2017-12-10T18:11:23.267918-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 0, status dbAwake
2017-12-10T18:11:24.769199-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 1, status beAwake
2017-12-10T18:11:29.873071-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 2, status beAwake
2017-12-10T18:11:30.273552-08:00 mythfrontend[2758]: E MythSocketThread(-1) mythsocket.cpp:827 (ReadStringListReal) MythSocket(7f485c019fd0:35): ReadStringList: Error, timed out after 7000 ms.
2017-12-10T18:11:30.273679-08:00 mythfrontend[2758]: C SendMessage mythcorecontext.cpp:1636 (CheckProtoVersion) Protocol version check failure.#012#011#011#011The response to MYTH_PROTO_VERSION was empty.#012#011#011#011This happens when the backend is too busy to respond,#012#011#011#011or has deadlocked due to bugs or hardware failure.
2017-12-10T18:11:30.274035-08:00 mythfrontend[2758]: I SendMessage mythcorecontext.cpp:448 (ConnectCommandSocket) MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.2.141:6543 (try 1 of 1)
2017-12-10T18:11:34.878857-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 3, status beAwake
2017-12-10T18:11:37.280701-08:00 mythfrontend[2758]: E MythSocketThread(-1) mythsocket.cpp:827 (ReadStringListReal) MythSocket(7f485c00a540:35): ReadStringList: Error, timed out after 7000 ms.
2017-12-10T18:11:37.280981-08:00 mythfrontend[2758]: C SendMessage mythcorecontext.cpp:1636 (CheckProtoVersion) Protocol version check failure.#012#011#011#011The response to MYTH_PROTO_VERSION was empty.#012#011#011#011This happens when the backend is too busy to respond,#012#011#011#011or has deadlocked due to bugs or hardware failure.
2017-12-10T18:11:37.281095-08:00 mythfrontend[2758]: I SendMessage mythcorecontext.cpp:448 (ConnectCommandSocket) MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.2.141:6543 (try 1 of 1)
2017-12-10T18:11:39.882781-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 4, status beAwake
2017-12-10T18:11:44.285900-08:00 mythfrontend[2758]: E MythSocketThread(-1) mythsocket.cpp:827 (ReadStringListReal) MythSocket(7f4864034cc0:38): ReadStringList: Error, timed out after 7000 ms.
2017-12-10T18:11:44.286024-08:00 mythfrontend[2758]: C SendMessage mythcorecontext.cpp:1636 (CheckProtoVersion) Protocol version check failure.#012#011#011#011The response to MYTH_PROTO_VERSION was empty.#012#011#011#011This happens when the backend is too busy to respond,#012#011#011#011or has deadlocked due to bugs or hardware failure.
2017-12-10T18:11:44.986673-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 5, status beAwake
2017-12-10T18:11:49.990048-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 6, status beAwake
2017-12-10T18:11:54.993365-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 7, status beAwake
2017-12-10T18:11:59.996805-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 8, status beAwake
2017-12-10T18:12:05.100285-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 9, status beAwake
2017-12-10T18:12:10.103676-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 10, status beAwake
2017-12-10T18:12:15.107405-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:971 (TestDBconnection) Start up failure. host 192.168.2.141, status beAwakeFail
2017-12-10T18:12:15.107960-08:00 mythfrontend[2758]: A CoreContext mythcontext.cpp:509 (FindDatabase) Cannot connect to backend
2017-12-10T18:12:15.108342-08:00 mythfrontend[2758]: I SendMessage mythcorecontext.cpp:448 (ConnectCommandSocket) MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.2.141:6543 (try 1 of 1)
2017-12-10T18:12:15.108577-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 0, status dbAwake
2017-12-10T18:12:16.710293-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 1, status beAwake
2017-12-10T18:12:21.714001-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 2, status beAwake
2017-12-10T18:12:22.014874-08:00 mythfrontend[2758]: I SendMessage mythcorecontext.cpp:1665 (CheckProtoVersion) MythCoreContext::CheckProtoVersion(): Using protocol version 91 BuzzOff
2017-12-10T18:12:26.818029-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 3, status beAwake
2017-12-10T18:12:31.821521-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 4, status beAwake
2017-12-10T18:12:36.824832-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 5, status beAwake
2017-12-10T18:12:41.928218-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 6, status beAwake
2017-12-10T18:12:46.931542-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 7, status beAwake
2017-12-10T18:12:51.935103-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 8, status beAwake
2017-12-10T18:12:57.039049-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 9, status beAwake
2017-12-10T18:13:02.043666-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 10, status beAwake
2017-12-10T18:13:07.047807-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:971 (TestDBconnection) Start up failure. host 192.168.2.141, status beAwakeFail
2017-12-10T18:13:07.048635-08:00 mythfrontend[2758]: A CoreContext mythcontext.cpp:509 (FindDatabase) Cannot connect to backend
2017-12-10T18:13:07.048873-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 0, status dbAwake
2017-12-10T18:13:08.749053-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 1, status beAwake
2017-12-10T18:13:13.852611-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 2, status beAwake
2017-12-10T18:13:18.856153-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 3, status beAwake
2017-12-10T18:13:23.859530-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 4, status beAwake
2017-12-10T18:13:28.962997-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 5, status beAwake
2017-12-10T18:13:33.966454-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 6, status beAwake
2017-12-10T18:13:38.969810-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 7, status beAwake
2017-12-10T18:13:44.073340-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 8, status beAwake
2017-12-10T18:13:49.076651-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 9, status beAwake
2017-12-10T18:13:54.080118-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB 192.168.2.141, BE , attempt 10, status beAwake
2017-12-10T18:13:59.183549-08:00 mythfrontend[2758]: I CoreContext mythcontext.cpp:971 (TestDBconnection) Start up failure. host 192.168.2.141, status beAwakeFail
2017-12-10T18:13:59.183820-08:00 mythfrontend[2758]: A CoreContext mythcontext.cpp:509 (FindDatabase) Cannot connect to backend


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 8:27 pm 
Offline
Joined: Fri Mar 26, 2004 9:00 am
Posts: 239
I thought I'd see if MythWeb can talk to anything. It can't, but I noted this:


Code:
  datetime:  2017-12-10 18:20:05 (PST)
    errornum:  256
  error type:  User Error
error string:  !!NoTrans: MasterServerIP or MasterServerPort not found! You may need to check your mythweb.conf file or re-run mythtv-setup!!
    filename:  /usr/share/mythtv/bindings/php/MythBackend.php
  error line:  43


So it seems I may not have successfully gotten through mythtv-setup yet. Not surprising since I get jailed at this "can not connect" screen and I can't seem to get to the main setup menu to do anything. Is there a way to break the loop and move around inside mythtv setup when it can't talk to the master backend? I think I just need healthy config files and I have a feeling things will snap in to place.

-Jeff


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 8:36 pm 
Offline
Joined: Fri Mar 26, 2004 9:00 am
Posts: 239
This looks promising:

Code:
https://lists.gt.net/mythtv/users/613497


Quote:
Interestingly All Frontends & Mythweb could not connect to the backend
after the upgrade until I enabled the option "Allow Connections from all
Subnets
<https://www.mythtv.org/wiki/Setup_General#Host_Address_Backend_Setup_.28v29.29>",
FE & CombinedFE/BE are both on the same subnet (172.16.107.0/24)....


Alas, I can't get in to the setup menus in order to try this. :(

Is there a watchdog/cron job somewhere that keeps spawning setup/mythfrontend that I can disable to move around on my own?

-Jeff


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 8:49 pm 
Offline
Joined: Fri Mar 26, 2004 9:00 am
Posts: 239
** PARTIAL SOLUTION **

In order to break out of the Myth Startup jail, I just used the handy ALT-x shortcut with an attached keyboard.

From the resulting shell I quickly launched mythtv-setup manually and it painted over top of the other process that is looping.

Once in there I did as mentioned in the Gossamer Threads archive from the Mythtv-Users list and I went in to the backend setup under General and I ticked the "Allow Connections from all Subnets" option.

I then did the "save and exit" by hitting escape and rebooted.

Lo and behold, when the system came up again I could see the normal myth main menu and my recordings. Yay!

My custom remote config needs to be restored, but that is on me, I don't think I followed the instructions properly so upgrades often cause me to have to put that back.

Semi-surprising is that I don't have HDMI audio out working, but I'll dig in to that now. I suspect the new driver renamed the audio output and I need to look in setup and rebind a few things. Also my normal "scale/fill" option in the player (tested against an HD recording from OTA) looks to have been lost as the image was centered with black bars. Small issues I suspect can be fixed in setup.

I'll report back with more as I resolve things. If anyone can give me a jump start on the sound issue I would appreciate it.

-Jeff


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 8:54 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1110
Location: SC
Jeff,

I am not convinced from that log that you are running the nvidia driver. Run sudo xconfig.sh again.

Alt+s will open mythtv-setup over top of the MythFrontend backend search screen. From there save the IPs as I mentioned above and those new settings that MythWeb mentioned should be set.


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 9:00 pm 
Offline
Joined: Fri Mar 26, 2004 9:00 am
Posts: 239
I noted that in the LinHES menu the audio was set to the analog outputs but in the mythtv-setup it was correctly set to HDMI. I set the LinHES one to HDMI and tried the audio test but that still didn't work. Trying a reboot and will continue exploring after dinner.

I have a vague recollection that it was a bit of a bear to get this working years ago as well (for HDMI audio out with this chipset).

-Jeff


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 9:09 pm 
Offline
Joined: Fri Mar 26, 2004 9:00 am
Posts: 239
brfransen wrote:
Jeff,

I am not convinced from that log that you are running the nvidia driver. Run sudo xconfig.sh again.

Alt+s will open mythtv-setup over top of the MythFrontend backend search screen. From there save the IPs as I mentioned above and those new settings that MythWeb mentioned should be set.


Ok I ran xconfig.sh but it looked like it reverted to the release driver.

When I rebooted I was back where I started. Going to re-run your pacman command with the test driver and see if I get back to where I was just before this.

-Jeff

Code:
And the result:

[root@mythtv ~]# pacman -U http://linhes.org/repo/x86_64/core-testing/nvidia-340xx-340.104-8-x86_64.pkg.tar.xz

loading packages...
resolving dependencies...
looking for conflicting packages...

Package (1)   Old Version  New Version  Net Change

nvidia-340xx  340.104-7    340.104-8      0.00 MiB

Total Installed Size:  4.69 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                                                                                               [###########################################################################] 100%
(1/1) checking package integrity                                                                                             [###########################################################################] 100%
(1/1) loading package files                                                                                                  [###########################################################################] 100%
(1/1) checking for file conflicts                                                                                            [###########################################################################] 100%
:: Processing package changes...
(1/1) upgrading nvidia-340xx                                                                                                 [###########################################################################] 100%
In order to use nvidia module, reboot the system.
[root@mythtv ~]#


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 9:22 pm 
Offline
Joined: Fri Mar 26, 2004 9:00 am
Posts: 239
VICTORY!

Looks like I am successfully running the upgraded 29 version of Mythtv, via HDMI out and the VDPAU driver with my older embedded NVIDIA chipset video and audio out over HDMI.

Things needed:

-The test NVidia 340 legacy driver brfransen posted earlier in this thread (I anticipate he'll merge that in to the mainline shortly?)

-For reasons still to be determined (and potentially reversed) I had to go in to mythtv-setup manually and allow connections from all subnets to the master backend under the General settings. This is especially odd since I run a combined FE/BE system.

-The mythtv-setup audio settings were correct with HDMI Nvidia ALSA driver selected but the LinHES Audio menu under the service menu had reverted to the analog output on the motherboard. I set that to HDMI and rebooted, and still no audio, but once I re-ran xconfig.sh and then re-installed the legacy NVidia driver, when the system was next rebooted everything was working as expected.

-My remote config still needs to be moved back in place. This one is totally on me. I must only be modifying the target and not the master source.

Where can I modify my MCE remote settings so they don't get over written? For the sake of the thread, this is the note I left for myself in the home directory:

Quote:
August 27, 2016
You need to edit this file to file the delete key. Set the Delete function to "Print" as the incoming key
sudo nano /usr/MythVantage/templates/remotes/favorites/mce/lircrc-mceusb
Search for "= D" and change "Clear" to "Print"


A BIG THANK YOU to everyone who has worked on KnoppMyth and LinHES over the years. I have been using it for roughly a decade and its been brilliant. Amazing work!

-Jeff


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 10:20 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1110
Location: SC
jac1d wrote:
-For reasons still to be determined (and potentially reversed) I had to go in to mythtv-setup manually and allow connections from all subnets to the master backend under the General settings. This is especially odd since I run a combined FE/BE system.
I don't think the allow connections from all subnets setting actually fixed the issue but rather going in and saving set the new missing settings and that is what allowed mythbackend to start. To confirm can you go back into mythtv-setup and disable allow connections from all subnets?

Quote:
-The mythtv-setup audio settings were correct with HDMI Nvidia ALSA driver selected but the LinHES Audio menu under the service menu had reverted to the analog output on the motherboard. I set that to HDMI and rebooted, and still no audio, but once I re-ran xconfig.sh and then re-installed the legacy NVidia driver, when the system was next rebooted everything was working as expected.
Without the nVidia driver audio over HDMI isn't going to work. The LinHES audio device setting only affect apps (Chrome, mplayer, aplay, etc) that rely on ALSA default device. MythTV has its own audio settings in mythfrontend settings (not mythtv-setup).

Quote:
Where can I modify my MCE remote settings so they don't get over written?
http://linhes.org/projects/linhes/wiki/ ... -Templates


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Mon Dec 11, 2017 9:21 am 
Offline
Joined: Wed Jan 07, 2004 12:14 pm
Posts: 393
Location: Charlotte, NC
UPDATE... I finally had time to concentrate on this upgrade. It actually went smoothly once certain things were done...

I was not able to get the ISO upgrade option to work well so I used the download option (faster anyway). The upgrade finishes (let the "attempting to connect to backend" script finish - it will fail); then reboot and manually start backend (alt-1). Then go into mythtv-setup (alt-s). Set the "Allow Connections from all Subnets". On my backend, the IP address was correct. All works beautifully. Have rebooted several times with no issues.

I still saw no message about update the DB schema although I did notice hard drive activity as I entered setup after the reboot...

I will now update frontends and report back.

_________________
Backend server - 4.0 TB 3.0ghz dual core 6 gig RAM, nVidia 9400, Gigabyte GA-870A-UD3 MB, 2 HD-5500, 2 HD Homerun dual tuners, 3 frontend machines - LinHES 8.5


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Mon Dec 11, 2017 11:34 am 
Offline
Joined: Wed Jan 07, 2004 12:14 pm
Posts: 393
Location: Charlotte, NC
UPGRADE 2... I have now upgraded my frontends with minimal problems. Two weird things that I have not yet tracked down. First, not clear why but every time I upgraded a front end and rebooted, the master backend machine hung - had to reboot. Haven't finished studying the logs but nothing apparent. Second, one of my Zotac machines didn't want to reboot (hung at the splash screen at the split). After the third reboot it went thru fine.

I am now officially on 8.5. Thanks to the team... All in all - very smooth (after a few minor issues).

_________________
Backend server - 4.0 TB 3.0ghz dual core 6 gig RAM, nVidia 9400, Gigabyte GA-870A-UD3 MB, 2 HD-5500, 2 HD Homerun dual tuners, 3 frontend machines - LinHES 8.5


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Mon Dec 11, 2017 5:03 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1110
Location: SC
Fixes for the Nvidia 340xx driver have been pushed to the release repo and R8.5.1 ISO has been posted.


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Tue Dec 12, 2017 8:46 am 
Offline
Joined: Wed Jan 04, 2006 10:20 am
Posts: 366
Location: South New Jersey, USA
I was able to get both of my systems working last night using the nvidia pacman update. I can also confirm that you need to go into myth setup and change (touch) something to force it to ask you if you want to save changes. Just going in and backing out is not enough. I went into the IP field and then escaped out without making changes and it asked me if I want to save my changes. I replied yes and the backend started connecting. At least in my case, no need to leave the "Allow Connections from all Subnets" checked. I now have LinHES 8.5 running smoothly on my BE/FE and second FE.

Big thanks to brfransen for all his help on this and all his work in keeping LinHES going.

_________________
LINHES 8.3 BE/FE - MSI K9N6SGM-V with AMD A64 X2 4600+, 1GB Ram. 1.5TB WD. HDHR Prime & PVR150. Nvidia GT210. Silver remote.
FrontEnd - Dell Vostro 400 3.0GHz Core2Duo NVidia GeForce210. MCE Remote


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 43 posts ] 
Go to page Previous  1, 2, 3



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu