[mythtv-users] One step forward, two steps back - Frontends not woring properly

Sun May 1 23:08:32 UTC 2016

On 01/05/2016 10:51, Hika van den Hoven wrote:
> Hoi Hika,
>
> Sunday, May 1, 2016, 11:38:12 AM, you wrote:
>
>> Hoi Vincent,
>> Sunday, May 1, 2016, 11:23:49 AM, you wrote:
>>> On Sat, Apr 30, 2016 at 04:32:53PM +0100, Damian wrote:
>>>>> What this shows is mysql is listening on ipv6 but not ipv4.
>>>>> First check your /sbin/ifconfig output. Should be safe to post it here,
>>>>> it's on an unroutable network. If there is an interface with an IP
>>>>> address that is not in 192.168.0.0/24, leave that out.
>>>> Thanks Vincent. Here you go ...
>>>>
>>>> $ /sbin/ifconfig
>>>> enp2s0    Link encap:Ethernet  HWaddr 00:9c:02:97:55:54
>>>>            inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
>>>>            inet6 addr: fe80::3b9c:8e34:fb44:2847/64 Scope:Link
>>>>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>            RX packets:3488095 errors:0 dropped:0 overruns:0 frame:0
>>>>            TX packets:5707203 errors:0 dropped:0 overruns:0 carrier:0
>>>>            collisions:0 txqueuelen:1000
>>>>            RX bytes:1009176206 (1.0 GB)  TX bytes:8235960424 (8.2 GB)
>>>>            Interrupt:18
>>>>
>>>> lo        Link encap:Local Loopback
>>>>            inet addr:127.0.0.1  Mask:255.0.0.0
>>>>            inet6 addr: ::1/128 Scope:Host
>>>>            UP LOOPBACK RUNNING  MTU:65536  Metric:1
>>>>            RX packets:2377579 errors:0 dropped:0 overruns:0 frame:0
>>>>            TX packets:2377579 errors:0 dropped:0 overruns:0 carrier:0
>>>>            collisions:0 txqueuelen:1
>>>>            RX bytes:373000387 (373.0 MB)  TX bytes:373000387 (373.0 MB)
>>>   
>>> Interesting. There is an IPv4 interface but the name is unusual,
>>> I was expecting it to be called eth0 not enp2s0.
>>> Nonetheless it seems you have a working interface with a IPv4 address
>>> and from what you say below it is responding to other hosts.
>>> For clarity, are there other network interfaces that you have left out?
>> This naming depends on the udev version. Some time in the past the
>> naming was changed from ethx to enpxsx. This naming comes from the pci
>> location as shown through lspci. It was implemented to make the naming
>> more consistent through reboots, especially when there are more
>> network cards. There are ways to go back to the old naming through
>> udev rules.
> Oh and to check if there are inactive interface run /sbin/ifconfig -a

Here you go ...

ifconfig -a
enp2s0    Link encap:Ethernet  HWaddr 00:9c:02:97:55:54
           inet addr:192.168.0.2  Bcast:192.168.0.255 Mask:255.255.255.0
           inet6 addr: fe80::90e1:63bc:2578:b658/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:363079 errors:0 dropped:0 overruns:0 frame:0
           TX packets:446351 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:269372639 (269.3 MB)  TX bytes:585137972 (585.1 MB)
           Interrupt:18

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:65536  Metric:1
           RX packets:83715 errors:0 dropped:0 overruns:0 frame:0
           TX packets:83715 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1
           RX bytes:13363894 (13.3 MB)  TX bytes:13363894 (13.3 MB)

>
>>>>> Is your network configured by network-manager or /etc/network/interfaces?
>>>>>
>>>> I'm not sure what you mean by this. I set up static IP's on my router if
>>>> that helps.
>>>>
>>> On an ubuntu system you can tell the machine how you want the network
>>> interfaces set up by editing the file /etc/network/interfaces.
>>> However I think the default is for 'network-manager' to look after all
>>> the network settings, through a GUI interface. You can mix and match too,
>>> if you set up an interface with /etc/network/interfaces,
>>> network-manager will not try to configure that interface.
>>>>> Other checks to try on the backend, please report pass/fail
>>>>> a) ping 192.168.0.2
>>>>>      is it pinging (pass) or not responding
>>>>>      eg 4 bytes from 192.168.0.2 icmp_seq=1 ttl=64 time=0.021 ms
>>>> Pass from the box itself and from the windows machine I'm connecting to it
>>>> with via SSH. I can't check the remote frontends at the moment, but I've
>>>> checked 192.168.0.2/mythweb with both of them before, and that was working
>>>> fine.
>>> So this means your IPv4 address is working and some services are
>>> listening on that address, but not mysql.
>>>>> c) repeat a) & b) from one of the frontends
>>>>>     If a & b pass but c fails, could be a firewall but there are other
>>>>>     possible issues.
>>>>>     Please post the ip address of the machine you tested from too.
>>>>>
>>>>> Vince
>>>>>
>>>> I'll do this from the frontends as soon as I can.
>>>   
>>> Ok.
>>> My next suggestion would be posting the mysql config files.
>>> This incantation should do the trick
>>>    cd /etc/mysql
>>>    sudo find . -type f -name "*.cnf" \
>>>                -exec egrep -Hv '^(\s*#|$)' {} \; | grep -v debian.cnf
>>> This will print out just the active lines in the config files.
>>> The last bit suppresses the content of debian.cnf (it has a password).
>>> Vince
>>> _______________________________________________
>
>
> Tot mails,
>    Hika                            mailto:hikavdh at 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 at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org