Topics

I like the updated look of the wiki, good job.

Under favorites, exemplary setups links to a non existent page (http://wiki.linuxmce.org/index.php/Categor:User_Setups)

I think it's supposed to go to this one: http://wiki.linuxmce.org/index.php/Category:User_Setups

I would fix it myself though I don't think I have access, if I do, I don't know how to edit that navigation bar!

All - I'm looking at the code under LMCEUpdate* : http://svn.linuxmce.org/trac.cgi/browser/branches/LinuxMCE-1004/src/Update


It looks like the system was built around the MCE devs providing an xml file, sample here:

Code Select Expand


<?xml version="1.0"?>
<lmce_update>
<update id="1">
  <description>Update mythtv packages from the Core to work with SchedulesDirect.</description>
  <priority>1</priority>
  <model>LMCE_CORE_1_1</model>
  <file
           URL="http://updates.linuxmce.com/update001.tar"
   action="untar"
   destination="/tmp/update001"
   md5="e9f1cf48cc688bbb223981d0df4e52f1"
   size="413168"
   autoexec="/tmp/update001/install-update.sh"
   />
</update>


Today I'm thinking we've moved away from this model and are pushing all updates through standard apt processes. At this point do we want to abandon this XML process in favor of being able to upgrade and notify end users through the standard APT process, or do we want to keep going down the XML road?

Is there any reason to run /usr/pluto/bin/Diskless_CreateTBZ.sh more than once?

Hello,

 I've spent some time consolidating the old 810 installer process and updating it to a single script for 1004 as well as making a couple of improvements. The improvements/updates include:

• A log file is now generated covering the entire installation process: /var/log/LinuxMCE_Setup.log
• Additional error checking
• Performs the apt-get and upgrade for you
• Updated pre-seed for package preferences method
• Logging output to the user with date/time stamp for each function

 I have had multiple successful VM installs and a few successful physical core installs (the issues I've been running into was more focused on the nVidia X setup post install which have now been corrected for 1004). I'd like for others to test it out before looking at archiving the old process. You can find information on how to use this installer here: http://wiki.linuxmce.org/index.php/Installing_1004

Please let me know if you run into issues or if you don't! If you do hit issues please let me know your sys specs (CPU, Memory and video card).

Known Issues with installation process:

• None at this time

Thank you!

  We came across a strategic question this weekend that I wanted to post to the larger audience to think about. The issue is - what are we supposed to be doing (i.e. what is ideal) when a package is dropped from a repo across distribution revisions of Kubuntu? As I was trying to clean up the /etc/apt/sources.list to remove the older repositories placed there by ConfirmDependencies I made a couple of database changes, one of which broke the 1004 install process (specifically I added an entry to the packages table for php-image-graph for lucid so the intrepid repo wouldn't show up in the sources.list file, unfortunately between intrepid and lucid, this package was dropped from the main repository and is installable via PEAR). Granted this specific entry may not be necessary since the only facility (data logger) to leverage this functionality is now installed via the data logger post install plugin script it does bring about a larger question of maintenance as we move from revision to revision in Kubuntu.

As I see we have a few courses of action which have some consquences:

   1. To leave the package defined in the database without the updated distribution (i.e. lucid) which will clutter up the sources.list
   2. To update the packages table to include the lucid distro but point to a dummy package name - this basically means we'd be maintaining this package in the database forever which I can see becoming pretty unmanageable 5 or 6 revisions of Kubuntu down the line.
   3. Update or enhance confirmdependencies that would drop a dependency if the dependency does not have an package defined in the databse equal to the running distro (i.e.  lucid) entry in the packages table. I haven't deep dived on this option, so I'm not certain how hairy updating the logic would be, and I'm also not certain of the downstream impacts this would have (i.e. what functionality would we be losing by making this update)
   4. Rolling up our own package and manage it going forward - depending on the package I'm thinking this could be more of a management nightmare as well.



What do you all think?

Hello, I'm building a new MD and i've gone through the AVWizard setup and initial setup, the orbiter generates on the OSD though upon the generation I the screen is blank (X loads, though the cursor is idle in the middle). I'm not certain where to go next, here are some of the logs. Can anyone help point me in the right direction?

Code Select Expand


pluto.log
1       01/14/11 13:19:10       SetupAudioVideo (server)        Starting
1       01/14/11 13:19:13       Xconfigure (server)     Display Driver: nvidia
1       01/14/11 13:19:18       SetupAudioVideo (server)        '
1       01/14/11 13:19:18       SetupAudioVideo (server)        DBSetting: H3 Reboot:  Script Path: /usr/pluto/bin/
1       01/14/11 13:19:18       /etc/rc2.d/S99linuxmce (server) Starting X server (client: /usr/bin/xfwm4; parms: --compositor=off)
1       01/14/11 13:19:20       /etc/rc2.d/S99linuxmce (server) X server: backround; AlphaBlending: 0
1       01/14/11 13:21:02       DiskSpaceMonitor.sh (server)    Filesystem ( /mnt/device/36 ) has 135055 MB free
1       01/14/11 13:21:04       DiskSpaceMonitor.sh (server)    Filesystem ( /mnt/device/56 ) has 814915 MB free
1       01/14/11 13:22:00       /usr/pluto/bin/Spawn_Device.sh 101 (spawning-device)    14656 Dev: 101; Already Running list:
1       01/14/11 13:22:00       /usr/pluto/bin/Spawn_Device.sh 101 (spawning-device)    device: 101 ip: dcerouter cmd_line: App_Server
0       01/14/11 13:22:00       101 (spawning-device)   Entering 101
1       01/14/11 13:22:00       101 (spawning-device)   Starting... 1
1       01/14/11 13:22:00       101 (spawning-device)   Found /usr/pluto/bin/App_Server
1       01/14/11 13:22:01       /usr/pluto/bin/Spawn_Device.sh 102 (spawning-device)    14731 Dev: 102; Already Running list: 101,
1       01/14/11 13:22:01       /usr/pluto/bin/Spawn_Device.sh 102 (spawning-device)    device: 102 ip: dcerouter cmd_line: LaunchOrbiter.sh
0       01/14/11 13:22:02       102 (spawning-device)   Entering 102
1       01/14/11 13:22:02       102 (spawning-device)   Starting... 1
1       01/14/11 13:22:02       102 (spawning-device)   Found /usr/pluto/bin/LaunchOrbiter.sh
1       01/14/11 13:22:02       LaunchOrbiter (server)  Number of desktops found: 6 ; desktops activated? 1
1       01/14/11 13:22:02       LaunchOrbiter (server)  Primary desktop: 4 and secondary desktop 5
3       01/14/11 13:22:03       102 (spawning-device)   Device died... count=1/50 dev=102


run manually:
root@moon100:/usr/pluto/bin# /usr/pluto/bin/LaunchOrbiter.sh
+ /usr/pluto/bin/LaunchOrbiter.sh
WatchGyroRemote: no process killed
1       01/14/11 13:22:57       LaunchOrbiter (server)  Number of desktops found: 6 ; desktops activated? 1
1       01/14/11 13:22:57       LaunchOrbiter (server)  Primary desktop: 4 and secondary desktop 5
Copyright (C) 2004 Pluto, Inc., a Florida Corporation
www.plutohome.com
Phone: +1 (877) 758-8648
This program is distributed according to the terms of the Pluto Public License, available at:
http://plutohome.com/index.php?section=public_license
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY;
without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the Pluto Public License for more details.
-----

envir_utf8: 0
WmCtrl::LowLevelCommand() : opened pDisplay=0x9dc9a38
WmCtrl::LowLevelCommand() : closed pDisplay=0x9dc9a38
envir_utf8: 0
WmCtrl::LowLevelCommand() : opened pDisplay=0x9dc9a38
Invalid type of _NET_CLIENT_LIST property.
Invalid type of _WIN_CLIENT_LIST property.
Cannot get client list properties.
(_NET_CLIENT_LIST or _WIN_CLIENT_LIST)
WmCtrl::LowLevelCommand() : closed pDisplay=0x9dc9a38
envir_utf8: 0
WmCtrl::LowLevelCommand() : opened pDisplay=0x9dc9a38
Invalid type of _NET_CLIENT_LIST property.
Invalid type of _WIN_CLIENT_LIST property.
Cannot get client list properties.
(_NET_CLIENT_LIST or _WIN_CLIENT_LIST)
WmCtrl::LowLevelCommand() : closed pDisplay=0x9dc9a38
envir_utf8: 0
envir_utf8: 0
WmCtrl::LowLevelCommand() : opened pDisplay=0x9dc9a38
WmCtrl::LowLevelCommand() : closed pDisplay=0x9dc9a38
envir_utf8: 0
WmCtrl::LowLevelCommand() : opened pDisplay=0x9dc9a38
Invalid type of _NET_CLIENT_LIST property.
Invalid type of _WIN_CLIENT_LIST property.
Cannot get client list properties.
(_NET_CLIENT_LIST or _WIN_CLIENT_LIST)
WmCtrl::LowLevelCommand() : closed pDisplay=0x9dc9a38
./Orbiter: symbol lookup error: ./Orbiter: undefined symbol: _Z15db_wrapper_initP8st_mysql
++ echo -ne '\033]0;root@moon100: /usr/pluto/bin\007'
root@moon100:/usr/pluto/bin#

102_LaunchOrbiter.sh.log
========== NEW LOG SECTION ==========
1       01/14/11 13:25:11       102 (spawning-device)   Starting... 18
1       01/14/11 13:25:11       102 (spawning-device)   Found /usr/pluto/bin/LaunchOrbiter.sh
Return code: 127
3       01/14/11 13:25:12       102 (spawning-device)   Device died... count=18/50 dev=102
Fri Jan 14 13:25:12 CST 2011 died


Hello,

 I've hit a bit of a wall in troubleshooting an intermittent issue that occurs when I attempt to watch analog signals via the PCHD5500 cards. Essentially recorded shows and livetv affected by this issue will skip about every half second throughout the recording (or consistently throughout the live tv session). To correct it in livetv you just have to change chanels (channel up then channel down). Though I haven't found a workable solution to correct affected recordings. A snippet of the mythbackend.log is below, it seems every time this issue occurs i get the 'Strange error flushing buffer ...' message in the log.

Code Select Expand


2009-09-18 21:00:03.269 AutoExpire: CalcParams(): Max required Free Space: 11.0 GB w/freq: 15 min
strange error flushing buffer ...
2009-09-18 21:00:03.706 Started recording: Psych "Bollywood Homicide": channel 1039 on cardid 1, sourceid 1
2009-09-18 21:00:03.937 Using runtime prefix = /usr
2009-09-18 21:00:04.096 Empty LocalHostName.
2009-09-18 21:00:04.163 Using localhost value of dcerouter
2009-09-18 21:00:04.273 New DB connection, total: 1
2009-09-18 21:00:04.288 Connected to database 'mythconverg' at host: localhost
2009-09-18 21:00:04.308 Closing DB connection named 'DBManager0'
2009-09-18 21:00:04.324 Connected to database 'mythconverg' at host: localhost
2009-09-18 21:00:04.340 New DB connection, total: 2
2009-09-18 21:00:04.346 Connected to database 'mythconverg' at host: localhost
2009-09-18 21:00:04.360 Current Schema Version: 1214
2009-09-18 21:00:04.509 Preview: Grabbed preview '/home/public/data/pvr/1056_20090918200000.nuv' 480x480@64s
2009-09-18 21:00:04.960 Reschedule requested for id 0.
2009-09-18 21:00:05.284 Scheduled 228 items in 0.3 = 0.00 match + 0.32 place
2009-09-18 21:00:22.700 MainServer::HandleAnnounce Monitor
2009-09-18 21:00:22.704 adding: moon44 as a client (events: 0)
2009-09-18 21:00:22.708 MainServer::HandleAnnounce Monitor
2009-09-18 21:00:22.723 adding: moon44 as a client (events: 1)
2009-09-18 21:00:22.726 MainServer::HandleAnnounce Playback
2009-09-18 21:00:22.728 adding: moon44 as a client (events: 0)
2009-09-18 21:00:22.732 MainServer::HandleAnnounce FileTransfer
2009-09-18 21:00:22.736 adding: moon44 as a remote file transfer


 My questions are: is this something I have messed up in my logical config (setup is here: http://wiki.linuxmce.org/index.php/User:Murdock)? Is this a defect that needs to be in trac? Am I missing a valuable log that would help correct this issue?

Thank you,

Ryan

All - fyi

Sound quality issues on myth front end??

If you have analog sound related issues, ensure that 48000 is set BOTH at the mythtv-setup-->capture cards--->v4l AND on the myth front end (which seems to default to 32000) to get there, it's in Recording Profiles -> Software Encoders -> LiveTV, then just set up the encoding options, audio is on the second page.

Wiki updated: http://wiki.linuxmce.com/index.php/PcHDTV_HD5500#Troubleshooting

Hello -

  For security and/or lighting, I was wondering if there are any LMCE supported wall panel orbiters?


Thank you,

Ryan

I've noticed that when upgrading to either 1.0.19 or 1.0.20 ALSA driver I receive many 'unknown symbol' errors when upgrading either manually or via the upgrade script (details here: http://wiki.linuxmce.com/index.php/User:Murdock#My_810_Install_Instructions ).

After making multiple changes to different files and the repo i'm now able to see the /dev/dsp1 file and pull analog audio. The issue now is i'm not exactly certain which changes gave me the ability to receive audio.

When able to receive audio through the analog cable, I was on:
.20 of all alsa modules EXCEPT the driver
.17 of the alsa driver

Has anyone been successful in getting rid of the cx88_alsa 'unknown symbol' errors on .19 or .20?

I'll be continuing to work on this and derive exactly what is needed in order to get the /dev/dsp* and the cx88 card to be recognized in /proc/asounds/cards - though any thoughts/assistance would be appreciated.

I'm attempting to get my head around the development and release process. I'm going to throw out a few things and would like someone to comment:

1. Features and issues:
  Features are requested via the TRAC system and validity of features are decided upon by a PRB (priority review board) and are assigned (or dismissed) based on resource availability and whether the change is appropriate based on current release or future (roadmap) releae.

2. Release Strategy:
  Releases (builds) are done on each yearly x.10 release of Kubuntu and GA dates are based upon developer availability and number of issues/features included in the TRAC system.

3. Updates to code:
  If someone wants to correct an issue or correct a feature, this person would need to be plugged into either the PRB or community leader in order to be assigned via the TRAC system and have access to the latest build to update.

4. Testing cycle
  Upon completion of an update, information regarding the update is posted on the wiki to track the changes and a new alpha/beta release is made.


Comments are welcome!

Thank you,
Ryan

Hello,

I have been attempting to understand more of how the LinuxMCE system works at a technical level, documenting and uploading the information to the wiki. I'm struggling with a couple of errors I'm currently encountering in my DCERouter.log that repeat so often it's difficult to spot anything else.


05      03/15/09 11:00:10.169           void ClientSocket::Disconnect() on this socket: 0x855ab20 (m_Socket: 131) <0x9f4e8b90>
01      03/15/09 11:00:10.169           MythBackEnd_Socket::Close <0x9f4e8b90>
01      03/15/09 11:00:10.169           MythBackEnd_Socket::Connect failed m_bConnected=false <0x9f4e8b90>
05      03/15/09 11:00:11.289           Connect() failed, Error Code 111 (Connection refused)) <0x9f4e8b90>
05      03/15/09 11:00:12.289           Connect() failed, Error Code 111 (Connection refused)) <0x9f4e8b90>
05      03/15/09 11:00:13.289           Connect() failed, Error Code 111 (Connection refused)) <0x9f4e8b90>
05      03/15/09 11:00:13.289           ClientSocket::Connect() not successful <0x9f4e8b90>
05      03/15/09 11:00:13.289           void ClientSocket::Disconnect() on this socket: 0x855cc48 (m_Socket: 131) <0x9f4e8b90>
01      03/15/09 11:00:13.289           MythBackEnd_Socket::Close <0x9f4e8b90>
01      03/15/09 11:00:13.289           MythBackEnd_Socket::Connect failed m_bConnected=false <0x9f4e8b90>
01      03/15/09 11:00:13.289           MythBackEnd_Socket::SendMythString failed to reconnect <0x9f4e8b90>
01      03/15/09 11:00:13.289           MythTV_PlugIn::ConfirmMasterBackendOk -- lost communication with it.  Forcing it to die <0x9f4e8b90>
08      03/15/09 11:00:13.289           Received Message from 31 (MythTV Plug-In / ) to 15 (App Server / ), type 1 id 67 Command:Spawn Application, retry none, parameters: <0xa04eab90>
08      03/15/09 11:00:13.289             Parameter 13(Filename): /usr/pluto/bin/ForciblyKillProcess.sh <0xa04eab90>
08      03/15/09 11:00:13.289             Parameter 50(Name): killmyth <0xa04eab90>
08      03/15/09 11:00:13.289             Parameter 51(Arguments): mythbackend <0xa04eab90>
08      03/15/09 11:00:13.289             Parameter 94(SendOnFailure):  <0xa04eab90>
08      03/15/09 11:00:13.289             Parameter 95(SendOnSuccess):  <0xa04eab90>
08      03/15/09 11:00:13.289             Parameter 115(Show logo): 0 <0xa04eab90>
08      03/15/09 11:00:13.289             Parameter 120(Retransmit): 0 <0xa04eab90>
08      03/15/09 11:00:13.289             Parameter 126(Exclusive): 0 <0xa04eab90>
08      03/15/09 11:00:13.289             Parameter 241(Detach): 1 <0xa04eab90>
08      03/15/09 11:00:13.299           Received Message from 15 (App Server / ) to 15 (App Server / ), type 1 id 812 Command:Application Exited, retry none, parameters: <0x864b6b90>
08      03/15/09 11:00:13.299             Parameter 227(PID): 30532 <0x864b6b90>
08      03/15/09 11:00:13.299             Parameter 228(Exit Code): 0 <0x864b6b90>
05      03/15/09 11:00:41.045           Connect() failed, Error Code 111 (Connection refused)) <0x9ece7b90>



