Couchbase Startup
Hi Perry,
I was able to successfully build 2.0. Part of the problem was that the spidermonkey build created the soname libmozjs.so when Couchbase was looking for libjs.so. So I just created a symlink named libjs.so to point to libmozjs.so.
I have two questions:
1) First, during the build I noticed several git calls. The TIlera box does not have git installed and does not have access to the outside world. These are obviously failing. Does this matter for the build? What are the calls for?
make[1]: Leaving directory `/opt/membase-2.0-repo/ns_server'
make -C geocouch COUCH_SRC=../couchdb/src/couchdb
make[1]: git: Command not found
make[1]: Entering directory `/opt/membase-2.0-repo/geocouch'
make[1]: git: Command not found
make[1]: Leaving directory `/opt/membase-2.0-repo/geocouch'
mkdir -p /opt/membase-2.0-repo/install/lib/couchdb/plugins/geocouch/ebin
cp -r geocouch/build/* /opt/membase-2.0-repo/install/lib/couchdb/plugins/geocouch/ebin
mkdir -p /opt/membase-2.0-repo/install/etc/couchdb/local.d
cp -r geocouch/etc/couchdb/local.d/* /opt/membase-2.0-repo/install/etc/couchdb/local.d
mkdir -p /opt/membase-2.0-repo/install/share/couchdb/www/script/test
cp -r geocouch/share/www/script/test/* /opt/membase-2.0-repo/install/share/couchdb/www/script/test
make -C mccouch
make[1]: git: Command not found
make[1]: Entering directory `/opt/membase-2.0-repo/mccouch'
make[1]: git: Command not found
erl -pa build -noinput +B -eval 'case make:all([{i, "'../couchdb/src/couchdb'"}]) of up_to_date -> halt(0); error -> halt(1) end.'
make[1]: Leaving directory `/opt/membase-2.0-repo/mccouch'
mkdir -p /opt/membase-2.0-repo/install/lib/couchdb/plugins/mccouch/ebin
cp -r mccouch/ebin/* /opt/membase-2.0-repo/install/lib/couchdb/plugins/mccouch/ebin
mkdir -p /opt/membase-2.0-repo/install/etc/couchdb/local.d
cp -r mccouch/etc/couchdb/local.d/* /opt/membase-2.0-repo/install/etc/couchdb/local.d
-sh-4.1#
2) When I run Couchbase 2.0, it crashes on startup with the following log. I as able to launch couchdb successfully. Do any of the following messages indicate to you why it may be crashing:
bash-4.1$ ./membase-server
Erlang R14B (erts-5.8.1) [source] [smp:64:54] [rq:64] [async-threads:16] [kernel-poll:true]
Eshell V5.8.1 (abort with ^G)
1>
=PROGRESS REPORT==== 31-Aug-2011::18:34:05 ===
supervisor: {local,sasl_safe_sup}
started: [{pid,<0.40.0>},
{name,alarm_handler},
{mfargs,{alarm_handler,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
=PROGRESS REPORT==== 31-Aug-2011::18:34:05 ===
supervisor: {local,sasl_safe_sup}
started: [{pid,<0.41.0>},
{name,overload},
{mfargs,{overload,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
=PROGRESS REPORT==== 31-Aug-2011::18:34:05 ===
supervisor: {local,sasl_sup}
started: [{pid,<0.39.0>},
{name,sasl_safe_sup},
{mfargs,
{supervisor,start_link,
[{local,sasl_safe_sup},sasl,safe]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 31-Aug-2011::18:34:05 ===
supervisor: {local,sasl_sup}
started: [{pid,<0.42.0>},
{name,release_handler},
{mfargs,{release_handler,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
=PROGRESS REPORT==== 31-Aug-2011::18:34:05 ===
application: sasl
started_at: nonode@nohost
=PROGRESS REPORT==== 31-Aug-2011::18:34:05 ===
supervisor: {local,os_mon_sup}
started: [{pid,<0.48.0>},
{name,disksup},
{mfargs,{disksup,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
=PROGRESS REPORT==== 31-Aug-2011::18:34:05 ===
supervisor: {local,os_mon_sup}
started: [{pid,<0.49.0>},
{name,memsup},
{mfargs,{memsup,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
=PROGRESS REPORT==== 31-Aug-2011::18:34:05 ===
supervisor: {local,os_mon_sup}
started: [{pid,<0.51.0>},
{name,cpu_sup},
{mfargs,{cpu_sup,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
=PROGRESS REPORT==== 31-Aug-2011::18:34:05 ===
application: os_mon
started_at: nonode@nohost
=PROGRESS REPORT==== 31-Aug-2011::18:34:05 ===
supervisor: {local,kernel_safe_sup}
started: [{pid,<0.54.0>},
{name,timer_server},
{mfargs,{timer,start_link,[]}},
{restart_type,permanent},
{shutdown,1000},
{child_type,worker}]
=INFO REPORT==== 31-Aug-2011::18:34:05 ===
Static config terms:
[{error_logger_mf_dir,"/opt/membase-2.0-repo/install/var/lib/membase/logs"},
{error_logger_mf_maxbytes,10485760},
{error_logger_mf_maxfiles,20},
{path_config_bindir,"/opt/membase-2.0-repo/install/bin"},
{path_config_etcdir,"/opt/membase-2.0-repo/install/etc/membase"},
{path_config_libdir,"/opt/membase-2.0-repo/install/lib"},
{path_config_datadir,"/opt/membase-2.0-repo/install/var/lib/membase"},
{path_config_tmpdir,"/opt/membase-2.0-repo/install/var/lib/membase/tmp"}]
=SUPERVISOR REPORT==== 31-Aug-2011::18:34:06 ===
Supervisor: {local,ns_server_cluster_sup}
Context: start_error
Reason: {'EXIT',{undef,[{couch_app,start,[fake,[]]},
{supervisor,do_start_child,2},
{supervisor,start_children,3},
{supervisor,init_children,2},
{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]}}
Offender: [{pid,undefined},
{name,couch_app},
{mfargs,{couch_app,start,[fake,[]]}},
{restart_type,permanent},
{shutdown,5000},
{child_type,supervisor}]
=INFO REPORT==== 31-Aug-2011::18:34:06 ===
application: ns_server
exited: {shutdown,{ns_server,start,[normal,[]]}}
type: temporary
{"init terminating in do_boot",{{badmatch,{error,{shutdown,{ns_server,start,[normal,[]]}}}},[{init,start_it,1},{init,start_em,1}]}}
/opt/erlang/otp_src_R14B/lib/os_mon/priv/bin/memsup: Erlang has closed.
Erlang has closed
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
bash-4.1$
Thanks.
-Jon
Hi Perry,
I used the repo tool to download the source. I am not sure which version. How can I determine this from the code?
-Jon
There should be a VERSION.TXT file under the main couchbase directory where you installed it.
Perry
Perry,
There is no VERSION.TXT file.
I used the repo tool to grab the source and built from that.
Here is the output of my manifests.xml file:
-sh-4.1# more manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
-sh-4.1#
your system is missing git. And build process requires it. ns_server crashes because you haven't built everything. Particularly, couchdb.
Jon, while we're looking into this, was this for Couchbase Single 2.0 or Couchbase Server 2.0?
Want to make sure I have it in the right forum section...
Forum support is great for free but sometimes you need a guaranteed response time and dedicated resources for your questions or issues.
Consider purchasing enterprise-level support from Couchbase: http://www.couchbase.com/products-and-services/overview
Call or email "sales -at- couchbase-dot- com" today!