[mythtv-users] Backend can't connect (it was all working fine!) - mysql strangeness
Damian
myth at surr.co.uk
Sun Apr 10 18:38:31 UTC 2016
On 10/04/2016 18:27, Noah Beck wrote:
> On Sat, Apr 9, 2016 at 9:51 PM, Damian <myth at surr.co.uk> wrote:
>> Hi All,
>>
>> I'm setting up a new Mythbuntu backend (on top of Xubuntu 15.10 OS), and
>> it's just being weird!
>>
>> One minute the backend can't connect to mysql. Then I get it all fixed, and
>> it's fine through several reboots. Now it's broken again. I can't get my
>> head around what's going on.
>
> Is there anything in journalctl -b related to mysql, mariadb,
> mythbackend, or x11vnc? Selinux in particular has created problems
> for me in the past.
>
> Noah
>
Hi Noah,
Thanks for helping. I've run 'journalctl -b'
I didn't know how to write it to a file (to search), or to narrow down
the output, so I have gone through it and posted the 'red bits' below ...
kernel: ERST: Failed to get Error Log Address Range.
kernel: i8042: No controller found
NetworkManager[594]: nm_device_get_device_type: assertion 'NM_IS_DEVICE
(self)' failed
NetworkManager[594]: <error> [1460312021.044915]
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq
mythbackend[676]: mythbackend[676]: C thread_unknown
mythcommandlineparser.cpp:2595 (ConfigureLogging)
mythbackend[676]: mythbackend[676]: C thread_unknown
mythcommandlineparser.cpp:2597 (ConfigureLogging)
mythbackend[676]: mythbackend[676]: E CoreContext mythdbcon.cpp:216
(OpenDatabase) Unable to connect t
mythbackend[676]: mythbackend[676]: E CoreContext mythdbcon.cpp:217
(OpenDatabase) Driver error was [1
QMYSQL: Unable to connect
Database error was:
Can't connect to MySQL
server on '192.168.0.2' (111)
mythbackend[676]: mythbackend[676]: C CoreContext main.cpp:130 (main)
Failed to init MythContext.
mythbackend[1601]: mythbackend[1601]: C thread_unknown
mythcommandlineparser.cpp:2595 (ConfigureLoggin
mythbackend[1601]: mythbackend[1601]: C thread_unknown
mythcommandlineparser.cpp:2597 (ConfigureLoggin
mythbackend[1601]: mythbackend[1601]: E CoreContext mythdbcon.cpp:216
(OpenDatabase) Unable to connect
mythbackend[1601]: mythbackend[1601]: E CoreContext mythdbcon.cpp:217
(OpenDatabase) Driver error was
QMYSQL: Unable to connect
Database error was:
Can't connect to MySQL
server on '192.168.0.2' (111)
mythbackend[1601]: mythbackend[1601]: C CoreContext main.cpp:130 (main)
Failed to init MythContext.
mythbackend[1685]: mythbackend[1685]: C thread_unknown
mythcommandlineparser.cpp:2595 (ConfigureLoggin
mythbackend[1685]: mythbackend[1685]: C thread_unknown
mythcommandlineparser.cpp:2597 (ConfigureLoggin
mythbackend[1685]: mythbackend[1685]: E CoreContext mythdbcon.cpp:216
(OpenDatabase) Unable to connect
mythbackend[1685]: mythbackend[1685]: E CoreContext mythdbcon.cpp:217
(OpenDatabase) Driver error was
QMYSQL: Unable to connect
Database error was:
Can't connect to MySQL
server on '192.168.0.2' (111)
mythbackend[1685]: mythbackend[1685]: C CoreContext main.cpp:130 (main)
Failed to init MythContext.
mythbackend[1701]: mythbackend[1701]: C thread_unknown
mythcommandlineparser.cpp:2595 (ConfigureLoggin
mythbackend[1701]: mythbackend[1701]: C thread_unknown
mythcommandlineparser.cpp:2597 (ConfigureLoggin
mythbackend[1701]: mythbackend[1701]: E CoreContext mythdbcon.cpp:216
(OpenDatabase) Unable to connect
mythbackend[1701]: mythbackend[1701]: E CoreContext mythdbcon.cpp:217
(OpenDatabase) Driver error was
QMYSQL: Unable to connect
Database error was:
Can't connect to MySQL
server on '192.168.0.2' (111)
Apr 10 19:13:47 gingerserver mythbackend[1701]: mythbackend[1701]: C
CoreContext main.cpp:130 (main) Failed to init MythContext.
mythbackend[1729]: mythbackend[1729]: C thread_unknown
mythcommandlineparser.cpp:2595 (ConfigureLoggin
Apr 10 19:13:49 gingerserver mythbackend[1729]: mythbackend[1729]: C
thread_unknown mythcommandlineparser.cpp:2597 (ConfigureLoggin
mythbackend[1729]: mythbackend[1729]: E CoreContext mythdbcon.cpp:216
(OpenDatabase) Unable to connect
mythbackend[1729]: mythbackend[1729]: E CoreContext mythdbcon.cpp:217
(OpenDatabase) Driver error was
QMYSQL: Unable to connect
Database error was:
Can't connect to MySQL
server on '192.168.0.2' (111)
mythbackend[1729]: mythbackend[1729]: C CoreContext main.cpp:130 (main)
Failed to init MythContext.
mythbackend[1777]: mythbackend[1777]: C thread_unknown
mythcommandlineparser.cpp:2595 (ConfigureLoggin
mythbackend[1777]: mythbackend[1777]: C thread_unknown
mythcommandlineparser.cpp:2597 (ConfigureLoggin
mythbackend[1777]: mythbackend[1777]: E CoreContext mythdbcon.cpp:216
(OpenDatabase) Unable to connect
mythbackend[1777]: mythbackend[1777]: E CoreContext mythdbcon.cpp:217
(OpenDatabase) Driver error was
QMYSQL: Unable to connect
Database error was:
Can't connect to MySQL
server on '192.168.0.2' (111)
mythbackend[1777]: mythbackend[1777]: C CoreContext main.cpp:130 (main)
Failed to init MythContext.
mythbackend[1803]: mythbackend[1803]: C thread_unknown
mythcommandlineparser.cpp:2595 (ConfigureLoggin
mythbackend[1803]: mythbackend[1803]: C thread_unknown
mythcommandlineparser.cpp:2597 (ConfigureLoggin
(and more like these, and then ...)
systemd[1]: Failed to start MythTV Backend.
pulseaudio[2201]: [pulseaudio] pid.c: Daemon already running.
systemd[1]: Failed to start MySQL Community Server.
Few!
there were lots more bits highlighted as bold white too. These are just
the 'red' bits.
Is this useful?
Thanks,
Damian
More information about the mythtv-users
mailing list