The errors seem to be centered around the MythTV (which I do not have setup yet, my cable company doesn't release a box has an activated firewire/1394 port), though I have not performed any kind of setup, are these errors expected in the router log? Is there a recommended way to get around these errors or disable the mythtv piece to clean up the log?


Thank you,

Ryan

I have purchased a fiire 12TB and a prestige lite with usb ir transceiver, below is my experience.

Experience was decent. My order was placed Nov 9th and was shipped Nov 24th. All but 1 item was originally shipped (USB IR Transceiver). I engaged support regarding this about and 1 faulty 500GB hard drive on 11/30. The UIRT and hard drive has been replaced as of 12/8.

I would purchase from fiire again.

Hello,

  I receive my USB IR Transceiver yesterday, I was going through setting up the AV devices attached to the MD and set up a test media scenario. This morning I rebooted my core and found that I the DCERouter will not start. I've since backed out all configuration changes I've made yesterday and have attempted the solutions recommended by previous posts.

Here's a sample of the dcerouter.log:
========== NEW LOG SECTION ==========
1       12/07/08 12:03:38       DCERouter (server)      Starting... 1
Sun Dec  7 12:03:38 CST 2008 Starting
05      12/07/08 12:03:38.621           Socket::ReceiveData 0x8112e80 failed, bytes left 0 start: 40000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 8 Incoming_Conn Socket 8 127.0.0.1 <0xb3c6cb90>
05      12/07/08 12:03:38.622           Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 8 127.0.0.1 <0xb3c6cb90>
05      12/07/08 12:03:38.622           TCPIP: Closing connection to -1 (Router Dev #0) 0x8112e80 m_Socket: -1 <0xb3c6cb90>
05      12/07/08 12:03:38.622           Router::RemoveAndDeleteSocket 0x8112e80 -1 <0xb3c6cb90>
05      12/07/08 12:03:39.039           Loaded plug-in device: 3 master device: 10 -- ./File_Grids_Plugin.so <0xb6c736c0>
05      12/07/08 12:03:39.071           Loaded plug-in device: 4 master device: 27 -- ./General_Info_Plugin.so <0xb6c736c0>
05      12/07/08 12:03:39.078           Loaded plug-in device: 5 master device: 31 -- ./Climate_Plugin.so <0xb6c736c0>
05      12/07/08 12:03:39.090           Loaded plug-in device: 6 master device: 9 -- ./Datagrid_Plugin.so <0xb6c736c0>
05      12/07/08 12:03:39.105           Loaded plug-in device: 7 master device: 39 -- ./Infrared_Plugin.so <0xb6c736c0>
05      12/07/08 12:03:39.126           Loaded plug-in device: 8 master device: 32 -- ./Lighting_Plugin.so <0xb6c736c0>
05      12/07/08 12:03:39.185           Loaded plug-in device: 9 master device: 12 -- ./Orbiter_Plugin.so <0xb6c736c0>
05      12/07/08 12:03:39.235           Loaded plug-in device: 10 master device: 2 -- ./Media_Plugin.so <0xb6c736c0>
05      12/07/08 12:03:39.306           Loaded plug-in device: 11 master device: 34 -- ./Telecom_Plugin.so <0xb6c736c0>
05      12/07/08 12:03:39.319           Loaded plug-in device: 12 master device: 52 -- ./Event_Plugin.so <0xb6c736c0>
05      12/07/08 12:03:39.331           Loaded plug-in device: 13 master device: 33 -- ./Security_Plugin.so <0xb6c736c0>
05      12/07/08 12:03:39.344           Loaded plug-in device: 14 master device: 1809 -- ./Plug_And_Play_Plugin.so <0xb6c736c0>
05      12/07/08 12:03:39.355           Loaded plug-in device: 27 master device: 6 -- ./Xine_Plugin.so <0xb6c736c0>
05      12/07/08 12:03:39.370           Loaded plug-in device: 31 master device: 36 -- ./MythTV_PlugIn.so <0xb6c736c0>
05      12/07/08 12:03:39.456           Plugin 3 activated <0xb6c736c0>
05      12/07/08 12:03:39.540           Plugin 4 activated <0xb6c736c0>
05      12/07/08 12:03:39.620           Plugin 5 activated <0xb6c736c0>
05      12/07/08 12:03:39.700           Plugin 6 activated <0xb6c736c0>
05      12/07/08 12:03:39.780           Plugin 7 activated <0xb6c736c0>
05      12/07/08 12:03:39.860           Plugin 8 activated <0xb6c736c0>
05      12/07/08 12:03:39.982           Plugin 9 activated <0xb6c736c0>
05      12/07/08 12:03:40.108           Plugin 10 activated <0xb6c736c0>
05      12/07/08 12:03:40.193           Phone device 35 with extension 200 <0xb6c736c0>
01      12/07/08 12:03:40.195           Telecom_Plugin::GetConfig - no pbx device <0xb6c736c0>
05      12/07/08 12:03:40.210           Plugin 11 activated <0xb6c736c0>
05      12/07/08 12:03:40.299           Plugin 12 activated <0xb6c736c0>
05      12/07/08 12:03:40.381           Plugin 13 activated <0xb6c736c0>
05      12/07/08 12:03:40.464           Plugin 14 activated <0xb6c736c0>
05      12/07/08 12:03:40.544           Plugin 27 activated <0xb6c736c0>
05      12/07/08 12:03:40.628           Plugin 31 activated <0xb6c736c0>
05      12/07/08 12:03:40.630           Remote Control 41 has no orbiter <0xb6c736c0>
05      12/07/08 12:03:40.632           Remote Control 44 has no orbiter <0xb6c736c0>
Return code: 139
3       12/07/08 12:03:40       DCERouter (server)      Device died... count=1/200 dev=DCERouter
Sun Dec  7 12:03:40 CST 2008 died

Here is a successful start from yesterday (section):
========== NEW LOG SECTION ==========
1       12/06/08 08:54:30       DCERouter (server)      ^[[1;00mStarting... 1^[[1;00m
Sat Dec  6 08:54:30 CST 2008 Starting
05      12/06/08 8:54:30.860            ^[[33;1mSocket::ReceiveData 0x8112c28 failed, bytes left 0 start: 50000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 7 Incoming_Conn Socket 7 127.0.0.1^[[0m <0xb3bd7b90>
05      12/06/08 8:54:30.860            ^[[33;1mSocket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 7 127.0.0.1^[[0m <0xb3bd7b90>
05      12/06/08 8:54:30.860            ^[[33;1mTCPIP: Closing connection to -1 (Router Dev #0) 0x8112c28 m_Socket: -1^[[0m <0xb3bd7b90>
05      12/06/08 8:54:30.860            ^[[33;1mRouter::RemoveAndDeleteSocket 0x8112c28 -1^[[0m <0xb3bd7b90>
05      12/06/08 8:54:31.341            ^[[33;1mLoaded plug-in device: 3 master device: 10 -- ./File_Grids_Plugin.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.382            ^[[33;1mLoaded plug-in device: 4 master device: 27 -- ./General_Info_Plugin.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.389            ^[[33;1mLoaded plug-in device: 5 master device: 31 -- ./Climate_Plugin.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.400            ^[[33;1mLoaded plug-in device: 6 master device: 9 -- ./Datagrid_Plugin.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.416            ^[[33;1mLoaded plug-in device: 7 master device: 39 -- ./Infrared_Plugin.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.437            ^[[33;1mLoaded plug-in device: 8 master device: 32 -- ./Lighting_Plugin.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.495            ^[[33;1mLoaded plug-in device: 9 master device: 12 -- ./Orbiter_Plugin.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.545            ^[[33;1mLoaded plug-in device: 10 master device: 2 -- ./Media_Plugin.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.617            ^[[33;1mLoaded plug-in device: 11 master device: 34 -- ./Telecom_Plugin.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.630            ^[[33;1mLoaded plug-in device: 12 master device: 52 -- ./Event_Plugin.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.641            ^[[33;1mLoaded plug-in device: 13 master device: 33 -- ./Security_Plugin.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.655            ^[[33;1mLoaded plug-in device: 14 master device: 1809 -- ./Plug_And_Play_Plugin.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.665            ^[[33;1mLoaded plug-in device: 27 master device: 6 -- ./Xine_Plugin.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.681            ^[[33;1mLoaded plug-in device: 31 master device: 36 -- ./MythTV_PlugIn.so^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.774            ^[[33;1mPlugin 3 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.873            ^[[33;1mPlugin 4 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:31.954            ^[[33;1mPlugin 5 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:32.034            ^[[33;1mPlugin 6 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:32.124            ^[[33;1mPlugin 7 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:32.214            ^[[33;1mPlugin 8 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:32.336            ^[[33;1mPlugin 9 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:32.479            ^[[33;1mPlugin 10 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:32.563            ^[[33;1mPhone device 35 with extension 200^[[0m <0xb6bde6c0>
01      12/06/08 8:54:32.565            ^[[31;1mTelecom_Plugin::GetConfig - no pbx device^[[0m <0xb6bde6c0>
05      12/06/08 8:54:32.588            ^[[33;1mPlugin 11 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:32.706            ^[[33;1mPlugin 12 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:32.817            ^[[33;1mPlugin 13 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:32.903            ^[[33;1mPlugin 14 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:32.986            ^[[33;1mPlugin 27 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:33.116            ^[[33;1mPlugin 31 activated^[[0m <0xb6bde6c0>
05      12/06/08 8:54:33.118            ^[[33;1mRemote Control 41 has no orbiter^[[0m <0xb6bde6c0>
05      12/06/08 8:54:33.118            ^[[33;1mRemote Control 44 has no orbiter^[[0m <0xb6bde6c0>
08      12/06/08 8:54:33.206            Received Message from 11 (^[[36;1mTelecom Plug-in / ^[[0m) to 0 (^[[36;1munknown / ^[[0m), type 1 id 922 Command:^[[35;1mSend Asterisk Status^[[0m, retry retry, parameters: <0xa8014b90>
05      12/06/08 8:54:33.234            ^[[33;1mMythTV_PlugIn::SetPaths: won't create tv_shows for device 0. We are probably out of sync!^[[0m <0xb6bde6c0>
05      12/06/08 8:54:34.420            ^[[33;1mConnect() failed, Error Code 111 (Connection refused))^[[0m <0xb6bde6c0>
05      12/06/08 8:54:35.420            ^[[33;1mConnect() failed, Error Code 111 (Connection refused))^[[0m <0xb6bde6c0>
05      12/06/08 8:54:36.420            ^[[33;1mConnect() failed, Error Code 111 (Connection refused))^[[0m <0xb6bde6c0>
05      12/06/08 8:54:36.420            ^[[33;1mClientSocket::Connect() not successful^[[0m <0xb6bde6c0>
                                                                                                               


  I've searched the previous posts and attempted to disable the mythtv plugin and other plugins, but re-enabled when that did not work. I'm not certain what the issue is, would anyone be able to point me in the right direction of a more verbose log or suggest an idea on what the issue may be?


Thank you,

Ryan

Hello all,

  The occassional system freeze issues i've been having were traced to NIC card issues, to isolate the problem I ran a few tests.

  1. Shut down LMCE
  2. Shut down all NICs but 1 (eth1)
  3. hard wired this nic with my external network and tested small file copies and large.

  The issue occurs when large file copies (~250MB), the failure occurs between file 2 and file 5 in a series. The problem is a total system freeze that requires a hard boot. My pci bus information and ifconfig info is below. Has anyone run into this in the past?

dcerouter_97614:/etc/network# ifconfig

eth1      Link encap:Ethernet  HWaddr 00:E0:4C:A0:01:04
          inet addr:192.168.1.155  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2e0:4cff:fea0:104/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6663 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7871 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:896809 (875.7 KB)  TX bytes:2038965 (1.9 MB)
          Interrupt:21 Base address:0xe800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:61869 errors:0 dropped:0 overruns:0 frame:0
          TX packets:61869 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6593019 (6.2 MB)  TX bytes:6593019 (6.2 MB)

dcerouter_97614:/etc/network# lspci
00:00.0 Host bridge: nVidia Corporation Unknown device 07c0 (rev a2)
00:00.1 RAM memory: nVidia Corporation Unknown device 07cb (rev a2)
00:01.0 RAM memory: nVidia Corporation Unknown device 07cd (rev a1)
00:01.1 RAM memory: nVidia Corporation Unknown device 07ce (rev a1)
00:01.2 RAM memory: nVidia Corporation Unknown device 07cf (rev a1)
00:01.3 RAM memory: nVidia Corporation Unknown device 07d0 (rev a1)
00:01.4 RAM memory: nVidia Corporation Unknown device 07d1 (rev a1)
00:01.5 RAM memory: nVidia Corporation Unknown device 07d2 (rev a1)
00:01.6 RAM memory: nVidia Corporation Unknown device 07d3 (rev a1)
00:02.0 RAM memory: nVidia Corporation Unknown device 07d6 (rev a1)
00:03.0 ISA bridge: nVidia Corporation Unknown device 07d7 (rev a2)
00:03.1 SMBus: nVidia Corporation Unknown device 07d8 (rev a1)
00:03.2 RAM memory: nVidia Corporation Unknown device 07d9 (rev a1)
00:03.3 Co-processor: nVidia Corporation Unknown device 07da (rev a2)
00:03.4 RAM memory: nVidia Corporation Unknown device 07c8 (rev a1)
00:04.0 USB Controller: nVidia Corporation Unknown device 07fe (rev a1)
00:04.1 USB Controller: nVidia Corporation Unknown device 056a (rev a1)
00:08.0 IDE interface: nVidia Corporation Unknown device 056c (rev a1)
00:09.0 Audio device: nVidia Corporation Unknown device 07fc (rev a1)
00:0a.0 PCI bridge: nVidia Corporation Unknown device 056d (rev a1)
00:0b.0 PCI bridge: nVidia Corporation Unknown device 056e (rev a1)
00:0c.0 PCI bridge: nVidia Corporation Unknown device 056f (rev a1)
00:0d.0 PCI bridge: nVidia Corporation Unknown device 056f (rev a1)
00:0e.0 IDE interface: nVidia Corporation Unknown device 07f0 (rev a2)
00:0f.0 Ethernet controller: nVidia Corporation Unknown device 07dc (rev a2)
00:10.0 VGA compatible controller: nVidia Corporation Unknown device 07e0 (rev a2)
01:06.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
02:00.0 RAID bus controller: 3ware Inc 9650SE SATA-II RAID (rev 01)
03:00.0 Ethernet controller: VIA Technologies, Inc. VT6120/VT6121/VT6122 Gigabit Ethernet Adapter (rev 81)
04:00.0 FireWire (IEEE 1394): JMicron Technologies, Inc. Unknown device 2380

Hello all,

  After doing research over the course of a month or two i decided to pull the trigger and purchase some hardware to use with LMCE. I ended up utilizing Fiire (despite many suggestions to the contrary), the 12TB (http://wiki.linuxmce.org/index.php/Fiire_Engine) and Prestige-lite (http://wiki.linuxmce.org/index.php/Fiire_Station). My experience with fiire has been *ok* in that it took a bit longer than i expected for my order to ship, I have a potential issue with a 500GB hard drive (mentioned below) and the UIRT i had included in my order did not arrive with the rest of my equipment. On the bright side, both pieces of hardware look good, the 12TB has what seems to be an aluminum case for cooling, and quite a few relatively quiet fans and the prestige is ultra quiet.

Here are some additional details:

Hardware:
Core - Fiire 12TB
MD - Fiire Prestige-lite (diskless/pxe boot)
Remote - Fiire chief (not wild about the color)
Network (LMCE) - Netgear 1gbps switch
Network (External) - Linksys (wireless g)

Software:
LMCE from DVD (no base OS loaded first)

  The most difficult part of the implementation was implementing the wireless NIC in a configuration that LMCE/pluto would recognize as the external NIC. I ended up working around the issue by creating a udev rule then modifying the interface file to match accordingly.
Example from my system:
/etc/udev/rules.d# cat 70-persistent-net.rules
# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.

# PCI device 0x1022:0x2000 (pcnet32)
#SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:f7:6c:d5", NAME="eth0"
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:12:17:71:fd:6a", ATTRS{type}=="1", NAME="eth0"

# PCI device 0x10de:0x07dc (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1d:92:63:39:d5", NAME="eth1"

# PCI device 0x1106:0x3119 (via-velocity)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:e0:4c:a0:01:04", NAME="eth2"

# PCI device 0x1814:0x0201 (rt2500pci)
#SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:12:17:71:fd:6a", ATTRS{type}=="1", NAME="wlan0"


My sample interface file:
cat /etc/network/interfaces
auto lo
        iface lo inet loopback
        address 127.0.0.1
        netmask 255.0.0.0

auto eth1
iface eth1 inet static
        address 192.168.80.1
        netmask 255.255.255.0
auto eth0
iface eth0 inet static
wireless-essid #######
wireless-key #######
address 192.168.1.105
netmask 255.255.255.0


  The other issue i had was with the original boot drive, it had unrecoverable issues on rootfs, so i swapped the 500GB with a 1TB drive and redeployed MCE and things have been much better since. I do need to run a diagnostic on that drive though, if anyone is aware of a good linux disk utility please let me know.

  MCE works great (fantastic job to every contributor), the only gripe I have is occasional OS level hangs (screen freeze) on the core which halts my media director as well. I'm thinking this may be due to the non-specific/inherent wireless driver i'm using though I can't find any evidence to support that. Due to the fact that i'm now more comfortable with the solution I'm giving consideration to rebuilding the core with a base kubuntu deployment and installing MCE on top of it, though I do need to do additional research before beginning to see if doing this is worth it (does anyone have any thoughts on this?).

- Ryan