1 |
On 26/10/2011 22:19, Michael Sullivan wrote: |
2 |
> On 10/26/11 14:45, Michael Sullivan wrote: |
3 |
>> On 10/26/11 14:05, Michael Sullivan wrote: |
4 |
>>> On 10/26/11 14:03, Michael Sullivan wrote: |
5 |
>>>> On 10/26/11 13:31, Michael Sullivan wrote: |
6 |
>>>>> On 10/26/11 11:36, Mark Knecht wrote: |
7 |
>>>>>> On Wed, Oct 26, 2011 at 9:29 AM, Michael Sullivan<msulli1355@×××××.com> wrote: |
8 |
>>>>>>> On 10/26/11 11:07, Neil Bothwick wrote: |
9 |
>>>>>>>> On Wed, 26 Oct 2011 09:23:30 -0500, Michael Sullivan wrote: |
10 |
>>>>>>>> |
11 |
>>>>>>>>> At first I thought that sometime that installed since Oct 12 was causing |
12 |
>>>>>>>>> the segfault, so I tried unmerging the 350+ packages that had installed |
13 |
>>>>>>>>> since then and listing them in package.mask, but that blew up in my face |
14 |
>>>>>>>>> because I don't know a command that forces portage to ignore masked |
15 |
>>>>>>>>> packages and install next-highest stable versions. |
16 |
>>>>>>>> |
17 |
>>>>>>>> Mask higher versions in package mask |
18 |
>>>>>>>> |
19 |
>>>>>>>>> cat/pkg-version.you.want |
20 |
>>>>>>>> |
21 |
>>>>>>>> |
22 |
>>>>>>> |
23 |
>>>>>>> I did, but as I said there where 350+ of them. And every time I tried |
24 |
>>>>>>> to emerge anything else, I couldn't because some package I needed was |
25 |
>>>>>>> listed in package mask. I got the package list that I added to |
26 |
>>>>>>> package.mask from /var/log/portage-logs for files dated from October 12 |
27 |
>>>>>>> till 24. It was an epic fail. I couldn't even emerge -e world because |
28 |
>>>>>>> of those stupid masked package versions... |
29 |
>>>>>> |
30 |
>>>>>> OK, I haven't used Myth now in over a year so take this with a grain |
31 |
>>>>>> of salt. From the log file it appears that your client isn't |
32 |
>>>>>> connecting to the server which likely explains why you don't see the |
33 |
>>>>>> programs. I wonder if you've tested connecting to mythconverg manually |
34 |
>>>>>> via a terminal? Maybe something like /etc/my.cnf or one of the Myth |
35 |
>>>>>> config files got messed up in the update. |
36 |
>>>>>> |
37 |
>>>>>> Good luck, |
38 |
>>>>>> Mark |
39 |
>>>>>> |
40 |
>>>>> |
41 |
>>>>> Mysql on camille is broken: |
42 |
>>>>> |
43 |
>>>>> camille ~ # mysql -u root -p |
44 |
>>>>> mysql: unknown variable 'expire_logs_days=10' |
45 |
>>>>> |
46 |
>>>>> I'll do some googling, but I thinmichael@camille ~ $ sudo mythbackend |
47 |
>>>> 2011-10-26 13:48:02.094 mythbackend version: branches/release-0-23-fixes |
48 |
>>>> [27077] www.mythtv.org |
49 |
>>>> 2011-10-26 13:48:02.094 Using runtime prefix = /usr |
50 |
>>>> 2011-10-26 13:48:02.094 Using configuration directory = /root/.mythtv |
51 |
>>>> 2011-10-26 13:48:02.124 Unable to read configuration file mysql.txt |
52 |
>>>> 2011-10-26 13:48:02.124 Empty LocalHostName. |
53 |
>>>> 2011-10-26 13:48:02.124 Using localhost value of camille |
54 |
>>>> 2011-10-26 13:48:02.176 New DB connection, total: 1 |
55 |
>>>> 2011-10-26 13:48:02.223 Connected to database 'mythconverg' at host: |
56 |
>>>> localhost |
57 |
>>>> 2011-10-26 13:48:02.223 Closing DB connection named 'DBManager0' |
58 |
>>>> 2011-10-26 13:48:02.231 Connected to database 'mythconverg' at host: |
59 |
>>>> localhost |
60 |
>>>> 2011-10-26 13:48:02.344 Current MythTV Schema Version (DBSchemaVer): 1254 |
61 |
>>>> 2011-10-26 13:48:02.348 MythBackend: Running as a slave backend. |
62 |
>>>> 2011-10-26 13:48:02.384 mythbackend: MythBackend started as a slave backend |
63 |
>>>> 2011-10-26 13:48:02.390 New DB connection, total: 2 |
64 |
>>>> 2011-10-26 13:48:02.401 Connected to database 'mythconverg' at host: |
65 |
>>>> localhost |
66 |
>>>> 2011-10-26 13:48:02.426 New DB connection, total: 3 |
67 |
>>>> 2011-10-26 13:48:02.462 Connected to database 'mythconverg' at host: |
68 |
>>>> localhost |
69 |
>>>> 2011-10-26 13:48:02.728 MediaServer:: Loopback address specified - |
70 |
>>>> 127.0.0.1. Disabling UPnP |
71 |
>>>> 2011-10-26 13:48:02.728 Main::Registering HttpStatus Extension |
72 |
>>>> 2011-10-26 13:48:02.728 Enabled verbose msgs: important general |
73 |
>>>> 2011-10-26 13:48:03.773 Connecting to master server: 192.168.2.3:6543 |
74 |
>>>> 2011-10-26 13:48:03.773 Connected successfully |
75 |
>>>> 2011-10-26 13:48:12.673 mythbackend: Running housekeeping thread |
76 |
>>>> 2011-10-26 13:48:33.781 MythSocket(8219290:23): readStringList: Error, |
77 |
>>>> timed out after 30000 ms. |
78 |
>>>> QMutex::unlock: mutex lock failure: Invalid argument |
79 |
>>>> k that sounds like a config file |
80 |
>>>> |
81 |
>>>> It's been up for about 20 minutes and it hasn't crashed. None of the |
82 |
>>>> things I mentioned before work, but at least it's not crashing, right? |
83 |
>>>> This is a good step forward... |
84 |
>>>>> directive. I'll probably do a rebuild of mysql as well... |
85 |
>>>> |
86 |
>>>> |
87 |
>>>> I googled the expire_logs thing and what I found said to comment it out |
88 |
>>>> and restart mysql. I did that, and now the output of mythbackend says: |
89 |
>>>> |
90 |
>>>> |
91 |
>>>> |
92 |
>>> I forgot that I was going to post the output of mythbackend to see if |
93 |
>>> any of the changes provide hints to solving any of my other myth problems: |
94 |
>>> |
95 |
>>> michael@camille ~ $ sudo mythbackend |
96 |
>>> 2011-10-26 13:48:02.094 mythbackend version: branches/release-0-23-fixes |
97 |
>>> [27077] www.mythtv.org |
98 |
>>> 2011-10-26 13:48:02.094 Using runtime prefix = /usr |
99 |
>>> 2011-10-26 13:48:02.094 Using configuration directory = /root/.mythtv |
100 |
>>> 2011-10-26 13:48:02.124 Unable to read configuration file mysql.txt |
101 |
>>> 2011-10-26 13:48:02.124 Empty LocalHostName. |
102 |
>>> 2011-10-26 13:48:02.124 Using localhost value of camille |
103 |
>>> 2011-10-26 13:48:02.176 New DB connection, total: 1 |
104 |
>>> 2011-10-26 13:48:02.223 Connected to database 'mythconverg' at host: |
105 |
>>> localhost |
106 |
>>> 2011-10-26 13:48:02.223 Closing DB connection named 'DBManager0' |
107 |
>>> 2011-10-26 13:48:02.231 Connected to database 'mythconverg' at host: |
108 |
>>> localhost |
109 |
>>> 2011-10-26 13:48:02.344 Current MythTV Schema Version (DBSchemaVer): 1254 |
110 |
>>> 2011-10-26 13:48:02.348 MythBackend: Running as a slave backend. |
111 |
>>> 2011-10-26 13:48:02.384 mythbackend: MythBackend started as a slave backend |
112 |
>>> 2011-10-26 13:48:02.390 New DB connection, total: 2 |
113 |
>>> 2011-10-26 13:48:02.401 Connected to database 'mythconverg' at host: |
114 |
>>> localhost |
115 |
>>> 2011-10-26 13:48:02.426 New DB connection, total: 3 |
116 |
>>> 2011-10-26 13:48:02.462 Connected to database 'mythconverg' at host: |
117 |
>>> localhost |
118 |
>>> 2011-10-26 13:48:02.728 MediaServer:: Loopback address specified - |
119 |
>>> 127.0.0.1. Disabling UPnP |
120 |
>>> 2011-10-26 13:48:02.728 Main::Registering HttpStatus Extension |
121 |
>>> 2011-10-26 13:48:02.728 Enabled verbose msgs: important general |
122 |
>>> 2011-10-26 13:48:03.773 Connecting to master server: 192.168.2.3:6543 |
123 |
>>> 2011-10-26 13:48:03.773 Connected successfully |
124 |
>>> 2011-10-26 13:48:12.673 mythbackend: Running housekeeping thread |
125 |
>>> 2011-10-26 13:48:33.781 MythSocket(8219290:23): readStringList: Error, |
126 |
>>> timed out after 30000 ms. |
127 |
>>> QMutex::unlock: mutex lock failure: Invalid argument |
128 |
>>> |
129 |
>> |
130 |
>> I just ran mythfilldatabase to see if everything looked like it usually |
131 |
>> did. At the end of the run I saw this: |
132 |
>> |
133 |
>> 2011-10-26 14:41:39.486 MythContext: Connecting to backend server: |
134 |
>> 192.168.2.3:6543 (try 1 of 1) |
135 |
>> 2011-10-26 14:41:39.486 Connection to master server timed out. |
136 |
>> Either the server is down or the master server settings |
137 |
>> in mythtv-settings does not contain the proper IP address |
138 |
>> |
139 |
>> 2011-10-26 14:41:39.486 Error rescheduling id -1 in |
140 |
>> ScheduledRecording::signalChange |
141 |
>> 2011-10-26 14:41:39.487 MythContext: Connecting to backend server: |
142 |
>> 192.168.2.3:6543 (try 1 of 1) |
143 |
>> 2011-10-26 14:41:39.487 Connection to master server timed out. |
144 |
>> Either the server is down or the master server settings |
145 |
>> in mythtv-settings does not contain the proper IP address |
146 |
>> |
147 |
>> 2011-10-26 14:41:39.487 MythContext: Connecting to backend server: |
148 |
>> 192.168.2.3:6543 (try 1 of 1) |
149 |
>> 2011-10-26 14:41:39.487 Connection to master server timed out. |
150 |
>> Either the server is down or the master server settings |
151 |
>> in mythtv-settings does not contain the proper IP address |
152 |
>> |
153 |
>> In mythtv-setup I have: |
154 |
>> |
155 |
>> Local Backend (camille) section IP Address 127.0.0.1 |
156 |
>> |
157 |
>> Master Backend section IP Address 192.168.2.3 |
158 |
>> |
159 |
>> Is that not correct? |
160 |
> |
161 |
> |
162 |
> I changed Local Backend IP address to 192.168.2.3 and now I have |
163 |
> everything back except Upcoming Recordings, Program Finder and Program |
164 |
> Guide. Any thoughts? |
165 |
> |
166 |
|
167 |
Does it need a forced mythfilldatabase? If your backend hasn't been well |
168 |
for a while it's possible the data is all outdated now. |
169 |
|
170 |
HTH |