[mythtv-users] new system doesn't record...

[Nick Morrott]

On 15 March 2010 03:45, Udo van den Heuvel <udovdh at xs4all.nl> wrote:
> Even worse:
>
> # mythbackend --resched
> 2010-03-15 04:44:04.094 Using runtime prefix = /usr
> 2010-03-15 04:44:04.106 Using localhost value of localhost
> 2010-03-15 04:44:04.134 New DB connection, total: 1
> 2010-03-15 04:44:04.140 Connected to database 'mythconverg' at host:
> localhost
> 2010-03-15 04:44:04.142 Closing DB connection named 'DBManager0'
> 2010-03-15 04:44:04.142 Connected to database 'mythconverg' at host:
> localhost
> 2010-03-15 04:44:04.143 New DB connection, total: 2
> 2010-03-15 04:44:04.144 Connected to database 'mythconverg' at host:
> localhost
> 2010-03-15 04:44:04.147 Current Schema Version: 1214
> 2010-03-15 04:44:04.153 Connecting to backend server: 127.0.0.1:6543
> (try 1 of 5)
> 2010-03-15 04:44:11.156 MythSocket(1f7ab20:5): readStringList: Error,
> timeout (quick).
> 2010-03-15 04:44:11.156 Protocol version check failure. The response to
> MYTH_PROTO_VERSION was empty.
> 2010-03-15 04:44:11.157 Cannot connect to master for reschedule
>
> The backend process is running.
> No response.

Make sure you are not seeing the problems reported here:

http://svn.mythtv.org/trac/ticket/7469

Double check all of your master/local backend and database server IP
settings. If you restored an old database it is possible for settings
to become out-of-date. Make sure none of your network settings have
changed since the restore.

Adding MythSocket debugging to your log output may be helpful in
tracking this down.

Cheers,
Nick

-- 
Nick Morrott

MythTV Official wiki: http://mythtv.org/wiki/
MythTV users list archive: http://www.gossamer-threads.com/lists/mythtv/users

"An investment in knowledge always pays the best interest." - Benjamin Franklin