Mailing List Archive

Hoi Barry,

Saturday, June 20, 2020, 10:50:22 PM, you wrote:

> Hi Folks!

> Got a new router and so all of my LAN addresses had to
> be changed from 192.168.0.x to 192.168.4.x. Was able to change
> the static address of my Backend (Ubuntu 18.04, MythTV v. 30,
> MariaDB. Changed the config.xml to the new address
> without problem, and can access the machine via the webpage
> (192.168.4.3:6544). The problem is the database won’t stay
> updated. Takes at least five minutes to get to the GUI (even using
> mythtv-setup.real), I can change the database address to the
> desired 192.168.4.3, save and close. Run mythfilldatabase and
> it gives errors and as it’s already looking at the old 192.168.0.3 address.
>
> (Stephen Worthington: I did update your routine to look to
> ascertain the network was up.)
>
> Subquestion: A while back there was a thread to post to
> the website and not this e-mailed forum. What’s the
> site?? I found the Gossamer Threads repost but not the original. Thanks!
>

>
>
> TIA
>
> Barry
>

Why didn't you change your new router to your old subnet?



Tot mails,
Hika mailto:hikavdh@gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sat, 20 Jun 2020 15:50:22 -0500, you wrote:

>Hi Folks!
>
>Got a new router and so all of my LAN addresses had to be changed from
>192.168.0.x to 192.168.4.x. Was able to change the static address of my
>Backend (Ubuntu 18.04, MythTV v. 30, MariaDB. Changed the config.xml to
>the new address without problem, and can access the machine via the
>webpage (192.168.4.3:6544). The problem is the database won?t stay
>updated. Takes at least five minutes to get to the GUI (even using
>mythtv-setup.real), I can change the database address to the desired
>192.168.4.3, save and close. Run mythfilldatabase and it gives errors
>and as it?s already looking at the old 192.168.0.3 address.
>
>(Stephen Worthington: I did update your routine to look to ascertain the
>network was up.)
>
>Subquestion: A while back there was a thread to post to the website and
>not this e-mailed forum. What?s the site?? I found the Gossamer Threads
>repost but not the original. Thanks!
>
>
>TIA
>
>Barry

Check all the settings in your database for the old IP address:

sudo su
mysql
use mythconverg;
select * from settings where data like '%192.168.%';
exit
exit

That should tell you if there is one you missed. I get this on my
MythTV box:

MariaDB [mythconverg]> select * from settings where data like '%10.%';
+-------------------+----------+----------+
| value | data | hostname |
+-------------------+----------+----------+
| MasterServerIP | 10.0.2.4 | NULL |
| BackendServerIP | 10.0.2.4 | mypvr |
| BackendServerAddr | 10.0.2.4 | mypvr |
+-------------------+----------+----------+
3 rows in set (0.00 sec)


Then check all the different config.xml files:

/etc/mythtv/config.xml
/home/mythtv/.mythtv/config.xml
/home/<mythfrontend user>/.mythtv/config.xml

It can also be a good idea to check all settings in /etc for the old
IP address, such as /etc/hosts:

sudo su
cd /etc
grep -r "192.168." *
exit

The MythTV forums are here:

https://forum.mythtv.org
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

> Why didn't you change your new router to your old subnet?

Hi Hika!

That was my first hope and preference! I did call tech support for the
fiber optic service and chatted with the gentleman who said he was the
one who brought that particular router over to this company when he was
hired. (So apparently he knows his stuff.) He did close to an hour with
me trying to figure a few options.

Barry

Hoi Barry,

Sunday, June 21, 2020, 6:45:41 PM, you wrote:



>
> Why didn't you change your new router to your old subnet?

>
>
> Hi Hika!
>
> That was my first hope and preference! I did call tech
> support for the fiber optic service and chatted with the
> gentleman who said he was the one who brought that particular
> router over to this company when he was hired. (So apparently
> he knows his stuff.) He did close to an hour with me trying to figure a few options.
>
> Barry
>

You can always but a simple basic extra router between the new router
and your network.
Anyway any router with a subnet range hard set or blocked from
setting by your provider is not worth having.


Tot mails,
Hika mailto:hikavdh@gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Hoi Hika,

Sunday, June 21, 2020, 6:58:50 PM, you wrote:

> Hoi Barry,

> Sunday, June 21, 2020, 6:45:41 PM, you wrote:



>>
>> Why didn't you change your new router to your old subnet?

>>
>>
>> Hi Hika!
>>
>> That was my first hope and preference! I did call tech
>> support for the fiber optic service and chatted with the
>> gentleman who said he was the one who brought that particular
>> router over to this company when he was hired. (So apparently
>> he knows his stuff.) He did close to an hour with me trying to figure a few options.
>>
>> Barry
>>

> You can always but a simple basic extra router between the new router
> and your network.
> Anyway any router with a subnet range hard set or blocked from
> setting by your provider is not worth having.


I once for reasons I forgot, changed my subnet and even years later
on occasion remnants from my old subnet popped up somewhere.


Tot mails,
Hika mailto:hikavdh@gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Hi Stephen!


Thanks for coming to my rescue again!


> sudo su
> mysql
> use mythconverg;
> select * from settings where data like '%192.168.%';
> exit
> exit

Here got:

+-------------------+------------------------------------------+-----------+

| value |  data                                  + hostname  |

+-------------------+------------------------------------------+-----------+

| BackendServerAddr | 192.168.0.3 | backend-3 |

| EventCmdAll | mythsgu event -h 192.168.0.4 %EVENTNAME% | backend-3 |

+-------------------+------------------------------------------+-----------+

2 rows in set (0.04 sec)


MariaDB [mythconverg]>


- - -


> Then check all the different config.xml files:

/etc/mythtv/config.xml ==> localhost
//home/mythtv//.mythtv/config.xml ==> localhost
//home//<mythfrontend user>/.mythtv/config.xml ==> u = barry ==>
192.168.4.3


- - -

> It can also be a good idea to check all settings in /etc for the old
> IP address, such as /etc/hosts:
>
> sudo su
> cd /etc
> grep -r "192.168." *
> exit

4^th line down – bolded in my draft – is a backup copy. Appears to be
the only instance of the old IP, though habe no idea why some other
networks are in there (the new LAN is 192.168.4.x)


root@Backend-3:/etc# grep -r "192.168.*"

NetworkManager/system-connections/Static
IP:address1=192.168.4.3/24,192.168.4.1

NetworkManager/system-connections/Static IP:dns=192.168.4.1;8.8.8.8;

*mythtv/config.xml_original: <Host>192.168.0.3</Host>*

cups/cups-browsed.conf:# BrowseAllow 192.168.1.12

cups/cups-browsed.conf:# BrowseAllow 192.168.1.0/24

cups/cups-browsed.conf:# BrowseAllow 192.168.1.0/255.255.255.0

cups/cups-browsed.conf:# BrowseDeny 192.168.1.13

cups/cups-browsed.conf:# BrowseDeny 192.168.3.0/24

cups/cups-browsed.conf:# BrowseDeny 192.168.3.0/255.255.255.0

ppp/options:# ms-dns 192.168.1.1

ppp/options:# ms-dns 192.168.1.2

ppp/options:# ms-wins 192.168.1.50

ppp/options:# ms-wins 192.168.1.51

security/access.conf:#+ : root : 192.168.200.1 192.168.200.4 192.168.200.9

security/access.conf:# User "root" should get access from network
192.168.201.

security/access.conf:# The same is 192.168.201.0/24 or
192.168.201.0/255.255.255.0

security/access.conf:#+ : root : 192.168.201.

ntp.conf:#restrict 192.168.123.0 mask 255.255.255.0 notrust

ntp.conf:#broadcast 192.168.123.255

fstab://192.168.0.120/Backups/Backend_3 /media/NSA320_BE_3 cifs
username=Barry,password=B********6,iocharset=utf8,gid=1000,uid=1000,file_mode=0777,dirmode=0777,vers=1.00
0

avahi/hosts:# 192.168.0.1 router.local

avahi/avahi-daemon.conf:#publish-dns-servers=192.168.50.1, 192.168.50.2

sane.d/dell1600n_net.conf:#named_scanner: 192.168.0.20

sane.d/magicolor.conf:# net 192.168.0.1

sane.d/saned.conf:#192.168.0.1

sane.d/saned.conf:#192.168.0.1/29

sane.d/epson2.conf:# net 192.168.1.123

sane.d/epsonds.conf:# net 192.168.1.123

sane.d/kodakaio.conf:#net 192.168.1.2 0x4041

sane.d/kodakaio.conf:#net 192.168.1.17 0x4067

fwupd/redfish.conf:# ex: https://192.168.0.133:443

systemd/system/local-network-pingable.service:ExecStartPre=/bin/bash -c
"/usr/lo

ffserver.conf:ACL allow 192.168.0.0 192.168.255.255

dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes:#
new_rfc3442_classless_static_routes='24 192 168 10 192 168 1 1 8 10 10
17 66 41'

dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes:# 192.168.10.0/24
via 192.168.1.1

root@Backend-3:/etc#



Visually scanned that list -- not sure what some of it is though looks
like with the power failure I had this morning some of the devices
automatically updated to the new network. Tried a grep command to make
sure only the one old (192.168.0.3) noted during the visual scan:


root@Backend-3:/etc# grep -r "192.168.*" | grep 192.168.0.3

mythtv/config.xml_original: <Host>192.168.0.3</Host>


Half-thinking to delete or otherwise modify that file -- my old MS-DOS
8.3 days is kicking in: filenames were a max of eight characters, dot,
max. of three characters. Decided to post and await instructions!


TIA

Barry

On 6/21/20 12:42 PM, Barry Martin wrote:
>
>> Then check all the different config.xml files:
>
> /etc/mythtv/config.xml ==> localhost
> //home/mythtv//.mythtv/config.xml ==> localhost
> //home//<mythfrontend user>/.mythtv/config.xml ==> u = barry ==> 192.168.4.3

https://forum.mythtv.org/viewtopic.php?f=36&t=3871&p=18787#p18787

From the discussion on the Forum, this allowed DB access:

mysql --user=mythtv --password --host=<your DB IP or hostname> mythconverg

Retry with: --host=localhost if the IP address was used please.

The above shows a broken link (~/.mythtv/config.xml is different from
~mythtv/.mythtv/config.xml.) localhost is the proper value for a backend
<Assuming> that the DB is on the same host. Won't fix this issue, but
prevents a future one.

Remove ~/.mythtv/config.xml and link it to the one in /etc:

ln -s /etc/mythtv/config.xml ~/.mythtv/config.xml

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Hi Bill!


> mysql --user=mythtv --password --host=<your DB IP or hostname> mythconverg
>
> Retry with: --host=localhost if the IP address was used please.

(1) First command line’s results:


barry@Backend-3:~$ mysql --user=mythtv --password --host=192.168.4.3
mythconverg

Enter password:

ERROR 1045 (28000): Access denied for user 'mythtv'@'192.168.4.3' (using
password: YES)

barry@Backend-3:~$


I'll assume "password: Yes" means it is being used as it asked for it.



(1a) OK, maybe stupidly put in the address the database seems to think
it wants: (The original IP)


barry@Backend-3:~$ mysql --user=mythtv --password --host=192.168.0.3
mythconverg

Enter password:


Eventually timed out.



(2) The second “Retry” command line result:

barry@Backend-3:~$ mysql --user=mythtv --password --host=localhost
mythconverg

Enter password:

Reading table information for completion of table and column names

You can turn off this feature to get a quicker startup with -A


Welcome to the MariaDB monitor. Commands end with ; or \g.

Your MariaDB connection id is 1356

Server version: 10.1.44-MariaDB-0ubuntu0.18.04.1 Ubuntu 18.04


Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.


Type 'help;' or '\h' for help. Type '\c' to clear the current input
statement.


MariaDB [mythconverg]>



OK, that looks semi-promising. Typed 'exit' as I no instructions on what
to do next. Well, while I’m in the database; I do have this to do:


> Remove ~/.mythtv/config.xml and link it to the one in /etc:
>
> ln -s /etc/mythtv/config.xml ~/.mythtv/config.xml

Checked and “etc’s” has host=localhost. (Just verifying before doing!
Not that I don’t trust but want to make sure we’re not accidentally
creating a bigger problem.)


ls ~/.mythtv/config.xml ==> now is light blue on black, so must be the
“I’m a link” colour. cat /home/barry/.mythtv/config.xml looks good.


Thanks!

Barry

On 6/21/20 7:03 PM, Barry Martin wrote:

...

> (2) The second “Retry” command line result:
>
> barry@Backend-3:~$ mysql --user=mythtv --password --host=localhost mythconverg
>
> Enter password:

...

> Welcome to the MariaDB monitor. Commands end with ; or \g.

...

> OK, that looks semi-promising. Typed 'exit' as I no instructions on what to do next. Well, while I’m in the database; I do have this to do:

That command used the credentials from config.xml and works OK.

You should now be able to run mythtv-setup. Or at least proceed to the
next problem.

>> Remove ~/.mythtv/config.xml and link it to the one in /etc:
>>
>>     ln -s /etc/mythtv/config.xml ~/.mythtv/config.xml
>
> Checked and “etc’s” has host=localhost. (Just verifying before doing! Not that I don’t trust but want to make sure we’re not accidentally
> creating a bigger problem.)
>
>
> ls ~/.mythtv/config.xml ==> now is light blue on black, so must be the “I’m a link” colour. cat /home/barry/.mythtv/config.xml looks good.

Good. ls -l ~/.mythtv/config.xml will show a leading 'l', which means
link plus the file it links to.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Hi Bill!


Did a quick test first. Remembered Stephen had me do this:

sudo su
mysql
use mythconverg;
select * from settings where data like '%192.168.%';
exit
exit


Got the same results as before:

+-------------------+------------------------------------------+-----------+

| value |  data + hostname  |

+-------------------+------------------------------------------+-----------+

| BackendServerAddr | 192.168.0.3 | backend-3 |

| EventCmdAll | mythsgu event -h 192.168.0.4 %EVENTNAME% | backend-3 |

+-------------------+------------------------------------------+-----------+


<whimper!>

Try rebooting, hopefully install the updated values. Used /sudo shutdown
-r now/ – telling only because know a reboot is different from a power boot.


Retry above commands. Same results. :(


Try mythtv-setup. Well, it’s not taking five minutes to do anything –
that’s a definite improvement! On exit see where it’s still looking at
the old 192.168.0.3 – sort of expected that with the results from above.


Tried mythtv-setup.real – “Ubuntu version”. Does the same thing.


mythfrontend – when wrong that’s when I get the MythTV Startup Status
screen with the Database Configuration screen and try to switch the
Hostname field to the correct one. (I can update on the GUI, just
doesn’t ‘stick’ ? see it has changed back on exit and see Terminal stuff.


OK: at the Database configuration screen. (And didn’t take forever!).
Hostname field is now ‘localhost’. Overlay error window is “Cannot
connect to backend”. Clear that, enter “192.168.4.3”, save and exit…..
Tries to reconnect even though I told it to exit…. Well, maybe. Terminal
now has 192.168.4.3 but errors on timing out.


Try mythfrontend again (let the data ‘take’) Seems to be showing the
right IP but back to the Startup Status screen. Does have the correct
192.168.4.3 now, but the “Cannot connect to backend” error window.


Reboot… let some variable repopulate? ...Nope: Terminal display the
right IP, goes to the MythTV Startup Status Screen. Hmmm: now goes to
the Database Configuration screen (before a screen without the Hostname
– IP field). Is “192.168.4.3” (correct one).


See what this does now:

sudo su
mysql
use mythconverg;
select * from settings where data like '%192.168.%';
exit
exit


OK, that seems to give a reason why its not working: same results:

+-------------------+------------------------------------------+-----------+

| value |  data + hostname  |

+-------------------+------------------------------------------+-----------+

| BackendServerAddr | 192.168.0.3 | backend-3 |

| EventCmdAll | mythsgu event -h 192.168.0.4 %EVENTNAME% | backend-3 |

+-------------------+------------------------------------------+-----------+


‘Nuff for now! See what the next step is!


Barry

On 6/22/20 11:18 AM, Barry Martin wrote:
>
>
> Hi Bill!
>
>
> Did a quick test first. Remembered Stephen had me do this:
>
> sudo su
> mysql
> use mythconverg;
> select * from settings where data like '%192.168.%';
> exit
> exit
>
>
> Got the same results as before:
>
> +-------------------+------------------------------------------+-----------+
>
> | value |  data + hostname  |
>
> +-------------------+------------------------------------------+-----------+
>
> | BackendServerAddr | 192.168.0.3 | backend-3 |
>
> | EventCmdAll | mythsgu event -h 192.168.0.4 %EVENTNAME% | backend-3 |
>
> +-------------------+------------------------------------------+-----------+
>
>
> <whimper!>
>
> Try rebooting, hopefully install the updated values. Used /sudo shutdown -r now/ – telling only because know a reboot is different from a power
> boot.
>
>
> Retry above commands. Same results. :(
>
>
> Try mythtv-setup. Well, it’s not taking five minutes to do anything – that’s a definite improvement! On exit see where it’s still looking at the
> old 192.168.0.3 – sort of expected that with the results from above.
>
>
> Tried mythtv-setup.real – “Ubuntu version”. Does the same thing.
>
>
> mythfrontend – when wrong that’s when I get the MythTV Startup Status screen with the Database Configuration screen and try to switch the
> Hostname field to the correct one. (I can update on the GUI, just doesn’t ‘stick’ ? see it has changed back on exit and see Terminal stuff.
>
>
> OK: at the Database configuration screen. (And didn’t take forever!). Hostname field is now ‘localhost’. Overlay error window is “Cannot connect
> to backend”. Clear that, enter “192.168.4.3”, save and exit….. Tries to reconnect even though I told it to exit…. Well, maybe. Terminal now has
> 192.168.4.3 but errors on timing out.
>
>
> Try mythfrontend again (let the data ‘take’) Seems to be showing the right IP but back to the Startup Status screen. Does have the correct
> 192.168.4.3 now, but the “Cannot connect to backend” error window.
>
>
> Reboot… let some variable repopulate? ...Nope: Terminal display the right IP, goes to the MythTV Startup Status Screen. Hmmm: now goes to the
> Database Configuration screen (before a screen without the Hostname – IP field). Is “192.168.4.3” (correct one).
>
>
> See what this does now:
>
> sudo su
> mysql
> use mythconverg;
> select * from settings where data like '%192.168.%';
> exit
> exit
>
>
> OK, that seems to give a reason why its not working: same results:
>
> +-------------------+------------------------------------------+-----------+
>
> | value |  data + hostname  |
>
> +-------------------+------------------------------------------+-----------+
>
> | BackendServerAddr | 192.168.0.3 | backend-3 |
>
> | EventCmdAll | mythsgu event -h 192.168.0.4 %EVENTNAME% | backend-3 |
>
> +-------------------+------------------------------------------+-----------+
>
>
> ‘Nuff for now! See what the next step is!

Is there another backend running?

I'd disconnect this backend (backend-3) from the LAN and try again.

Use mythtv-setup.real -v upnp # pastebin the output if this doesn't help.

BackendServerAddr isn't used when running mythtv-setup.

Don't bother running mythfrontend 'til BackendServerAddr is fixed.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Hi Bill!


> Is there another backend running?
Nope. It’s the third Backend since starting with MythTV. I’m just not
all that great at coming up with device names,



> BackendServerAddr isn't used when running mythtv-setup.

OK – thought maybe it was giving a clue as to why the Setup Screen is
saying one thing and something else is looking at another.




> I'd disconnect this backend (backend-3) from the LAN and try again.
>
> Use mythtv-setup.real -v upnp # pastebin the output if this doesn't help.

Figure out which Ethernet cable (well, at least some are identified!
...Now this one is!)

myth-setup ==> database fails to start. Take out the .3, re-insert,
save, exit.


mythfilldatabase – hmm: wonder why the complaints? (Ethernet still
unplugged, on purpose.)


Plug Ethernet back in. mythtv-setup – back to the 1.General screen.
Exit; whatever it went in to automatically seeing the old 192.168.0.3
address


Do pastebin stuff…. trying “mythtv-setup.real -v upnp” as I’m
interpreting the octothorpe as a comment character. (Will find out!)



Old IP is 192.168.0.3 – find showing two hits.

New IP is 192.168.4.3 – bunch of hits. Too bad majority doesn’t rule! <g>



Bill Meek 3.txt at https://pastebin.com/Q7m2Rv2r


Good luck and Thank you!

Barry

On Mon, 22 Jun 2020 11:18:10 -0500, you wrote:

>
>
>Hi Bill!
>
>
>Did a quick test first. Remembered Stephen had me do this:
>
>sudo su
>mysql
>use mythconverg;
>select * from settings where data like '%192.168.%';
>exit
>exit
>
>
>Got the same results as before:
>
>+-------------------+------------------------------------------+-----------+
>
>| value |? data + hostname? |
>
>+-------------------+------------------------------------------+-----------+
>
>| BackendServerAddr | 192.168.0.3 | backend-3 |
>
>| EventCmdAll | mythsgu event -h 192.168.0.4 %EVENTNAME% | backend-3 |
>
>+-------------------+------------------------------------------+-----------+
>
>
><whimper!>
>
>Try rebooting, hopefully install the updated values. Used /sudo shutdown
>-r now/ ? telling only because know a reboot is different from a power boot.
>
>
>Retry above commands. Same results. :(
>
>
>Try mythtv-setup. Well, it?s not taking five minutes to do anything ?
>that?s a definite improvement! On exit see where it?s still looking at
>the old 192.168.0.3 ? sort of expected that with the results from above.
>
>
>Tried mythtv-setup.real ? ?Ubuntu version?. Does the same thing.
>
>
>mythfrontend ? when wrong that?s when I get the MythTV Startup Status
>screen with the Database Configuration screen and try to switch the
>Hostname field to the correct one. (I can update on the GUI, just
>doesn?t ?stick? ? see it has changed back on exit and see Terminal stuff.
>
>
>OK: at the Database configuration screen. (And didn?t take forever!).
>Hostname field is now ?localhost?. Overlay error window is ?Cannot
>connect to backend?. Clear that, enter ?192.168.4.3?, save and exit?..
>Tries to reconnect even though I told it to exit?. Well, maybe. Terminal
>now has 192.168.4.3 but errors on timing out.
>
>
>Try mythfrontend again (let the data ?take?) Seems to be showing the
>right IP but back to the Startup Status screen. Does have the correct
>192.168.4.3 now, but the ?Cannot connect to backend? error window.
>
>
>Reboot? let some variable repopulate? ...Nope: Terminal display the
>right IP, goes to the MythTV Startup Status Screen. Hmmm: now goes to
>the Database Configuration screen (before a screen without the Hostname
>? IP field). Is ?192.168.4.3? (correct one).
>
>
>See what this does now:
>
>sudo su
>mysql
>use mythconverg;
>select * from settings where data like '%192.168.%';
>exit
>exit
>
>
>OK, that seems to give a reason why its not working: same results:
>
>+-------------------+------------------------------------------+-----------+
>
>| value |? data + hostname? |
>
>+-------------------+------------------------------------------+-----------+
>
>| BackendServerAddr | 192.168.0.3 | backend-3 |
>
>| EventCmdAll | mythsgu event -h 192.168.0.4 %EVENTNAME% | backend-3 |
>
>+-------------------+------------------------------------------+-----------+
>
>
>?Nuff for now! See what the next step is!
>
>
>Barry
>

I am thinking that the simple way to fix this is to just directly
change the BackendServerAddr in the database. And the mythsgu event
is no longer needed, so it can just be removed:

sudo su
mysql
use mythconverg;
update settings set data='192.168.4.3' where value='BackendServerAddr'
and hostname='backend-3';
update settings set data='' where value='EventCmdAll' and
hostname='backend-3';
quit
systemctl restart mythtv-backend
exit
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Hi Stephen!


> I am thinking that the simple way to fix this is to just directly
> change the BackendServerAddr in the database. And the mythsgu event
> is no longer needed, so it can just be removed:
>
> sudo su
> mysql
> use mythconverg;
> update settings set data='192.168.4.3' where value='BackendServerAddr'
> and hostname='backend-3';
> update settings set data='' where value='EventCmdAll' and
> hostname='backend-3';
> quit
> systemctl restart mythtv-backend
> exit

I’m getting better at this stuff! Caught the line wrapping! The ‘and
hostname’ didn’t make sense, then looked and noticed the lack of the
semicolon after the line previous.



Results:


barry@Backend-3:~$ sudo su

[sudo] password for barry:

root@Backend-3:/home/barry# mysql

Welcome to the MariaDB monitor. Commands end with ; or \g.

Your MariaDB connection id is 617

Server version: 10.1.44-MariaDB-0ubuntu0.18.04.1 Ubuntu 18.04


Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.


Type 'help;' or '\h' for help. Type '\c' to clear the current input
statement.


MariaDB [(none)]> use mythconverg;

Reading table information for completion of table and column names

You can turn off this feature to get a quicker startup with -A


Database changed

MariaDB [mythconverg]> update settings set data='192.168.4.3' where
value='BackendServerAddr' and hostname='backend-3';

Query OK, 1 row affected (0.00 sec)

Rows matched: 1 Changed: 1 Warnings: 0


MariaDB [mythconverg]> update settings set data='' where
value='EventCmdAll' and hostname='backend-3';

Query OK, 1 row affected (0.02 sec)

Rows matched: 1 Changed: 1 Warnings: 0


MariaDB [mythconverg]> quit

Bye

root@Backend-3:/home/barry# systemctl restart mythtv-backend

root@Backend-3:/home/barry# exit

exit

barry@Backend-3:~$



- - -


Took maybe two minutes to get back to the prompt at the restart
mythtv-backend line.


---

And now the test! <drumroll...>


YESSSS!!!!!! <Cartwheels, fireworks, marching bands> :)


Test on a stand-alone device:

Errors because (remote) FE still set to the old IP; correct that. ..
Thinks a while, connects!! (Figured it would, just wanted to verify.)


Thanks to you and Bill and Hika (hope I didn’t miss any one) for helping
out!


Should your correction/update command set be placed in a Wiki or some
sort of help page? This issue is bound to come up again.


Barry

On Tue, 23 Jun 2020 09:17:15 -0500, you wrote:

>
>Hi Stephen!
>
>
>> I am thinking that the simple way to fix this is to just directly
>> change the BackendServerAddr in the database. And the mythsgu event
>> is no longer needed, so it can just be removed:
>>
>> sudo su
>> mysql
>> use mythconverg;
>> update settings set data='192.168.4.3' where value='BackendServerAddr'
>> and hostname='backend-3';
>> update settings set data='' where value='EventCmdAll' and
>> hostname='backend-3';
>> quit
>> systemctl restart mythtv-backend
>> exit
>
>I?m getting better at this stuff! Caught the line wrapping! The ?and
>hostname? didn?t make sense, then looked and noticed the lack of the
>semicolon after the line previous.
>
>
>
>Results:
>
>
>barry@Backend-3:~$ sudo su
>
>[sudo] password for barry:
>
>root@Backend-3:/home/barry# mysql
>
>Welcome to the MariaDB monitor. Commands end with ; or \g.
>
>Your MariaDB connection id is 617
>
>Server version: 10.1.44-MariaDB-0ubuntu0.18.04.1 Ubuntu 18.04
>
>
>Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
>
>
>Type 'help;' or '\h' for help. Type '\c' to clear the current input
>statement.
>
>
>MariaDB [(none)]> use mythconverg;
>
>Reading table information for completion of table and column names
>
>You can turn off this feature to get a quicker startup with -A
>
>
>Database changed
>
>MariaDB [mythconverg]> update settings set data='192.168.4.3' where
>value='BackendServerAddr' and hostname='backend-3';
>
>Query OK, 1 row affected (0.00 sec)
>
>Rows matched: 1 Changed: 1 Warnings: 0
>
>
>MariaDB [mythconverg]> update settings set data='' where
>value='EventCmdAll' and hostname='backend-3';
>
>Query OK, 1 row affected (0.02 sec)
>
>Rows matched: 1 Changed: 1 Warnings: 0
>
>
>MariaDB [mythconverg]> quit
>
>Bye
>
>root@Backend-3:/home/barry# systemctl restart mythtv-backend
>
>root@Backend-3:/home/barry# exit
>
>exit
>
>barry@Backend-3:~$
>
>
>
>- - -
>
>
>Took maybe two minutes to get back to the prompt at the restart
>mythtv-backend line.
>
>
>---
>
>And now the test! <drumroll...>
>
>
>YESSSS!!!!!! <Cartwheels, fireworks, marching bands> :)
>
>
>Test on a stand-alone device:
>
>Errors because (remote) FE still set to the old IP; correct that. ..
>Thinks a while, connects!! (Figured it would, just wanted to verify.)
>
>
>Thanks to you and Bill and Hika (hope I didn?t miss any one) for helping
>out!
>
>
>Should your correction/update command set be placed in a Wiki or some
>sort of help page? This issue is bound to come up again.

As direct updates to the database are potentially disastrous, it is
better not to have people who do not fully understand them doing them
without supervision. You really need to do the right queries to
understand what is in the database before you do any updates. And
then be very careful how the update is done. It is like that old
adage in the building trade - measure twice, cut once. A runaway
update command is like a chainsaw that has its trigger stuck down and
has escaped its owners grip - flopping around destroying things at
random!

I think there is probably a way to get mythtv-setup to run in the
situation you had by using a command line override to give it the
right IP address setting. But messing around with working that out
would have taken a while, so I gave you a customised database update
as a fix that we could do today to get you going again. I wrote it
around 14:00, then went out for an hour or so and checked it again
when I got back before I sent the email.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Hi Stephen!

> As direct updates to the database are potentially disastrous, it is
> better not to have people who do not fully understand them doing them
> without supervision. You really need to do the right queries to
> understand what is in the database before you do any updates. And
> then be very careful how the update is done. It is like that old
> adage in the building trade - measure twice, cut once. A runaway
> update command is like a chainsaw that has its trigger stuck down and
> has escaped its owners grip - flopping around destroying things at
> random!
>
> I think there is probably a way to get mythtv-setup to run in the
> situation you had by using a command line override to give it the
> right IP address setting. But messing around with working that out
> would have taken a while, so I gave you a customised database update
> as a fix that we could do today to get you going again. I wrote it
> around 14:00, then went out for an hour or so and checked it again
> when I got back before I sent the email.

Makes sense. As always I do appreciate all the time and testing you (and
of course the others) have put into my problem. What looks like a simple
fix on the surface is more complicated as one tries to find the source.

<Rhetorical rambling> I don’t know if I stumbled across a bug or because
of a something unique in by overall configuration, but the updating of
the IP value in the GUI wasn’t taking/changing the environmental (?)
value.   One reason for detailing what I saw on this end to you folks
helping. Perhaps my issue will help strengthen the code.

Again, thank you very much!

Barry