Solution:
Verify if the Ioland connection has been established.
If you are using a permanent (-p) connection then the daemon will immediately establish the connection, if you are not then you will have to open the Ioland device with a process.
When the daemon has established a connection you will see two process's running. Example:
# ps -eaf | grep ioland
root 8656 8655 0 13:25:02 ? 00:00:00 ioland -C -m -p iolan2 10003 io3
root 8655 1 0 13:25:02 ? 00:00:00 ioland -C -m -p iolan2 10003 io3
If you see more than two process's per device then the daemon was spawned more than once. You must kill all the process's and then restart the daemon again.
If the is only one process (master) then this indicates that the slave could not establish the socket connection.
Verify that your device server is configured to listen for a TCP connection.
If your application requires full IO control then you must specify the -m or -a (push STREAMS) option for Ioland.
If more troubleshooting is required then you can enable the debug option on the daemon by adding the -x option. This will log detailed information in the /etc/ioland.lg file
See your Iolan+ User Guide for details on the switch options.