Author |
Message |
tscholl
|
Posted: Tue Jul 08, 2008 1:28 pm |
|
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 997
Location:
Lexington, Ky
|
I ran into the following problem during an attempted upgrade.
Everything went smoothly until it got to this point:
Quote: Waiting for database upgrade to complete...................................................
From here on out the just keeps writing dots.
The contents of last 25 lines in the KnoppMyth-run.log look like this.
Code: root@mythtv:/var/log/mythtv# tail -25 KnoppMy* Generating a list of tables and record counts in the DB dump... Generating a list of tables and record counts in the live DB... Comparing live versus saved tables... Live and saved table lists match.
Restore passes all checks. Doing any needed file updates... Stopping MythTV server: mythbackend No /usr/bin/mythbackend found running; none killed. . Starting MythTV server: mythbackend. END mythrestore log You can configure your IR blasters as root by running irblaster.sh You can reconfigure the screensaver as root by running configure_xscreensaver.sh 'mythtv' web user account setup ... Using old MythWeb password. Run ToggleWebSecurity.sh to toggle security off or on. --- Starting Apache...
Stopping mythtv-backend... Restarting LIRC
Starting mythtv-backend... And when I grep the process I see this. Code: root@mythtv:/var/log/mythtv# ps -ef | grep KnoppMyth-run mythtv 3455 3414 0 14:48 ? 00:00:01 xterm -fn *18* +sb -T Configuration: -e sh -c ??BADPASSWORD=1??echo -en '\n ?[34mPlease provide the ?[31mroot?[0m '??while [[ $BADPASSWORD == 1 ]]??do???su -p -c "KnoppMyth-run -~" -???BADPASSWORD=$???done?? mythtv 3469 3455 0 14:48 ttyp0 00:00:00 sh -c ??BADPASSWORD=1??echo -en '\n ?[34mPlease provide the ?[31mroot?[0m '??while [[ $BADPASSWORD == 1 ]]??do???su -p -c "KnoppMyth-run -~" -???BADPASSWORD=$???done?? root 3471 3469 0 14:48 ttyp0 00:00:00 su -p -c KnoppMyth-run -~ - root 3472 3471 0 14:48 ttyp0 00:00:00 /bin/bash /usr/local/bin/KnoppMyth-run -~ root 6232 5206 0 15:07 ttyp1 00:00:00 grep KnoppMyth-run
All userid and password are the same. I tried it a second time with the same results. If I shutdown the machine is does come up but has problems with keyboard keys repeating. Did the upgrade really finish?
Any ideas or suggestions?
|
|
Top |
|
|
mythman13
|
Posted: Tue Jul 08, 2008 3:14 pm |
|
Joined: Sun Sep 02, 2007 2:30 pm
Posts: 94
|
Sorry I can't be of any help but just so you know you're not alone, but the same thing ahppened when I tried to upgrade from R5F27.
No idea why, I waited for a bit before power cycling the PC. The install media was tested to be OK. I then tried again and the upgrade seemed to wipe my /myth partition! So I then opted for a clean install as none of the scripts came up right at first boot (since it never really got there the first time).
Mythman
|
|
Top |
|
|
tjc
|
Posted: Tue Jul 08, 2008 6:34 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
tscholl wrote: Did the upgrade really finish?
Yes. There's not really anything in the scripts after that point and various testers saw this failure to detect completion kind of intermittently. Human can comment further...
|
|
Top |
|
|
Human
|
Posted: Tue Jul 08, 2008 7:38 pm |
|
Joined: Thu Sep 30, 2004 11:29 am
Posts: 2419
Location:
Mechanicsburg, PA
|
Can you post the results of this command?
Code: tail -50 /var/log/mythtv/mythbackend.log
KnoppMyth-run is looking for a string ("Seem to be woken up by USER") that indicates the backend is up and running. If it doesn't find it, it'll loop. As for why it's looping, I (and/or others) would need to see what's in your backend log instead of the expected string.
EDIT: My command went away... Or I was tired. In any case, it's there now.
_________________ KnoppMyth R5.5
MythiC Dragon v2.0
Join the KnoppMyth Frappr!
Last edited by Human on Wed Jul 09, 2008 9:05 am, edited 1 time in total.
|
|
Top |
|
|
mjl
|
Posted: Tue Jul 08, 2008 8:04 pm |
|
Joined: Sun Jun 12, 2005 10:55 pm
Posts: 3161
Location:
Warwick, RI
|
Hi,
Do you have an older nvidia card? I found if the driver is nv my keys would do multi steps. Changed to nvidia and rebooted. Been fine since.
Mike
|
|
Top |
|
|
bigB
|
Posted: Tue Jul 08, 2008 8:34 pm |
|
Joined: Mon Feb 06, 2006 5:11 pm
Posts: 353
Location:
Brisbane, Australia
|
Human,
What would happen if the backend believed it was due to start a recording?
|
|
Top |
|
|
tscholl
|
Posted: Tue Jul 08, 2008 9:08 pm |
|
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 997
Location:
Lexington, Ky
|
Human wrote: Can you post the results of this command?
I will have a look tomorrow and post what I find in the backend log.
mjl
I did have an older nvidia card installed at one time but it has been removed. Where do I need to look to check the driver?
|
|
Top |
|
|
mjl
|
Posted: Tue Jul 08, 2008 9:31 pm |
|
Joined: Sun Jun 12, 2005 10:55 pm
Posts: 3161
Location:
Warwick, RI
|
Hi,
Just to check, open an xterm the do less /etc/X11/xorg.conf
Page down to bottom, then page up once a couple of up arrows should show Driver "nv"
If true switch to su -
and do nano -w /etc/X11/xorg.conf
go to the same place and change to "nvidia" exit and save then press crtl alt bksp to restart the xserver. You may not have to reboot.
No guarentees that is your issue, but is something to investigate.
Mike
|
|
Top |
|
|
Human
|
Posted: Wed Jul 09, 2008 9:07 am |
|
Joined: Thu Sep 30, 2004 11:29 am
Posts: 2419
Location:
Mechanicsburg, PA
|
bigB wrote: What would happen if the backend believed it was due to start a recording?
I believe it'd still need to produce the string I'm looking for in the backend log before it can start recording anything. If that's not the case, I'll need to look for more than what I look for now.
_________________ KnoppMyth R5.5
MythiC Dragon v2.0
Join the KnoppMyth Frappr!
|
|
Top |
|
|
tscholl
|
Posted: Wed Jul 09, 2008 10:53 am |
|
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 997
Location:
Lexington, Ky
|
mjl,
Great catch, my xorg.conf had vesa (which also gave a blackscreen on startup) and I had to change it to vga. That fixed the multi step key problem.
Human,
Here is the mythbackend.log it shows both installs.
This is my test box so the errors about the video cards, and schedulesdirect are expected.
|
|
Top |
|
|
Human
|
Posted: Wed Jul 09, 2008 11:23 am |
|
Joined: Thu Sep 30, 2004 11:29 am
Posts: 2419
Location:
Mechanicsburg, PA
|
Hmm, you have
Code: Starting up as the master server. as well as Code: mythbackend: MythBackend started as master server but not Code: Seem to be woken up by USER
I could change KnoppMyth-run to look for the first or second string instead, but I'm guessing it'd fail to match slave backends. Can someone with a slave backend post their backend logs, too, so I can find a general pattern?
_________________ KnoppMyth R5.5
MythiC Dragon v2.0
Join the KnoppMyth Frappr!
|
|
Top |
|
|
stevenj
|
Posted: Sun Jul 13, 2008 9:11 pm |
|
Joined: Thu Jan 01, 2004 9:21 pm
Posts: 84
Location:
Fort Collins, CO USA
|
Here's my mythbackend.log from one of my slave backends. I had this problem on my master and both my slave backends.
2008-07-13 19:27:33.934 Using runtime prefix = /usr 2008-07-13 19:27:34.032 Empty LocalHostName. 2008-07-13 19:27:34.037 Using localhost value of latitude 2008-07-13 19:27:34.320 New DB connection, total: 1 2008-07-13 19:27:34.354 Connected to database 'mythconverg' at host: localhost 2008-07-13 19:27:34.365 Closing DB connection named 'DBManager0' 2008-07-13 19:27:34.376 Connected to database 'mythconverg' at host: localhost 2008-07-13 19:27:34.521 New DB connection, total: 2 2008-07-13 19:27:34.527 Connected to database 'mythconverg' at host: localhost 2008-07-13 19:27:34.535 Current Schema Version: 2008-07-13 19:27:34.539 DataDirectProcessor::FixProgramIDs() -- begin 2008-07-13 19:27:34.543 New DB DataDirect connection 2008-07-13 19:27:34.546 Connected to database 'mythconverg' at host: localhost 2008-07-13 19:27:34.551 DB Error (Fixing program ids in recorded): Query was: UPDATE recorded SET programid=CONCAT(SUBSTRING(programid, 1, 2), '00', SUBSTRING(programid, 3)) WHERE length(programid) = 12 Driver error was [2/1146]: QMYSQL3: Unable to execute query Database error was: Table 'mythconverg.recorded' doesn't exist
2008-07-13 19:27:34.558 DB Error (Clear setting): Query was: DELETE FROM settings WHERE value = 'BackupDBLastRunStart' AND hostname is NULL; Driver error was [2/1146]: QMYSQL3: Unable to execute query Database error was: Table 'mythconverg.settings' doesn't exist
2008-07-13 19:27:34.561 DB Error (SaveSettingOnHost query failure: ): Query was: INSERT INTO settings (value,data,hostname ) VALUES ( 'BackupDBLastRunStart', '2008-07-13 19:27:34', NULL ); Driver error was [2/1146]: QMYSQL3: Unable to execute query Database error was: Table 'mythconverg.settings' doesn't exist
2008-07-13 19:27:34.567 DB Error (StorageGroup::StorageGroup()): Query was: SELECT DISTINCT dirname FROM storagegroup WHERE groupname = 'DB Backups' AND hostname = 'latitude' Driver error was [2/1146]: QMYSQL3: Unable to execute query Database error was: Table 'mythconverg.storagegroup' doesn't exist
2008-07-13 19:27:34.570 New DB connection, total: 3 2008-07-13 19:27:34.573 Connected to database 'mythconverg' at host: localhost 2008-07-13 19:27:34.577 SG(DB Backups) Error: Directory value for Default Storage Group is empty. Using hardcoded default value of '/mnt/store' 2008-07-13 19:27:34.643 SG(DB Backups) Error: FindNextDirMostFree: '/mnt/store' does not exist! 2008-07-13 19:27:34.648 Backing up database to file: /tmp/mythconverg--20080713192734.sql 2008-07-13 19:27:34.806 Compressing database backup file. 2008-07-13 19:27:34.960 Database Backup filename: /tmp/mythconverg--20080713192734.sql.gz 2008-07-13 19:27:34.968 Database Backup complete. 2008-07-13 19:27:34.974 DB Error (Clear setting): Query was: DELETE FROM settings WHERE value = 'BackupDBLastRunEnd' AND hostname is NULL; Driver error was [2/1146]: QMYSQL3: Unable to execute query Database error was: Table 'mythconverg.settings' doesn't exist
2008-07-13 19:27:34.978 DB Error (SaveSettingOnHost query failure: ): Query was: INSERT INTO settings (value,data,hostname ) VALUES ( 'BackupDBLastRunEnd', '2008-07-13 19:27:34', NULL ); Driver error was [2/1146]: QMYSQL3: Unable to execute query Database error was: Table 'mythconverg.settings' doesn't exist
2008-07-13 19:27:34.982 No current database version. Auto upgrading 2008-07-13 19:27:34.986 Newest Schema Version : 1214 2008-07-13 19:27:34.993 Inserting MythTV initial database information. 2008-07-13 19:27:35.142 Upgrading to schema version 1112 2008-07-13 19:27:37.182 New DB connection, total: 4 2008-07-13 19:27:37.528 Connected to database 'mythconverg' at host: localhost 2008-07-13 19:27:37.687 Upgrading to schema version 1113 2008-07-13 19:27:37.842 Upgrading to schema version 1114 2008-07-13 19:27:38.016 Upgrading to schema version 1115 2008-07-13 19:27:38.273 Upgrading to schema version 1116 2008-07-13 19:27:38.549 Upgrading to schema version 1117 2008-07-13 19:27:38.854 Upgrading to schema version 1118 2008-07-13 19:27:39.376 Upgrading to schema version 1119 2008-07-13 19:27:39.528 Upgrading to schema version 1120 2008-07-13 19:27:39.894 Upgrading to schema version 1121 2008-07-13 19:27:40.699 Upgrading to schema version 1122 2008-07-13 19:27:41.106 Upgrading to schema version 1123 2008-07-13 19:27:41.506 Upgrading to schema version 1124 2008-07-13 19:27:41.802 Upgrading to schema version 1125 2008-07-13 19:27:42.242 Upgrading to schema version 1126 2008-07-13 19:27:42.521 Upgrading to schema version 1127 2008-07-13 19:27:42.824 Upgrading to schema version 1128 2008-07-13 19:27:43.109 Upgrading to schema version 1129 2008-07-13 19:27:43.619 Upgrading to schema version 1130 2008-07-13 19:27:43.648 Upgrading to schema version 1131 2008-07-13 19:27:43.814 Upgrading to schema version 1132 2008-07-13 19:27:43.881 Upgrading to schema version 1133 2008-07-13 19:27:43.903 Upgrading to schema version 1134 2008-07-13 19:27:43.912 Upgrading to schema version 1135 2008-07-13 19:27:43.931 Upgrading to schema version 1136 2008-07-13 19:27:43.947 Upgrading to schema version 1137 2008-07-13 19:27:43.963 Upgrading to schema version 1138 2008-07-13 19:27:43.971 Upgrading to schema version 1139 2008-07-13 19:27:44.010 Upgrading to schema version 1140 2008-07-13 19:27:44.017 Upgrading to schema version 1141 2008-07-13 19:27:44.039 Upgrading to schema version 1142 2008-07-13 19:27:44.065 Upgrading to schema version 1143 2008-07-13 19:27:44.081 Upgrading to schema version 1144 2008-07-13 19:27:44.090 Upgrading to schema version 1145 2008-07-13 19:27:44.100 Upgrading to schema version 1146 2008-07-13 19:27:44.108 Upgrading to schema version 1147 2008-07-13 19:27:44.131 Upgrading to schema version 1148 2008-07-13 19:27:44.174 Upgrading to schema version 1149 2008-07-13 19:27:44.191 Upgrading to schema version 1150 2008-07-13 19:27:44.198 Upgrading to schema version 1151 2008-07-13 19:27:44.222 Upgrading to schema version 1152 2008-07-13 19:27:44.237 Upgrading to schema version 1153 2008-07-13 19:27:44.290 Upgrading to schema version 1154 2008-07-13 19:27:44.317 Upgrading to schema version 1155 2008-07-13 19:27:44.340 Upgrading to schema version 1156 2008-07-13 19:27:44.356 Upgrading to schema version 1157 2008-07-13 19:27:44.364 Upgrading to schema version 1158 2008-07-13 19:27:44.438 Upgrading to schema version 1159 2008-07-13 19:27:44.456 Upgrading to schema version 1160 2008-07-13 19:27:44.463 Upgrading to schema version 1161 2008-07-13 19:27:44.478 Upgrading to schema version 1162 2008-07-13 19:27:44.487 Upgrading to schema version 1163 2008-07-13 19:27:44.491 Upgrading to schema version 1164 2008-07-13 19:27:44.564 Upgrading to schema version 1165 2008-07-13 19:27:44.582 Upgrading to schema version 1166 2008-07-13 19:27:44.604 Upgrading to schema version 1167 2008-07-13 19:27:44.612 Upgrading to schema version 1168 2008-07-13 19:27:44.622 Upgrading to schema version 1169 2008-07-13 19:27:44.631 Upgrading to schema version 1170 2008-07-13 19:27:44.636 Upgrading to schema version 1171 2008-07-13 19:27:44.685 Upgrading to schema version 1172 2008-07-13 19:27:44.697 Upgrading to schema version 1173 2008-07-13 19:27:44.730 Upgrading to schema version 1174 2008-07-13 19:27:44.738 Upgrading to schema version 1175 2008-07-13 19:27:44.746 Upgrading to schema version 1176 2008-07-13 19:27:44.751 Upgrading to schema version 1177 2008-07-13 19:27:44.764 Upgrading to schema version 1178 2008-07-13 19:27:45.226 Upgrading to schema version 1179 2008-07-13 19:27:46.329 Upgrading to schema version 1180 2008-07-13 19:27:46.545 Upgrading to schema version 1181 2008-07-13 19:27:47.027 Upgrading to schema version 1182 2008-07-13 19:27:47.257 Upgrading to schema version 1183 2008-07-13 19:27:47.565 Upgrading to schema version 1184 2008-07-13 19:27:47.861 Upgrading to schema version 1185 2008-07-13 19:27:48.114 Upgrading to schema version 1186 2008-07-13 19:27:48.209 Upgrading to schema version 1187 2008-07-13 19:27:48.312 Upgrading to schema version 1188 2008-07-13 19:27:48.326 Upgrading to schema version 1189 2008-07-13 19:27:48.340 Upgrading to schema version 1190 2008-07-13 19:27:48.503 Upgrading to schema version 1191 2008-07-13 19:27:48.660 Upgrading to schema version 1192 2008-07-13 19:27:48.816 Upgrading to schema version 1193 2008-07-13 19:27:48.864 Upgrading to schema version 1194 2008-07-13 19:27:48.882 Upgrading to schema version 1195 2008-07-13 19:27:49.031 Upgrading to schema version 1196 2008-07-13 19:27:49.202 Upgrading to schema version 1197 2008-07-13 19:27:49.379 Upgrading to schema version 1198 2008-07-13 19:27:49.578 Upgrading to schema version 1199 2008-07-13 19:27:49.730 Upgrading to schema version 1200 2008-07-13 19:27:49.882 Upgrading to schema version 1201 2008-07-13 19:27:49.894 Upgrading to schema version 1202 2008-07-13 19:27:50.287 Upgrading to schema version 1203 2008-07-13 19:27:50.538 Upgrading to schema version 1204 2008-07-13 19:27:50.646 Upgrading to schema version 1205 2008-07-13 19:27:50.659 Upgrading to schema version 1206 2008-07-13 19:27:50.667 Upgrading to schema version 1207 2008-07-13 19:27:50.690 Upgrading to schema version 1208 2008-07-13 19:27:51.082 Upgrading to schema version 1209 2008-07-13 19:27:51.492 Upgrading to schema version 1210 2008-07-13 19:27:52.381 Upgrading to schema version 1211 2008-07-13 19:27:53.272 Upgrading to schema version 1212 2008-07-13 19:27:53.411 Upgrading to schema version 1213 2008-07-13 19:27:53.422 In 1213 upg 2008-07-13 19:27:53.427 Upgrading to schema version 1214 2008-07-13 19:27:53.431 Database Schema upgrade complete, unlocking. No setting found for this machine's BackendServerIP. Please run setup on this machine and modify the first page of the general settings. 2008-07-13 20:31:36.960 Using runtime prefix = /usr 2008-07-13 20:31:37.150 Empty LocalHostName. 2008-07-13 20:31:37.153 Using localhost value of latitude 2008-07-13 20:31:37.156 Testing network connectivity to mythtv1 2008-07-13 20:31:37.291 New DB connection, total: 1 2008-07-13 20:31:37.337 Connected to database 'mythconverg' at host: mythtv1 2008-07-13 20:31:37.487 Closing DB connection named 'DBManager0' 2008-07-13 20:31:37.562 Connected to database 'mythconverg' at host: mythtv1 2008-07-13 20:31:37.745 New DB connection, total: 2 2008-07-13 20:31:37.750 Connected to database 'mythconverg' at host: mythtv1 2008-07-13 20:31:37.960 Current Schema Version: 1214 2008-07-13 20:31:38.043 DataDirectProcessor::FixProgramIDs() -- begin 2008-07-13 20:31:38.068 New DB DataDirect connection 2008-07-13 20:31:38.073 Connected to database 'mythconverg' at host: mythtv1 2008-07-13 20:31:40.521 DataDirectProcessor::FixProgramIDs() -- end Running as a slave backend. ERROR: no valid capture cards are defined in the database. Perhaps you should read the installation instructions? 2008-07-13 20:31:41.473 Main::Registering HttpStatus Extension 2008-07-13 20:31:41.746 mythbackend version: 0.21.20080304-1 www.mythtv.org 2008-07-13 20:31:41.829 Enabled verbose msgs: important general 2008-07-13 20:31:42.900 Connecting to master server: 192.168.0.220:6543 2008-07-13 20:31:42.907 Connected successfully 2008-07-13 20:32:11.994 Using runtime prefix = /usr 2008-07-13 20:32:12.001 Empty LocalHostName. 2008-07-13 20:32:12.004 Using localhost value of latitude 2008-07-13 20:32:12.008 Testing network connectivity to mythtv1 2008-07-13 20:32:12.138 New DB connection, total: 1 2008-07-13 20:32:12.183 Connected to database 'mythconverg' at host: mythtv1 2008-07-13 20:32:12.274 Closing DB connection named 'DBManager0' 2008-07-13 20:32:12.318 Connected to database 'mythconverg' at host: mythtv1 2008-07-13 20:32:12.425 New DB connection, total: 2 2008-07-13 20:32:12.523 Connected to database 'mythconverg' at host: mythtv1 2008-07-13 20:32:12.608 Current Schema Version: 1214 Running as a slave backend. ERROR: no valid capture cards are defined in the database. Perhaps you should read the installation instructions? 2008-07-13 20:32:12.648 New DB connection, total: 3 2008-07-13 20:32:12.659 Connected to database 'mythconverg' at host: mythtv1 2008-07-13 20:32:13.286 Main::Registering HttpStatus Extension 2008-07-13 20:32:13.308 mythbackend version: 0.21.20080304-1 www.mythtv.org 2008-07-13 20:32:13.309 Enabled verbose msgs: important general 2008-07-13 20:32:14.318 Connecting to master server: 192.168.0.220:6543 2008-07-13 20:32:14.330 Connected successfully
|
|
Top |
|
|
tjc
|
Posted: Sun Jul 13, 2008 9:51 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Looks like you need to run mythtv-setup on each of your BE machines and define your capture cards...
|
|
Top |
|
|
Human
|
Posted: Mon Jul 14, 2008 1:01 pm |
|
Joined: Thu Sep 30, 2004 11:29 am
Posts: 2419
Location:
Mechanicsburg, PA
|
tjc wrote: Looks like you need to run mythtv-setup on each of your BE machines and define your capture cards...
Shouldn't that information have survived the upgrade?
_________________ KnoppMyth R5.5
MythiC Dragon v2.0
Join the KnoppMyth Frappr!
|
|
Top |
|
|
tjc
|
Posted: Mon Jul 14, 2008 6:33 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Yeah, think so, but who knows what else happened. Hostname changes, missing /etc/hosts, ...
|
|
Top |
|
|