Orbiter on the Core not showing up [SOLVED]

[Avner]

Hi,

After upgrading my lmce 1004 to the latest (apt-get upgrade), I don't get an Orbiter for the core.
Looking at the log file I see the following message repeating over and over again.

Code Select Expand

tail -f /var/log/pluto/23_LaunchProxy_Orbiter.sh.log
...
05      12/21/13 0:43:49.195            Received ANYNEWS? 10149, but device hasn't identified itself yet. <0xb4bb3b70>
05      12/21/13 0:43:49.195            Received: ANYNEWS? 10149 <0xb4bb3b70>
05      12/21/13 0:43:49.196            Socket::ReceiveData 0xadc2638 failed, bytes left 0 start: 4970000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 28 Incoming_Conn Socket 28 ::ffff:192.168.80.1 <0xb4bb3b70>
05      12/21/13 0:43:49.196            Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 28 ::ffff:192.168.80.1 <0xb4bb3b70>
05      12/21/13 0:43:49.196            TCPIP: Closing connection to -1 (Proxy_Orbiter) 0xadc2638 m_Socket: -1 <0xb4bb3b70>
...

05      12/21/13 8:33:20.435            Received ANYNEWS? 10296, but device hasn't identified itself yet. <0xb4bb4b70>
05      12/21/13 8:33:20.436            Received: ANYNEWS? 10296 <0xb4bb4b70>
05      12/21/13 8:33:20.436            Socket::ReceiveData 0x921c460 failed, bytes left 0 start: 15720000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 11 Incoming_Conn Socket 11 ::ffff:192.168.80.1 <0xb4bb4b70>
05      12/21/13 8:33:20.436            Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 11 ::ffff:192.168.80.1 <0xb4bb4b70>
05      12/21/13 8:33:20.436            TCPIP: Closing connection to -1 (Proxy_Orbiter) 0x921c460 m_Socket: -1 <0xb4bb4b70>

...


How come I'm getting a negative ID? (-1 Proxy_Orbiter)
Any ideas how to fix this problem?

Thanks,
Avner

[Avner]

Just to close this thread, this was a headless installation, so no Core orbiter is expected. What mislead me is that webadmin shows the following orbiters:
in "show device tree" view:

Code Select Expand

CORE

The core/hybrid
   The core 53
      OnScreen orbiter 55

Generic PC as MD 65
   OnScreen orbiter 67

Generic PC as MD 75
   OnScreen orbiter 77

It turns out that in a headless (core only) installation, "The core/hybrid" is just a skeleton structure but does not contain instances,
i.e. "OnScreen orbiter 55" does not exist.
Both CORE and The core/hybrid are installed, but the 'hybrid' portion will not run on a 'core only' install