Mailing List Archive

New install - mythbackend password not accepted
Hi All

I'm in the process of doing a new install of mythtv on xubuntu 20.04 and
using Mythbuntu Control Panel

I've come upon this problem where ,in mythbackend setup where it asks
you to stop the backend and requires the password ,it does not accept
any password.

I've tried the operating system user password , set the Host Address
Backend Setup  security PIN to 0000 and tried that, tried a blank
password ,tried "root" and many others.

What I have been doing is entering blank three times in a row and it the
asks if I want to run mythfilldatabase. It seems to retain all my settings.

I have a vague memory that I ran into this before but searches have been
fruitless.


Also ,what's with the mythtvnz archives? they are a total disaster as
far as searching for anything ,or am I missing something?


Paul



_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On Sat, 3 Apr 2021 17:20:44 +1300, you wrote:

>Hi All
>
>I'm in the process of doing a new install of mythtv on xubuntu 20.04 and
>using Mythbuntu Control Panel
>
>I've come upon this problem where ,in mythbackend setup where it asks
>you to stop the backend and requires the password ,it does not accept
>any password.
>
>I've tried the operating system user password , set the Host Address
>Backend Setup  security PIN to 0000 and tried that, tried a blank
>password ,tried "root" and many others.
>
>What I have been doing is entering blank three times in a row and it the
>asks if I want to run mythfilldatabase. It seems to retain all my settings.
>
>I have a vague memory that I ran into this before but searches have been
>fruitless.
>
>
>Also ,what's with the mythtvnz archives? they are a total disaster as
>far as searching for anything ,or am I missing something?
>
>
>Paul

The password for stopping and starting things that are run by root is
the sudo password. This is the password you are asked for when the
installer creates your initial (admin enabled) account at the start of
the install process, and the same password that you need to use to
login to your user account if you have not set it to autologin.

If you have set it up to autologin and have forgotten the normal login
password, you can reset it by opening a terminal and using the
"passwd" command. There is probably also a GUI way of doing that.

The root account is not set up with a password by default. To use it,
you can do "sudo su" from your user account, or you can set a root
password with "sudo passwd".

I have an alternate way of setting up mythfrontend where it uses an
sudo helper script to do systemctl commands so that it does not need
to ask for the password to stop mythbackend. You can find it here:

https://lists.archive.carbon60.com/mythtv/users/625993

_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On 3/04/21 9:39 pm, Stephen Worthington wrote:
> On Sat, 3 Apr 2021 17:20:44 +1300, you wrote:
>
>> Hi All
>>
>> I'm in the process of doing a new install of mythtv on xubuntu 20.04 and
>> using Mythbuntu Control Panel
>>
>> I've come upon this problem where ,in mythbackend setup where it asks
>> you to stop the backend and requires the password ,it does not accept
>> any password.
>>
>> I've tried the operating system user password , set the Host Address
>> Backend Setup  security PIN to 0000 and tried that, tried a blank
>> password ,tried "root" and many others.
>>
>> What I have been doing is entering blank three times in a row and it the
>> asks if I want to run mythfilldatabase. It seems to retain all my settings.
>>
>> I have a vague memory that I ran into this before but searches have been
>> fruitless.
>>
>>
>> Also ,what's with the mythtvnz archives? they are a total disaster as
>> far as searching for anything ,or am I missing something?
>>
>>
>> Paul
> The password for stopping and starting things that are run by root is
> the sudo password. This is the password you are asked for when the
> installer creates your initial (admin enabled) account at the start of
> the install process, and the same password that you need to use to
> login to your user account if you have not set it to autologin.
>
> If you have set it up to autologin and have forgotten the normal login
> password, you can reset it by opening a terminal and using the
> "passwd" command. There is probably also a GUI way of doing that.
>
> The root account is not set up with a password by default. To use it,
> you can do "sudo su" from your user account, or you can set a root
> password with "sudo passwd".
>
> I have an alternate way of setting up mythfrontend where it uses an
> sudo helper script to do systemctl commands so that it does not need
> to ask for the password to stop mythbackend. You can find it here:
>
> https://lists.archive.carbon60.com/mythtv/users/625993
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz@lists.ourshack.com
> https://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/


Thanks Stephen I'll give that a try.

I did set autologin and the sudo password does fail to work to authorise
backend stop/start.

P.S. you also answered my comment about the mailing list archive.

I had been looking at this:
http://lists.ourshack.com/pipermail/mythtvnz/
<http://lists.ourshack.com/pipermail/mythtvnz/>

I never managed to find the correct pages on carbo60.com

I'll let you know how I get on with the scripts.

-Paul


_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
> The password for stopping and starting things that are run by root is
> the sudo password. This is the password you are asked for when the
> installer creates your initial (admin enabled) account at the start of
> the install process, and the same password that you need to use to
> login to your user account if you have not set it to autologin.
>
> If you have set it up to autologin and have forgotten the normal login
> password, you can reset it by opening a terminal and using the
> "passwd" command. There is probably also a GUI way of doing that.
>
> The root account is not set up with a password by default. To use it,
> you can do "sudo su" from your user account, or you can set a root
> password with "sudo passwd".
>
> I have an alternate way of setting up mythfrontend where it uses an
> sudo helper script to do systemctl commands so that it does not need
> to ask for the password to stop mythbackend. You can find it here:
>
> https://lists.archive.carbon60.com/mythtv/users/625993
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz@lists.ourshack.com
> https://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

Ok ,I tried your scripts which don't appear to work correctly in this system

While running htop in another workspace ,I can issue sudo
/home/mythtv/bin/mythtv-systemctl-helper.sh stop and sudo
/home/mythtv/bin/mythtv-systemctl-helper.sh start commands and observe
that the processes related to /usr/bin/mythtv disappear and reappear.

If I start mythtv backend setup ,first I get a window asking to stop
myth backend ,I click yes, I get another window asking for the password
and I close it.

Myth backend setup starts and says myth backend is still running ,htop
confirms this, there are 3 choices: 'stop backend' , 'continue' or 'exit'.

'Continue' allows me to  make changes  using the setup app. 'Stop
backend' freezes the workspace. I can switch workspaces to where htop is
running and see there are /usr/bin/mythtv processes running - workspace
2 is not frozen. I can issue sudo
/home/mythtv/bin/mythtv-systemctl-helper.sh stop in the terminal and the
mythtv processes stop. Back in workpace 1  the frozen myth backend setup
gui closes and leaves a mythtv terminal which along with other messages
says "trying to close mythbackend" and "connection to mythbackend was lost"

This freezing of the workspace happened before running your scripts. The
scripts have allowed the closure of the password request box without it
respawning.Before the scripts I had to click ok 3 times and then the
password box would not come back.

It might be easier for you to point me to an up to date install
procedure for OSs that use systemd  and for me to do a reinstall.

During the mythtv install via myth control panel ,the installer exited 
due to the absence of 'pwgen' which appear to be an old bug:
https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/592521
<https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/592521> but I
never encountered it when Mythbuntu was available.

I have a very strong suspicion there were setup option request windows
hidden by the "failed to install message" box ,there was a box with a
"default" button revealed when the closed "failed to install message" box

I installed pwgen and started myth control panel which seemed to be
happy except for asking for passwords.

What is the best way to remove all trace of mythtv including config
files from the system  and begin again?

Do you think Myth Control Panel complicates the install?

Thanks for you help

Paul


_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On Sun, 4 Apr 2021 10:55:34 +1200, you wrote:

>Ok ,I tried your scripts which don't appear to work correctly in this system
>
>While running htop in another workspace ,I can issue sudo
>/home/mythtv/bin/mythtv-systemctl-helper.sh stop and sudo
>/home/mythtv/bin/mythtv-systemctl-helper.sh start commands and observe
>that the processes related to /usr/bin/mythtv disappear and reappear.
>
>If I start mythtv backend setup ,first I get a window asking to stop
>myth backend ,I click yes, I get another window asking for the password
>and I close it.

If my scripts are installed correctly, you should not get a popup
window asking for the password. So you need to check that the scripts
are installed. Try doing this:

sudo mysql
use mythconverg;
select * from settings where data like '%helper%' order by hostname;
quit

This is what I get:

MariaDB [mythconverg]> select * from settings where data like
'%helper%' order by hostname;
+---------------------+---------------------------------------------------------+----------+
| value | data | hostname |
+---------------------+---------------------------------------------------------+----------+
| ServerHaltCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh halt | NULL |
| BackendStartCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh start | NULL |
| BackendStopCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh stop | NULL |
| HaltCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh poweroff | mypvr |
| RebootCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh reboot | mypvr |
| HaltCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh poweroff | savaidh |
| RebootCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh reboot | savaidh |
+---------------------+---------------------------------------------------------+----------+
7 rows in set (0.001 sec)

That shows the hostname=NULL commands, and the commands for two
different frontends (mypvr which is also the backend, and savaidh).
The BackendSartCommand and BackendStopCommand ones are the vital ones
for running mythtv-setup. If you are having trouble installing them,
it can be done from the mysql command line. Be aware that the update
command is dangerous - typos can destroy your database so it is best
to just cut and paste if you are not confident with the mysql command
line:

sudo mysql
use mythconverg;
update settings set data='sudo
/usr/local/bin/mythtv-systemctl-helper.sh start' where hostname is
NULL and value='BackendStartCommand';
update settings set data='sudo
/usr/local/bin/mythtv-systemctl-helper.sh stop' where hostname is NULL
and value='BackendStopCommand';
select * from settings where data like '%helper%' order by hostname;
quit

Note that my email client wraps lines - cut and paste the above into
an editor and unwrap the 'update' lines so that they are all on one
line before pasting them to a terminal. It will not work if the
command string between the single quotes is wrapped.

_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On 4/04/21 7:54 pm, Stephen Worthington wrote:
> On Sun, 4 Apr 2021 10:55:34 +1200, you wrote:
>
>> Ok ,I tried your scripts which don't appear to work correctly in this system
>>
>> While running htop in another workspace ,I can issue sudo
>> /home/mythtv/bin/mythtv-systemctl-helper.sh stop and sudo
>> /home/mythtv/bin/mythtv-systemctl-helper.sh start commands and observe
>> that the processes related to /usr/bin/mythtv disappear and reappear.
>>
>> If I start mythtv backend setup ,first I get a window asking to stop
>> myth backend ,I click yes, I get another window asking for the password
>> and I close it.
> If my scripts are installed correctly, you should not get a popup
> window asking for the password. So you need to check that the scripts
> are installed. Try doing this:
>
> sudo mysql
> use mythconverg;
> select * from settings where data like '%helper%' order by hostname;
> quit
>
> This is what I get:
>
> MariaDB [mythconverg]> select * from settings where data like
> '%helper%' order by hostname;
> +---------------------+---------------------------------------------------------+----------+
> | value | data | hostname |
> +---------------------+---------------------------------------------------------+----------+
> | ServerHaltCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh halt | NULL |
> | BackendStartCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh start | NULL |
> | BackendStopCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh stop | NULL |
> | HaltCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh poweroff | mypvr |
> | RebootCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh reboot | mypvr |
> | HaltCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh poweroff | savaidh |
> | RebootCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh reboot | savaidh |
> +---------------------+---------------------------------------------------------+----------+
> 7 rows in set (0.001 sec)
>
> That shows the hostname=NULL commands, and the commands for two
> different frontends (mypvr which is also the backend, and savaidh).
> The BackendSartCommand and BackendStopCommand ones are the vital ones
> for running mythtv-setup. If you are having trouble installing them,
> it can be done from the mysql command line. Be aware that the update
> command is dangerous - typos can destroy your database so it is best
> to just cut and paste if you are not confident with the mysql command
> line:
>
> sudo mysql
> use mythconverg;
> update settings set data='sudo
> /usr/local/bin/mythtv-systemctl-helper.sh start' where hostname is
> NULL and value='BackendStartCommand';
> update settings set data='sudo
> /usr/local/bin/mythtv-systemctl-helper.sh stop' where hostname is NULL
> and value='BackendStopCommand';
> select * from settings where data like '%helper%' order by hostname;
> quit
>
> Note that my email client wraps lines - cut and paste the above into
> an editor and unwrap the 'update' lines so that they are all on one
> line before pasting them to a terminal. It will not work if the
> command string between the single quotes is wrapped.
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz@lists.ourshack.com
> https://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

It looks like they installed correctly:

+---------------------+-----------------------------------------------------------+----------+
| value                 |
data                                                            | hostname |
+---------------------+-----------------------------------------------------------+----------+
| ServerHaltCommand   | sudo /home/mythtv/bin.systemctl-helper-sh
halt            | NULL     |
| BackendStopCommand  | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
stop     | NULL     |
| BackendStartCommand | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
start    | NULL     |
| HaltCommand         | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
poweroff | myth     |
| RebootCommand       | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
reboot   | myth     |
+---------------------+-----------------------------------------------------------+----------+
5 rows in set (0.01 sec)


_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On Mon, 5 Apr 2021 09:09:30 +1200, you wrote:

>
>On 4/04/21 7:54 pm, Stephen Worthington wrote:
>> On Sun, 4 Apr 2021 10:55:34 +1200, you wrote:
>>
>>> Ok ,I tried your scripts which don't appear to work correctly in this system
>>>
>>> While running htop in another workspace ,I can issue sudo
>>> /home/mythtv/bin/mythtv-systemctl-helper.sh stop and sudo
>>> /home/mythtv/bin/mythtv-systemctl-helper.sh start commands and observe
>>> that the processes related to /usr/bin/mythtv disappear and reappear.
>>>
>>> If I start mythtv backend setup ,first I get a window asking to stop
>>> myth backend ,I click yes, I get another window asking for the password
>>> and I close it.
>> If my scripts are installed correctly, you should not get a popup
>> window asking for the password. So you need to check that the scripts
>> are installed. Try doing this:
>>
>> sudo mysql
>> use mythconverg;
>> select * from settings where data like '%helper%' order by hostname;
>> quit
>>
>> This is what I get:
>>
>> MariaDB [mythconverg]> select * from settings where data like
>> '%helper%' order by hostname;
>> +---------------------+---------------------------------------------------------+----------+
>> | value | data | hostname |
>> +---------------------+---------------------------------------------------------+----------+
>> | ServerHaltCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh halt | NULL |
>> | BackendStartCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh start | NULL |
>> | BackendStopCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh stop | NULL |
>> | HaltCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh poweroff | mypvr |
>> | RebootCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh reboot | mypvr |
>> | HaltCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh poweroff | savaidh |
>> | RebootCommand | sudo /usr/local/bin/mythtv-systemctl-helper.sh reboot | savaidh |
>> +---------------------+---------------------------------------------------------+----------+
>> 7 rows in set (0.001 sec)
>>
>> That shows the hostname=NULL commands, and the commands for two
>> different frontends (mypvr which is also the backend, and savaidh).
>> The BackendSartCommand and BackendStopCommand ones are the vital ones
>> for running mythtv-setup. If you are having trouble installing them,
>> it can be done from the mysql command line. Be aware that the update
>> command is dangerous - typos can destroy your database so it is best
>> to just cut and paste if you are not confident with the mysql command
>> line:
>>
>> sudo mysql
>> use mythconverg;
>> update settings set data='sudo
>> /usr/local/bin/mythtv-systemctl-helper.sh start' where hostname is
>> NULL and value='BackendStartCommand';
>> update settings set data='sudo
>> /usr/local/bin/mythtv-systemctl-helper.sh stop' where hostname is NULL
>> and value='BackendStopCommand';
>> select * from settings where data like '%helper%' order by hostname;
>> quit
>>
>> Note that my email client wraps lines - cut and paste the above into
>> an editor and unwrap the 'update' lines so that they are all on one
>> line before pasting them to a terminal. It will not work if the
>> command string between the single quotes is wrapped.

>It looks like they installed correctly:
>
>+---------------------+-----------------------------------------------------------+----------+
>| value                 |
>data                                                            | hostname |
>+---------------------+-----------------------------------------------------------+----------+
>| ServerHaltCommand   | sudo /home/mythtv/bin.systemctl-helper-sh
>halt            | NULL     |
>| BackendStopCommand  | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
>stop     | NULL     |
>| BackendStartCommand | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
>start    | NULL     |
>| HaltCommand         | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
>poweroff | myth     |
>| RebootCommand       | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
>reboot   | myth     |
>+---------------------+-----------------------------------------------------------+----------+
>5 rows in set (0.01 sec)

No, there is a typo in all of them. Between "bin" and
"mythtv-systemctl-helper.sh" it should be a "/" not a ".".

And "ServerHaltCommand" also has "systemctl-helper-sh" instead of
"mythtv-systemctl-helper.sh" (missing "mythtv-" at the front and has
"-sh" instead of ".sh").

_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On 5/04/21 2:59 pm, Stephen Worthington wrote:
>
>> It looks like they installed correctly:
>>
>> +---------------------+-----------------------------------------------------------+----------+
>> | value                 |
>> data                                                            | hostname |
>> +---------------------+-----------------------------------------------------------+----------+
>> | ServerHaltCommand   | sudo /home/mythtv/bin.systemctl-helper-sh
>> halt            | NULL     |
>> | BackendStopCommand  | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
>> stop     | NULL     |
>> | BackendStartCommand | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
>> start    | NULL     |
>> | HaltCommand         | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
>> poweroff | myth     |
>> | RebootCommand       | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
>> reboot   | myth     |
>> +---------------------+-----------------------------------------------------------+----------+
>> 5 rows in set (0.01 sec)
> No, there is a typo in all of them. Between "bin" and
> "mythtv-systemctl-helper.sh" it should be a "/" not a ".".
>
> And "ServerHaltCommand" also has "systemctl-helper-sh" instead of
> "mythtv-systemctl-helper.sh" (missing "mythtv-" at the front and has
> "-sh" instead of ".sh").
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz@lists.ourshack.com
> https://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/


Oh , OK I saw that  in your post at:
https://lists.archive.carbon60.com/mythtv/users/625993
<https://lists.archive.carbon60.com/mythtv/users/625993> and thought it
looked wrong ,but I chose not to question the maestro as I'm not
experienced with mysql. I just copied and pasted the commands directly.

It might pay to correct that typo at
https://lists.archive.carbon60.com/mythtv/users/625993.

I chose to reinstall the OS and MCP yesterday. I haven't got around to
using MCP to install mythtv yet.

One question: I use ACPI wakeup and Mythwelcome. Will the changes in the
start and stop commands affect how ACPI wakeup and Mythwelcome function?

-Paul



_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On Tue, 6 Apr 2021 06:02:53 +1200, you wrote:

>
>On 5/04/21 2:59 pm, Stephen Worthington wrote:
>>
>>> It looks like they installed correctly:
>>>
>>> +---------------------+-----------------------------------------------------------+----------+
>>> | value                 |
>>> data                                                            | hostname |
>>> +---------------------+-----------------------------------------------------------+----------+
>>> | ServerHaltCommand   | sudo /home/mythtv/bin.systemctl-helper-sh
>>> halt            | NULL     |
>>> | BackendStopCommand  | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
>>> stop     | NULL     |
>>> | BackendStartCommand | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
>>> start    | NULL     |
>>> | HaltCommand         | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
>>> poweroff | myth     |
>>> | RebootCommand       | sudo /home/mythtv/bin.mythtv-systemctl-helper.sh
>>> reboot   | myth     |
>>> +---------------------+-----------------------------------------------------------+----------+
>>> 5 rows in set (0.01 sec)
>> No, there is a typo in all of them. Between "bin" and
>> "mythtv-systemctl-helper.sh" it should be a "/" not a ".".
>>
>> And "ServerHaltCommand" also has "systemctl-helper-sh" instead of
>> "mythtv-systemctl-helper.sh" (missing "mythtv-" at the front and has
>> "-sh" instead of ".sh").
>
>Oh , OK I saw that  in your post at:
>https://lists.archive.carbon60.com/mythtv/users/625993
><https://lists.archive.carbon60.com/mythtv/users/625993> and thought it
>looked wrong ,but I chose not to question the maestro as I'm not
>experienced with mysql. I just copied and pasted the commands directly.
>
>It might pay to correct that typo at
>https://lists.archive.carbon60.com/mythtv/users/625993.

Ouch! Sorry about that. I have posted a follow up message.

>I chose to reinstall the OS and MCP yesterday. I haven't got around to
>using MCP to install mythtv yet.
>
>One question: I use ACPI wakeup and Mythwelcome. Will the changes in the
>start and stop commands affect how ACPI wakeup and Mythwelcome function?
>
>-Paul

I have never used ACPI wakeup and Mythwelcome, so I do not know what
effect the above commands have on it. I would have thought that
having to type in a password would have made the ACPI code
non-functional and my helper scripts might make it work again, but I
do not actually know if the ACPI code uses those settings or has some
other way of doing shutdowns.

_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
> Ouch! Sorry about that. I have posted a follow up message.
>
>> I chose to reinstall the OS and MCP yesterday. I haven't got around to
>> using MCP to install mythtv yet.
>>
>> One question: I use ACPI wakeup and Mythwelcome. Will the changes in the
>> start and stop commands affect how ACPI wakeup and Mythwelcome function?
>>
>> -Paul
> I have never used ACPI wakeup and Mythwelcome, so I do not know what
> effect the above commands have on it. I would have thought that
> having to type in a password would have made the ACPI code
> non-functional and my helper scripts might make it work again, but I
> do not actually know if the ACPI code uses those settings or has some
> other way of doing shutdowns.
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz@lists.ourshack.com
> https://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

I installed your helper scripts and it is looking good but with a couple
of idiosyncrasies.

I was running htop on a second workspace to monitor the stopping and
starting of the backend.

When I start myth backend setup  a small dialogue opens stating that
myth backend needs to be closed > selecting 'Yes' results in a mythtv
dialogue asking for a password - which won't accept the sudo password or
any password in the known universe. NB there are two users: the Xubuntu
user called myth and mythtv , I don't know if that is enlightening.

The password dialogue is despatched into the land of wind and ghosts
with a simple esc keystroke or clicking 'X' or "Cancel"

A terminal window shows myth backend setup starting.

Myth backend setup opens and states the backend is running and htop
confirms this > selecting 'stop backend' closes the message box and
,after 10 seconds,myth backend setup is ready for use.

Exiting myth backend setup results in the GUI closing , A terminal
window shows myth backend  starting, a mythtv dialogue asking for a
password appears which is  closed with an "esc" . A dialogue opens
asking if I want to run mythfilldatabase.

htop confirms myth backend is running.

When the helper script commands had the error (typo) the 10 second delay
was where the Myth backend setup would hang indefinitely.

Except for the irrelevant password requests it seems to be behaving
pretty much the same as my existing Mythbuntu 16.04 installation.


> mysql> select * from settings where data like '%helper%' order by hostname;
> +---------------------+-----------------------------------------------------------+-------------+
> | value | data | hostname |
> +---------------------+-----------------------------------------------------------+-------------+
> | ServerHaltCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh halt | NULL |
> | BackendStopCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh stop | NULL |
> | BackendStartCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh start | NULL |
> | HaltCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh poweroff | myth-system |
> | RebootCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh reboot | myth-system |
> +---------------------+-----------------------------------------------------------+-------------+
> 5 rows in set (0.00 sec)
>
Set up will continue over following days.

Thanks

Paul


_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On Wed, 7 Apr 2021 15:31:30 +1200, you wrote:

>I installed your helper scripts and it is looking good but with a couple
>of idiosyncrasies.
>
>I was running htop on a second workspace to monitor the stopping and
>starting of the backend.
>
>When I start myth backend setup  a small dialogue opens stating that
>myth backend needs to be closed > selecting 'Yes' results in a mythtv
>dialogue asking for a password - which won't accept the sudo password or
>any password in the known universe. NB there are two users: the Xubuntu
>user called myth and mythtv , I don't know if that is enlightening.

There should not be a password request here. The question about
shutting down mythbackend is new in v31 I think, and will always be
there, but after that there should not be any further dialogs - the
helper script should be run and mythbackend should shut down.

However, shutting down mythbackend has a complication. When MythTV
programs such as mythbackend or mythfrontend are requested to shut
down externally, there is a bug in the MythTV codebase that happens.
The request to shut down is a "kill -15" aka "kill -SIGTERM". When
MythTV code receives one of these signals, it mostly shuts down except
for one final thread, which keeps on running. Sending a second "kill
-15" shortly after the first one will shut down this final thread. The
systemd .service file for mythbackend (mythtv-backend.service) does
not know about this problem as installed from the packages. It only
sends one "kill -15" and then waits for mythbackend to stop - and
keeps on waiting and waiting and when it finally times out (90?
seconds later), it does a kill -9 on mythbackend which then kills off
the last thread. The kill -9 happening does no damage as mythbackend
is no longer doing anything, just waiting in that final thread. But
that long timeout will be affecting you as mythbackend will still be
running when mythtv-setup starts. So I think you need to install my
fix for this problem:

https://lists.archive.carbon60.com/mythtv/users/627999
(search that page for "mythbackendstop.sh")

Installing this fix will not fix the problem of a password dialog
popping up - that should not be happening with my helper scripts in
place.

>The password dialogue is despatched into the land of wind and ghosts
>with a simple esc keystroke or clicking 'X' or "Cancel"
>
>A terminal window shows myth backend setup starting.
>
>Myth backend setup opens and states the backend is running and htop
>confirms this > selecting 'stop backend' closes the message box and
>,after 10 seconds,myth backend setup is ready for use.
>
>Exiting myth backend setup results in the GUI closing , A terminal
>window shows myth backend  starting, a mythtv dialogue asking for a
>password appears which is  closed with an "esc" . A dialogue opens
>asking if I want to run mythfilldatabase.

I am afraid I just do not understand where that password dialog is
coming from, unless the sudoers setup is not correct. Check that
setup by doing these commands:

ll /etc/sudoers.d/mythtv-systemctl-helper
cat /etc/sudoers.d/mythtv-systemctl-helper

This is what I get:

root@mypvr:/usr/local/bin# ll /etc/sudoers.d/mythtv-systemctl-helper
-r--r----- 1 root root 70 Jun 7 2020
/etc/sudoers.d/mythtv-systemctl-helper
root@mypvr:/usr/local/bin# cat /etc/sudoers.d/mythtv-systemctl-helper
mythtv,%mythtv ALL=NOPASSWD:/usr/local/bin/mythtv-systemctl-helper.sh

If the sudoers setup was wrong, dismissing the password dialog should
result in the helper script never being run, so mythbackend would just
keep on running.

>htop confirms myth backend is running.
>
>When the helper script commands had the error (typo) the 10 second delay
>was where the Myth backend setup would hang indefinitely.
>
>Except for the irrelevant password requests it seems to be behaving
>pretty much the same as my existing Mythbuntu 16.04 installation.
>
>
>> mysql> select * from settings where data like '%helper%' order by hostname;
>> +---------------------+-----------------------------------------------------------+-------------+
>> | value | data | hostname |
>> +---------------------+-----------------------------------------------------------+-------------+
>> | ServerHaltCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh halt | NULL |
>> | BackendStopCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh stop | NULL |
>> | BackendStartCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh start | NULL |
>> | HaltCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh poweroff | myth-system |
>> | RebootCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh reboot | myth-system |
>> +---------------------+-----------------------------------------------------------+-------------+
>> 5 rows in set (0.00 sec)

That all looks right.

>Set up will continue over following days.
>
>Thanks
>
>Paul

BTW The same shutdown bug happens in mythfrontend, so I have a script
that sends it two "kill -15" that I use to shut it down when it
freezes on a bug or otherwise. Running "killm" will kill only
"mythfrontend.real" and the mythfrontend script will then restart it.
Running "killm x" (any parameter value) will kill the "mythfrontend"
script and then kill "mythfrontend.real", so it will not restart.

To install killm on Ubuntu run this:

sudo su
cd /usr/local/bin
wget http://www.jsw.gen.nz/mythtv/killm
chown root:root killm
chmod u=rwx,og=rx killm
exit

_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On 7/04/21 10:10 pm, Stephen Worthington wrote:
> On Wed, 7 Apr 2021 15:31:30 +1200, you wrote:
>
>> I installed your helper scripts and it is looking good but with a couple
>> of idiosyncrasies.
>>
>> I was running htop on a second workspace to monitor the stopping and
>> starting of the backend.
>>
>> When I start myth backend setup  a small dialogue opens stating that
>> myth backend needs to be closed > selecting 'Yes' results in a mythtv
>> dialogue asking for a password - which won't accept the sudo password or
>> any password in the known universe. NB there are two users: the Xubuntu
>> user called myth and mythtv , I don't know if that is enlightening.
> There should not be a password request here. The question about
> shutting down mythbackend is new in v31 I think, and will always be
> there, but after that there should not be any further dialogs - the
> helper script should be run and mythbackend should shut down.
>
> However, shutting down mythbackend has a complication. When MythTV
> programs such as mythbackend or mythfrontend are requested to shut
> down externally, there is a bug in the MythTV codebase that happens.
> The request to shut down is a "kill -15" aka "kill -SIGTERM". When
> MythTV code receives one of these signals, it mostly shuts down except
> for one final thread, which keeps on running. Sending a second "kill
> -15" shortly after the first one will shut down this final thread. The
> systemd .service file for mythbackend (mythtv-backend.service) does
> not know about this problem as installed from the packages. It only
> sends one "kill -15" and then waits for mythbackend to stop - and
> keeps on waiting and waiting and when it finally times out (90?
> seconds later), it does a kill -9 on mythbackend which then kills off
> the last thread. The kill -9 happening does no damage as mythbackend
> is no longer doing anything, just waiting in that final thread. But
> that long timeout will be affecting you as mythbackend will still be
> running when mythtv-setup starts. So I think you need to install my
> fix for this problem:
>
> https://lists.archive.carbon60.com/mythtv/users/627999
> (search that page for "mythbackendstop.sh")
>
> Installing this fix will not fix the problem of a password dialog
> popping up - that should not be happening with my helper scripts in
> place.
>
>> The password dialogue is despatched into the land of wind and ghosts
>> with a simple esc keystroke or clicking 'X' or "Cancel"
>>
>> A terminal window shows myth backend setup starting.
>>
>> Myth backend setup opens and states the backend is running and htop
>> confirms this > selecting 'stop backend' closes the message box and
>> ,after 10 seconds,myth backend setup is ready for use.
>>
>> Exiting myth backend setup results in the GUI closing , A terminal
>> window shows myth backend  starting, a mythtv dialogue asking for a
>> password appears which is  closed with an "esc" . A dialogue opens
>> asking if I want to run mythfilldatabase.
> I am afraid I just do not understand where that password dialog is
> coming from, unless the sudoers setup is not correct. Check that
> setup by doing these commands:
>
> ll /etc/sudoers.d/mythtv-systemctl-helper
> cat /etc/sudoers.d/mythtv-systemctl-helper
>
> This is what I get:
>
> root@mypvr:/usr/local/bin# ll /etc/sudoers.d/mythtv-systemctl-helper
> -r--r----- 1 root root 70 Jun 7 2020
> /etc/sudoers.d/mythtv-systemctl-helper
> root@mypvr:/usr/local/bin# cat /etc/sudoers.d/mythtv-systemctl-helper
> mythtv,%mythtv ALL=NOPASSWD:/usr/local/bin/mythtv-systemctl-helper.sh
>
> If the sudoers setup was wrong, dismissing the password dialog should
> result in the helper script never being run, so mythbackend would just
> keep on running.
>
>> htop confirms myth backend is running.
>>
>> When the helper script commands had the error (typo) the 10 second delay
>> was where the Myth backend setup would hang indefinitely.
>>
>> Except for the irrelevant password requests it seems to be behaving
>> pretty much the same as my existing Mythbuntu 16.04 installation.
>>
>>
>>> mysql> select * from settings where data like '%helper%' order by hostname;
>>> +---------------------+-----------------------------------------------------------+-------------+
>>> | value | data | hostname |
>>> +---------------------+-----------------------------------------------------------+-------------+
>>> | ServerHaltCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh halt | NULL |
>>> | BackendStopCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh stop | NULL |
>>> | BackendStartCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh start | NULL |
>>> | HaltCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh poweroff | myth-system |
>>> | RebootCommand | sudo /home/mythtv/bin/mythtv-systemctl-helper.sh reboot | myth-system |
>>> +---------------------+-----------------------------------------------------------+-------------+
>>> 5 rows in set (0.00 sec)
> That all looks right.
>
>> Set up will continue over following days.
>>
>> Thanks
>>
>> Paul
> BTW The same shutdown bug happens in mythfrontend, so I have a script
> that sends it two "kill -15" that I use to shut it down when it
> freezes on a bug or otherwise. Running "killm" will kill only
> "mythfrontend.real" and the mythfrontend script will then restart it.
> Running "killm x" (any parameter value) will kill the "mythfrontend"
> script and then kill "mythfrontend.real", so it will not restart.
>
> To install killm on Ubuntu run this:
>
> sudo su
> cd /usr/local/bin
> wget http://www.jsw.gen.nz/mythtv/killm
> chown root:root killm
> chmod u=rwx,og=rx killm
> exit
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz@lists.ourshack.com
> https://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

