<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 21, 2024 at 12:44 PM James Abernathy <<a href="mailto:jfabernathy@gmail.com">jfabernathy@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 21, 2024 at 12:37 PM James Abernathy <<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 21, 2024 at 12:31 PM Peter Bennett <<a href="mailto:pb.mythtv@gmail.com" target="_blank">pb.mythtv@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
<p><br>
</p>
<div>On 6/21/24 10:52, James Abernathy
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jun 20, 2024 at
6:11 PM James Abernathy <<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jun 20, 2024
at 5:59 PM Mike Perkins <<a href="mailto:mikep@randomtraveller.org.uk" target="_blank">mikep@randomtraveller.org.uk</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On
20/06/2024 22:46, James Abernathy wrote:<br>
> On Thu, Jun 20, 2024 at 7:09 AM James Abernathy
<<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a>><br>
> wrote:<br>
><br>
>> Not sure where I went wrong. On Debian 12
Bookworm, if I create the mythtv<br>
>> group and user before I install the .deb
packages I can get mythtv setup<br>
>> using Web App, but with some extra steps.
The backend works correctly. The<br>
>> problem shows up running mythfrontend as a
mythtv user permission issue.<br>
>><br>
>> If I don't create user mythtv and just
install the deb packages, Web App<br>
>> starts showing mythconverg already setup
completely. In this case<br>
>> mythfrontend works.<br>
>><br>
>> Jim A<br>
>><br>
><br>
> As a further test case I created a system on
Kubuntu 24.04 LTS and<br>
> installed maradb-server.<br>
><br>
> Next I created the mythtv group id 200 and mythtv
user id 200. I then<br>
> added my user, jim, to group mythtv.<br>
><br>
> Then I installed mythtv using the
<a>ppa:mythbuntu/34</a>. After installation, I<br>
> rebooted.<br>
><br>
> At this point the Web app came up with no issues.
The database was already<br>
> set up without further messing around.<br>
><br>
> So maybe the Debian mythtv packaging does
something funny if the user and<br>
> group mythtv is created before installing the
mythtv packages. I use the<br>
> Debian 12 packages for mythtv that I build
regularly on a VM and store in a<br>
> repo on my NAS.<br>
><br>
Please note that user/200 and group/200 are /still/ in
the system uid and gid range. The numbers in<br>
this range can be arbitrarily allocated to various
susbsytems in random order if and when they are<br>
installed. I do not know if the install mechanism has
any collision detection.<br>
<br>
It is possible that your previous attempt re-used a
uid or gid that had already been allocated.<br>
<br>
I always allocate the mythtv user and group before
installing any software. I make sure I put mine<br>
in the *user* range (> 1000), in my case 1006/1006.
This ensures no accidents or collisions.<br>
<br>
--<br>
<br>
Mike Perkins<br>
</blockquote>
<div><br>
</div>
<div>Thanks, I don't think it's a collision at this
point in either group our user is. However I just got
the same error with mythfrontend on Kubuntu 24.04 as I
got on Debian 12 with the user created before
installation.</div>
<div><br>
</div>
<div>Either way, I'll test with users> 1000 and see
what happens.</div>
<div><br>
</div>
<div>The error on mythfrontend is:</div>
<div><span style="font-family:monospace">2024-06-20
18:03:04.715443 I Start up testing connections. DB
localhost, BE , attempt 0, status dbAwake, Delay:
2000<br>
2024-06-20 18:03:05.248215 E [DBManager0] Unable to
connect to database!<br>
2024-06-20 18:03:05.248264 E Driver error was
[1/1045]:<br>
QMYSQL: Unable to connect<br>
Database error was:<br>
Access denied for user 'mythtv'@'localhost' (using
password: YES)</span></div>
<div><span style="font-family:monospace"><br>
</span></div>
<div><span style="font-family:arial,sans-serif">Jim A</span></div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>After more testing, I've found that this is not related
to whether you have mysql or mariadb as your database. It
appears that if you don't create your mythtv user/group
ahead of time. Debian 12 and Ubuntu create the database
properly and set up config.xml so that mythfrontend works.
I did find that on mysql database you get a Web App
warning/error about needing to have the timezones setup
correctly. It gives you the command to execute in a terminal
and that fixes it. On mariadb you don't get this error.</div>
<div><br>
</div>
<div>I have not found a way to setup the mythtv user and group
ahead of the mythtv installation that allows mythfrontend to
work without a permission problem. It appears that the
backend is working in these cases, but on my test VM I can't
test that without mythfrontend.</div>
<div><br>
</div>
<div>Jim A<br>
<br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</blockquote>
<p>Is the backend on the same VM as the frontend and using the same
login user?<br>
</p>
<p>Unable to connect to database looks like a problem with the
config.xml. Perhaps this is only set up in the install script if
the mythtv user does not yet exist.</p>
<p>Peter</p></div></blockquote><div><br></div><div>The backend is on the same VM as the frontend. I'm running it as user jim. I did not setup config.xml for jim before running mythfrontend,</div><div><br></div><div>That usually happens automatically, I think. I didn't mess with the mariadb cnf files for bind-address since it was on the same VM.</div><div><br></div><div>I tried linking to the same config.xml as the mythtv user config.xml which agrees with the /etc/mythtv/config.xml</div><div><br></div><div>Jim A<br></div></div></div></blockquote><div><br></div><div>Okay, it's fixed now. What I did was delete the link in /home/jim/.mythtv for config.xml to /home/mythtv/.mythtv/config.xml.</div><div><br></div><div>Then I just copied /etc/mythtv/config.xml to /home/jim/.mythtv/config.xml and that worked.</div><div><br></div><div>So it seems that if you create your own mythtv group and user and manually add user 'jim' to group mythtv. The web app will configure the backend fine but the config.xml for the use is left to that user to do.</div><div><br></div><div>I previously had to install kodi to test if the backend was working and I could watch live tv that way before I got mythfrontend running.</div><div><br></div><div>Thanks,</div><div><br></div><div>JIm A<br></div></div></div></blockquote><div><br></div><div>I just confirmed the fix also on Debian 12. Previous fix was for Linux Mint 21.3 which is Ubuntu 22.04.</div><div><br></div><div>So the process is as follows.</div><div><br></div><div>1. On a fresh Debian 12 system or Ubuntu system, set up a file in /etc/sources.list.d/ to include either your local Debian mythtv package repo location or using the ppa on Ubuntu.</div><div>2. Install mariadb or mysql and if using BTRFS, turn off COW by chattr <a class="gmail_plusreply" id="plusReplyChip-0">+C /var/lib/mysql</a><br></div><div>3. Create the mythtv user to the desired gid/uid and add your own user to the mythtv group</div><div>i.e. </div><div><span style="font-family:monospace">sudo addgroup --gid 1006 mythtv<br>sudo adduser --ingroup mythtv --home /home/mythtv --shell /bin/bash --uid 1006 mythtv<br>sudo usermod -aG mythtv jim</span></div><div><span style="font-family:arial,sans-serif">4. I reboot for safety reasons, then</span><span style="font-family:monospace"> sudo apt install mythtv</span></div><div><font face="arial,sans-serif">5. point browser to localhost:6544. The mythconverg database should be set up.<br></font></div><div><font face="arial,sans-serif">6. Continue with the remaining backend setup using Web App and restart the backend with the button at the top.<br></font></div><div><font face="arial,sans-serif">7. In a terminal in your user copy /etc/mythtv/config.xml to ~/,mythtv/config.xml</font></div><div><font face="arial,sans-serif">8. Run mythfrontend.</font></div><div><font face="arial,sans-serif"><br></font></div><div><font face="arial,sans-serif">Jim A<br><br></font></div><div><span style="font-family:monospace"><br></span></div></div></div>