nicom wrote:
Does this help anyone?
Well not you obviously
Clearly mysql needed to be running for the command but wasn't. I would try and start. Chances are, it will not start but will give you a clue as to why.
| LinHES Forums http://forums.linhes.org/ |
|
| Fails to boot past splash screen -SOLVED http://forums.linhes.org/viewtopic.php?f=21&t=21611 |
Page 1 of 1 |
| Author: | nicom [ Wed Sep 15, 2010 4:15 am ] |
| Post subject: | Fails to boot past splash screen -SOLVED |
I've broken it. Help needed urgently. I was attempting to change the type of machine from Standalone to Master backend. The process started and then went into a process of updating the database with a rolling progress bar This continued for about an hour and as I was running out of time I assumed it was stuck and rebooted. Now it does not boot beyond the splash screen. The backend is running and it is recording shows. Even the ACPI wakeup and shutdown when idle works . I can SSH into it so I tried restoring with mythrestore and it seemed to go OK, but no change after a reboot. Can anyone help? |
|
| Author: | craigtv [ Wed Sep 15, 2010 9:03 am ] |
| Post subject: | |
The master backend configuration doesn't start X or a frontend by default. It's actually booting and working as designed. Follow this post for instructions on adding back the frontend: http://mysettopbox.tv/phpBB2/viewtopic.php?t=20182 Craig |
|
| Author: | nicom [ Wed Sep 15, 2010 5:48 pm ] |
| Post subject: | |
Thanks for the response. I checked the contents of /var/service and frontend is present as a link to /etc/sv/frontend which has the following contents: Code: $ ls -l /etc/sv/frontend
total 16 -rwxr-xr-x 1 root root 1496 2010-01-31 14:19 finish drwxr-xr-x 3 root root 4096 2010-08-01 12:17 log -rwxr-xr-x 1 root root 389 2009-09-09 02:50 run drwx------ 2 root root 4096 2010-09-15 19:53 supervise $ I will start trawling through the logs |
|
| Author: | nicom [ Wed Sep 15, 2010 6:07 pm ] |
| Post subject: | |
The /var/log/mythtv/mythfrontend.log is full of errors Code: ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111) Does this help anyone?
-c restore -t syssettings -d 127.0.0.1 failed c restore t syssettings template is syssettings d 127.0.0.1 0 ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111) -c restore -t syssettings -d 127.0.0.1 failed mythinstall: Fatal IO error: client killed mythfrontend: Fatal IO error: client killed |
|
| Author: | manicmike [ Wed Sep 15, 2010 8:22 pm ] |
| Post subject: | |
nicom wrote: Does this help anyone?
Well not you obviously
Clearly mysql needed to be running for the command but wasn't. I would try and start. Chances are, it will not start but will give you a clue as to why. |
|
| Author: | nicom [ Wed Sep 15, 2010 8:37 pm ] |
| Post subject: | |
Mike, I just tried rebooting and looking at the logs but I can't find anything of note. Which logs do you suggest I look at? |
|
| Author: | nicom [ Wed Sep 15, 2010 10:20 pm ] |
| Post subject: | |
I just tried restarting mysql with Code: sudo sv start mysql It seemed to start OK and got a PID number but still no luck. I noticed /var/log/mysqld.log is empty.
|
|
| Author: | nicom [ Thu Sep 16, 2010 6:58 pm ] |
| Post subject: | |
Am I looking at a reinstall to fix this? |
|
| Author: | snaproll [ Thu Sep 16, 2010 8:14 pm ] |
| Post subject: | |
I had this, hung at 27% checking files..... After about an hour it cleared and finished..... It wasn't hung. it was just taking a really long time checking the files.... Hope this is your case too. |
|
| Author: | nicom [ Thu Sep 16, 2010 9:00 pm ] |
| Post subject: | |
I am afraid it is not the same. It is well and truly hung with the frontend refusing to start for 3 days now. If I cannot solve it will an upgrade rather than clean install fix it? Using that with backup/restore I should be easier. |
|
| Author: | snaproll [ Fri Sep 17, 2010 5:02 am ] |
| Post subject: | |
Well, in the absence of ideas as to what else it is, I would move on with getting it working. I've always had better luck with clean installs than upgrades, but it only costs a little extra time to try an upgrade first. (I have always considered the content on my Mythboxes expendable, but then I am running several..... If I had any files I considered important, I copied them to off Mythbox storage.) |
|
| Author: | jams [ Sun Sep 19, 2010 4:15 pm ] |
| Post subject: | |
This is good information. I will try to look at this for R7. |
|
| Author: | nicom [ Sun Sep 19, 2010 9:10 pm ] |
| Post subject: | |
Well I managed to get it back working after a lot of possibly unnecessary work. Firstly I tried an update installation - no change. Then I tried a complete installation and got it back working. When I performed the mythrestore the problem came back and I was no longer able to start to the frontend. So finally I tried a restore with an even older backup (.gz.3) and it now works. I had already tried .gz.1 and .gz.2 but they did not work. It is quite possible that my automatic backup every 10 boots was triggered a couple of times during my debugging. It all makes me think that if I had done the older restore sooner I might have saved myself a lot of work. I then had to rebuild the database to find the new recordings since the backup. Just trying "myth.rebuilddatabase.pl --try_default" would not work and gave an error saying cannot connect to db. I then modified the /usr/bin/myth.rebuilddatabase.pl script as recommended in segamifo's post and it worked. Definitely something to think about for R7 or an update. I still have more work to get it back to correct functionality. I don't think I will play with master backend again unless it's on a test machine. |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|