This is probably being caused the the single core you have on the EC2 node. You will need to enable your Erlang to be smp capable to make innostore work. Add the following to your /etc/riak/vm.args file (anywhere will do): -smp enable
This is something we are going to add to the vm.args we distribute to work around the issue. Give the above a try and report back with any issues you have. Grant Schofield Developer Advocate Basho Technologies, Inc. On Apr 13, 2010, at 3:09 PM, Tyler Smart wrote: > hi Grant, I am running innostore 8, as downloaded from here, the 32bit deb > > http://downloads.basho.com/riak/riak-0.9/ > > Here is the erland log file, the last 100 lines of it, but I did not see a > SASS log file in the /var/log directory. > Erlang File: > > > ===== > Exec: /usr/lib/riak/erts-5.7.4/bin/erlexec -boot > /usr/lib/riak/releases/0.9.1/riak -embedded -config /etc/riak/app.config > -args_file /etc/riak/vm.args -- console > Root: /usr/lib/riak > Erlang R13B03 (erts-5.7.4) [source] [rq:1] [async-threads:5] > [kernel-poll:true] > > > =INFO REPORT==== 13-Apr-2010::15:18:38 === > Spidermonkey VM host starting (<0.104.0>) > > =INFO REPORT==== 13-Apr-2010::15:18:38 === > Spidermonkey VM host starting (<0.105.0>) > > =INFO REPORT==== 13-Apr-2010::15:18:38 === > Spidermonkey VM host starting (<0.106.0>) > > =INFO REPORT==== 13-Apr-2010::15:18:38 === > Spidermonkey VM host starting (<0.107.0>) > > =INFO REPORT==== 13-Apr-2010::15:18:38 === > Spidermonkey VM host starting (<0.108.0>) > > =INFO REPORT==== 13-Apr-2010::15:18:38 === > Spidermonkey VM host starting (<0.109.0>) > > =INFO REPORT==== 13-Apr-2010::15:18:38 === > Spidermonkey VM host starting (<0.110.0>) > > =INFO REPORT==== 13-Apr-2010::15:18:38 === > Spidermonkey VM host starting (<0.111.0>) > > =ERROR REPORT==== 13-Apr-2010::15:18:38 === > No ring file available. > Eshell V5.7.4 (abort with ^G) > ([email protected])1> > =ERROR REPORT==== 13-Apr-2010::15:19:22 === > Skipping config setting included_applications; unknown option. > InnoDB: Mutexes and rw_locks use GCC atomic builtins > InnoDB: The first specified data file /riak/data/ibdata1 did not exist: > InnoDB: a new database to be created! > 100413 15:19:31 InnoDB: Setting file /riak/data/ibdata1 size to 32 MB > InnoDB: Database physically writes the file full: wait... > 100413 15:19:32 InnoDB: Log file /riak/logs/ib_logfile0 did not exist: new > to be created > InnoDB: Setting log file /riak/logs/ib_logfile0 size to 16 MB > InnoDB: Database physically writes the file full: wait... > 100413 15:19:33 InnoDB: Log file /riak/logs/ib_logfile1 did not exist: new > to be created > InnoDB: Setting log file /riak/logs/ib_logfile1 size to 16 MB > InnoDB: Database physically writes the file full: wait... > InnoDB: Doublewrite buffer not found: creating new > InnoDB: Doublewrite buffer created > InnoDB: Creating foreign key constraint system tables > InnoDB: Foreign key constraint system tables created > 100413 15:19:33 Embedded InnoDB 1.0.6.6750 started; log sequence number 0 > > ===== ALIVE Tue Apr 13 15:34:33 UTC 2010 > > ===== ALIVE Tue Apr 13 15:49:34 UTC 2010 > > ===== ALIVE Tue Apr 13 16:04:34 UTC 2010 > > ===== ALIVE Tue Apr 13 16:19:34 UTC 2010 > > ===== ALIVE Tue Apr 13 16:34:34 UTC 2010 > > ===== ALIVE Tue Apr 13 16:49:34 UTC 2010 > > ===== ALIVE Tue Apr 13 17:04:34 UTC 2010 > > ===== Tue Apr 13 17:18:31 UTC 2010 > > =ERROR REPORT==== 13-Apr-2010::17:18:31 === > ** State machine <0.566.0> terminating > ** Last message in was flow_timeout > ** When State == executing > ** Data == {state,50096623, > [<0.568.0>,<0.567.0>], > <0.560.0>,66000, > {1271179111446655,#Ref<0.0.0.1123>}, > []} > ** Reason for termination = > ** flow_timeout > > ===== ALIVE Tue Apr 13 17:33:31 UTC 2010 > > ===== ALIVE Tue Apr 13 17:48:31 UTC 2010 > > ===== ALIVE Tue Apr 13 18:03:31 UTC 2010 > > ===== ALIVE Tue Apr 13 18:18:31 UTC 2010 > > ===== ALIVE Tue Apr 13 18:33:32 UTC 2010 > > ===== ALIVE Tue Apr 13 18:48:32 UTC 2010 > > ===== ALIVE Tue Apr 13 19:03:32 UTC 2010 > > ===== ALIVE Tue Apr 13 19:18:32 UTC 2010 > > ===== ALIVE Tue Apr 13 19:33:32 UTC 2010 > > ===== ALIVE Tue Apr 13 19:48:32 UTC 2010 > > > > > > > > > > > > > > > > > > > > On Tue, Apr 13, 2010 at 3:22 PM, Grant Schofield <[email protected]> wrote: > What version of Riak and Innostore are you running? Also providing both your > erlang.log.1 as well as your sasl-error.log files from the log directory > would help us diagnose the issue you're experiencing. > > Thanks, > Grant Schofield > Developer Advocate > Basho Technologies, Inc. > > > On Apr 13, 2010, at 12:55 PM, Tyler Smart wrote: > >> {riak, [ >> %% storage_backend specifies the Erlang module defining the storage >> mechanism >> %% that will be used on this node. >> %% {storage_backend, riak_dets_backend}, >> {storage_backend, innostore_riak}, >> >> %% Different storage backends can use other configuration >> variables. For >> %% instance, riak_dets_backend_root determines the directory under >> which >> %% dets files will be placed. >> {riak_dets_backend_root, "/riak/backendroot"}, >> >> %% Default location of ringstate >> {ring_state_dir, "/riak/ringstate"}, >> >> %% riak_web_ip is the IP address that Riak's HTTP interface will >> bind to. >> %% If this is undefined, the HTTP interface will not run. >> {riak_web_ip, "127.0.0.1"}, >> >> %% riak_web_port is the TCP port that Riak's HTTP interface will >> bind to. >> {riak_web_port, 8098}, >> >> %% riak_handoff_port is the TCP port that Riak uses for >> intra-cluster >> %% data handoff. >> {riak_handoff_port, 8099}, >> >> %% mapred_name is URL used to submit map/reduce requests to Riak. >> {mapred_name, "mapred"}, >> >> %% js_vm_count is the number of Javascript VMs to start per Riak >> node. >> %% 8 is a good default for smaller installations. A larger number >> like >> %% 12 or 16 is appropriate for installations handling lots of >> map/reduce >> %% processing. >> {js_vm_count, 8}, >> >> %% js_source_dir should point to a directory containing Javascript >> source >> %% files which will be loaded by Riak when it initializes >> Javascript VMs. >> %{js_source_dir, "/tmp/js_source"} >> >> >> %% riak_stat enables the use of the "riak-admin status" command to >> %% retrieve information the Riak node for performance and debugging >> needs >> {riak_stat, true} >> ]}, >> >> %% SASL config >> {sasl, [ >> {sasl_error_logger, {file, "log/sasl-error.log"}}, >> {errlog_type, error}, >> {error_logger_mf_dir, "log/sasl"}, % Log directory >> {error_logger_mf_maxbytes, 10485760}, % 10 MB max file >> size >> {error_logger_mf_maxfiles, 5} % 5 files max >> ]}, >> >> {innostore, [ >> {data_home_dir, "/riak/data"}, %% Where data files go >> {log_group_home_dir, "/riak/logs"}, %% Where log files go, >> ideally the logs and data are on separate drives for performance...maybe >> later >> {buffer_pool_size, 268435456} %% 256MB in-memory buffer in bytes >> ]} >> ]. >> >> >> Sorry for the confusion, that is the config file, I hope it helps. >> >> Sincerely, >> Tyler >> >> On Tue, Apr 13, 2010 at 1:27 PM, Tyler Smart <[email protected]> wrote: >> Hi all! >> >> I have installed Riak on an Ubuntu 8.04 EC-2 instance and it stores all of >> its' data on an EBS block (10GB). The machine is 32 bit (small). It will >> accept information in a bucket easily with a curl request like this: >> >> curl -X PUT -H "content-type: text/plain" >> https://127.0.0.1/riak/example/foo --data "I have a document." >> >> If I query the data like this: >> >> curl -i -k https://127.0.0.1/riak/example/foo >> >> I get back the data, it works perfectly. (It sits behind nginx as a reverse >> proxy that adds SSL). >> >> However, if I perform this query: >> >> https://127.0.0.1/riak/example >> >> it never finishes executing, nor if I try https://127.0.0.1/riak/test >> >> I have attached the conf file, if it will help, and I appreciate any time >> you guys have! >> >> Sincerely, >> Tyler >> >> >> The problem I am having is that I can >> >> _______________________________________________ >> riak-users mailing list >> [email protected] >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
