Orbiter failed to register with the router error

[Junni]

This afternoon, I did a complete format, followed by a Ubuntu install + automatic update. In the meanwhile I downloaded the LinuxMCE disc with the torrentfile. Installation of LinuxMCE is still working at the moment!! I don't know why it's working now....maybe the torrent file (before this, I had the .iso from Europe) ? Maybe the format?

[jester]

I can confirm the previous post from Junni: installation with the torrent file went ok. Still quite a lot '404 file not found' on several packages but a working LinuxMCE install.

Now figuring out how the hell i got to configure it

Regards,
jester.

[Olav]

I also tried to download linuxmce from bittorrent. I installed it on a new ubuntu installation, but the problem is still there! Hoping this will be fixed soon, i have tried to install ubuntu and linuxmce 6 times now... :/

[wolfbite]

same here failing at Orbiter failed to register with the router error
switching from black to grey

full installs once with dchp, one without
always fails at same spot (else looks like it almost works)

check previous notes, will check logs later, but seems to be an issues
the error message has got to be coming from somewhere and have a reason

anyone want to break down in steps whats happening?
 

[efiniti]

i'm getting the same thing.  =(

I installed from the 1.0 iso. 

[wolfbite]

home now
checked dcerouter.log
only thing that looks interesting is that it says
target device 9 (routed to device 9) has not registered
whats device 9? only tv added (just want a basic start for now)

one other thing I did, was to delete all the logs in pluto (after it got to the 2 swapping black/grey screens)
deleted ALL logs in pluto
switched back to swapping screens (waited 3/4 swaps)
then back
and the only logs in pluto
  19_Launchorbiter.sh.log
  Flicker.log
  Deaths
  orbiter_detected_leaks.log
  orbiter_textures_leaks.log
  pluto.log
  running.pids
  SambScanner.log
  died_19_19

no dcerouter.log

more info for those that care (still stuck with swaping black/grey screens)

[rictec]

i think maybe is the network card try to check if even ubuntu can work with it

[efiniti]

Ok I posted a link to my log file (filesize a little bit too big).  I only included what happened earlier.  The log incorporates me turning on my computer, letting LinuxMCE start up, and the error showing up.  Right after that I made the log and uploaded it (it said I already made a post so I couldn't post until now).  I installed it as a core+hyrbrid and told it to start up LinuxMCE at startup.

Oh and btw my ra0 works fine (wireless card that connects to the internet).  LinuxMCE apparently installed a dhcp server on eth0 which is my onboard ethernet card.  That sounds kinda weird to me so right now I'm in the process of installing without a dhcp server.  So anyway, here's my log.  Maybe can make heads or tails of it.

http://c-forcecomputers.com/mylog.txt

[zyanide]

I have the exact same problem. After a fresh install the problem appears when I configure something on the admin webpage and do a "quick reload router".

08   04/04/07 18:53:54.574      Received Message from 31 (OnScreen Orbiter / Kontor) to Orbiter Plug-in(9), type 1 id 266 Command:Regen Orbiter, parameters: <0x847bdba0>
08   04/04/07 18:53:54.574        Parameter 2(PK_Device): 31 <0x847bdba0>
08   04/04/07 18:53:54.574        Parameter 21(Force):  <0x847bdba0>
08   04/04/07 18:53:54.574        Parameter 24(Reset):  <0x847bdba0>
05   04/04/07 18:53:54.575      The target device 9 (routed to 9) has not registered. <0x847bdba0>
05   04/04/07 18:53:54.575      Sender: 31 sent message type: 1 ID: 266 and expected a confirmation from 9 <0x847bdba0>
05   04/04/07 18:54:05.690      Socket::ReceiveData 0x8447a30 failed, bytes left 0 start: 1200000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 119 Incoming_Conn Socket 119 192.168.80.2 <0x847bdba0>
05   04/04/07 18:54:05.690      Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 119 192.168.80.2 <0x847bdba0>
05   04/04/07 18:54:05.690      TCPIP: Closing connection to -1003 (Router Dev #0) 0x8447a30 m_Socket: -1 <0x847bdba0>


Device 9 appears to be something called "Orbiter Plugin"

Any hints on how to fix this issue would be nice.

Rgds,
Atle

[zyanide]

Update: After playing around with this a bit more I noticed that every time I ran the wizard I turned off Asterisk and Text-to-speech. After turning them back on the "Orbiter plugin" is once again able to register.

Seems to be a nasty little bug there.

Rgds,
Atle

[wolfbite]

hmmm I also turned off asterix, but not the text to speech.

Its a clue, will test tonight

[efiniti]

hmm i did a reinstall and now i'm now getting the issue.  not sure what it could've been, but now i don't see the issue so i dunno.  gl to others out there tho.  =\

[madboo]

I had the same problem, re-enabling asterisk fixed it.

[Audun]

Update: After playing around with this a bit more I noticed that every time I ran the wizard I turned off Asterisk and Text-to-speech. After turning them back on the "Orbiter plugin" is once again able to register.

I can confirm that. Re-enabling Aterisk and Text-to-speech and a reboot did it.

[wolfbite]

Yep! confirmed here too

Might surgest a warning against that flag (or disabled until proven fixed)