Usually you don't have the ability to create directories or files in /home unless you're root. Perhaps you should create /home/client_logfile and give it the right permissions? If that doesn't work, make sure you are editing the configuration that you are actually using. You can force cfuse to use the configuration you want with -c. regards, Colin On Thu, May 19, 2011 at 6:01 PM, huang jun <hjwsm1989@xxxxxxxxx> wrote: > hi,colin > i try it as you said, but i can not see anything > [client] > log_file = /home/client_logfile > debug ms = 1 > debug client = 10 > client cache size = 1024*1024*100 > is there anything wrong with this setting? > > thanks! > 2011/5/20 Colin Patrick McCabe <colin.mccabe@xxxxxxxxxxxxx>: >> Hi Huang, >> >> cfuse is a client, so it will use whatever the logging settings are for clients. >> you can set this by adding something like this to the [client] section >> of your configuration file: >> >> log_file = /my_log_file >> >> You can also use this command-line switch to override the configuration: >> --log-file=/my/log/file >> >> cheers, >> Colin >> >> >> On Thu, May 19, 2011 at 4:52 PM, huang jun <hjwsm1989@xxxxxxxxx> wrote: >>> hi,brian >>> my 'ceph -s' shows everything is ok >>> and if i do it on the other machine, i did not find this error. >>> i trun on the debug on ceph.conf like : >>> [client] >>> debug ms = 1 >>> debug client = 10 >>> but i can't find where does this info goes to ? not in /var/log/ceph/ >>> so where should i look for this debug output? >>> >>> thanks! >>> >>> 2011/5/19 Brian Chrisman <brchrisman@xxxxxxxxx>: >>>> On Thu, May 19, 2011 at 4:12 AM, huang jun <hjwsm1989@xxxxxxxxx> wrote: >>>>> hi, all >>>>> i just encountered a problem about cfuse: >>>>> i mount cfsue successfully on /mnt by using >>>>> "cfuse -m 192.168.0.170:6789 /mnt" >>>>> but when i enter /mnt directory, it shows that: >>>>> [root@localhost mnt]# ll >>>>> ls: .: Transport endpoint is not connected >>>> >>>> This is a FUSE failure message that generally occurs when your >>>> userspace process (in this case cfuse) has exited (closed its >>>> connection to the FUSE kernel driver). >>>> does 'ceph -s' show that your ceph cluster is up and healthy? >>>> You may want to turn on client debugging to see why cfuse is exiting: >>>> http://ceph.newdream.net/wiki/Debugging >>>> >>>> >>>>> my cfuse client is on centos5, it kernel version is 2.6.18 >>>>> and OSD cluster is on debian5, 2.6.35 >>>>> i don't know whether it related to SimpleMessenger,so anyone can give >>>>> me some prompts? >>>>> >>>>> thanks! >>>>> -- >>>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >>>>> the body of a message to majordomo@xxxxxxxxxxxxxxx >>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>>>> >>>> >>> -- >>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >>> the body of a message to majordomo@xxxxxxxxxxxxxxx >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> >> > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
