| Author |
Message |
|
SWC
|
 Posted: Tue Nov 06, 2007 9:10 pm |
|
|
Joined: Sun Mar 07, 2004 4:05 pm
Posts: 42
|
|
Hello all, I am having an issue with my recordings. Namely, they aren't happening.
If I go to the guide, and bring up the info on a show, I can select "Record only this showing" for example. But if I thengo down to Preview Schedule Changes, it says that "The recording schedule would not be affected.".
If I log in via MythWeb, and view schedules, I can see the shows listed as "Record every week in this time slot" for example, but if I then go to Upcoming Recordings, there is nothing listed.
What is going on? I can view live TV fine, and can view previously recorded shows, but nothing else is recording.
Pointers?
|
|
| Top |
|
 |
|
SWC
|
Posted: Tue Nov 06, 2007 9:32 pm |
|
|
Joined: Sun Mar 07, 2004 4:05 pm
Posts: 42
|
Some of the forum posts indicated checking the mysql files, but those all seem normal. I ran the following test:
Code: cd /var/lib/mysql/mythconverg
/etc/init.d/mythtv-backend stop
/etc/init.d/mysql stop
myisamchk *.MYI
No errors of any kind.
Next steps?
|
|
| Top |
|
|
|
tjc
|
Posted: Tue Nov 06, 2007 10:09 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
The first rule of debugging is always, "what else has changed?"
How long has the problem existed? What events occurred just before that? You might even go so far as to use find to check for files that have changed since the last time it worked, presuming of course you didn't totally reset the system with an upgrade or the like.
Also check your capture card definitions and input connections in mythtv-setup. If you don't have a valid input connection defined there aren't any "available inputs" so it can't schedule recordings.
|
|
| Top |
|
|
|
SWC
|
Posted: Wed Nov 07, 2007 6:23 am |
|
|
Joined: Sun Mar 07, 2004 4:05 pm
Posts: 42
|
|
The last show that recorded successfully was on Nov. 2nd, but I don't know how long before that the scheduling stopped working. Presumeably no more than a week.
The only changes I have done recently are to add a new front end client. To do that, I did four things:
- Install the client on another box.
- Update mysql to enable networking.
- Copy the MasterServerIP line in the settings table, and make an additional entry with the backend box's IP address and my frontend's hostname.
- Update the BackendServerIP value in the settings table to be my backend's actual IP (192.168.1.1).
The front end works fine now, it is just that the backend isn't scheduling any more.
If my capture sources weren't set up right I wouldn't be able to watch TV, would I? I'll check there though, as another starting point.
Thanks for the assistance.
|
|
| Top |
|
|
|
SWC
|
Posted: Wed Nov 07, 2007 6:13 pm |
|
|
Joined: Sun Mar 07, 2004 4:05 pm
Posts: 42
|
|
Thanks tjc. Walked through mythsetup again, deleting my existing inputs and then the connections, and readded everything. As far as I know, nothing should have changed here, but when I restarted the mythbackend after making these changes, the upcoming recordings list was populated correctly.
Many thanks!
|
|
| Top |
|
|
|
tjc
|
Posted: Wed Nov 07, 2007 8:47 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
Certain things in the db are keyed by hostname or IP, I'm guessing that the setup changes to allow the new FE perturbed this, possibly from localhost to a different name.
|
|
| Top |
|
|
|
arriflex
|
Posted: Sun Apr 13, 2008 12:19 am |
|
|
Joined: Thu Feb 23, 2006 2:41 pm
Posts: 68
|
|
I just had this happen as well, I commented out the bind-address field in mysql.cnf to facilitate additional front-ends connectivity as directed in the hints. Suddenly my capture cards are gone, and input connections are wiped out. I guess I could re-add them... it just seems strange that this would happen.
edit: Actually, it won't let me add them, when I press "finish," I just get back to the Capture Cards screen with
(New capture card)
(Delete all capture cards on mythtv)
(Delete all capture cards)
guess I'll try and un-comment my bind-address back and try again.
edit: nope, that didn't work either, I'll try deleting what isn't there and adding them back... nope, that doesn't work either.
crap.
sure wish I'd done a backup before I changed everything but the stinkin thing always tells me it failed anyway.
Yup, it didn't want to restore system, it just flew threw the phrases "restoring system," "verifying system," restoration failed" as quickly as it could play them as if it didn't even see my last backup.
I also ran the optimize_db.sh and rebooted between each of the above events.
I don't know what to do.
arri
_________________
Athlon 64 X2 4200+ 2GB Ram
MSI K8N Neo4-F NF4 939
ASUS N EN6200TC256/TD/64M
500gb SATA
1x Plextor PX-M402U
1x HD5000
R5.5 Upgrade from F27
|
|
| Top |
|
|
|
arriflex
|
Posted: Sun Apr 13, 2008 12:55 am |
|
|
Joined: Thu Feb 23, 2006 2:41 pm
Posts: 68
|
Well it definitely appears mysql related. As I tried using setup to add the cards manually, I was getting DB errors:
Code: DB error (CaptureCard::fillSelections):
Query was:
SELECT cardid, cardtype, videodevice FROM capturecard WHERE hostname = 'mythtv' AND parentid='0'
Driver error was [2/1054]:
QMYSQL3: Unable to execute query
Database error was:
Unknown column 'parentid' in 'where clause'
I think that means that my database is either sorely corrupted, or just not where or how it was meant to be.
All of this from wanting to add a front end. I did try and connect to this backend from both an osx frontend build that should have been the proper one (successfully), and an Ubuntu build that was likely newer than Knoppmyth's (not successfully).
I'm going to bed.
arri
_________________
Athlon 64 X2 4200+ 2GB Ram
MSI K8N Neo4-F NF4 939
ASUS N EN6200TC256/TD/64M
500gb SATA
1x Plextor PX-M402U
1x HD5000
R5.5 Upgrade from F27
|
|
| Top |
|
|
|
tjc
|
Posted: Sun Apr 13, 2008 8:14 am |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
arriflex wrote: sure wish I'd done a backup before I changed everything but the stinkin thing always tells me it failed anyway.
I'd really like to be able to fix whatever the problem is, but if people don't post their error logs when it happens it's basically impossible. Can't fix it if we don't know what's going wrong... 
|
|
| Top |
|
|
|
arriflex
|
Posted: Sun Apr 13, 2008 10:39 am |
|
|
Joined: Thu Feb 23, 2006 2:41 pm
Posts: 68
|
I'm sorry, it was late and I was frustrated, and there was actually a bottle of very nice wine having been consumed as well when the wife told me her CSI wasn't being recorded.
Anyway, excuses aside, I do appreciate your help...
the mysql.err log is empty, which I interpret as good.
syslog filtered for mysqld repeats almost identically the following for every reboot of the machine or restart of mysql (done when I changed the bind-address):
Code: Apr 12 23:29:48 mythtv mysqld_safe[3070]: started
Apr 12 23:29:48 mythtv mysqld[3073]: 080412 23:29:48 InnoDB: Started; log sequence number 0 43665
Apr 12 23:29:48 mythtv mysqld[3073]: 080412 23:29:48 [Note] /usr/sbin/mysqld: ready for connections.
Apr 12 23:29:48 mythtv mysqld[3073]: Version: '5.0.32-Debian_7etch1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch distribution
Apr 12 23:40:44 mythtv mysqld[3073]: 080412 23:40:44 [Note] /usr/sbin/mysqld: Normal shutdown
Apr 12 23:40:44 mythtv mysqld[3073]:
Apr 12 23:40:44 mythtv mysqld[3073]: 080412 23:40:44 InnoDB: Starting shutdown...
Apr 12 23:40:46 mythtv mysqld[3073]: 080412 23:40:46 InnoDB: Shutdown completed; log sequence number 0 43665
Apr 12 23:40:46 mythtv mysqld[3073]: 080412 23:40:46 [Note] /usr/sbin/mysqld: Shutdown complete
Apr 12 23:40:46 mythtv mysqld[3073]:
Apr 12 23:40:46 mythtv mysqld_safe[3772]: ended The newest stuff in my backend log is this: Code: 2008-04-07 06:02:06.094 EITScanner: Added 147 EIT Events
2008-04-07 06:02:06.097 Reschedule requested for id -1.
2008-04-07 06:02:06.254 Invalid search key in recordid 55
2008-04-07 06:02:08.817 Scheduled 755 items in 2.7 = 0.18 match + 2.54 place
2008-04-07 06:03:31.380 Expiring "Curious George" from Thu Mar 20 06:00:00 2008, 1116 MBytes, too many episodes (only want 5).
2008-04-07 06:03:31.414 Reschedule requested for id 0.
2008-04-07 06:03:33.919 Scheduled 755 items in 2.5 = 0.00 match + 2.50 place
2008-04-07 06:03:38.771 Reschedule requested for id 0.
2008-04-07 06:03:41.504 Scheduled 755 items in 2.7 = 0.00 match + 2.73 place
2008-04-07 06:06:16.265 DVBChan(0) Warning: Symbol Rate setting (0) is out of range (min/max:5056941/10762000)
2008-04-07 06:06:16.275 EITScanner: Now looking for EIT data on multiplex of channel 45_1
2008-04-07 06:07:28.896 EITScanner: Added 298 EIT Events
2008-04-07 06:07:28.899 Reschedule requested for id -1.
2008-04-07 06:07:29.080 Invalid search key in recordid 55
2008-04-07 06:07:31.779 Scheduled 755 items in 2.9 = 0.21 match + 2.67 place
2008-04-07 06:11:43.652 DVBChan(0) Warning: Symbol Rate setting (0) is out of range (min/max:5056941/10762000)
2008-04-07 06:11:43.664 EITScanner: Now looking for EIT data on multiplex of channel 23_1
2008-04-07 06:13:18.123 EITScanner: Added 148 EIT Events
2008-04-07 06:13:18.128 Reschedule requested for id -1.
2008-04-07 06:13:18.344 Invalid search key in recordid 55
2008-04-07 06:13:21.233 Scheduled 755 items in 3.1 = 0.25 match + 2.85 place
2008-04-07 06:17:11.014 DVBChan(0) Warning: Symbol Rate setting (0) is out of range (min/max:5056941/10762000)
2008-04-07 06:17:11.023 EITScanner: Now looking for EIT data on multiplex of channel 45_1
2008-04-07 06:18:23.711 EITScanner: Added 298 EIT Events
2008-04-07 06:18:23.716 Reschedule requested for id -1.
2008-04-07 06:18:23.887 Invalid search key in recordid 55
2008-04-07 06:18:26.550 Scheduled 755 items in 2.8 = 0.20 match + 2.64 place
2008-04-07 06:22:38.377 DVBChan(0) Warning: Symbol Rate setting (0) is out of range (min/max:5056941/10762000)
2008-04-07 06:22:38.391 EITScanner: Now looking for EIT data on multiplex of channel 23_1
2008-04-07 06:24:30.114 EITScanner: Added 147 EIT Events
2008-04-07 06:24:30.116 Reschedule requested for id -1.
2008-04-07 06:24:30.297 Invalid search key in recordid 55
2008-04-07 06:24:33.231 Scheduled 755 items in 3.1 = 0.21 match + 2.90 place
I keep reading that "The backup error should be harmless." Since it was giving me the "backup failed" within a week of a fresh install, I didn't pay much attention to it after reading a number of different comments by much smarter people than myself suggesting it wasn't important.
I'm not sure what to look for all in all. Given my restarts, the syslog is kind of full of what appear to me to be normal startup logs and I have an aversion to cluttering these forums with that kind of noise.
arri
_________________
Athlon 64 X2 4200+ 2GB Ram
MSI K8N Neo4-F NF4 939
ASUS N EN6200TC256/TD/64M
500gb SATA
1x Plextor PX-M402U
1x HD5000
R5.5 Upgrade from F27
|
|
| Top |
|
|
|
arriflex
|
Posted: Sun Apr 13, 2008 10:42 am |
|
|
Joined: Thu Feb 23, 2006 2:41 pm
Posts: 68
|
I'll take a shot at rolling back to a previous backup and restoring and grab those log files when I do.
gotta go do some reading first!
arri
_________________
Athlon 64 X2 4200+ 2GB Ram
MSI K8N Neo4-F NF4 939
ASUS N EN6200TC256/TD/64M
500gb SATA
1x Plextor PX-M402U
1x HD5000
R5.5 Upgrade from F27
|
|
| Top |
|
|
|
arriflex
|
Posted: Sun Apr 13, 2008 11:39 am |
|
|
Joined: Thu Feb 23, 2006 2:41 pm
Posts: 68
|
Something started happening when I ran optimize_db.sh, I still can't add cards though. Still working on a proper rollback restore...
my backend log...
Code: 2008-04-13 10:14:54.703 MainServer::HandleAnnounce Playback
2008-04-13 10:14:54.707 adding: mythtv as a client (events: 0)
2008-04-13 10:14:54.708 MainServer::HandleAnnounce Monitor
2008-04-13 10:14:54.708 adding: mythtv as a client (events: 1)
2008-04-13 10:15:36.437 Using runtime prefix = /usr
2008-04-13 10:15:36.461 New DB connection, total: 1
2008-04-13 10:15:36.466 Connected to database 'mythconverg' at host: localhost
2008-04-13 10:15:36.470 Current Schema Version: 1214
2008-04-13 10:15:36.472 New DB connection, total: 2
2008-04-13 10:15:36.473 Connected to database 'mythconverg' at host: localhost
2008-04-13 10:15:36.474 Newest Schema Version : 1160
2008-04-13 10:15:36.476 New DB connection, total: 3
2008-04-13 10:15:36.477 Connected to database 'mythconverg' at host: localhost
2008-04-13 10:15:36.477 Setting Lock for Database Schema upgrade. If you see a long pause here it means the Schema is already locked and is being upgraded by another Myth process.
2008-04-13 10:15:36.479 New DB connection, total: 4
2008-04-13 10:15:36.479 Connected to database 'mythconverg' at host: localhost
2008-04-13 10:15:36.480 Database Schema upgrade complete, unlocking.
Starting up as the master server.
ERROR: no valid capture cards are defined in the database.
Perhaps you should read the installation instructions?
2008-04-13 10:15:37.726 Main::Registering HttpStatus Extension
2008-04-13 10:15:37.729 mythbackend version: 0.20.20070821-1 www.mythtv.org
2008-04-13 10:15:37.729 Enabled verbose msgs: important general
2008-04-13 10:15:37.730 AutoExpire: Found 0 recorders w/max rate of 0 MiB/min
2008-04-13 10:15:37.732 AutoExpire: Required Free Space: 1.0 GB w/freq: 10 min and from the syslog at that time: Code: Apr 13 10:10:01 mythtv /USR/SBIN/CRON[13869]: (root) CMD (test -x /usr/local/bin/run_rrd && /usr/local/bin/run_rrd)
Apr 13 10:15:01 mythtv /USR/SBIN/CRON[13956]: (root) CMD (test -x /usr/local/bin/run_rrd && /usr/local/bin/run_rrd)
Apr 13 10:15:01 mythtv /USR/SBIN/CRON[13957]: (root) CMD ([ -x /usr/lib/sysstat/sa1 ] && { [ -r "$DEFAULT" ] && . "$DEFAULT" ; [ "$ENABLED" = "true" ] && exec /usr/lib/sysstat/sa1 $SA1_OPTIONS 1 1 ; })
Apr 13 10:15:12 mythtv mysqld[4040]: 080413 10:15:12 [Note] /usr/sbin/mysqld: Normal shutdown
Apr 13 10:15:12 mythtv mysqld[4040]:
Apr 13 10:15:12 mythtv mysqld[4040]: 080413 10:15:12 InnoDB: Starting shutdown...
Apr 13 10:15:13 mythtv mysqld[4040]: 080413 10:15:13 InnoDB: Shutdown completed; log sequence number 0 43665
Apr 13 10:15:13 mythtv mysqld[4040]: 080413 10:15:13 [Note] /usr/sbin/mysqld: Shutdown complete
Apr 13 10:15:13 mythtv mysqld[4040]:
Apr 13 10:15:13 mythtv mysqld_safe[14024]: ended
Apr 13 10:15:35 mythtv mysqld_safe[14290]: started
Apr 13 10:15:35 mythtv mysqld[14293]: 080413 10:15:35 InnoDB: Started; log sequence number 0 43665
Apr 13 10:15:35 mythtv mysqld[14293]: 080413 10:15:35 [Note] /usr/sbin/mysqld: ready for connections.
Apr 13 10:15:35 mythtv mysqld[14293]: Version: '5.0.32-Debian_7etch1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch distribution
Apr 13 10:15:36 mythtv /etc/mysql/debian-start[14327]: Upgrading MySQL tables if necessary.
Apr 13 10:15:36 mythtv /etc/mysql/debian-start[14344]: Checking for crashed MySQL tables.
Apr 13 10:17:01 mythtv /USR/SBIN/CRON[14415]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 13 10:17:23 mythtv lircd-0.8.2-CVS-pvr150[2999]: accepted new client on /dev/lircd
Apr 13 10:17:54 mythtv lircd-0.8.2-CVS-pvr150[2999]: removed client
Apr 13 10:20:01 mythtv /USR/SBIN/CRON[14728]: (root) CMD (test -x /usr/local/bin/run_rrd && /usr/local/bin/run_rrd)
_________________
Athlon 64 X2 4200+ 2GB Ram
MSI K8N Neo4-F NF4 939
ASUS N EN6200TC256/TD/64M
500gb SATA
1x Plextor PX-M402U
1x HD5000
R5.5 Upgrade from F27
|
|
| Top |
|
|
|
tjc
|
Posted: Sun Apr 13, 2008 12:07 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
The easiest thing to do is become root, run mythbackup from the command line and capture the output. We're generally only interested in the output from the checkbackup part that it does internally.
Also, do the backup diagnostics suggested in the R5F27 Hints to catch multiple ambiguous versions of the backup files...
|
|
| Top |
|
|
|
arriflex
|
Posted: Sun Apr 13, 2008 12:36 pm |
|
|
Joined: Thu Feb 23, 2006 2:41 pm
Posts: 68
|
I moved my troubleshooting of the backup and restore issues over to taking advantage of enhanced backup and restore scripts here:
http://mysettopbox.tv/phpBB2/viewtopic. ... 786#109786
I figured it was more appropriate in that thread than here.
I am curious, why would I want to backup a known bad state? I thought I should be trying to restore a known good state...
arri
_________________
Athlon 64 X2 4200+ 2GB Ram
MSI K8N Neo4-F NF4 939
ASUS N EN6200TC256/TD/64M
500gb SATA
1x Plextor PX-M402U
1x HD5000
R5.5 Upgrade from F27
|
|
| Top |
|
|
|
tjc
|
Posted: Sun Apr 13, 2008 1:39 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
arriflex wrote: I am curious, why would I want to backup a known bad state? I thought I should be trying to restore a known good state...
The suggestion was meant as a "how to gather diagnostics to report the problem you're having with the backup". If you get failures every time you run mythbackup or mythrestore I'd really like to know the cause so we can fix it before the upcoming 5.5 release.
|
|
| Top |
|
|
View unanswered posts
View active topics
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register
