2 Problems after 810B2 update from 2/23/2010

[craasch]

I did the apt-get update/dist-upgrade update on 2/24/2010 and have run into a serious "snag".

My core upgrade just fine.  I decided to delete my MDs and let the rebuild so they would be cleaner.

The MDs go through the first phase of setup and build the image.  After reboot they fail.  I tracked it down to bad symlinks in tftboot pointing to a non-existent /usr/pluto/diskless/xx/boot/vmlinuz-2.6.27-17-generic and matching initrd.img files.

What kernel version should it be? Did my upgrade miss files?  If so how can I fix?

I copied the -16- file to -17- to ge the md to boot, which allowed it to boot again.  System seems to run but Myth will die in about 1min of live tv.  Using another machine as a remote, it never notifies what station is being loaded, nor does remote channel selection work.  It also does not jump directly into live tv, it just launches myth.  It seems to indicate a communication problem, but I don't know how to research from here.

Thanks in advance.

[phenigma]

The MD rebuild restores the MDs to the state they were in when you first ran /usr/pluto/bin/Diskless_CreateTBZ.sh.  None of the updates/upgrades applied to the core since that time will exist in your rebuilt MDs.  It looks like a mismatch has arisen with a new kernel installed on your core and the MDs not being updated appropriately.

I think that re-running /usr/pluto/bin/Diskless_CreateTBZ.sh on your core and then rebuilding your MDs will fix the kernel mismatch problem... it may also fix your other problems, I'm not certain though.

J.

[ccoudsi]

phenigma,
It happened to me too, I had to recreate the link with the current "16" after MD booted I updated and it went to version "17"

[craasch]

Thanks phenigma, the Diskless_CreateTBZ.sh fixed the image problem, still having trouble with myth.

My impression is that the myth scripts aren't firing, as I can't change channel remotely, nor does it show current status remotely.

Also when myth starts, it just goes to menu, it doesn't go into tv.

My core is fine, just something with the MD orbiters.

Chris

[phenigma]

Have you run mythtv-setup from the computing menu on your MDs yet?  Be sure to run it from the computing menu.  I seem to recall something about having to run it on each MD before myth would work properly.

J.

[craasch]

I tried running the myth-setup from the computing menu, and it had no change.

Loaded another MD, same issues.

Myth just launches just doesn't seem to communicate, I would really like to avoid a rebuild, is there a way to re-run the previous scripts?  If the one didn't run, what other scripts do I need to rerun?

Chris

[phenigma]

Myth just launches just doesn't seem to communicate, I would really like to avoid a rebuild, is there a way to re-run the previous scripts?  If the one didn't run, what other scripts do I need to rerun?

It's not that a script didn't run, it's that the /usr/pluto/bin/Diskless_CreateTBZ.sh script takes a long time to run and is often run only when the core is first installed.  It is currently left to the user to run the above script it if he/she wants to install an MD (some people use only a hybrid and have no need to wait for the initial MD image to build).  The script can be run again to update the initial MD image.

I don't think you'll need to re-install your system, your core works... so it must be a myth config issue or a network issue.  I havn't been running myth lately.... been watching HD olympics (I've no way, currently, to get HD tv into LMCE). 

J.

[craasch]

To add some more information:

I can watch MPG movies on the MD without issue (from a quick test), but mythtv is being actively shutdown after a minute or so, even if just left to sit at the main screen.  When myth closes there is a brief flash of a blue info screen, but too fast to read, then back to the main UI2 screen.

I need to get this issue resolved soon, or I will have a family revolt on my hands.

[craasch]

Looking through the logs I found the following in my logs, just hoping someone knows what it may mean.  Thanks in advance.

Chris

01   03/02/10 6:18:30.346      Unable to connect to MythTV client <0xb78dfb90>
05   03/02/10 6:18:30.346      MythTV_Player::pollMythStatus no jump livetv  <0xb78dfb90>
05   03/02/10 6:18:30.445      Going to send command jump livetv <0xb78dfb90>
05   03/02/10 6:18:31.489      Connect() failed, Error Code 111 (Connection refused)) <0xb78dfb90>
05   03/02/10 6:18:32.489      Connect() failed, Error Code 111 (Connection refused)) <0xb78dfb90>
05   03/02/10 6:18:33.489      Connect() failed, Error Code 111 (Connection refused)) <0xb78dfb90>
05   03/02/10 6:18:33.490      ClientSocket::Connect() not successful <0xb78dfb90>
05   03/02/10 6:18:33.490      void ClientSocket::Disconnect() on this socket: 0x9253188 (m_Socket: <0xb78dfb90>
01   03/02/10 6:18:33.490      Unable to connect to MythTV client <0xb78dfb90>
05   03/02/10 6:18:33.490      MythTV_Player::pollMythStatus no jump livetv  <0xb78dfb90>
01   03/02/10 6:18:33.490      Failed initial communications with Mythfrontend. <0xb78dfb90>
01   03/02/10 6:18:33.515      Killed Mythfrontend. <0xb78dfb90>
05   03/02/10 6:18:33.522      Going to send command quit <0xb68ddb90>
05   03/02/10 6:18:34.713      Connect() failed, Error Code 111 (Connection refused)) <0xb68ddb90>
05   03/02/10 6:18:35.713      Connect() failed, Error Code 111 (Connection refused)) <0xb68ddb90>
05   03/02/10 6:18:36.713      Connect() failed, Error Code 111 (Connection refused)) <0xb68ddb90>
05   03/02/10 6:18:36.713      ClientSocket::Connect() not successful <0xb68ddb90>
05   03/02/10 6:18:36.714      void ClientSocket::Disconnect() on this socket: 0x9281830 (m_Socket: <0xb68ddb90>
01   03/02/10 6:18:36.714      Unable to connect to MythTV client <0xb68ddb90>