Client Problems

1. Client does not connect to testserver.coda.cs.cmu.edu.
2. Venus comes up but prints cannot find RootVolume.
3. Trying to access a file returns Connection timed out (ETIMEDOUT).
4. Commands do not return, except by using ^C.
5. Venus fails when restarted.
6. Venus doesn't start.
7. I'm disconnected and Venus doesn't start.
8. I cannot get tokens while disconnected.
9. Hoard doesn't work.
10. File System Full

1. Client does not connect to testserver.coda.cs.cmu.edu.

When you have set up your client for the first time, and it can not connect to the testserver at CMU, there are a couple of possible reasons. You might be running an old release of Coda, check the Coda web-site to see what the latest release is.

Another common reason is that your site is behind a firewall, which blocks, or allows only outgoing, udp traffic. Either try Coda on a machine outside of the firewall, or set up your own server.

The third reason is that the testserver might be down, for maintenance or upgrades. That does not happen often, but you can check whether it is up, and how long it has been running using cmon.

client$ cmon testserver.coda.cs.cmu.edu

2. Venus comes up but prints cannot find RootVolume.

All of the reasons in the previous item could be the cause. It is also possible that your /etc/services file is not allright. It needs the entries:
# IANA allocated Coda filesystem port numbers
rpc2portmap     369/tcp    
rpc2portmap     369/udp    # Coda portmapper
codaauth2       370/tcp    
codaauth2       370/udp    # Coda authentication server

venus           2430/tcp   # codacon port
venus           2430/udp   # Venus callback/wbc interface 
venus-se        2431/tcp   # tcp side effects
venus-se        2431/udp   # udp sftp side effect
codasrv         2432/tcp   # not used
codasrv         2432/udp   # server port
codasrv-se      2433/tcp   # tcp side effects
codasrv-se      2433/udp   # udp sftp side effect

3. Trying to access a file returns Connection timed out (ETIMEDOUT).

The main reason for getting Connection timed out errors is that the volume where the file is located is disconnected from the servers. However, it can also occur in some cases when the client is in write-disconnected mode, and there is an attempt to read a file which is open for writing. See the section called Disconnections. for more information.

4. Commands do not return, except by using ^C.

When command are hanging it is likely that venus has crashed. Check /usr/coda/etc/console and /usr/coda/venus.cache/venus.log.

5. Venus fails when restarted.

If venus complains in venus.log about not being able to open /dev/cfs0, it is because /coda is still mounted.
# umount /coda
Another reason for not restarting is that another copy of venus is still around, and venus is unable to open it's network socket. In this case there will be a message in venus.log stating that RPC2_CommInit has failed.

6. Venus doesn't start.

A reason is that you do not have the correct kernel module. This can be tested by inserting the module by hand, and then listing the available modules. coda should show up in that listing. Otherwise reinstall (or recompile) a new module.
# depmod -a
# insmod coda.o
# lsmod
Module                  Size  Used by
coda                   50488   2
If the kernel-module can be loaded without errors, check venus.log. A message Cannot get rootvolume name indicated either a misconfigured server or the codasrv and/or codasrv-se ports are not defined in /etc/services, which should contain the following entries. See above for the entries needed.

7. I'm disconnected and Venus doesn't start.

Put the hostnames of your servers in /etc/hosts.

8. I cannot get tokens while disconnected.

Take a vacation until we release a version of Coda which uses it's telepathic abilities to contact the auth2 server. We will add this feature.

9. Hoard doesn't work.

Make sure you have version 5.0 of Coda or later. Before you can hoard you must make sure that:

  • You started Venus with the flag -primaryuser youruid

  • You have tokens

10. File System Full

You may get a message of the form, /usr: file system full when you have not put any extra data on that disk. If the venus.cache directory is on that disk, that is probably your problem. You can execute either cfs flushobject object or cfs flushvolume dir to try to free up some disk space.

Warning

Be careful when flushing anything while disconnected. You will lose any changes that you made.

In the long term, the cache size as specified in /etc/coda/venus.conf is probably too large for the disk and should be made smaller.