1 |
On 10/26/11 13:31, Michael Sullivan wrote: |
2 |
> On 10/26/11 11:36, Mark Knecht wrote: |
3 |
>> On Wed, Oct 26, 2011 at 9:29 AM, Michael Sullivan <msulli1355@×××××.com> wrote: |
4 |
>>> On 10/26/11 11:07, Neil Bothwick wrote: |
5 |
>>>> On Wed, 26 Oct 2011 09:23:30 -0500, Michael Sullivan wrote: |
6 |
>>>> |
7 |
>>>>> At first I thought that sometime that installed since Oct 12 was causing |
8 |
>>>>> the segfault, so I tried unmerging the 350+ packages that had installed |
9 |
>>>>> since then and listing them in package.mask, but that blew up in my face |
10 |
>>>>> because I don't know a command that forces portage to ignore masked |
11 |
>>>>> packages and install next-highest stable versions. |
12 |
>>>> |
13 |
>>>> Mask higher versions in package mask |
14 |
>>>> |
15 |
>>>>> cat/pkg-version.you.want |
16 |
>>>> |
17 |
>>>> |
18 |
>>> |
19 |
>>> I did, but as I said there where 350+ of them. And every time I tried |
20 |
>>> to emerge anything else, I couldn't because some package I needed was |
21 |
>>> listed in package mask. I got the package list that I added to |
22 |
>>> package.mask from /var/log/portage-logs for files dated from October 12 |
23 |
>>> till 24. It was an epic fail. I couldn't even emerge -e world because |
24 |
>>> of those stupid masked package versions... |
25 |
>> |
26 |
>> OK, I haven't used Myth now in over a year so take this with a grain |
27 |
>> of salt. From the log file it appears that your client isn't |
28 |
>> connecting to the server which likely explains why you don't see the |
29 |
>> programs. I wonder if you've tested connecting to mythconverg manually |
30 |
>> via a terminal? Maybe something like /etc/my.cnf or one of the Myth |
31 |
>> config files got messed up in the update. |
32 |
>> |
33 |
>> Good luck, |
34 |
>> Mark |
35 |
>> |
36 |
> |
37 |
> Mysql on camille is broken: |
38 |
> |
39 |
> camille ~ # mysql -u root -p |
40 |
> mysql: unknown variable 'expire_logs_days=10' |
41 |
> |
42 |
> I'll do some googling, but I thinmichael@camille ~ $ sudo mythbackend |
43 |
2011-10-26 13:48:02.094 mythbackend version: branches/release-0-23-fixes |
44 |
[27077] www.mythtv.org |
45 |
2011-10-26 13:48:02.094 Using runtime prefix = /usr |
46 |
2011-10-26 13:48:02.094 Using configuration directory = /root/.mythtv |
47 |
2011-10-26 13:48:02.124 Unable to read configuration file mysql.txt |
48 |
2011-10-26 13:48:02.124 Empty LocalHostName. |
49 |
2011-10-26 13:48:02.124 Using localhost value of camille |
50 |
2011-10-26 13:48:02.176 New DB connection, total: 1 |
51 |
2011-10-26 13:48:02.223 Connected to database 'mythconverg' at host: |
52 |
localhost |
53 |
2011-10-26 13:48:02.223 Closing DB connection named 'DBManager0' |
54 |
2011-10-26 13:48:02.231 Connected to database 'mythconverg' at host: |
55 |
localhost |
56 |
2011-10-26 13:48:02.344 Current MythTV Schema Version (DBSchemaVer): 1254 |
57 |
2011-10-26 13:48:02.348 MythBackend: Running as a slave backend. |
58 |
2011-10-26 13:48:02.384 mythbackend: MythBackend started as a slave backend |
59 |
2011-10-26 13:48:02.390 New DB connection, total: 2 |
60 |
2011-10-26 13:48:02.401 Connected to database 'mythconverg' at host: |
61 |
localhost |
62 |
2011-10-26 13:48:02.426 New DB connection, total: 3 |
63 |
2011-10-26 13:48:02.462 Connected to database 'mythconverg' at host: |
64 |
localhost |
65 |
2011-10-26 13:48:02.728 MediaServer:: Loopback address specified - |
66 |
127.0.0.1. Disabling UPnP |
67 |
2011-10-26 13:48:02.728 Main::Registering HttpStatus Extension |
68 |
2011-10-26 13:48:02.728 Enabled verbose msgs: important general |
69 |
2011-10-26 13:48:03.773 Connecting to master server: 192.168.2.3:6543 |
70 |
2011-10-26 13:48:03.773 Connected successfully |
71 |
2011-10-26 13:48:12.673 mythbackend: Running housekeeping thread |
72 |
2011-10-26 13:48:33.781 MythSocket(8219290:23): readStringList: Error, |
73 |
timed out after 30000 ms. |
74 |
QMutex::unlock: mutex lock failure: Invalid argument |
75 |
k that sounds like a config file |
76 |
|
77 |
It's been up for about 20 minutes and it hasn't crashed. None of the |
78 |
things I mentioned before work, but at least it's not crashing, right? |
79 |
This is a good step forward... |
80 |
> directive. I'll probably do a rebuild of mysql as well... |
81 |
|
82 |
|
83 |
I googled the expire_logs thing and what I found said to comment it out |
84 |
and restart mysql. I did that, and now the output of mythbackend says: |