To answer the question about logs, there are several ways to get to them depending on what you have available and which method you are most comfortable with. If you have a the desktop running, simply open the file browser and (like windows) move through the directory tree to the path /var/log/pluto/. Double-clicking the file named DCErouter.log will open it up.
If you don't have a desktop running, Alt+F2 should take you to another console/terminal window. In here you can use the same commands as if you were SSHd into the box from another machine...
Run an SSH client such as putty from another machine on the network and connect to the IP address of your linux box. Login with the credentials you use for admin on the web interface and you should be dropped into a prompt like (userid)@DCErouter:. Use the CD command to change directories like old DOS machines like so:
cd /var/log/pluto and hit enter.
Now you can "tail ./DCERouter.log" without the ""s to see the last few lines of the log file. You can also "more DCERouter.log" (again without the ""s) to page through the file one screen at a time. The DOS dir command works just like it did back then or else use the ls command to list files. The q key will quit out of a "more" display.
As for your error, I'm not getting the same thing on boot, but I can't add an orbiter to my system because it says it can't connect to the DCERouter. I'm wondering if they are related.
I have two core dumps on my system to look at, but I can't open them. The tail of my DCERouter.log file shows several internal communications on 127.0.0.1 which is the machine passing messages to itself, but no errors. If I more the file (it's big) I see lots of stuff, but no failures in the first few thousand lines. PS shows the DCERouter is running.
If anyone else can shed some light, that would be great. I'm hoping to test orbiters on Windows hosts and PXE boot of diskless machines to put by my TVs.
Thanks in advance for the help and I hope I answered some of your questions.