You might also want to check netstat to see if any of the TCP sockets linger unnecessarily. Also, what's the output of riak-admin status while your node is running?
Sean Cribbs <s...@basho.com> Developer Advocate Basho Technologies, Inc. http://basho.com/ On Oct 5, 2010, at 12:59 PM, Alex Wolfe wrote: > Hi Sean, > > Thanks for responding. I have my ulimit set to 9000, and still have the same > problem. And wouldn't stopping and restarting riak solve this issue, at > least temporarily? I cannot make a single request to riak, even immediately > after restarting the server. > > Here's evidence of my ulimit settings: > $ ulimit -a > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > file size (blocks, -f) unlimited > max locked memory (kbytes, -l) unlimited > max memory size (kbytes, -m) unlimited > open files (-n) 9000 > pipe size (512 bytes, -p) 1 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 266 > virtual memory (kbytes, -v) unlimited > > Alex > > > On Oct 5, 2010, at 11:54 AM, Sean Cribbs wrote: > >> Make sure you set ulimit -n before starting Riak. A value of 1024 or larger >> is recommended (on OS/X the default is 256). Example: >> >> $ ulimit -a >> core file size (blocks, -c) 0 >> data seg size (kbytes, -d) unlimited >> file size (blocks, -f) unlimited >> max locked memory (kbytes, -l) unlimited >> max memory size (kbytes, -m) unlimited >> open files (-n) 256 >> pipe size (512 bytes, -p) 1 >> stack size (kbytes, -s) 8192 >> cpu time (seconds, -t) unlimited >> max user processes (-u) 266 >> virtual memory (kbytes, -v) unlimited >> >> $ ulimit -n 1024 >> >> This is a common cause of timeouts and connection failures on OS/X. >> >> Sean Cribbs <s...@basho.com> >> Developer Advocate >> Basho Technologies, Inc. >> http://basho.com/ >> >> On Oct 5, 2010, at 12:43 PM, Alex Wolfe wrote: >> >>> I've run into a problem with Riak on my development machine, and I can't >>> quite sort out what's happening. I've tried stopping the riak processes >>> and restarting it back up again, but it will not service any requests. >>> >>> Has anyone seen this before? >>> >>> >>> $ curl -v -X POST http://riak:8098/riak/test -d'{"foo":"bar"}' -H >>> 'Content-Type:application/json' >>> * About to connect() to riak port 8098 (#0) >>> * Trying ::1... Connection refused >>> * Trying fe80::1... Connection refused >>> * Trying 127.0.0.1... connected >>> * Connected to riak (127.0.0.1) port 8098 (#0) >>>> POST /riak/test HTTP/1.1 >>>> User-Agent: curl/7.19.7 (universal-apple-darwin10.0) libcurl/7.19.7 >>>> OpenSSL/0.9.8l zlib/1.2.3 >>>> Host: riak:8098 >>>> Accept: */* >>>> Content-Type:application/json >>>> Content-Length: 13 >>>> >>> < HTTP/1.1 500 Internal Server Error >>> < Vary: Accept-Encoding >>> < Server: MochiWeb/1.1 WebMachine/1.7.1 (participate in the frantic) >>> < Location: /riak/test/RmfYZCM8LtBPRu4gqZivu8pfVoh >>> < Date: Tue, 05 Oct 2010 16:36:57 GMT >>> < Content-Type: text/html >>> < Content-Length: 713 >>> < >>> <html><head><title>500 Internal Server >>> Error</title></head><body><h1>Internal Server Error</h1>The server >>> encountered an error while processing this >>> request:<br><pre>{error,{error,{case_clause,{error,timeout}}, >>> [{riak_kv_wm_raw,accept_doc_body,2}, >>> {webmachine_resource,resource_call,3}, >>> {webmachine_resource,do,3}, >>> {webmachine_decision_core,resource_call,1}, >>> {webmachine_decision_core,accept_helper,0}, >>> {webmachine_decision_core,decision,1}, >>> {webmachine_decision_core,handle_request,2}, >>> * Connection #0 to host riak left intact >>> * Closing connection #0 >>> >>> {webmachine_mochiweb,loop,1}]}}</pre><P><HR><ADDRESS>mochiweb+webmachine >>> web server</ADDRESS></body></html> >>> >>> >>> >>> _______________________________________________ >>> riak-users mailing list >>> riak-users@lists.basho.com >>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >> > _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
