[mythtv-users] mythweb unable to connect after upgrade to 028

[George Bingham]

OK,

I think I know what happened. Since this is mythbuntu, at some point while
troubleshooting I used the 'mythbuntu control center' and enabled 'mysql
performance tweaks'   - I guess that adds a file called "mythtv-tweaks.cnf"
in the /etc/mysql/conf.d directory, and that file contains the line
'table_cache = 128' which is no longer correct.

I am thinking that's a bug in mythbuntu control center?

Anyway, renaming that file so it no longer has a .cnf extension allows
mysql to come up properly and as of my last reboot, both it and mythbackend
were there waiting for me.

I was also having a audio configuration issue, I guess my mainboard audio
decided now was a good time to fizzle out, but luckily I had an old system
with an even older soundcard that I was able to put in my server and after
finding and downloading it's firmware, got that up and running.

I think I am doing OK now.... will let this go for a few days and see how
it goes and then set my frontend to launch automatically again and we
should be back to normal.

Keeping my fingers crossed!

George

-- George

On Sun, May 8, 2016 at 12:51 PM, George Bingham <georgeb1962 at gmail.com>
wrote:

> Hey Bill,
>
> I think you can see my reply to Richard where I list the mysql service
> file.
>
> My run files are different than yours, not sure why:
>
> * ls -ld /run/mysqld /run/mysqld/**
> *drwxr-xr-x 2 mysql mysql 100 May  7 17:17 /run/mysqld*
> *-rw-r----- 1 mysql mysql   5 May  7 17:17 /run/mysqld/mysqld.pid*
> *srwxrwxrwx 1 mysql mysql   0 May  7 17:17 /run/mysqld/mysqld.sock*
> *-rw------- 1 mysql mysql   5 May  7 17:17 /run/mysqld/mysqld.sock.lock*
>
> Owner and group are mysql.
>
>
> -- George
>
> On Sun, May 8, 2016 at 9:26 AM, Bill Meek <keemllib at gmail.com> wrote:
>
>> On 05/07/2016 09:48 PM, George Bingham wrote:
>> ...
>> > I *think* have have it using a proper ipv6 address, however, booting up
>> I
>>
>>> still see problems.
>>>
>>
>> Likely ::1
>>
>> ...
>>
>> I am not sure why, but mysql is refusing connections because although it
>>> is
>>> "up" it's socket address isn't there yet.
>>>
>>
>> I see this, noting the mysql owner and root user:
>>
>> $ ls -ld /run/mysqld /run/mysqld/*
>> drwxr-xr-x 2 mysql root 80 May  8 07:02 /run/mysqld
>> -rw-rw---- 1 mysql root  5 May  8 07:02 /run/mysqld/mysqld.pid
>> srwxrwxrwx 1 mysql root  0 May  8 07:02 /run/mysqld/mysqld.sock
>>
>> I may have deleted too many old emails on this thread, but don't see the
>> .service file you're using to start mysql.  How 'bout doing this:
>>
>> systemctl cat mysql<then type the tab character twice>
>>
>> That will give you a list of the (or all) .service files in use. Please
>> select and pastebin a copy of each file.
>>
>> ...
>>
>>> Are you happy with having to restart the backend at the tail end of the
>>> boot process or have you found a way to make it all just "work".
>>>
>>
>> Mine just work, so I'm happy.
>>
>>
>> --
>> Bill
>> _______________________________________________
>> 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
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160508/5dae5252/attachment.html>