Gerry, you can specify the location of the spec file either as 1. -f (spec file) or 2. -s (spec file server) with an optional -p (port). you have to do it either in the "1." style or "2." style and not mix them. thanks, avati 2007/7/1, Gerry Reno <greno@xxxxxxxxxxx>:
Hi all, Well I'm finally starting to do some glusterfs testing and I updated to mainline--2.5 patch 247. I tried rerunning an old startup script I had but it is now erroring: ============================================================ glusterfsd --spec-file /usr/local/etc/glusterfs/test-server0.vol glusterfsd --spec-file /usr/local/etc/glusterfs/test-server1.vol glusterfsd --spec-file /usr/local/etc/glusterfs/test-server2.vol glusterfsd --spec-file /usr/local/etc/glusterfs/test-server3.vol glusterfs -l /var/log/glusterfs.log -L DEBUG --spec-file /usr/local/etc/glusterfs/test-client.vol --port=6996 /mnt/glusterfs0/ glusterfs -l /var/log/glusterfs.log -L DEBUG --spec-file /usr/local/etc/glusterfs/test-client.vol --port=6997 /mnt/glusterfs1/ glusterfs -l /var/log/glusterfs.log -L DEBUG --spec-file /usr/local/etc/glusterfs/test-client.vol --port=6998 /mnt/glusterfs2/ glusterfs -l /var/log/glusterfs.log -L DEBUG --spec-file /usr/local/etc/glusterfs/test-client.vol --port=6999 /mnt/glusterfs3/ ============================================================ Running: [root@grp-01-30-01 glusterfs]# ./test-startall.sh glusterfsd: FATAL: already running as PID 10018! glusterfsd: FATAL: already running as PID 10018! glusterfsd: FATAL: already running as PID 10018! glusterfs: -p|--port requires -s|--server option to be specified glusterfs: -p|--port requires -s|--server option to be specified glusterfs: -p|--port requires -s|--server option to be specified glusterfs: -p|--port requires -s|--server option to be specified Looks like it will not allow me to start multiple copies of glusterfsd. And it is now requiring --server option when --port is present. [root@grp-01-30-01 glusterfs]# vi test-startall.sh # so I add --server options ============================================================ ... glusterfs -l /var/log/glusterfs.log -L DEBUG --spec-file /usr/local/etc/glusterfs/test-client.vol --server 192.168.1.25 --port=6996 /mnt/glusterfs0/ glusterfs -l /var/log/glusterfs.log -L DEBUG --spec-file /usr/local/etc/glusterfs/test-client.vol --server 192.168.1.25 --port=6997 /mnt/glusterfs1/ glusterfs -l /var/log/glusterfs.log -L DEBUG --spec-file /usr/local/etc/glusterfs/test-client.vol --server 192.168.1.25 --port=6998 /mnt/glusterfs2/ glusterfs -l /var/log/glusterfs.log -L DEBUG --spec-file /usr/local/etc/glusterfs/test-client.vol --server 192.168.1.25 --port=6999 /mnt/glusterfs3/ ============================================================ Running: [root@grp-01-30-01 glusterfs]# ./test-startall.sh glusterfsd: FATAL: already running as PID 10018! glusterfsd: FATAL: already running as PID 10018! glusterfsd: FATAL: already running as PID 10018! glusterfsd: FATAL: already running as PID 10018! glusterfs: -s|--server option cannot be combined with -f|--spec-file option glusterfs: -s|--server option cannot be combined with -f|--spec-file option glusterfs: -s|--server option cannot be combined with -f|--spec-file option glusterfs: -s|--server option cannot be combined with -f|--spec-file option Ok, wait a minute, I need the --spec-file option! Here is test-client.vol: ============================================================ ### Add client feature and attach to remote subvolume volume client0 type protocol/client option transport-type tcp/client # for TCP/IP transport option remote-host 192.168.1.25 # IP address of the remote brick option remote-port 6996 # default server port is 6996 option remote-subvolume brick # name of the remote volume end-volume volume client1 type protocol/client option transport-type tcp/client option remote-host 192.168.1.25 option remote-port 6997 option remote-subvolume brick end-volume volume client2 type protocol/client option transport-type tcp/client option remote-host 192.168.1.25 option remote-port 6998 option remote-subvolume brick end-volume volume client3 type protocol/client option transport-type tcp/client option remote-host 192.168.1.25 option remote-port 6999 option remote-subvolume brick end-volume ### Add automatice file replication (AFR) feature volume afr type cluster/afr subvolumes client0 client1 client2 client3 option replicate *:4 end-volume ============================================================ and here is test-server0.vol (the rest are similar) ============================================================ volume brick type storage/posix # POSIX FS translator option directory /root/export0 # Export this directory end-volume ### Add network serving capability to above brick. volume server type protocol/server option transport-type tcp/server # For TCP/IP transport option listen-port 6996 # Default is 6996 subvolumes brick option auth.ip.brick.allow * # Allow full access to "brick" volume end-volume ============================================================ How to fix these two problems? Gerry _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxx http://lists.nongnu.org/mailman/listinfo/gluster-devel
-- Anand V. Avati
