You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after, command "python kfssetup.py -f machines.cfg -m machines.txt -b ../build
-w ../webui" and command "python kfslaunch.py -f machines.cfg -m machines.txt
-s", I tend to run command "kfsping -m -s 192.168.1.107 -p 20000", but can not
connect.
It display the following info
[root@bogon tools]# ./kfsping -m -s 192.168.1.107 -p 20000
Connect: : Connection refused
02-19-2012 14:23:40.960 ERROR - (kfsping_main.cc:127) Unable to connect to
192.168.1.107 20000
actually, Meta Server don't run.
So, I use cmd "./metaserver MetaServer.prp", shell tell me that
Loading key metaServer.clientPort with value 20000
Loading key metaServer.chunkServerPort with value 30000
Loading key metaServer.logDir with value ./kfslog
Loading key metaServer.cpDir with value ./kfscp
Using meta server client port: 20000
Using meta server chunk server port: 30000
Setting cluster key to:
Setting md5sumFilename to:
min. # of chunkserver that should connect: 1
min. # of replicas per file: 1
max. # of replicas per file: 64
Setting the # of open files to: 1024
restoring from checkpoint of Tue Feb 14 23:06:31 2012
log file is ./kfslog/log.0
Log time: Tue Feb 14 23:06:31 2012
kfs_startup() end
02-20-2012 16:39:45.170 INFO - (metaserver_main.cc:88) Starting metaserver...
02-20-2012 16:39:45.203 INFO - (replay.cc:57) Doing log replay from file:
./kfslog/log.0
02-20-2012 16:39:45.204 INFO - (replay.cc:57) Doing log replay from file:
./kfslog/log.0
02-20-2012 16:39:45.231 DEBUG - (logger.cc:122) Opening ./kfslog/log.0 in
append mode
and no response.
why I can't start meta server and chunk server??
OS: Centos 5.7 x86_64
KFS Code: kfs-0.5
Thank you very much!
Original issue reported on code.google.com by [email protected] on 20 Feb 2012 at 8:48
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 20 Feb 2012 at 8:48The text was updated successfully, but these errors were encountered: