setup

Have a MythTV related problem? Ask for help from other MythTV users here.

Moderator: Forum Moderators

User avatar
bill6502
Developer
Posts: 2307
Joined: Fri Feb 07, 2014 5:28 pm
United States of America

Re: setup

Post by bill6502 »

The output of these two:

Code: Select all

hostname
ls -ld  {~,~mythtv}/.mythtv/config.xml /etc/mythtv/config.xml
gcook12
Junior
Posts: 89
Joined: Sun Nov 06, 2016 1:35 am
United States of America

Re: setup

Post by gcook12 »

I typed those ccmmands in and this is what came back

gcook12@gcook12-Aspire-5253:~$ hostname
gcook12-Aspire-5253
gcook12@gcook12-Aspire-5253:~$ 1s -1d {~,~mythtv}/.mythtv/config.xml /etc/mythtv/config.xml
1s: command not found
gcook12@gcook12-Aspire-5253:~$
User avatar
bill6502
Developer
Posts: 2307
Joined: Fri Feb 07, 2014 5:28 pm
United States of America

Re: setup

Post by bill6502 »

ls -ld, not 1s -1d
gcook12
Junior
Posts: 89
Joined: Sun Nov 06, 2016 1:35 am
United States of America

Re: setup

Post by gcook12 »

I put in I and this is what printed out. This looks better but I still have no idea what all of this means. I am sorry this is taking so much of your time.

gcook12@gcook12-Aspire-5253:~$ hostname
gcook12-Aspire-5253
gcook12@gcook12-Aspire-5253:~$ ls -ld {~,~mythtv}/.mythtv/config.xml /etc/mythtv/config.xml
-rw-rw---- 1 mythtv mythtv 452 Apr 27 20:49 /etc/mythtv/config.xml
-rw-rw-r-- 1 gcook12 gcook12 616 May 6 14:59 /home/gcook12/.mythtv/config.xml
lrwxrwxrwx 1 root root 22 Sep 21 2016 /home/mythtv/.mythtv/config.xml -> /etc/mythtv/config.xml
gcook12
Junior
Posts: 89
Joined: Sun Nov 06, 2016 1:35 am
United States of America

Re: setup

Post by gcook12 »

going to the setup page, I find these values, are they correct?

Hostname gcook12-Aspire-5253
Ping test server checked
Port 3306
Database name mythconverg
User mythtv
Password NCi0hdAh
Use custom identifier for frontend preferences checked
User avatar
bill6502
Developer
Posts: 2307
Joined: Fri Feb 07, 2014 5:28 pm
United States of America

Re: setup

Post by bill6502 »

The Hostname matches the backend log discussed earlier, and that's good.

The last, Use custom identifier for frontend preferences isn't normally used.
That MAY be the cause of the differences between the config.xml files. I
use Ubuntu, but build from source and don't have the Mythbuntu tools.

Mythbuntu normally points the user (gcook12) login's config.xml and the mythtv login's config.xml
to the same file, as seen above: lrwxrwxrwx 1 root root 22 Sep 21 2016 /home/mythtv/.mythtv/config.xml -> /etc/mythtv/config.xml
for user mythtv. Your own user doesn't have that link and is just a file.

I would remove /home/gcook12/.mythtv/config.xml and re-establish the link to /etc/mythtv/config.xml.
Like this:

Code: Select all

rm /home/gcook12/.mythtv/config.xml
ln -s /etc/mythtv/config.xml  /home/gcook12/.mythtv/config.xml
If you don't understand the command, type man ln or man rm and read
the page. Also, this Wiki has a troubleshooting section that applies here
and is worth studying: https://www.mythtv.org/wiki/Config.xml#Troubleshooting

Once the link is back, look at the backend log and see if the failure is gone
or at least changed to a different one.
gcook12
Junior
Posts: 89
Joined: Sun Nov 06, 2016 1:35 am
United States of America

Re: setup

Post by gcook12 »

I tried it but no change. Here is what I installed just in case there was a typo

gcook12@gcook12-Aspire-5253:~$ rm /home/gcook12/.mythtv/config.xml
gcook12@gcook12-Aspire-5253:~$ ln -s /etc/mythtv/config.xml /home/gcook12/.mythtv/config.xml
gcook12@gcook12-Aspire-5253:~$
gcook12
Junior
Posts: 89
Joined: Sun Nov 06, 2016 1:35 am
United States of America

