Orbiter won't start after configuration changes.

[archived]

After installing the core the orbiter would start in ratpoison when the machine was booted.  I logged into the web based configuration and tried to set up my CM11A and a lighting scenario.  On the next reboot the orbiter failed to start.  Not knowing the system I am at a loss when troubleshooting.  I've included the output from two relevant files below.  Does this indicate the problem is with the orbiter or the dce Router?  Is there any simple way to clear all of the configuration for a device?

Thanks in advance.

/var/log/pluto/pluto.log
1       01/16/05 15:20:11       /usr/pluto/bin/Spawn_Device.sh 2243 (spawning-device)   Appending log...
1       01/16/05 15:20:11       /usr/pluto/bin/Spawn_Device.sh 2243 (spawning-device)   Starting... 10
1       01/16/05 15:20:11       /usr/pluto/bin/Spawn_Device.sh 2243 (spawning-device)   Found ./Orbiter
3       01/16/05 15:20:13       /usr/pluto/bin/Spawn_Device.sh 2243 (spawning-device)   Device died... 10 2243
/var/log/pluto/####_Orbiter.newlog

10      01/16/05 15:20:11.456           Device: 2243 starting
01      01/16/05 15:20:11.457           Connect() failed, Error Code 111
01      01/16/05 15:20:11.457           Connect() failed, Error Code 111
01      01/16/05 15:20:11.457           Connect() failed, Error Code 111
01      01/16/05 15:20:11.457           ClientSocket::Connect() not successful
01      01/16/05 15:20:11.458           void ClientSocket::Disconnect()
01      01/16/05 15:20:11.458           Socket::ReceiveString failed, m_socket -1 buf 0xbfffe540 Event Dev #2243
21      01/16/05 15:20:11.458           Dumping locks 0x811096c mutex 0x8110978

21      01/16/05 15:20:11.458           Size of locks: 0

01      01/16/05 15:20:11.458           DCE Router cannot give us config:
13      01/16/05 15:20:11.458           RequestSocket::Disconnect 0x811ebf0 device: 2243
01      01/16/05 15:20:11.458           void ClientSocket::Disconnect()
Sun Jan 16 15:20:13 CST 2005 died

[archived]

The problem is that it's not able to connect to the DCERouter, which listens on port 3450.  The Orbiter will attempt to connect to the Router on port 3450.  So the problem is actually with the router--not the Orbiter.  Is your Router running on the same computer as the Orbiter (ie a hybrid), or is it running on another computer across the network?  On whatever computer the Router is running, you can type "screen -ls" to see a list of the active screen sessions.  You should see one called DCERouter, if the router is running.  You can also type "screen -r ID" where ID is the screen session's ID returned from screen -ls.  That will attach to the DCERouter that is running so you can see what it's doing.  You can also tail the DCERouter.newlog in /var/log/pluto to see what it's doing (you'll see the same thing as if you attach to the screen session).  If you have time when you get this, please click on 'live help' so we can have an instant chat and narrow it down.  I'll then post the results back in this forum.

Thanks,
Aaron

[archived]

Hi aaron,

I have the same problem. I've just made a new installation of Plutohome (I've installed Core/Hybrid). Now I can access to the Pluto admin site and login to the dcerouter via ssh but the Orbiter shows nothing. It displays just initial gray screen. I've run screen -ls and then screen -r <pid which belongs to OnScreen Orbiter>. The output is there:

Code:

10      03/17/06 6:08:14.864            Device: 18 starting
10      03/17/06 6:08:14.897            Orbiter 0x81acf40 constructor
10      03/17/06 6:08:14.916            XRecordExtensionHandler::recordingThreadMainFunction(): Available XRecord extension with version 13.1.
10      03/17/06 6:08:14.918            XRecordExtensionHandler::recordingThreadMainFunction(): Recording thread going to sleep!!!
10      03/17/06 6:08:15.159            Initialized SDL
10      03/17/06 6:08:15.160            Inside Hacktrhead #2
01      03/17/06 6:08:17.177            Another stupid problem since the kernel upgrade.  SDL_SetVideoMode can just hang on init.  It happened. Kill ourselves
/usr/pluto/bin/Spawn_Device.sh: line 167:  5814 Segmentation fault      (core dumped) /usr/pluto/bin/Spawn_Wrapper.sh "$Path$cmd_line" -d "$device_id" -r "$ip_of_router" >&>(tee "$new_log")
3       03/17/06 06:08:18       /usr/pluto/bin/Spawn_Device.sh /usr/pluto/bin/Spawn_Device.sh 18 (spawning-device)      Device died... 1 18
out
1       03/17/06 06:08:39       /usr/pluto/bin/Spawn_Device.sh /usr/pluto/bin/Spawn_Device.sh 18 (spawning-device)      Appending log...
1       03/17/06 06:08:39       /usr/pluto/bin/Spawn_Device.sh /usr/pluto/bin/Spawn_Device.sh 18 (spawning-device)      Starting... 2
1       03/17/06 06:08:39       /usr/pluto/bin/Spawn_Device.sh /usr/pluto/bin/Spawn_Device.sh 18 (spawning-device)      Found ./LaunchOrbiter.sh
Processing #19 (200)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2767  100  2767    0     0   1763      0  0:00:01  0:00:01 --:--:--  4906
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  9910    0  9910    0     0   3974      0 --:--:--  0:00:02 --:--:--  6655

You can see there a message "Segmentation fault" when the script Spawn_Device.sh is running. Any idea why the Orbiter is not working and how to fix it?
Thank in advanced.