main | install | faq | rio | redrat | sdk |
Describing symptoms and diagnostic steps you can follow to get things working.
You may also want to check out server-trouble.
In some systems, especially those with multiple network interfaces, the default interface selected by Java isn't necessarily the one that is visible to the Rio. Resolve this by entering the IP which is visible to the Rio.
By default this restriction includes two popular internal subnets:
192.168.xxx.xxx and 10.xxx.xxx.xxxIf your Rio is using an IP not in this range, visit the Rio settings and set the "Hosts to Allow Access" option.
ps aux | grep dhcpd
Check your configuration as stated in the install docs.
Try pinging the Rio:
ping RIOIP
where RIOIP is the fixed IP you've assigned to your Rio.
Try a test mount, preferably from another system. Under Linux...
mkdir /rio_temp mount -t nfs HOSTNAME:/tftpboot/RIOIP /rio_temp
where HOSTNAME is the server hosting the receiver.arf NFS share and RIOIP is the fixed IP address you've assigned to your Rio.
Examine the /var/log/syslog and look for denied connections.
Are permissions set correctly?
Make certain you've added read permissions to /tftpbootchmod -R u+r,o+r /tftpboot
Try browsing to
http://HOSTNAME:8080/tagswhere HOSTNAME is the server hosting Jetty and the jrec_rio.war webapp.
Restart Jetty if necessary. Under Linux...
$JREC_HOME/bin/jrec_jetty.sh restart
See Enabling Debugging in the JRec FAQ.
main | install | faq | rio | redrat | sdk |