orca-robotics INTRODUCTION Overview Download and Install Quick Start Documentation Publications REPOSITORY Interfaces Components Libraries Utilities Software Map DEVELOPER Tutorials Examples Dev Guide Dashboard Wiki login/pass: orca/orca PEOPLE Contributors Users Project Download Mailing lists

Frequently Asked Questions Note: Reviewed for release 2.0.0. Troubleshooting Ice-Related Problems Getting "socket exception: Cannot assign requested address" on startup. Most likely your system is misconfigured. Turn up the warning level with Ice.Trace.Network=2 to see what address it is trying to assign. Check that it matches your actual IP address. Getting "syscall exception: No such file or directory" on starting IceBox. If you use a single config file for the whole IceBox application service then individual services are started without a configuration file. In such a case make sure that the environment variable ICE_CONFIG is not set to some non-existing file. That could be what the run-time is complaining about. Components not connecting while looking for 127.0.1.1 Some installers in Debian distribution may add a line in /etc/hosts which sets assigns the IP address 127.0.1.1 to the hostname. Comment this line out. Tips on using IceStorm service When misconfigured, IceStorm can lock up. When IceStorm encounters a problem with a subscriber, it immidiately drops it but only when a finite timeout is set. Otherwise, that thread will hang indefinitely and the tread pool will eventually become exausted. To solve this problem one must set a sensitive timeout. Here's a sample configuration. Ice.Override.ConnectTimeout=1000 Ice.Override.Timeout=300 Ice.ThreadPool.Client.Size=3 Ice.ThreadPool.Client.SizeWarn=5 Ice.ThreadPool.Client.SizeMax=5 Ice.ThreadPool.Server.Size=3 Ice.ThreadPool.Server.SizeWarn=5 Ice.ThreadPool.Server.SizeMax=5

Webmaster: Tobias Kaupp (tobasco at users.sourceforge.net)

---