Building membase 1.7 on Ubuntu
Hi,
I followed the instructions here: http://www.couchbase.org/wiki/display/membase/Building+Membase+on+Linux+...
And got membase built and running. Looking at the console as the server starts, I don't see any errors. However, I'm running into some weird issues when I try using it in any way:
1. Can't use telnet...
telnet localhost 11211
Trying ::1...
Connected to localhost.localdomain.
Escape character is '^]'.
Connection closed by foreign host.
netstat -an | grep LISTEN tells me port 11211 is Listening
2. Using the web console
http://localhost:8091/index.html
Will open the console just fine, except it just prompts me for a login/password. I haven't set any of those yet, so... that's a problem...
Any ideas? Chances are I'm doing something (or several things) stupid, but I'm not too sure what.
Thanks
Seems like there's something wrong with the building. Can you post the output from a clean make?
Also, can you post the output of that netstat command, it would appear that either nothing or something wrong is listening on port 11211.
Perry
make DISABLE_COUCH=1
BUILD RESULTS: http://dl.dropbox.com/u/3091257/membase/build-results.txt
./install/bin/membase-server
CONSOLE OUTPUT: http://dl.dropbox.com/u/3091257/membase/console.txt
netstat -an | grep "11211"
tcp 0 0 0.0.0.0:11211 0.0.0.0:* LISTEN
tcp6 0 0 :::11211 :::* LISTEN
Thanks, we'll take a look at those outputs.
Can you post the output of "netstat -anp | grep "11211""? That will show what process is actually listening on that port.
Vasken, is it possible to use the pre-packaged binaries that we provide to ensure that Membase is able to work properly on your system?
Hi,
netstat -anp | grep "11211"
tcp 0 0 0.0.0.0:11211 0.0.0.0:* LISTEN 2224/moxi
tcp6 0 0 :::11211 :::* LISTEN 2224/moxi
Hmmm... Installing the .deb failed. The logs I get when re-installing it are:
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 229588 files and directories currently installed.)
Preparing to replace membase-server 1.7.0 (using .../membase-server-community_x86_1.7.0.deb) ...
* Stopped Membase server
Upgrading previous membase ... (1.7.0)
Stopping previous membase ... (1.7.0)
* Stopped Membase server
Saving previous membase config.dat ...
Cleaning symlinks ...
Unpacking replacement membase-server ...
Setting up membase-server (1.7.0) ...
Upgrading from 1.7.0 ...
/opt/membase/bin/mbupgrade -c /etc/opt/membase/1.7.0 -a yes
Automatic mode: running without interactive questions or confirmations.
Error: previous config directory incorrect: /etc/opt/membase/1.7.0
dpkg: error processing membase-server (--install):
subprocess installed post-installation script returned error exit status 1
Processing triggers for ureadahead ...
Errors were encountered while processing:
membase-server
Well it appears that Moxi is running on that machine. Can you confirm when the service is completely stopped that Moxi goes away? If not, I presume that Moxi is running on it's own and would then conflict with the one that Membase wants to start up.
As far as the install error goes, I've asked one of our engineers to take a look.
Can you do a completely clean install (deleting/moving all data from /opt/membase, /var/opt/membase, /etc/opt/membase)?
I want to ensure that this works for you at a base-level and then we can investigate any other issues you may be having.
Thanks
Hi, adding onto what Perry mentioned, it also looks like dpkg thought there was an existing membase 1.7.0 already installed on that node.
Please also do a 'dpkg -P membase-server' so that that part is also clean.
Cheers,
Steve
1.6.5 seems to work just fine. I was able to go through the console wizard and then telnet into 11211