Could not find or open pipes for Riak console #278
Comments
|
@xn Did you try deleting the generated directory and retrying? Also note that the test server will not work per-se with LevelDB. Unless you've monkey-patched the |
|
Another thing to check is to see if you already have a test beam process running; if you do, try killing it and then re-running. |
|
Thanks for the comments. Deleted sudo rm -rf /tmp/.identity.riak ** Invoke default (first_time)
** Invoke test (first_time)
** Execute test
/home/xn/.rvm/rubies/ruby-1.9.2-p290/bin/ruby -I"lib:lib:test" -I"/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib" "/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/rake_test_loader.rb" "test/**/*_test.rb"
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/bundler/gems/soap4r-24601670d998/lib/xsd/charset.rb:13: warning: variable $KCODE is no longer effective
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/bundler/gems/soap4r-24601670d998/lib/soap/property.rb:68: warning: encoding option is ignored - u
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/bundler/gems/soap4r-24601670d998/lib/soap/property.rb:69: warning: encoding option is ignored - u
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/bundler/gems/soap4r-24601670d998/lib/soap/property.rb:70: warning: encoding option is ignored - u
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/bundler/gems/ripple-6b5ac7fe139c/riak-client/lib/riak/util/tcp_socket_extensions.rb:54:in `wait_for_service_termination_with_timeout': Socket did not terminate within 10 seconds (SocketError)
from /home/xn/.rvm/gems/ruby-1.9.2-p290@identity/bundler/gems/ripple-6b5ac7fe139c/riak-client/lib/riak/node/control.rb:202:in `wait_for_shutdown'
from /home/xn/.rvm/gems/ruby-1.9.2-p290@identity/bundler/gems/ripple-6b5ac7fe139c/riak-client/lib/riak/node/control.rb:37:in `stop'
from /home/xn/.rvm/gems/ruby-1.9.2-p290@identity/bundler/gems/ripple-6b5ac7fe139c/riak-client/lib/riak/test_server.rb:47:in `stop'
from /home/xn/.rvm/gems/ruby-1.9.2-p290@identity/bundler/gems/ripple-6b5ac7fe139c/riak-client/lib/riak/node/generation.rb:44:in `delete'
from /home/xn/.rvm/gems/ruby-1.9.2-p290@identity/bundler/gems/ripple-6b5ac7fe139c/riak-client/lib/riak/node/generation.rb:12:in `recreate'
from /home/xn/sites/att-identity/test/support/ripple_test_server.rb:17:in `setup'
from /home/xn/sites/att-identity/test/test_helper.rb:22:in `<top (required)>'
from /home/xn/sites/att-identity/test/lib/oauth2/models/application_test.rb:2:in `require'
from /home/xn/sites/att-identity/test/lib/oauth2/models/application_test.rb:2:in `<top (required)>'
from /home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/rake_test_loader.rb:10:in `require'
from /home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/rake_test_loader.rb:10:in `block (2 levels) in <main>'
from /home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/rake_test_loader.rb:9:in `each'
from /home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/rake_test_loader.rb:9:in `block in <main>'
from /home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/rake_test_loader.rb:4:in `select'
from /home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/rake_test_loader.rb:4:in `<main>'
rake aborted!
Command failed with status (1): [/home/xn/.rvm/rubies/ruby-1.9.2-p290/bin/r...]
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/file_utils.rb:53:in `block in create_shell_runner'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/file_utils.rb:45:in `call'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/file_utils.rb:45:in `sh'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/file_utils_ext.rb:39:in `sh'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/file_utils.rb:82:in `ruby'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/file_utils_ext.rb:39:in `ruby'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/testtask.rb:99:in `block (2 levels) in define'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/file_utils_ext.rb:60:in `verbose'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/testtask.rb:98:in `block in define'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `call'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `block in execute'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `each'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `execute'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/task.rb:158:in `block in invoke_with_call_chain'
/home/xn/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/task.rb:176:in `block in invoke_prerequisites'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/task.rb:174:in `each'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/task.rb:174:in `invoke_prerequisites'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/task.rb:157:in `block in invoke_with_call_chain'
/home/xn/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/task.rb:144:in `invoke'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/application.rb:116:in `invoke_task'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `block (2 levels) in top_level'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `each'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `block in top_level'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/application.rb:88:in `top_level'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/application.rb:66:in `block in run'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/lib/rake/application.rb:63:in `run'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/gems/rake-0.9.2.2/bin/rake:33:in `<top (required)>'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/bin/rake:19:in `load'
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/bin/rake:19:in `<main>'
Tasks: TOP => default => test |
|
I do see that the test is trying to connect @ /tmp/.identity.riak and the console attaches to: /tmp/riak/erlang.pipe.1 |
|
@xn did you get this working? If not, can you create a small test project that shows the issue? |
|
I'm having the same issue in an app I just started. so I created this small test project here: https://github.com/rafaelss/riak_issue_278 I'm using let me know if you need something else. |
|
I had this issue after running the ripple rspec suite. To recover, I ran and killed every process. I also deleted /tmp/usr and deleted ./tmp/riak_test_server. I could then run my app's rspec suite again. |
|
I ran into a similar problem and the way I was able to fix the problem was to, from the rails app root, |
|
Yes, this is a recurring issue that I haven't had a chance to investigate yet; I think it has to do with things not getting shut down properly if/when the machine reboots, but I'm not sure. Regardless of what's causing it, we need to add some code to recognize the situation when the test server is starting up and clean out the broken artifacts if necessary. |
|
I can verify that this does still occur with beta2. Not sure which one of the above steps finally fixed the problem |
|
For what it's worth I'm also seeing this issue with beta2 and riak 1.2.1 on Mac OSX. I fixed it by doing:
|
|
We experience intermittent test failures running tests: On RHEL 6 Using JRuby 1.7.1Linux themachinename 2.6.32-220.7.1.el6.x86_64 #1 SMP Fri Feb 10 15:22:22 EST 2012 x86_64 x86_64 x86_64 GNU/Linux riak (1.2.1 2012-10-15) RedHat x86_64 jruby 1.7.1 (1.9.3p327) 2012-12-03 30a153b on Java HotSpot(TM) 64-Bit Server VM 1.7.0_09-b05 [linux-amd64] Gemfile excerptgem 'rails', '3.2.9' Ripple.ymltest: Test results:
crash.log and error.log are empty... run_erl.logrun_erl [32389] Fri Dec 7 18:59:00 2012 erlang_log.1(riak129268@127.0.0.1)34> console.log2012-12-07 18:58:59.769 [info] <0.7.0> Application lager started on node 'riak129268@127.0.0.1' |
|
I ran the tests again and included the debug flags DEBUG_RIAK_CONSOLE=1 DEBUG_RIAK_TEST_SERVER=1 DEBUG_RIAK_NODE=1 jruby -I:"test" test/unit/foo_test.rb" Running tests:Opening write pipe. (riak129268@127.0.0.1)53>Initialized console: #File:/tmp/riak_test_server/pipe/erlang.pipe.1.r #File:/tmp/riak_test_server/pipe/erlang.pipe.1.w (riak129268@127.0.0.1)53>Sending command "riak_search_test_backend:reset()." (riak129268@127.0.0.1)53>ESending command "riak_kv_memory_backend:reset()." (riak129268@127.0.0.1)53>Sending command "riak_search_test_backend:reset()." (riak129268@127.0.0.1)53>.Sending command "riak_kv_memory_backend:reset()." (riak129268@127.0.0.1)53>Sending command "riak_search_test_backend:reset()." (riak129268@127.0.0.1)53>.Sending command "riak_kv_memory_backend:reset()." (riak129268@127.0.0.1)53>Sending command "riak_search_test_backend:reset()." (riak129268@127.0.0.1)53>. Finished tests in 0.511000s, 7.8278 tests/s, 13.6986 assertions/s. Finished tests in 0.511000s, 7.8278 tests/s, 13.6986 assertions/s.
|
|
DEBUG_RIAK_CONSOLE=1 DEBUG_RIAK_TEST_SERVER=1 DEBUG_RIAK_NODE=1 jruby -I:"test" test/unit/foo_test.rb *** Mocha deprecation warning: Change Run options: Running tests:Opening write pipe. (riak129268@127.0.0.1)62>Initialized console: #File:/tmp/riak_test_server/pipe/erlang.pipe.1.r #File:/tmp/riak_test_server/pipe/erlang.pipe.1.w (riak129268@127.0.0.1)62>Sending command "riak_search_test_backend:reset()." (riak129268@127.0.0.1)62>.Sending command "riak_kv_memory_backend:reset()." (riak129268@127.0.0.1)62>Sending command "riak_search_test_backend:reset()." (riak129268@127.0.0.1)62>.Sending command "riak_kv_memory_backend:reset()." (riak129268@127.0.0.1)62>Sending command "riak_search_test_backend:reset()." (riak129268@127.0.0.1)62>.Sending command "riak_kv_memory_backend:reset()." (riak129268@127.0.0.1)62>Sending command "riak_search_test_backend:reset()." (riak129268@127.0.0.1)62>. Finished tests in 0.641000s, 6.2402 tests/s, 17.1607 assertions/s. 4 tests, 11 assertions, 0 failures, 0 errors, 0 skips |
|
We have decided to move away from using Riak::TestServer until we can dedicate some time to debugging this issue. |
|
This started appearing sporadically in our travis builds since we upgraded to one of the latest SHAs that use riak-client 1.1.0 instead of 1.0.0. |
|
Has there been any progress on this issue? I'm also getting this error. I can get around it sometimes but it continues to occur occasionally. It'd be really great if there was some way to catch when this error happens and fix whatever is causing it. |
|
I've tried all of the above but still get this everytime: |
/home/xn/.rvm/gems/ruby-1.9.2-p290@identity/bundler/gems/ripple-6b5ac7fe139c/riak-client/lib/riak/node/console.rb:49:in `initialize': Could not find or open pipes for Riak console in /tmp/.identity.riak/pipe. (ArgumentError)
sudo riak attach Attempting to restart script through sudo -u riak Attaching to /tmp/riak/erlang.pipe.1 (^D to exit) {ok, Client} = riak:local_client(). {ok,{riak_client,'riak@127.0.0.1',undefined}} (riak@127.0.0.1)2>any ideas?
The text was updated successfully, but these errors were encountered: