Author Topic: Solved - This orbiter will be closed message.  (Read 5714 times)

pigdog

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1008
    • View Profile
Solved - This orbiter will be closed message.
« on: September 06, 2009, 02:50:24 am »
Hi,

After everything seemed to update correctly I rebooted.

On startup I am getting an OK screen (after flicker screen view) that states

An orbiter with the same device id of 127.0.0.1 was started.
This orbiter will be closed.

Then...grey screen of death.  Cursor moves.

Did a <CTRL/ALT>F1 or F2 then back to F7 kinda got main menu back, left/right mouse clicks - no flicker screens.

Used main menu to kinda get to KDE desktop but was part successful then lost everything but OrbiterGL screen on status bar.

Managed to get console window working.

Played around going back to orbiter but things really screwed up trying quick reload.

Got,

An orbiter with the same device id of 127.0.0.1 was started.
This orbiter will be closed.

...messages.

Did a Quick Regen this Orbiter.   Things seemed to settle down.

Did complete cold boot.  Power off PSU.  Power up.

Same black OK screen...

An orbiter with the same device id of 127.0.0.1 was started.
This orbiter will be closed.

...was generated.

Then grey screen of death.  Did <Ctrl/ALT> F1  Hit return for login prompt.

<CTRL/ALT> F7 main menu screen "no flicker photo background".

Main menu> Advanced> Regen this Orbiter get "Stage 1 of 2" messages.

Flicker photo background appears.

Main Menu> KDE Desktop works O.K.

Webadmin via Konqueror works.

Haven't tried MD's yet.

Is it only me?
« Last Edit: October 15, 2009, 11:57:04 am by pigdog »

fido

  • Regular Poster
  • **
  • Posts: 27
    • View Profile
Re: This orbiter will be closed message.
« Reply #1 on: September 06, 2009, 12:59:22 pm »
The very same thing happened to me since updating my 0810 build a couple of days ago.  I got the message

"An orbiter with the same device id of 127.0.0.1 was started.
This orbiter will be closed."

I had to reboot and thankfully it all worked again.  It has happened to me at least twice now.

In addition and whether this is related or not i dont know, but each time any new device is detected, DCERouter dies and reloads.  The device is added fine.....

Very strange.


maverick0815

  • Addicted
  • *
  • Posts: 545
    • View Profile
Re: This orbiter will be closed message.
« Reply #2 on: September 06, 2009, 01:20:34 pm »
same  happened here...

Itsik

  • Guru
  • ****
  • Posts: 190
    • View Profile
Re: This orbiter will be closed message.
« Reply #3 on: September 07, 2009, 04:10:26 pm »
yep, here as well ...

posde

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 3009
  • Wastes Life On LinuxMCE Since 2007
    • View Profile
    • My Home
Re: This orbiter will be closed message.
« Reply #4 on: September 07, 2009, 05:11:01 pm »
Did anyone open a trac ticket with some logs about this...

pigdog

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1008
    • View Profile
Re: This orbiter will be closed message.
« Reply #5 on: September 08, 2009, 01:28:12 am »
Hi posde,

I was considering doing a from scratch rebuild in order to determine if this was related to the alpha 2.30 snafu and/or 2.32/2.33 & 2.34 fixes.

If it returned I could grab logs, if gone it's then something residual.

Is there a way you'd rather proceed?

Cheers.

P.S.  If you don't Regen this orbiter on the Core and you go to KDE Desktop the main menu image (sans flicker - not running) is superimposed over the KDE image.
« Last Edit: September 08, 2009, 01:36:22 am by pigdog »

rocketlynx

  • Veteran
  • ***
  • Posts: 136
    • View Profile
Re: This orbiter will be closed message.
« Reply #6 on: September 08, 2009, 03:37:10 am »
I also have the same problem.  I've had this recently, I think, since the Alpha-2.3x updates but it could have been a few updates before that.  

It seems that the Core/Hybrid is confused and starts the Orbiter a second time on reboot and DCERouter reloads.  If I knew where the script that loads the Core's OnScreenOrbiter was, I'd look to see if somehow it got a double entry.  

Also, just checked, rebooted MDs and they seem to be OK!
« Last Edit: September 08, 2009, 03:46:08 am by rocketlynx »

maverick0815

  • Addicted
  • *
  • Posts: 545
    • View Profile
Re: This orbiter will be closed message.
« Reply #7 on: September 08, 2009, 03:46:38 pm »
I did a clean install after this, and got no messages like that again

pigdog

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1008
    • View Profile
Re: This orbiter will be closed message.
« Reply #8 on: September 08, 2009, 04:52:45 pm »
Hi,

I did a re-install and this problem was corrected.

I will rename the title to Resolved.

Cheers.

rocketlynx

  • Veteran
  • ***
  • Posts: 136
    • View Profile
Re: This orbiter will be closed message.
« Reply #9 on: September 08, 2009, 06:20:46 pm »
Hi,

I did a re-install and this problem was corrected.

I will rename the title to Resolved.

Cheers.

Ok, before I do a re-install, I have a question.  Are you doing a backup and then a restore after the clean re-install?  Also, I've done backus but never had to use them.  What does the backup contain and what does it restore?  Does it restore MDs or, do you restore the backup and then create the MDs?  Or, do you stay away from the restore because it may re-corrupt the new installation.

What's the order?

Thanks,
Charles

pigdog

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1008
    • View Profile
Re: Resolved - This orbiter will be closed message.
« Reply #10 on: September 08, 2009, 06:41:16 pm »
Hi,

The script responsible for generating backups is /usr/pluto/bin/PlutoRestorePoint.sh

It looks like it does this...

-pluto_main database
-asterisk database
-files needed by the web admin
   - floorplans, users, rooms, scenarios
-the pluto.conf config file

If you have media on your LinuxMCE HDD, or mythtv stuff, vdr, etc this stuff would probably be lost.  You may be able to mod the script - I don't know.

I didn't do a backup/restore because I wasn't sure about corruption from original problem, cache-ng, etc., etc.

I'm rebuilding everything.

felpouse

  • Veteran
  • ***
  • Posts: 99
    • View Profile
Re: Resolved - This orbiter will be closed message.
« Reply #11 on: September 08, 2009, 08:04:53 pm »
Hi all,

I've encountered the same issue. But actually for me make a reinstall is really difficult.
I tried this way. If u check the processes via ssh with ps -auxwf u'll finf the pid of OrbiterGL -d NN process that is involved on the UI interface.

If u kill it, the fist pid one that was started restart and u can have again the interface working perfectly.

It could be better to understand why this happened, because until yesterday I never have it .

