Where is mythtv backend log

First, see the Where are the log files? The log generated by mythbackend is the log of interest here, at least for starters. Type: control-C to abort the tailf. Here are some samples of the output. There will be other entries, but for each action, these are the key ones:. Note that the following suggestions are really debugging level tools.

My typo, but in your previous post bottom of this the service name was mythbackend. You have two instances of the service. Do a: sudo systemctl daemon-reload after that. The systemctl cat If this is the case, it could be related to how you cloned the data. All rights reserved. Other names may be trademarks of their respective owners. I have verified that I can log into the database, and the password in the config. Interestingly, the mythtv-backend.

If you do not want this then use a weaker binding such as "Requires" or "Wants". So it needs to be set as well.

This variable must be defined or the service will not start. This service will never work. Make sure it's disabled. Again, I'd remove this one. The override below too, as it just overrides this non-working service. Using systemctl cat anyServiceName, as you did above, is always best. Note that doing that tells you the actual path to the service.

You never need to figure out where the services lives. From earlier email: Nov 05 Compromise mythbackend[]: mythbackend[]: E CoreContext mythdbcon. When you create a new system, the numbers corresponding to the user and group names are different. The numbers are what matter, not the names.

So when you copy things from a different system, as you did with rsync, you will get the group and user numbers from your old system, which will correspond to different groups and users on the new system. Last edited: Jun 2, Ok cool, so you've got a database but it's not configured to allow anyone to access it.

Sorry, I should have clarified. HyRax1 , Jun 3, OK this is weird. Access denied for user 'root' 'localhost'. Blinky , Jun 3, Try Last edited: Jun 3, You are using an incorrect password for your root account then. This architecture allows for a central media distribution system that can reach anywhere a network can.

This is a remarkably flexible system, and it even allows very low power machines to act as perfectly usable frontends. All systems are going to need a tuner card. Other cards, like those based on the BT chipset, are also used. Unlike the PVR series, BT based cards require significant amounts of CPU power to save the video, as these cards output raw frames and not compressed streams.

For the backend, it is also good to have LAMP working properly so that anybody can use a web browser to schedule programming through MythWeb.

While it is not necessary, it is a very handy feature. A working Xorg graphical environment is necessary. For setting MythTV up, a remote access via Xforwarding mechanism is sufficient. Install the mythtv AUR package and any desired plugins. The package creates the mythtv user. At this point a generic MythTV installation is present that must be refined into a backend, a frontend, or both.

Before setting up your backend, make sure you have a functioning video capture card or a firewire input from a STB. Unfortunately, that part of setup is outside the scope of this article.