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