Messages

1

Users / MythTV_Plugin keeps restarting the backend (810)

« on: March 08, 2010, 07:06:40 pm »

I have a fairly minimal setup. A Hybrid and 1 MD.
The hybrid is a core 2 dual-core with 4GB ram and a nvidia 8800 GT video card.
The MD is a Athlon XP with 1 GB ram and and a nvidia 6800 GT.

I had been using this setup with lmce 710 for quite some time without issue.
Even 810 Beta2 has been fairly stable.

The problem is that mythtv_plugin continuously restarts mythbackend because it thinks something is wrong even though everything is running fine. I've spent quite some time trying to debug this on my own and reinstalled the entire system numerous times but no luck.

I've attached a portion of DCErouter.log. This pattern keeps repeating making mythtv unusable until the maximum restart limit is reached after which point mythtv_plugin stops restarting the backend and Mythtv becomes usable (although significantly less responsive). Basically, each time I restart the core, I have to wait until the limit is reached before I can use mythtv on the core or md. Also, if I navigate too quickly (changing channels, browsing the guide, etc.) the restarts begin happening again. I've tried seaching the forum and wiki for a solution and came up with nothing. I'm at my wits end about what exactly is wrong and what I can try next. Any ideas would be appreciated.

Code: [Select]

05 03/08/10 12:43:41.631 Socket::ReceiveData 0x8a5c2be8 failed, bytes left 0 start: 3090000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 114 Incoming_Conn Socket 114 192.168.80.1 <0x6ccc4b90>
05 03/08/10 12:43:41.631 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 114 192.168.80.1 <0x6ccc4b90>
05 03/08/10 12:43:41.631 TCPIP: Closing connection to -1003 (Router Dev #0) 0x8a5c2be8 m_Socket: -1 <0x6ccc4b90>
05 03/08/10 12:43:41.631 Router::RemoveAndDeleteSocket 0x8a5c2be8 -1003 <0x6ccc4b90>
01 03/08/10 12:44:16.027 MythBackEnd_Socket::SendMythString sent MYTH_PROTO_VERSION 50 but timeout getting response containing ACCEPT <0x9def8b90>
01 03/08/10 12:44:16.027 MythBackEnd_Socket::Connect couldn't send MYTH_PROTO_VERSION m_bConnected=false <0x9def8b90>
05 03/08/10 12:44:16.027 void ClientSocket::Disconnect() on this socket: 0x8a5c2be8 (m_Socket: 114) <0x9def8b90>
01 03/08/10 12:44:16.027 MythBackEnd_Socket::ProcessSocket error reconnect 0 <0x9def8b90>
01 03/08/10 12:44:26.035 MythBackEnd_Socket::SendMythString sent MYTH_PROTO_VERSION 50 but timeout getting response containing ACCEPT <0x9def8b90>
01 03/08/10 12:44:26.035 MythBackEnd_Socket::Connect couldn't send MYTH_PROTO_VERSION m_bConnected=false <0x9def8b90>
05 03/08/10 12:44:26.035 void ClientSocket::Disconnect() on this socket: 0x8a5c2be8 (m_Socket: 114) <0x9def8b90>
01 03/08/10 12:44:36.023 MythBackEnd_Socket::SendMythString sent MYTH_PROTO_VERSION 50 but timeout getting response containing ACCEPT <0x9def8b90>
01 03/08/10 12:44:36.023 MythBackEnd_Socket::Connect couldn't send MYTH_PROTO_VERSION m_bConnected=false <0x9def8b90>
05 03/08/10 12:44:36.023 void ClientSocket::Disconnect() on this socket: 0x8a5c2be8 (m_Socket: 114) <0x9def8b90>
01 03/08/10 12:44:36.023 MythBackEnd_Socket::SendMythString failed to reconnect <0x9def8b90>
01 03/08/10 12:44:36.023 MythTV_PlugIn::ConfirmMasterBackendOk -- lost communication with it.  Forcing it to die <0x9def8b90>
08 03/08/10 12:44:36.023 Received Message from 41 (MythTV Plug-In / Basement) to 15 (App Server / Basement), type 1 id 67 Command:Spawn Application, retry none, parameters: <0x9f6fbb90>
08 03/08/10 12:44:36.023   Parameter 13(Filename): /usr/pluto/bin/ForciblyKillProcess.sh <0x9f6fbb90>
08 03/08/10 12:44:36.023   Parameter 50(Name): killmyth <0x9f6fbb90>
08 03/08/10 12:44:36.023   Parameter 51(Arguments): mythbackend <0x9f6fbb90>
08 03/08/10 12:44:36.023   Parameter 94(SendOnFailure):  <0x9f6fbb90>
08 03/08/10 12:44:36.023   Parameter 95(SendOnSuccess):  <0x9f6fbb90>
08 03/08/10 12:44:36.023   Parameter 115(Show logo): 0 <0x9f6fbb90>
08 03/08/10 12:44:36.023   Parameter 120(Retransmit): 0 <0x9f6fbb90>
08 03/08/10 12:44:36.023   Parameter 126(Exclusive): 0 <0x9f6fbb90>
08 03/08/10 12:44:36.023   Parameter 241(Detach): 1 <0x9f6fbb90>

Thanks for reading and I appreciate any help.

2

Installation issues / Re: deb.linuxmce.org - Offline???

« on: October 28, 2009, 03:41:29 pm »

I just checked and its working for me now

3

Installation issues / Re: deb.linuxmce.org - Offline???

« on: October 28, 2009, 03:35:09 am »

I just attempted to download the beta installer files and ran into the same problem. deb.linuxmce.org is not responding. In the past I haven't had any trouble getting the files. I have to agree with the OP, deb.linuxmce.org appears to be down.

4

Users / Re: I have a Fiire Chief... Now What?

« on: December 31, 2008, 04:09:45 pm »

krys: If you are connecting your speakers to the headphone jack on your computer, have a look here: http://forum.linuxmce.org/index.php?topic=5738
This isnt normally necessary if you're connecting the speakers to the back of the computer, but i believe it has worked in a few of these cases.

5

Users / Re: Pictures?

« on: December 21, 2008, 10:05:02 pm »

I believe your network config should be fine. As for detecting the NAS again, I recently deleted one of my internal harddrives from the admin page and upon restarting the core it was automatically re-detected.

You shouldnt need to do any unlocking from the "unknown devices" page unless you chose to always ignore the device when it was detected. I suggest you unplug the NAS from the network, make sure it is deleted from the admin website, then restart the core. Upon restart plug the NAS in again and it should be detected within a few mins.

Also, please note that by default, the system reserves 192.168.80.[2-128] for LMCE devices with the rest being left for devices external to the system. This means that once the NAS is setup and being used by LMCE it will automatically be assigned an IP address within this range (I think this address remains constant for as long as the device exists). Your NAS' IP is outside this range, so unless you've changed the default network settings in the web-admin it would appear that LMCE doesnt know it can use the NAS for storage.

6

Users / Re: Pictures?

« on: December 20, 2008, 04:46:33 am »

To get the pictures on ur NAS or any drive in general to appear in the pictures menu on orbiter while keeping them on the device just do the following:

1) When the drive is detected by the system, use the LMCE directory structure on it. This will not erase or damage anything already on the drive, it will just give you some new directories (ie. public, user_1, user_2, etc.)
(In your case, you have to get LMCE to re-detect your NAS, I assume this can be done by simply removing it from the admin website and then plugging it in again. However, I've never tried this myself and cannot guarantee that it will be detected again automatically. Meaning, you might need to take additional steps to get it to be detected again)

2) Move the pictures into the "/public/data/pictures" directory on the NAS (you can have the pictures in sub-directories from this point forward). Now your pictures should appear in orbiter.