Re: setup

Post by gcook12 »

here is what is in the log

Code: Select all

May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: C thread_unknown mythcommandlineparser.cpp:2619 (ConfigureLogging) mythbackend version: fixes/29 [v29.1-15-g280138b] www.mythtv.org
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: C thread_unknown mythcommandlineparser.cpp:2621 (ConfigureLogging) Qt version: compile: 5.5.1, runtime: 5.5.1
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: N thread_unknown mythcommandlineparser.cpp:2623 (ConfigureLogging) Enabled verbose msgs:  general
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: N thread_unknown logging.cpp:927 (logStart) Setting Log Level to LOG_INFO
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I Logger logging.cpp:313 (run) Added logging to the console
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Interrupt handler
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Terminated handler
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Segmentation fault handler
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Aborted handler
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Bus error handler
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Floating point exception handler
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Illegal instruction handler
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Real-time signal 0 handler
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Hangup handler
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: N thread_unknown mythdirs.cpp:195 (InitializeMythDirs) Using runtime prefix = /usr
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: N thread_unknown mythdirs.cpp:197 (InitializeMythDirs) Using configuration directory = /home/mythtv/.mythtv
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I CoreContext mythcorecontext.cpp:271 (Init) Assumed character encoding: en_US.UTF-8
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: N CoreContext mythcontext.cpp:599 (LoadDatabaseSettings) Empty LocalHostName.
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I CoreContext mythcontext.cpp:607 (LoadDatabaseSettings) Using localhost value of gcook12-Aspire-5253
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up testing connections. DB localhost, BE , attempt 0, status dbAwake
May  9 19:42:38 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I LogForward loggingserver.cpp:302 (SyslogLogger) Added syslogging
May  9 19:42:39 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: N CoreContext mythcorecontext.cpp:1768 (InitLocale) Setting QT default locale to en_US
May  9 19:42:39 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I CoreContext mythcorecontext.cpp:1801 (SaveLocaleDefaults) Current locale en_US
May  9 19:42:39 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: N CoreContext mythlocale.cpp:123 (LoadDefaultsFromXML) Reading locale defaults from /usr/share/mythtv//locales/en_us.xml
May  9 19:42:39 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I CoreContext mythtranslation.cpp:73 (load) Loading en_us translation for module mythfrontend
May  9 19:42:39 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I CoreContext schemawizard.cpp:120 (Compare) Current MythTV Schema Version (DBSchemaVer): 1348
May  9 19:42:39 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: I CoreContext mythtranslation.cpp:73 (load) Loading en_us translation for module mythfrontend
May  9 19:42:39 gcook12-Aspire-5253 mythbackend: mythbackend[2084]: E MythSocketThread(-1) mythsocket.cpp:698 (ConnectToHostReal) MythSocket(236fea0:-1): Failed to connect to (127.0.0.1:6543) Connection refused
gcook12@gcook12-Aspire-5253:~$
User avatar
bill6502
Developer
Posts: 2307
Joined: Fri Feb 07, 2014 5:28 pm
United States of America

Re: setup

Post by bill6502 »

Hi,

You should rerun the diff command: diff {~,~mythtv}/.mythtv/config.xml
and what you entered looks fine. There should be no differences.

Next, go back to mythtv-seup and check your work there. I'd run it as mentioned
before: mythtv-setup.real --logpath /tmp and look in the file in /tmp for errors.

Rerun the backend to see if the output changed. No need to post if it's the same
error.

Do you have a firewall? Something blocking port 6543? Looks like this may be a
stand alone host based on the IP address.
gcook12
Junior
Posts: 89
Joined: Sun Nov 06, 2016 1:35 am
United States of America

Re: setup

Post by gcook12 »

Not sure I follow what is causing this but when I entered the command you suggested, the program went right to the setup page like there are no issues. However, If I try to start the program from a shortcut I have on the desktop or when I just power up the computer since I have it set to go straight to mythtv, the old issue reappears. I looked at teh command that was on the shortcut that I had written some time ago and the command is mythfrontend --service

