Strange Orbiter behavior on the core after the 9/14 update.

[seth]

 
Hey all,

Been a while since I have posted. But after this latest update, I needed to compare notes. I have updated all my MD's and he core to the latest fixes. Now all my MD's seem to be happy with the updates. Great things have happened. Storage groups work, excellent. However I have notice an issue.

My DirecTV boxes are controlled by the core with a USB-UIRT, and they are hooked into a PVR 500 and daughter card. Now the issue I am having is this:

I lose the orbiter on the core. I go downstairs to the wiring closet and all I see is the mouse cursor. Thinking it is asleep, I click, but the Main Orbiter screen does not come back. Only after repeated mashing on the F1, F2, and F7 keys does it come back, but then after time it goes away. Since there is no orbiter, my USB-UIRT can not change the channels. So I reboot the core, and for a while it comes back, but then after time it goes away again.

Now watching it reboot, I see it come up like it is supposed to, but I notice the orbiter and all the device loads once, then it loads itself again. I am wondering if something is calling it twice in the beginning. And if so, what?

This is what ps -ef shows:

Code: [Select]

seth@dcerouter:~$ ps -ef | grep Orbiter
seth      8425 26341  0 08:50 pts/9    00:00:00 grep Orbiter
root     30805     1  0 06:04 ?        00:00:01 /usr/bin/SCREEN -d -m -S OnScreen_Orbiter21 /usr/pluto/bin/Spawn_Device.sh 21 localhost LaunchOrbiter.sh
root     30807 30805  0 06:04 pts/27   00:00:00 /bin/bash /usr/pluto/bin/Spawn_Device.sh 21 localhost LaunchOrbiter.sh
root     30902 30807  0 06:04 pts/27   00:00:00 /bin/bash /usr/pluto/bin/LaunchOrbiter.sh -d 21 -r localhost -l /var/log/pluto/21_LaunchOrbiter.sh.log
root     30948 30902  0 06:04 pts/27   00:01:39 ./Orbiter -d 21 -r localhost -l /var/log/pluto/21_LaunchOrbiter.sh.log

This is a bit from the log:

Code: [Select]

Tue Sep 15 23:10:15 EDT 2009 died
========== NEW LOG SECTION ==========
1       09/15/09 23:10:26       21 (spawning-device)    ^[[1;00mStarting... 50^[[1;00m
1       09/15/09 23:10:26       21 (spawning-device)    ^[[1;00mFound /usr/pluto/bin/LaunchOrbiter.sh^[[1;00m
01      09/15/09 23:10:28.439           ^[[31;1mSDL_SetVideoMode hangs on init. Xorg is not initialized yet? Restarting...^[[0m <0xb6952b90>
Return code: 137
3       09/15/09 23:10:28       21 (spawning-device)    ^[[1;31mDevice died... count=50/50 dev=21^[[1;00m
Tue Sep 15 23:10:28 EDT 2009 died
3       09/15/09 23:10:38       21 (spawning-device)    ^[[1;31mAborting restart of device 21...^[[1
And if it is calling it twice, is this normal, and if not, where do I modify it to not do so.

Regards,

Seth

[phenigma]

Looks like you're experiencing the same issues many are:

http://forum.linuxmce.org/index.php?topic=8868.0
http://forum.linuxmce.org/index.php?topic=8815.0

J.

[rocketlynx]

Hey all,

Been a while since I have posted. But after this latest update, I needed to compare notes.....

My DirecTV boxes are controlled by the core with a USB-UIRT, and they are hooked into a PVR 500 and daughter card. Now the issue I am having is this:

I lose the orbiter on the core.

Hi Seth: I know you are having trouble with your Core's Orbiter, many of us are, but I only quoted a portion of your comment as I am interested in how you are using your DirecTV receivers throught LMCE.  I have several Dish Network Sat Receivers and would like to intergrate them directly into my core so I was wondering how you have your DirecTV sats hooked to a PVR-950 and available to the system (MDs)?

I don't want to Hi-Jack this threads purpose so we can do this on another topic or you can email me at my email address in my profile.

Thanks again and hang in there on the Core Orbiter's problem.  I just was astounded that last evening, my Core's Orbiter began working properly and I even checked it again this morning and it still was functioning as it should.  I'm thinking, if I reboot, the old evil 2 orbiters will appear again on the Core so I'm hoping I don't have to for a while.

Best Regards,
Charles