Hi,
I removed queries that tinkered recordmatch but still the situation is the
same. Everything seems to be ok in ~/.mythtv/mysql.txt file and backend is
running.
Here is an example from /var/log/mythbackend.log file when everyting works:
------
2005-09-12 17:47:44.097 MainServer::HandleAnnounce Playback
2005-09-12 17:47:44.102 adding: dhcppc3 as a client (events: 0)
2005-09-12 17:47:44.136 Reschedule requested for id 85.
2005-09-12 17:47:44.185 Scheduled 1 items in 0.0 = 0.04 match + 0.01 place
-------
And here is an example what happens when I'm running mythbackend --resched
manually
----
2005-09-12 17:48:55.499 MainServer::HandleAnnounce Playback
2005-09-12 17:48:55.515 adding: dhcppc3 as a client (events: 0)
2005-09-12 17:48:55.528 Reschedule requested for id -1.
2005-09-12 17:48:55.576 Scheduled 0 items in 0.0 = 0.04 match + 0.01 place
-----
So where is the information about recordid needed for rescheduler? What is
the right table for this information?
Br,
JP
From: Bruce Markey <[EMAIL PROTECTED]>
Reply-To: Discussion about mythtv <[email protected]>
To: Discussion about mythtv <[email protected]>
Subject: Re: [mythtv-users] using mythbackend --resched
Date: Sun, 11 Sep 2005 14:22:44 -0700
J P wrote:
I'm trying to start recording manually by inserting data manually to
database tables e.g. record and recordmatch. After this I run
Don't tinker with recordmatch, the scheduler fills this based
on the record rules and listings so it's unnecessary and can hoze
things if it isn't an actual match. If you are doing an actual
"kManualSearch" then the scheduler should add the program entry
with a manualid.
mythbackend --resched. This worked in mythtv 0.18 but when I updated to
0.18.1 this feature stopped to work. Any ideas?
Here are the messages in mythbackend.log:
2005-09-11 14:53:16.324 Reschedule requested for id -1.
2005-09-11 14:53:16.361 unknown socket
^^^^^^^^^^^^^^
No mystery here. it should say:
2005-09-11 14:53:16.361 Connecting to backend server: 192.168.0.35:6543
(try 1of 5)
2005-09-11 14:53:16.568 Connected to master for reschedule
Is the masterbackend running and is it finding the correct mysql.txt
file and are the parameters correct for the host where you ran mythbackend
--resched ? Check to see if there is a mysql.txt in
the current directory or in ~/.mythtv/mysql.txt for the user
that issued the command.
-- bjm
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
