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?

_________________
Intel DG965WH, Dvico DVB-T Lite x2, HDHR, Gigabyte GT220, KingstonSSD, WD20EARS version=latest

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

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:

I will start trawling through the logs

_________________
Intel DG965WH, Dvico DVB-T Lite x2, HDHR, Gigabyte GT220, KingstonSSD, WD20EARS version=latest

The /var/log/mythtv/mythfrontend.log is full of errorsDoes this help anyone?

_________________
Intel DG965WH, Dvico DVB-T Lite x2, HDHR, Gigabyte GT220, KingstonSSD, WD20EARS version=latest

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 7.4
Australian Dragon
*********************

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?

_________________
Intel DG965WH, Dvico DVB-T Lite x2, HDHR, Gigabyte GT220, KingstonSSD, WD20EARS version=latest

I just tried restarting mysql with It seemed to start OK and got a PID number but still no luck. I noticed /var/log/mysqld.log is empty.

_________________
Intel DG965WH, Dvico DVB-T Lite x2, HDHR, Gigabyte GT220, KingstonSSD, WD20EARS version=latest

Am I looking at a reinstall to fix this?

_________________
Intel DG965WH, Dvico DVB-T Lite x2, HDHR, Gigabyte GT220, KingstonSSD, WD20EARS version=latest

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.

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.

_________________
Intel DG965WH, Dvico DVB-T Lite x2, HDHR, Gigabyte GT220, KingstonSSD, WD20EARS version=latest

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.)

This is good information. I will try to look at this for R7.

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.

_________________
Intel DG965WH, Dvico DVB-T Lite x2, HDHR, Gigabyte GT220, KingstonSSD, WD20EARS version=latest