I'll check the sudoers.d helper and make the other changes regarding the
shutdown bug .

One thing I wondered about regarding the helper script was ,in your
installation procedure ,for the helper script in /mythtv/bin you issue:
chmod ug=rx,o= mythtv-systemctl-helper.sh  command and for the one in
/etc/sudoers.d you use: chmod ug=r,o= mythtv-systemctl-helper  without x
to make executable. Was this intentional? or a typo?

I'll be busy for the following 2 days and be  making the changes on
Saturday.

-Paul



_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On Thu, 8 Apr 2021 04:39:05 +1200, you wrote:


>I'll check the sudoers.d helper and make the other changes regarding the
>shutdown bug .
>
>One thing I wondered about regarding the helper script was ,in your
>installation procedure ,for the helper script in /mythtv/bin you issue:
>chmod ug=rx,o= mythtv-systemctl-helper.sh  command and for the one in
>/etc/sudoers.d you use: chmod ug=r,o= mythtv-systemctl-helper  without x
>to make executable. Was this intentional? or a typo?

The helper script is a bash script, so it must have executable
permissions. It is not particularly security sensitive as its ability
to do things without a password is not in this file but in the sudoers
config file referring to it. Using it only makes sense in the context
of using it with an sudoers configuration that allows it to work
without needing a password. In any other situation where you do need
to use a password, it is normally simpler just to use the systemctl
commands directly.

The sudoers file is not executable, it is a configuration file, and a
very security sensitive one at that. The permissions on sudoers files
have to be exactly right or sudo will ignore them, as if they have the
wrong permissions that would allow someone to easily get root access.
The recommendation for sudoers files is that they have no more than
read access for the user and group and nothing else, and be only root
ownership and root group. So even root can not write them without
changing their permissions first. When you do an sudo command from
other than a root account, sudo will be run as root and will look up
its sudoers config files to see if it has permission to do what it is
being asked to do. So it will be reading those sudoers config files
as root:root. If it does not find a match in the sudoers file, it
will not execute the command (at all, and certainly not as root). If
it does find a match, it sees what permissions it has been given to
execute things. In this case the config says it can execute the
specified file without requesting a password, so that is what it does.
When you do a normal sudo command from your non-root account, sudo
will match that against this config found in /etc/sudoers:

# Allow members of group sudo to execute any command
%sudo ALL=(ALL:ALL) ALL

That says that sudo is allowed to execute any command as root if the
account is a member of the sudo group, but as there is not a NOPASSWD
option, it has to ask for a password first. The login account that
gets set up when you install Ubuntu is automatically added to the sudo
group (and the admin group that is allowed to use su to switch to the
root account).

>I'll be busy for the following 2 days and be  making the changes on
>Saturday.
>
>-Paul

_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On 8/04/21 6:24 am, Stephen Worthington wrote:
> On Thu, 8 Apr 2021 04:39:05 +1200, you wrote:
>
>
>> I'll check the sudoers.d helper and make the other changes regarding the
>> shutdown bug .
>>
>> One thing I wondered about regarding the helper script was ,in your
>> installation procedure ,for the helper script in /mythtv/bin you issue:
>> chmod ug=rx,o= mythtv-systemctl-helper.sh  command and for the one in
>> /etc/sudoers.d you use: chmod ug=r,o= mythtv-systemctl-helper  without x
>> to make executable. Was this intentional? or a typo?
> The helper script is a bash script, so it must have executable
> permissions. It is not particularly security sensitive as its ability
> to do things without a password is not in this file but in the sudoers
> config file referring to it. Using it only makes sense in the context
> of using it with an sudoers configuration that allows it to work
> without needing a password. In any other situation where you do need
> to use a password, it is normally simpler just to use the systemctl
> commands directly.
>
> The sudoers file is not executable, it is a configuration file, and a
> very security sensitive one at that. The permissions on sudoers files
> have to be exactly right or sudo will ignore them, as if they have the
> wrong permissions that would allow someone to easily get root access.
> The recommendation for sudoers files is that they have no more than
> read access for the user and group and nothing else, and be only root
> ownership and root group. So even root can not write them without
> changing their permissions first. When you do an sudo command from
> other than a root account, sudo will be run as root and will look up
> its sudoers config files to see if it has permission to do what it is
> being asked to do. So it will be reading those sudoers config files
> as root:root. If it does not find a match in the sudoers file, it
> will not execute the command (at all, and certainly not as root). If
> it does find a match, it sees what permissions it has been given to
> execute things. In this case the config says it can execute the
> specified file without requesting a password, so that is what it does.
> When you do a normal sudo command from your non-root account, sudo
> will match that against this config found in /etc/sudoers:
>
> # Allow members of group sudo to execute any command
> %sudo ALL=(ALL:ALL) ALL
>
> That says that sudo is allowed to execute any command as root if the
> account is a member of the sudo group, but as there is not a NOPASSWD
> option, it has to ask for a password first. The login account that
> gets set up when you install Ubuntu is automatically added to the sudo
> group (and the admin group that is allowed to use su to switch to the
> root account).
>
>> I'll be busy for the following 2 days and be  making the changes on
>> Saturday.
>>
>> -Paul
> _______________________________________________
> mythtvnz mailing list
> mythtvnz@lists.ourshack.com
> https://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/


