Troubleshooting

Updating the Security Jar File

This is updated on the Kiosk Controller in the folder /bin/KioskNet/secure-dir-api/

Network Card of the VIA BOX Doesnt Work

Problems with the Kiosk Controller : On the first boot up the ethernet port of the VIA box may not turn up . It because of some driver problem so we need to do the following:

$ cd /lib/modules/2.6.18-6-486/kernel/drivers/net

               $ rmmod via-rhine.ko

               $ insmod via-rhine.ko

These two steps could easily help in bringing up one of the ethernet ports of the Kiosk Controller in the VIA box.

Installing the package on Debian

The command below searches for any installed packages on the machine.

$dpkg -l | grep <package name>

If you want to search on the web for the packages

$apt-cache search <packagename>

If you want to download and install the package

$apt-get install <package name>

Modifying the Subnet

Some times when setting up the stuff in laboratory we might need to change the subnets.As by default the things are set to 192.168.1.* subnet. If we want to change it to a different value 192.168.2.*.

So we need to modify the things in following three files which are by default hard coded

/etc/dhcpd.conf

/etc/exports

/etc/networks/interfaces

Ethernet Problems

Some time the hardware link might be defective although ifconfig shows things alright but the system doesnt ping then try changing the ethernet port.

More than one ethernet port is coming up

Sometimes more than one ethernet port may come up after rebooting a server. If so, you need to manually bring down the ports you aren't using with the ifdown command.

For instance, suppose both eth7 and eth8 come up after a reboot, and you are only using eth7, you need to bring down eth8.

$ifdown eth8

Tips and Tricks

Tips and Tricks :

They would work only if you have all these scripts available on the gateway. They are available for download from the CVS.

Stopping OCMP

$ killall java

This command has to be executed on the kiosk and the ferry to stop the OCMP.

Restart OCMP

This has to be done on both the Kiosk and the Ferry.

$/etc/init.d/ocmpclient start

EID and IP of Proxy in ocmp.txt

Important : Take care of the proxy IP address and EID in the file ocmp.txt lying in the folder on all the node ----------> /var/ocmp/ocmp.txt They should be exactly similar to the IP address you assigned it during the installation and EID which was given during the installation of the Proxy.

Updating the OCMP code

Updated ocmp2.jar file should be placed in the folder /usr/local/ocmp/

Description File

Every file which is to be transmitted from the Kiosk to the Proxy should have a description file which tells about the destination ID of the file.

Its looks like this :
proxy2.self.uw2.kiosknet.org

Check if flipper is running

This is only relevant if you are testing KioskNet in a lab, and are simulating ferry movement using the essid_flipper script. To see if flipper is running do the following :

$ ps ax | grep essid

To see the functionality of the flipper online we can do the following :

$ tail -f /var/log/ocmpclient.log

We can see the flipping of association of the ferry with the gateway and the kiosk.

Return to deployment guide.