Installing couchbase 2.0 beta on Ubuntu 12.04
Started by
Nadi
, Nov 06 2012 09:15 AM
13 replies to this topic
#2
Posted 06 November 2012 - 10:37 AM
Visit this page and there you can choose your operating system, in your case, Ubuntu either 32-bit or 64-bit. More your mouse over the 'install instructions' link, a tooltip baloon will appear with the command that you need to run on your ubuntu server. Make sure you decide which build to use, if you want to try 2.0 beta, choose 2.0.0-beta from the drop down list under the 'Couchbase Server Downloads" title. It's recommended that you run the following commands before you begin:
Download Couchbase binary file
Log in to your server using the shell, I use putty ssh client. You need do download the files by clicking on the links in that page, either choose the 64-bit or 32-bit.
Upload binary file to the server
Upload the .deb binary file to your ubuntu server. I use Winscp for Windows. I've created a folder in the root, chmod it (chmod 777) so I won't get permission error due to folder permission restrictions. For me it took about 10 minutes to upload a 120MB file.
If you use Amazon Web Services, don't forget to create a private key so you can use it to connect to your server if you intend to use WinSCP for Windows
Install
Run this command:
At the end you should see:
"You have successfully installed Couchbase Server".. and other notes.
If you use Amazon AWS don't forget to open the following ports in your firewall using the Security Group for that instance:
11211, 11210, 11209, 4369, 8091, 21100 to 21299
IT WORKS!
couch_base_works.jpg 60.36K
0 downloads
Now all you need is to click the SETUP button to setup your first node.
Hope this helps.
$ apt-get update $ apt-get upgrade
Download Couchbase binary file
Log in to your server using the shell, I use putty ssh client. You need do download the files by clicking on the links in that page, either choose the 64-bit or 32-bit.
Upload binary file to the server
Upload the .deb binary file to your ubuntu server. I use Winscp for Windows. I've created a folder in the root, chmod it (chmod 777) so I won't get permission error due to folder permission restrictions. For me it took about 10 minutes to upload a 120MB file.
If you use Amazon Web Services, don't forget to create a private key so you can use it to connect to your server if you intend to use WinSCP for Windows
Install
Run this command:
sudo dpkg -i couchbase-server-community_x86_64_2.0.0-beta.deb
At the end you should see:
"You have successfully installed Couchbase Server".. and other notes.
If you use Amazon AWS don't forget to open the following ports in your firewall using the Security Group for that instance:
11211, 11210, 11209, 4369, 8091, 21100 to 21299
IT WORKS!
couch_base_works.jpg 60.36K
0 downloadsNow all you need is to click the SETUP button to setup your first node.
Hope this helps.
#3
Posted 06 November 2012 - 10:57 AM
thanks so much. Took me 10 minutes to set it all up. However, I have a problem. The first time I logged into the system my node was up and running. A minute later, and I didn't do anything, the node went down (-> Servers Down: 1) - In the 'Server Nodes' tab I know see "Pend".
I get the following error: "Difficulties communicating with the cluster; displaying cached information!".
I did open all the ports on my EC2 instance just to be sure that there isn't any closed port that causes the problem.
From the log:
- Port server memcached on node 'ns_1@127.0.0.1' exited with status 137. Restarting. Messages: (repeated 7 times)
- Service memcached exited on node 'ns_1@127.0.0.1' in 0.44s
- Service memcached exited on node 'ns_1@127.0.0.1' in 0.57s
What's the problem, it suppose to work?
I get the following error: "Difficulties communicating with the cluster; displaying cached information!".
I did open all the ports on my EC2 instance just to be sure that there isn't any closed port that causes the problem.
From the log:
- Port server memcached on node 'ns_1@127.0.0.1' exited with status 137. Restarting. Messages: (repeated 7 times)
- Service memcached exited on node 'ns_1@127.0.0.1' in 0.44s
- Service memcached exited on node 'ns_1@127.0.0.1' in 0.57s
What's the problem, it suppose to work?
#4
Posted 06 November 2012 - 10:59 AM
I think there is a problem with the connection between your computer and the server. Let's try something ( i hope you use EBS-backed EC2). Stop your serve and start it again and tell me if you can connect to the couchbase admin via the browser again. Don't forget to use the new public DNS, it will change if you stop and start the server.
tell me if it works.
tell me if it works.
#10
Posted 06 November 2012 - 11:26 AM
I am experiencing the same problem too with the latest build - I will ask couchbase for some help, maybe we are missing something.
Did you use the default quota setting for RAM and which type of instance did you deploy Couchbase on (I used Micro instance and with Ubuntu precise 12.04 AMD64 server).
Did you use the default quota setting for RAM and which type of instance did you deploy Couchbase on (I used Micro instance and with Ubuntu precise 12.04 AMD64 server).
#11
Posted 06 November 2012 - 11:42 AM
I'm just adding a screenshot of what I see on the screen, hopefully couchbase team can see this and might give us some suggestions on how to solve this.
error_reading_document.jpg 11.45K
0 downloads
I've installed the beer-sample and as you can see, I clicked on document and get an error.
From the log:
error_reading_document.jpg 11.45K
0 downloadsI've installed the beer-sample and as you can see, I clicked on document and get an error.
From the log:
Quote
Control connection to memcached on 'ns_1@127.0.0.1' disconnected: {badmatch,
{error,
closed}} (repeated 1 times) ns_memcached004 ns_1@127.0.0.1 13:40:40 - Tue Nov 6, 2012
Bucket "default" loaded on node 'ns_1@127.0.0.1' in 0 seconds. ns_memcached001 ns_1@127.0.0.1 13:40:36 - Tue Nov 6, 2012
Bucket "beer-sample" loaded on node 'ns_1@127.0.0.1' in 0 seconds. ns_memcached001 ns_1@127.0.0.1 13:40:36 - Tue Nov 6, 2012
Service memcached exited on node 'ns_1@127.0.0.1' in 2.20s
supervisor_cushion001 ns_1@127.0.0.1 13:40:27 - Tue Nov 6, 2012
Port server memcached on node 'ns_1@127.0.0.1' exited with status 137. Restarting. Messages: ns_port_server000 ns_1@127.0.0.1 13:40:27 - Tue Nov 6, 2012
Control connection to memcached on 'ns_1@127.0.0.1' disconnected: {badmatch,
{error,
closed}} ns_memcached004 ns_1@127.0.0.1 13:40:25 - Tue Nov 6, 2012
Port server memcached on node 'ns_1@127.0.0.1' exited with status 137. Restarting. Messages: Tue Nov 6 11:38:51.540564 UTC 3: Trying to connect to mccouch: "localhost:11213"
Tue Nov 6 11:38:51.993193 UTC 3: Connected to mccouch: "localhost:11213"
Tue Nov 6 11:39:03.522698 UTC 3: Extension support isn't implemented in this version of bucket_engine
Tue Nov 6 11:39:03.536164 UTC 3: Trying to connect to mccouch: "localhost:11213"
Tue Nov 6 11:39:03.538284 UTC 3: Connected to mccouch: "localhost:11213"
Tue Nov 6 11:39:03.703171 UTC 3: Failed to load mutation log, falling back to key dump
Tue Nov 6 11:39:03.842849 UTC 3: metadata loaded in 11 s
Tue Nov 6 11:39:03.912724 UTC 3: warmup completed in 11 s
Tue Nov 6 11:39:05.303041 UTC 3: Extension support isn't implemented in this version of bucket_engine
Tue Nov 6 11:39:05.420023 UTC 3: Failed to load mutation log, falling back to key dump
Tue Nov 6 11:39:06.151580 UTC 3: metadata loaded in 2592 ms
Tue Nov 6 11:39:06.513814 UTC 3: warmup completed in 2946 ms ns_port_server000 ns_1@127.0.0.1 13:40:25 - Tue Nov 6, 2012
{error,
closed}} (repeated 1 times) ns_memcached004 ns_1@127.0.0.1 13:40:40 - Tue Nov 6, 2012
Bucket "default" loaded on node 'ns_1@127.0.0.1' in 0 seconds. ns_memcached001 ns_1@127.0.0.1 13:40:36 - Tue Nov 6, 2012
Bucket "beer-sample" loaded on node 'ns_1@127.0.0.1' in 0 seconds. ns_memcached001 ns_1@127.0.0.1 13:40:36 - Tue Nov 6, 2012
Service memcached exited on node 'ns_1@127.0.0.1' in 2.20s
supervisor_cushion001 ns_1@127.0.0.1 13:40:27 - Tue Nov 6, 2012
Port server memcached on node 'ns_1@127.0.0.1' exited with status 137. Restarting. Messages: ns_port_server000 ns_1@127.0.0.1 13:40:27 - Tue Nov 6, 2012
Control connection to memcached on 'ns_1@127.0.0.1' disconnected: {badmatch,
{error,
closed}} ns_memcached004 ns_1@127.0.0.1 13:40:25 - Tue Nov 6, 2012
Port server memcached on node 'ns_1@127.0.0.1' exited with status 137. Restarting. Messages: Tue Nov 6 11:38:51.540564 UTC 3: Trying to connect to mccouch: "localhost:11213"
Tue Nov 6 11:38:51.993193 UTC 3: Connected to mccouch: "localhost:11213"
Tue Nov 6 11:39:03.522698 UTC 3: Extension support isn't implemented in this version of bucket_engine
Tue Nov 6 11:39:03.536164 UTC 3: Trying to connect to mccouch: "localhost:11213"
Tue Nov 6 11:39:03.538284 UTC 3: Connected to mccouch: "localhost:11213"
Tue Nov 6 11:39:03.703171 UTC 3: Failed to load mutation log, falling back to key dump
Tue Nov 6 11:39:03.842849 UTC 3: metadata loaded in 11 s
Tue Nov 6 11:39:03.912724 UTC 3: warmup completed in 11 s
Tue Nov 6 11:39:05.303041 UTC 3: Extension support isn't implemented in this version of bucket_engine
Tue Nov 6 11:39:05.420023 UTC 3: Failed to load mutation log, falling back to key dump
Tue Nov 6 11:39:06.151580 UTC 3: metadata loaded in 2592 ms
Tue Nov 6 11:39:06.513814 UTC 3: warmup completed in 2946 ms ns_port_server000 ns_1@127.0.0.1 13:40:25 - Tue Nov 6, 2012
#14
Posted 25 April 2013 - 07:22 AM
I typed,
couchbase-server-enterprise_x86_2.0.1
I get the error:
dpkg: error processing couchbase-server-enterprise_x86_2.0.1.deb (--install):
cannot access archive: No such file or directory
Errors were encountered while processing:
couchbase-server-enterprise_x86_2.0.1.deb
couchbase-server-enterprise_x86_2.0.1
I get the error:
dpkg: error processing couchbase-server-enterprise_x86_2.0.1.deb (--install):
cannot access archive: No such file or directory
Errors were encountered while processing:
couchbase-server-enterprise_x86_2.0.1.deb










