[mythtv-users] One step forward, two steps back - Frontends not woring properly
Damian
myth at surr.co.uk
Sun May 1 23:06:02 UTC 2016
On 01/05/2016 10:23, Vincent McIntyre 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?
Hi Vincent,
No, I don't think anything is missing. That's the entire output of ifconfig.
>
>>>
>>> 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.
It's looking like I might have to delve into this, but as I just
mentioned to Stephen, I've never had to do this before. In all of my
previous MythTV incarnations, I never touch the machines network
settings. Everything has always worked find just based on the IP
addresses I set each machine via my router.
>
>>> 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.
I guess that's half good! :-)
>
>>> 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
>
OK, here's the output, and a few notes at the end ...
./mysql.conf.d/mysqld_safe_syslog.cnf:[mysqld_safe]
./mysql.conf.d/mysqld_safe_syslog.cnf:syslog
./mysql.conf.d/mysqld.cnf:[mysqld_safe]
./mysql.conf.d/mysqld.cnf:socket = /var/run/mysqld/mysqld.sock
./mysql.conf.d/mysqld.cnf:nice = 0
./mysql.conf.d/mysqld.cnf:[mysqld]
./mysql.conf.d/mysqld.cnf:user = mysql
./mysql.conf.d/mysqld.cnf:pid-file = /var/run/mysqld/mysqld.pid
./mysql.conf.d/mysqld.cnf:socket = /var/run/mysqld/mysqld.sock
./mysql.conf.d/mysqld.cnf:port = 3306
./mysql.conf.d/mysqld.cnf:basedir = /usr
./mysql.conf.d/mysqld.cnf:datadir = /var/lib/mysql
./mysql.conf.d/mysqld.cnf:tmpdir = /tmp
./mysql.conf.d/mysqld.cnf:lc-messages-dir = /usr/share/mysql
./mysql.conf.d/mysqld.cnf:skip-external-locking
./mysql.conf.d/mysqld.cnf:key_buffer_size = 16M
./mysql.conf.d/mysqld.cnf:max_allowed_packet = 16M
./mysql.conf.d/mysqld.cnf:thread_stack = 192K
./mysql.conf.d/mysqld.cnf:thread_cache_size = 8
./mysql.conf.d/mysqld.cnf:myisam-recover-options = BACKUP
./mysql.conf.d/mysqld.cnf:query_cache_limit = 1M
./mysql.conf.d/mysqld.cnf:query_cache_size = 16M
./mysql.conf.d/mysqld.cnf:log_error = /var/log/mysql/error.log
./mysql.conf.d/mysqld.cnf:expire_logs_days = 10
./mysql.conf.d/mysqld.cnf:max_binlog_size = 100M
./mysql.cnf:!includedir /etc/mysql/conf.d/
./mysql.cnf:!includedir /etc/mysql/mysql.conf.d/
./conf.d/mysql.cnf:[mysql]
./conf.d/mythtv.cnf:[mysqld]
./conf.d/mythtv.cnf:bind-address=192.168.0.2
./conf.d/mythtv.cnf:max_connections=1000
./conf.d/mysqldump.cnf:[mysqldump]
./conf.d/mysqldump.cnf:quick
./conf.d/mysqldump.cnf:quote-names
./conf.d/mysqldump.cnf:max_allowed_packet = 16M
Notes:
The bind-address in ./conf.d/mythtv.cnf had been "bind-address=::". I
changed it to "bind-address=192.168.0.2" based on Stephen's advice.
max_connections in ./conf.d/mythtv.cnf had been 100. Due to Mark's
comment, I changed this to 250. That seemed to make the frontends more
responsive (but not fixed). I thought I'd try 1000 just to see if that
suddenly made it all work, but unfortunately it didn't.
Also, about half an hour ago I deleted the "mythtv-tweaks.cnf" file. I
believe this is part of Mythbuntu and it includes the 'table_cache' bit
that breaks everything, so I had very little faith in it! :-) For
completeness, here's the contents of that file ...
[mysqld]
# The following values were partly taken from:
# http://www.gossamer-threads.com/lists/mythtv/users/90942#90942
# key_buffer = 48M
# max_allowed_packet = 8M
# table_cache = 128
sort_buffer_size = 48M
net_buffer_length = 8M
# thread_cache_size = 4
query_cache_type = 1
query_cache_size = 32M
# don't do binary logs for mythconverg
binlog_ignore_db = mythconverg
Is this helping at all?
I can't understand what's going on. Surely Mythbuntu is supposed to get
rid of these configuration headaches for us mere mortal level geeks!
Part of my feels like wiping the server OS and starting again.
Thanks again for your help Vincent.
Damian
More information about the mythtv-users
mailing list