Code: [Select]
05      09/08/09 19:54:49.117           Got a reload command from 0  <0xb434db90>
05      09/08/09 19:54:49.375           Orbiter reloading... <0xb434db90>
05      09/08/09 19:54:49.375           Orbiter quiting... <0xb434db90>
05      09/08/09 19:54:49.375           Got an on quit.  Pushing an event into SDL <0xb434db90>
05      09/08/09 19:54:49.375           Got an on quit.  Pushing an event into SDL <0xb434db90>
05      09/08/09 19:54:49.449           XRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=142847376, pDisplay_DataConnection=142869320 ->Closing <0xb0afdb90>
05      09/08/09 19:54:49.450           XRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=142847376, pDisplay_DataConnection=142869320 ->Closed <0xb0afdb90>
05      09/08/09 19:54:52.842           void ClientSocket::Disconnect() on this socket: 0x87809c0 (m_Socket: 16) <0xb62f66e0>
Return code: 2
2       09/08/09 19:54:52       21 (spawning-device)    Device requests restart... count=2/50 dev=21
Tue Sep  8 19:54:52 CEST 2009 Restart
========== NEW LOG SECTION ==========
1       09/08/09 19:55:00       21 (spawning-device)    Starting... 2
1       09/08/09 19:55:00       21 (spawning-device)    Found /usr/pluto/bin/LaunchOrbiter.sh
05      09/08/09 19:55:11.433           Replacement SDL window created! <0xb5a4cb90>
05      09/08/09 19:55:11.613           Using masked UI? NO <0xb5a4cb90>
05      09/08/09 19:55:13.305           Creating child 22 <0xb624e6e0>
05      09/08/09 19:55:13.315           Creating child 23 <0xb624e6e0>
05      09/08/09 19:55:13.345           Creating child 25 <0xb624e6e0>
05      09/08/09 19:55:13.411           Creating child 26 <0xb624e6e0>
05      09/08/09 19:55:13.463           Creating child 30 <0xb624e6e0>
05      09/08/09 19:55:13.470           Creating child 35 <0xb624e6e0>
05      09/08/09 19:55:14.040           VisibilityNotify! <0xb624e6e0>
05      09/08/09 19:55:14.040           EnterNotify! <0xb624e6e0>
05      09/08/09 19:55:14.040           FocusIn! <0xb624e6e0>
05      09/08/09 19:55:14.040           VisibilityNotify! <0xb624e6e0>
05      09/08/09 19:55:14.040           VisibilityNotify! <0xb624e6e0>
05      09/08/09 19:55:14.040           FocusOut! <0xb624e6e0>
05      09/08/09 19:55:14.040           FocusIn! <0xb624e6e0>
05      09/08/09 19:55:14.041           LeaveNotify! <0xb624e6e0>
05      09/08/09 19:55:14.041           EnterNotify! <0xb624e6e0>
05      09/08/09 19:55:14.205           FocusOut! <0xb624e6e0>
== ATTEMPT FRESH START ==
1       09/08/09 19:55:14       /usr/pluto/bin/Spawn_Device.sh 21 (spawning-device)     11136 Dev: 21; Already Running list: 15,16,18,34,19,27,28,38,25,22,23,26,35,30,
== FRESH START ==
1       09/08/09 19:55:14       /usr/pluto/bin/Spawn_Device.sh 21 (spawning-device)     device: 21 ip: localhost cmd_line: LaunchOrbiter.sh
0       09/08/09 19:55:14       21 (spawning-device)    Entering 21
========== NEW LOG SECTION ==========
1       09/08/09 19:55:14       21 (spawning-device)    Starting... 1
1       09/08/09 19:55:14       21 (spawning-device)    Found /usr/pluto/bin/LaunchOrbiter.sh
05      09/08/09 19:55:14.872           Replacement SDL window created! <0xb5a1ab90>
05      09/08/09 19:55:15.073           Using masked UI? NO <0xb5a1ab90>
05      09/08/09 19:55:15.551           Creating child 22 <0xb62236e0>
05      09/08/09 19:55:15.591           Creating child 23 <0xb62236e0>
05      09/08/09 19:55:15.612           FocusOut! <0xb624e6e0>
05      09/08/09 19:55:15.612           LeaveNotify! <0xb624e6e0>
05      09/08/09 19:55:15.620           Creating child 25 <0xb62236e0>
05      09/08/09 19:55:15.742           Creating child 26 <0xb62236e0>
05      09/08/09 19:55:15.758           Creating child 30 <0xb62236e0>
05      09/08/09 19:55:15.789           Creating child 35 <0xb62236e0>
05      09/08/09 19:55:15.860           VisibilityNotify! <0xb624e6e0>
05      09/08/09 19:55:15.860           EnterNotify! <0xb624e6e0>
05      09/08/09 19:55:16.012           FocusIn! <0xb624e6e0>
05      09/08/09 19:55:16.052           FocusOut! <0xb624e6e0>
05      09/08/09 19:55:16.252           FocusIn! <0xb624e6e0>
05      09/08/09 19:55:16.423           LeaveNotify! <0xb624e6e0>
05      09/08/09 19:55:16.423           FocusOut! <0xb624e6e0>
05      09/08/09 19:55:16.423           VisibilityNotify! <0xb62236e0>
05      09/08/09 19:55:16.423           FocusIn! <0xb62236e0>
05      09/08/09 19:55:16.423           VisibilityNotify! <0xb62236e0>
05      09/08/09 19:55:16.423           VisibilityNotify! <0xb62236e0>
05      09/08/09 19:55:16.423           FocusOut! <0xb62236e0>
05      09/08/09 19:55:16.423           EnterNotify! <0xb62236e0>
05      09/08/09 19:55:16.423           FocusIn! <0xb62236e0>
05      09/08/09 19:55:16.684           FocusOut! <0xb624e6e0>
05      09/08/09 19:55:26.680           Orbiter quiting... <0xb43aab90>
05      09/08/09 19:55:26.681           Got an on quit.  Pushing an event into SDL <0xb43aab90>
05      09/08/09 19:55:26.685           XRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=167276088, pDisplay_DataConnection=167278208 ->Closing <0xb09fdb90>
05      09/08/09 19:55:26.686           XRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=167276088, pDisplay_DataConnection=167278208 ->Closed <0xb09fdb90>
05      09/08/09 19:55:26.820           LeaveNotify! <0xb62236e0>
05      09/08/09 19:55:26.820           FocusOut! <0xb62236e0>
05      09/08/09 19:55:30.654           void ClientSocket::Disconnect() on this socket: 0x9e7f9c0 (m_Socket: 16) <0xb624e6e0>
Return code: 0
2       09/08/09 19:55:30       21 (spawning-device)    Shutting down... count=2/50 dev=21
Tue Sep  8 19:55:30 CEST 2009 Shutdown
Return code: 137
3       09/08/09 19:56:45       21 (spawning-device)    Device died... count=1/50 dev=21
Tue Sep  8 19:56:45 CEST 2009 died
========== NEW LOG SECTION ==========
1       09/08/09 19:56:55       21 (spawning-device)    Starting... 2
1       09/08/09 19:56:55       21 (spawning-device)    Found /usr/pluto/bin/LaunchOrbiter.sh
05      09/08/09 19:56:56.333           Replacement SDL window created! <0xb58ffb90>
05      09/08/09 19:56:56.470           will overwrite wm window id // void X11wrapper::Assign_WmWindow(Window) <0xb58ffb90>
05      09/08/09 19:56:56.474           Using masked UI? NO <0xb58ffb90>
05      09/08/09 19:56:57.088           Creating child 22 <0xb62a16e0>
05      09/08/09 19:56:57.149           Creating child 23 <0xb62a16e0>
05      09/08/09 19:56:57.200           Creating child 25 <0xb62a16e0>
05      09/08/09 19:56:57.222           Creating child 26 <0xb62a16e0>
05      09/08/09 19:56:57.269           Creating child 30 <0xb62a16e0>
05      09/08/09 19:56:57.301           Creating child 35 <0xb62a16e0>
05      09/08/09 19:57:01.158           VisibilityNotify! <0xb62a16e0>
05      09/08/09 19:57:01.158           EnterNotify! <0xb62a16e0>
05      09/08/09 19:57:01.293           FocusIn! <0xb62a16e0>
05      09/08/09 19:57:01.293           VisibilityNotify! <0xb62a16e0>
05      09/08/09 19:57:01.293           VisibilityNotify! <0xb62a16e0>
05      09/08/09 19:57:01.293           LeaveNotify! <0xb62a16e0>
05      09/08/09 19:57:01.294           EnterNotify! <0xb62a16e0>
05      09/08/09 19:57:01.294           FocusOut! <0xb62a16e0>
05      09/08/09 19:57:01.294           FocusIn! <0xb62a16e0>
05      09/08/09 19:57:01.294           FocusOut! <0xb62a16e0>
05      09/08/09 19:57:01.294           LeaveNotify! <0xb62a16e0>
05      09/08/09 19:57:01.294           VisibilityNotify! <0xb62a16e0>
05      09/08/09 19:57:01.294           EnterNotify! <0xb62a16e0>
05      09/08/09 19:57:01.294           FocusIn! <0xb62a16e0>
05      09/08/09 19:57:01.421           FocusOut! <0xb62a16e0>

If someone could give me some support we can try to investigate on it.
I suppose that could be related to a defunct process/script lauched that involved in a second start of the LaunchOrbiter.sh script and the error on the UI interface.

Best regards

Luke

rocketlynx

  • Veteran
  • ***
  • Posts: 136
    • View Profile
Re: Resolved - This orbiter will be closed message.
« Reply #12 on: September 10, 2009, 07:08:05 am »
Hi all,

I've encountered the same issue. But actually for me make a reinstall is really difficult.
I tried this way. If u check the processes via ssh with ps -auxwf u'll finf the pid of OrbiterGL -d NN process that is involved on the UI interface.

If u kill it, the fist pid one that was started restart and u can have again the interface working perfectly.

It could be better to understand why this happened, because until yesterday I never have it .

If someone could give me some support we can try to investigate on it.
I suppose that could be related to a defunct process/script lauched that involved in a second start of the LaunchOrbiter.sh script and the error on the UI interface.

Best regards

Luke
This kill is only good for the current boot, correct?  That is, when you reboot, since it hasn't been fixed, the same problem will return.  I wonder if anyone who understands this strange situation could comment on where the problem is coming from and if there is a way to fix it short of a complete re-install.  Also, since my Core/Hybrid is in a closet and I don't really use it as a Media Director, I'll try to live with it until a fix comes along.