Basically what happens is, when you use the LMCE directory structure the new folders are created on the drive(if they dont already exist) and symlinks are automatically created to the appropriate places. ie. A symlink is created in the "/home/public/data/pictures/" directory on the root drive to "/public/data/pictures" on your NAS.

Hope that helps. Best of luck.

7

Users / Re: Pictures?

« on: December 17, 2008, 05:52:18 am »

Assuming I understand you correctly, what you are trying to do is not currently possible.

This is because when viewing pictures from orbiter, you can only sort them via "Filename". This means you can browse the pictures from the /home/public/data/pictures directory and only see pictures immediately in this directory and its sub-directories even if they have been catalogued. You will notice the exact same behaviour for your video and audio files if you sort by Filename. However, for video and audio files you have the option of sorting based on other criteria(ie. Title) which allow you to see all catalogued files.

I havnt a clue how it might be done but perhaps the other sort options can be made available for pictures in the future.
Until then, you have only 2 options:
1. As Zaerc said, use the LMCE directory structure on the NAS and move all the media files into the appropriate directories. The files would remain on the NAS so this shouldnt affect your RAID1 setup. And if your nightly network backup is of the entire NAS(with all directories and files), it should continue working just as it is. Thus, preserving the same level or redundancy you have now.
or
2. This option is not recommended, as Thom mentioned, but you can manually create a symlink to the pictures on the NAS in the /home/public/data/pictures directory and hope that nothing breaks. At the very least this will create duplicate entries in the database and possibly cause other problems.

Good luck

8

Users / Re: New Media Tagging System

« on: December 13, 2008, 10:53:38 pm »

Good to hear Glasswalker. Thank you for all the hard work.

9

Users / Re: New Media Tagging System

« on: December 13, 2008, 10:03:52 pm »

Just to let everyone know, this system doesn't work with apostrophes in the file name. Not a big deal but I just spent 30 mins trying to figure out why it wasnt working. I removed all the apostrophes and it worked great.

10

Users / Re: AV Commands not working

« on: December 13, 2008, 04:49:21 pm »

As far as I know there is a bug with the windows mce transmitter. I think there are cases of a few people getting it working but for most its been futile. One of the devs can confirm this. Your best bet is to use some other device to transmit ir codes to your devices.

I cant remember which tread it was but if you do a search for "mce_usb" you will probably come across a tread where some people tried to fix this issue and eventually gave up.

11

Users / Re: AV Commands not working

« on: December 13, 2008, 02:30:04 am »

I had the same problem you described with my Windows mce transceiver. I ended up getting USB UIRT and all works fine now. What interface device are you using to send the codes?

12

Developers / Re: New Feature: On-Orbiter TV Guide, movies attached.

« on: December 08, 2008, 05:07:53 am »

Thanks for the quick reply Thom. I look forward to the next release and this feature.

krippler

13

Developers / Re: New Feature: On-Orbiter TV Guide, movies attached.

« on: December 08, 2008, 04:43:17 am »

Did anything ever come of this? Is this functionality currently available? I cant do this on my orbiter. Do i need to do some sort of update?
I realize this an old thread but I'm interested in this feature. I've searched quite a bit to see if any other information was available on getting this working. I would appreciate it if someone could tell me how to set it up or if the feature was abandoned.

krippler