Coda File System

Clog problem 4.6.5

From: Khairul Azmi <k_azmi_at_hotmail.com>
Date: Mon, 07 Sep 1998 01:57:04 PDT
I'm a newbie who wants to explore about coda. I;ve succesfully install 
coda client on my machine (cel4) and a coda server (cel_linux2) on the 
other machine. However when I invoked command clog 
[root_at_cel4 azmi]# clog
Password: 
Invalid login (RPC2_NOTAUTHENTICATED (F)).

These are the step I took to install coda server (cel_linux2).

root_at_cel_linux2.mimos.my 18: /usr/sbin/vice-setup
Setting up config files (under /vice).
Directories under /vice are set up.

Setting up tokens for authentication.
The following tokens must be identical on all servers.
Enter a random token for auth2 authentication : xxxxxx01
The following tokens must be identical on all servers.
Enter a random token for volutil authentication :xxxxx02 
tokens done!

Setting up the file list for update

filelist for update ready.
Populating /vice/vol...
lockfiles created.

Services already present. Good.
Is this the master server, aka the SCM machine? (y/n) y
Now installing files specific to the SCM...
Setting up servers file.
Enter an id for this server (a number > 0 < 255) : 1
done!
Initializing the VSGDB to contain the SCM as E0000100
/vice/db/VSGDB set up

Setting up ROOTVOLUME file
Enter the name of the rootvolume (< 32 chars) : root:coda
done!

** When srv, updatesrv and updateclnt are running, 
** and you have a data partition PART (such as /vicepa) issue 
** the command createvol testcuba  scm-hostname PART

Setting up users and groups for Coda
1 user entries found
An initial administrative user "admin" with passwod "changeme" now 
exists.


You need a small log disk partition, preferrably on a disk by itself.
You need a metadata partition of approx 4% of you filespace.

For trial purposes you may give oridnary files instead of raw
partitions. Keep all size small if you do this.
Production servers will want partitions for speed.

-------------------------------------------------------
WARNING: you are going to play with your partitions now.
verify all answers you give.
-------------------------------------------------------

WARNING: these choices are not easy to change once you are up and 
running.

Are you ready to set up RVM? [yes/no] yes

What is your log partition? /dev/hdb2

The log size must be smaller than you log partition.
We recommend not more than 30M log size, and 2M is a good choice.
What is your log size? (enter as e.g. '12M') 12M

What is your data partition (or file)? /dev/hdb3

The data size must be approx 4% of you server file space.
We have templates for servers of approx: 500M, 1G, 2.2G, 3.3G, 8G
(you can store less, but not more on such servers).

The corresponding data sizes are  22M, 44M, 90M, 130M, 315M.
(use 330M only on very fast machines)
Pick one of the defaults, otherwise I will bail out

What is the size of you data partition (or file) [22M,44M, 90M, 130M, 
315M]: 90M

--------------------------------------------------------
WARNING: DATA and LOG partitions are about to be wiped.
--------------------------------------------------------

  --- log area: /dev/hdb2, size 12M.
  --- data area: /dev/hdb3, size 90M.

Proceed, and wipe out old data? [y/N] y


LOG file has been initialized!


Rdsinit will initialize data and log.
This takes a while.
rvm_initialize succeeded.
Going to initialize data file to zero, could take awhile.
done.
Just mapped in region (20000000,77594624)
Just mapped in region (24a00000,1048576)
rds_zap_heap completed successfully.
rvm_terminate succeeded.
RVM setup is done!

Your server directories will hold the files (not directories).
You can currently only have one directory per disk partition.

Where shall we store your data [/vicepa]? /vicepa
mkdir: cannot make directory `/vicepa': File exists
Shall I set up a vicetab entry for approx 256000 files for /vicepa (y/n) 
y
grep: /vice/db/vicetab: No such file or directory
Now initializing the partition. This takes a while....
Partition /vicepa: inodes in use: 0, total: 262144.

Date: Mon 08/24/98


16:32:31 Partition /vicepa: 910314 available size (1K blocks, 
minfree=5%), 
910301 free blocks.
done.
Server directory is set up!

Then I add a normal user.
/vice/db/user.coda
admin::500::Administrator::
azmi::502::Tuan::

/vice/db/group.coda
System:Administrators   -204    admin
System:Coda             -205    azmi

/vice/db/passwd.coda
500     changeme        admin user
502     testing         azmi user

Then I invoked command 
pwd2pdb -u /vice/db/user.coda -g /vice/db/group.coda > /vice/db/vice.pdb
2 user entries found
and
pcfgen /vice/db/vice.pdb 
and
initpw -k "drseuss" </vice/db/passwd.coda> /vice/db/auth2.pw


As I said clog azmi gave me
[root_at_cel4 azmi]# clog azmi
Password: 
Invalid login (RPC2_NOTAUTHENTICATED (F)).

while /vice/auth2/AuthLog gave me
16:53:07 In PWGetKeys()
16:53:07        vid = 502
16:53:07        vid = 502
16:53:07 Authentication failed for "azmi" from 26.133.228.192

Please help. 

Azmi


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
Received on 1998-09-07 05:00:41