Charles

canukguy1974

  • Regular Poster
  • **
  • Posts: 42
    • View Profile
Re: Resolved - This orbiter will be closed message.
« Reply #13 on: September 11, 2009, 12:50:56 am »
 I have the same problem. Is there away that we can revert the upgrade. I don't see how reinstalling it is away to resolve the issue. We need to find out why the handful of us have this issue and others don't. I deleted all the orbiters from web admin except Orbiter #20 the onscreen and I still get the same thing. When I check processes I notice that LaunchOrbiter.sh is listed like 10 times. I am still new to linuxmce so I am still guessing. I really don't want to re-install the whole system again. I have alot of media on this. When I do a re-install can I save my /home folder so I don't lose all my media and settings?

EDIT*******
this is the log for 20_LaunchOrbiter.sh.log
Code: [Select]
== ATTEMPT FRESH START ==
1 09/07/09 22:52:10 /usr/pluto/bin/Spawn_Device.sh 20 (spawning-device) 27482 Dev: 20; Already Running list: 21,25,22,30,24,15,16,17,18,27,28,
== FRESH START ==
1 09/07/09 22:52:10 /usr/pluto/bin/Spawn_Device.sh 20 (spawning-device) device: 20 ip: localhost cmd_line: LaunchOrbiter.sh
0 09/07/09 22:52:10 20 (spawning-device) Entering 20
========== NEW LOG SECTION ==========
1 09/07/09 22:52:10 20 (spawning-device) Starting... 1
1 09/07/09 22:52:10 20 (spawning-device) Found /usr/pluto/bin/LaunchOrbiter.sh
05 09/07/09 22:52:11.007 Replacement SDL window created! <0xb5939b90>
05 09/07/09 22:52:11.168 will overwrite wm window id // void X11wrapper::Assign_WmWindow(Window) <0xb5939b90>
05 09/07/09 22:52:11.174 Using masked UI? NO <0xb5939b90>
05 09/07/09 22:52:11.434 Creating child 21 <0xb613b6e0>
05 09/07/09 22:52:11.445 Creating child 22 <0xb613b6e0>
05 09/07/09 22:52:11.458 Creating child 24 <0xb613b6e0>
05 09/07/09 22:52:11.471 Creating child 25 <0xb613b6e0>
05 09/07/09 22:52:11.494 Creating child 30 <0xb613b6e0>
05 09/07/09 22:52:11.824 VisibilityNotify! <0xb613b6e0>
05 09/07/09 22:52:11.824 EnterNotify! <0xb613b6e0>
05 09/07/09 22:52:11.824 FocusIn! <0xb613b6e0>
05 09/07/09 22:52:11.824 VisibilityNotify! <0xb613b6e0>
05 09/07/09 22:52:11.824 VisibilityNotify! <0xb613b6e0>
05 09/07/09 22:52:11.824 LeaveNotify! <0xb613b6e0>
05 09/07/09 22:52:11.825 FocusOut! <0xb613b6e0>
05 09/07/09 22:52:11.825 EnterNotify! <0xb613b6e0>
05 09/07/09 22:52:11.825 FocusIn! <0xb613b6e0>
05 09/07/09 22:52:13.187 error_code==1 => ErrorText=='BadRequest (invalid request code or no such operation)' // bool X11wrapper::Mouse_Grab(Window, Window) <0xb62da6e0>
05 09/07/09 22:52:13.188 error_code==1 => ErrorText=='BadRequest (invalid request code or no such operation)' // bool X11wrapper::Keyboard_Grab(Window) <0xb62da6e0>
05 09/07/09 22:52:13.190 VisibilityNotify! <0xb62da6e0>
05 09/07/09 22:52:13.190 EnterNotify! <0xb62da6e0>
05 09/07/09 22:52:13.309 FocusIn! <0xb62da6e0>
05 09/07/09 22:52:13.309 VisibilityNotify! <0xb62da6e0>
05 09/07/09 22:52:13.309 VisibilityNotify! <0xb62da6e0>
05 09/07/09 22:52:13.309 FocusOut! <0xb62da6e0>
05 09/07/09 22:52:13.309 LeaveNotify! <0xb62da6e0>
05 09/07/09 22:52:13.309 EnterNotify! <0xb62da6e0>
05 09/07/09 22:52:13.309 LeaveNotify! <0xb62da6e0>
05 09/07/09 22:52:13.310 VisibilityNotify! <0xb62da6e0>
05 09/07/09 22:52:13.310 EnterNotify! <0xb62da6e0>
05 09/07/09 22:52:13.310 FocusIn! <0xb62da6e0>
05 09/07/09 22:52:13.310 LeaveNotify! <0xb62da6e0>
05 09/07/09 22:52:13.310 FocusOut! <0xb62da6e0>
05 09/07/09 22:52:13.310 FocusOut! <0xb62da6e0>
05 09/07/09 22:52:13.310 FocusIn! <0xb62da6e0>
05 09/07/09 22:52:13.591 FocusOut! <0xb62da6e0>
05 09/07/09 22:52:22.271 FocusIn! <0xb62da6e0>
05 09/07/09 22:52:22.435 FocusOut! <0xb62da6e0>
05 09/07/09 22:52:22.563 Orbiter quiting... <0xb45e8b90>
05 09/07/09 22:52:22.564 Got an on quit.  Pushing an event into SDL <0xb45e8b90>
05 09/07/09 22:52:22.583 XRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=163633600, pDisplay_DataConnection=-1307217360 ->Closing <0xb0ffdb90>
05 09/07/09 22:52:22.583 XRecordExtensionHandler::recordingThreadMainFunction(): pDisplay_ControlConnection=163633600, pDisplay_DataConnection=-1307217360 ->Closed <0xb0ffdb90>
05 09/07/09 22:52:22.659 LeaveNotify! <0xb613b6e0>
05 09/07/09 22:52:22.659 FocusOut! <0xb613b6e0>
05 09/07/09 22:52:26.795 void ClientSocket::Disconnect() on this socket: 0x9823f00 (m_Socket: 16) <0xb62da6e0>
Return code: 0
2 09/07/09 22:52:26 20 (spawning-device) Shutting down... count=1/50 dev=20
Mon Sep  7 22:52:26 EDT 2009 Shutdown
/code]
« Last Edit: September 11, 2009, 01:28:48 am by canukguy1974 »

pigdog

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1008
    • View Profile
Re: Resolved - This orbiter will be closed message.
« Reply #14 on: September 12, 2009, 12:01:43 am »
Hi canukguy1974,

I thought it might be possible to downgrade ...

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

... however, since I've rebuilt I've been fine and no re-occurrence

If your media is separate from your HDD that has your OS ie: on a NAS, partition, etc., you media will be fine.

If you have one big HDD with everything - don't do that!

Separated...

the OS may change but the media stays the same.

Queue the music.