Hi Stephen et al

I'm back setting up the new 20.04 MythTV system.

Can you point me to the best guides to set up systemd to wait for HDHR
and for Haupauge tuners to load before starting Mythbackend?

There is a lot of information out there (in the list) but I don't know
which is the most concise.

Thanks

Paul


_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On Sat, 3 Jul 2021 14:34:57 +1200, you wrote:

>Hi Stephen et al
>
>I'm back setting up the new 20.04 MythTV system.
>
>Can you point me to the best guides to set up systemd to wait for HDHR
>and for Haupauge tuners to load before starting Mythbackend?
>
>There is a lot of information out there (in the list) but I don't know
>which is the most concise.
>
>Thanks
>
>Paul

Presuming that the Hauppauge tuners are normal DVB ones, then to wait
for them you need to install this file:

root@mypvr:/etc/udev/rules.d# cat 99-tuner.rules
#
# Create systemd device units for capture devices
#
SUBSYSTEM=="video4linux", TAG+="systemd"
SUBSYSTEM=="dvb", TAG+="systemd"
SUBSYSTEM=="firewire", TAG+="systemd"

It should be chown root:root and chmod u=rw,og=r.

What that does is get udev to create a systemd unit for each tuner
when the tuner becomes available. Then you do:

sudo systemctl edit mythtv-backend

and add lines like these, one pair for each tuner, in the [Unit]
section:

[Unit]
Wants=dev-dvb-adapter0-frontend0.device
After=dev-dvb-adapter0-frontend0.device
Wants=dev-dvb-adapter1-frontend0.device
After=dev-dvb-adapter1-frontend0.device

Details of my fix to make mythbackend wait for network tuners to be
available are on this thread:

https://lists.archive.carbon60.com/mythtv/users/625992

_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On 4/07/21 3:41 am, Stephen Worthington wrote:
> On Sat, 3 Jul 2021 14:34:57 +1200, you wrote:
>
>> Hi Stephen et al
>>
>> I'm back setting up the new 20.04 MythTV system.
>>
>> Can you point me to the best guides to set up systemd to wait for HDHR
>> and for Haupauge tuners to load before starting Mythbackend?
>>
>> There is a lot of information out there (in the list) but I don't know
>> which is the most concise.
>>
>> Thanks
>>
>> Paul
> Presuming that the Hauppauge tuners are normal DVB ones, then to wait
> for them you need to install this file:
>
> root@mypvr:/etc/udev/rules.d# cat 99-tuner.rules
> #
> # Create systemd device units for capture devices
> #
> SUBSYSTEM=="video4linux", TAG+="systemd"
> SUBSYSTEM=="dvb", TAG+="systemd"
> SUBSYSTEM=="firewire", TAG+="systemd"
>
> It should be chown root:root and chmod u=rw,og=r.
>
> What that does is get udev to create a systemd unit for each tuner
> when the tuner becomes available. Then you do:
>
> sudo systemctl edit mythtv-backend
>
> and add lines like these, one pair for each tuner, in the [Unit]
> section:
>
> [Unit]
> Wants=dev-dvb-adapter0-frontend0.device
> After=dev-dvb-adapter0-frontend0.device
> Wants=dev-dvb-adapter1-frontend0.device
> After=dev-dvb-adapter1-frontend0.device
>
> Details of my fix to make mythbackend wait for network tuners to be
> available are on this thread:
>
> https://lists.archive.carbon60.com/mythtv/users/625992
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz@lists.ourshack.com
> https://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

Thanks Stephen

Yes, it's a dual tuner HVR2200 DVB-T

Pretty much word for word from my notes from 2017

I just wanted to make sure there had not been any changes to the best
set up.

Cheers

Paul


_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On Sat, 3 Jul 2021, at 12:34 PM, Paul wrote:
> Can you point me to the best guides to set up systemd to wait for HDHR
> and for Haupauge tuners to load before starting Mythbackend?

I also have the Hauppauge dualHD (usb id 2040:0265), and both tuners worked out of the box in Ubuntu 20.04 LTS. Before that you needed to use a Hauppauge kernel to access the second tuner.

--
Simon

_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: New install - mythbackend password not accepted [ In reply to ]
On 4/07/21 12:22 pm, Simon Green wrote:
> On Sat, 3 Jul 2021, at 12:34 PM, Paul wrote:
>> Can you point me to the best guides to set up systemd to wait for HDHR
>> and for Haupauge tuners to load before starting Mythbackend?
> I also have the Hauppauge dualHD (usb id 2040:0265), and both tuners worked out of the box in Ubuntu 20.04 LTS. Before that you needed to use a Hauppauge kernel to access the second tuner.
>
Yes I found a reference that says the newer Haupauge tuners have drivers
available in a PPA as well.

Mine is a HVR2200 and I think it still requires the driver to be
installed manually.

Paul


_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/