I don't recall how I entered the shortcut or the command from startup but I assume that if I enter the command you suggested, things will work. Not sure why that is the case.
User avatar
bill6502
Developer
Posts: 2307
Joined: Fri Feb 07, 2014 5:28 pm
United States of America

Re: setup

Post by bill6502 »

Three related programs here.
  • mythtv-setup.real works, good. I assume you checked all the values
    for correctness. Mostly the IP addresses. The help for each setting
    is pretty good.
  • Ignore your shortcut for now. You're saying it starts the frontend. That
    will always fail because the backend isn't running per your logs.
  • We need to get the backend working first:

    Code: Select all

    systemctl cat mythtv-backend
    systemctl status --no-pager mythtv-backend  # Expect: Active: inactive (dead) since ...
    sudo systemctl stop mythtv-backend # If the above shows it's: Active: active (running) ...
    sudo mythbackend --loglevel debug --logpath /tmp --user mythtv --quiet
    
    The last command won't print the log, it will be in /tmp.
Paste the commands and their output and attach the file in /tmp. It will
look similar to: mythbackend.20180509135807.2375.log

It would be nice if you'd put the 1st 3 commands/outpout above in a code display, you do
that by highlighting the section and clicking on the </> icon right above the
are where you enter the text.
gcook12
Junior
Posts: 89
Joined: Sun Nov 06, 2016 1:35 am
United States of America

Re: setup

Post by gcook12 »

Here is the first one

gcook12@gcook12-Aspire-5253:~$ systemctl cat mythtv-backend
# /lib/systemd/system/mythtv-backend.service
[Unit]
Description=MythTV Backend
Documentation=https://www.mythtv.org/wiki/Mythbackend
After=mysql.service network.target

[Service]
User=mythtv
EnvironmentFile=-/etc/mythtv/additional.args
ExecStart=/usr/bin/mythbackend --quiet --syslog local7 $ADDITIONAL_ARGS
StartLimitBurst=10
StartLimitInterval=10m
Restart=on-failure
RestartSec=1

[Install]
WantedBy=multi-user.target
gcook12@gcook12-Aspire-5253:~$
gcook12
Junior
Posts: 89
Joined: Sun Nov 06, 2016 1:35 am
United States of America

Re: setup

Post by gcook12 »

here is the second one

gcook12@gcook12-Aspire-5253:~$ systemctl status mythtv-backend # Expect: Active: inactive (dead) since ...
● mythtv-backend.service - MythTV Backend
Loaded: loaded (/lib/systemd/system/mythtv-backend.service; enabled; vendor p
Active: inactive (dead) (Result: exit-code) since Sat 2018-05-12 10:33:33 CDT
Docs: https://www.mythtv.org/wiki/Mythbackend
Process: 2393 ExecStart=/usr/bin/mythbackend --quiet --syslog local7 $ADDITION
Main PID: 2393 (code=exited, status=1/FAILURE)

May 12 10:33:32 gcook12-Aspire-5253 systemd[1]: mythtv-backend.service: Main pro
May 12 10:33:32 gcook12-Aspire-5253 systemd[1]: mythtv-backend.service: Unit ent
May 12 10:33:32 gcook12-Aspire-5253 systemd[1]: mythtv-backend.service: Failed w
May 12 10:33:33 gcook12-Aspire-5253 systemd[1]: mythtv-backend.service: Service
May 12 10:33:33 gcook12-Aspire-5253 systemd[1]: Stopped MythTV Backend.
May 12 10:33:33 gcook12-Aspire-5253 systemd[1]: mythtv-backend.service: Start re
May 12 10:33:33 gcook12-Aspire-5253 systemd[1]: Failed to start MythTV Backend.
lines 1-14/14 (END)
gcook12
Junior
Posts: 89
Joined: Sun Nov 06, 2016 1:35 am
United States of America

Re: setup

Post by gcook12 »

Cant put in the 3rd and fourth command because I do not get a command prompt
User avatar
bill6502
Developer
Posts: 2307
Joined: Fri Feb 07, 2014 5:28 pm
United States of America

Re: setup

Post by bill6502 »

The output of the 1st command looks normal.

The 2nd command automatically passes the output to a pager,
just type: q and your command prompt will come back.

You don't need the 3rd command because the output of the 2nd
says it's dead. But running it doesn't hurt anything.
Post Reply