beta1 not working - disabled options in web console
I just installed Membase Beta 1 (via rpm). The server is running and I am able to bring up the web console.
However, I can't actually do much.
here are some observations:
- MONITOR: all menu items are disabled except Log. Does any monitoring work in Beta 1?
- SETUP: Settings menu item is disabled. Can not use to configure anything.
- MANAGE > Data Buckets: "create new data bucket" is disabled, and "edit" is disabled on the default bucket. Can not add or configure buckets.
I am basically unable to do anything with Membase at this time since I can't create/edit data buckets. Is it possible I have something configured wrong?
-Corey
screenshot attached
[ATTACH]4[/ATTACH]
I can not get it to work with the .NET Enyim client (same code works against regular memcached server).
I am trying to use the 'default' bucket with credentials: default/default
is that correct, or is there a username/password I need to use?
a simplified version of my client code looks like this:
[CODE]using Enyim.Caching;
using Enyim.Caching.Configuration;
using Enyim.Caching.Memcached;
class Program
{
static void Main(string[] args)
{
MemcachedClientConfiguration config = new MemcachedClientConfiguration();
EndPointElement epe = new EndPointElement();
epe.Address = "xxx.xxx.com";
epe.Port = 11211;
config.Servers.Add(epe.EndPoint);
config.Protocol = MemcachedProtocol.Binary;
config.Authentication.Type = typeof(PlainTextAuthenticator);
config.Authentication.Parameters["bucket"] = "default";
config.Authentication.Parameters["userName"] = "default";
config.Authentication.Parameters["password"] = "default";
MemcachedClient _memCache = new MemcachedClient(config);
object res = _memCache.Get("123");
}
}[/CODE]
-Corey
Corey, membase doesn't use the same SASL authentication as our memcached server does. There is only one bucket right now, and it is avialable without any authentication on port 11211.
Can you try removing the authentication parameters/type and trying again? Are you completely unable to connect or are you getting errors back?
You should be able to test the basic funcitonality by telnetting to your membase server on port 11211 and running:
'stats'
'set test_key 0 0 1'
'a'
'get test_key'
Let me know if that helps...
Perry
telnet interface works. I can set/get keys just fine.
I tried removing authentication from my client code and still no luck. I get no errors, just can't connect or do any operations. all operations hang and eventually return null.
-Corey
Corey, please remove the: "config.Protocol = MemcachedProtocol.Binary;" line and try again. While membase does technically support the binary protocol, it requires some extra flags to work properly that have not yet been integrated into client libraries. We are working on getting that done, but in the meantime everything goes through a proxy that is embedded within the server. Unfortunately, that proxy does not yet support binary->binary proxying and so clients must use the ASCII protocol.
Hope that helps, let me know if you were successful.
Perry
Perry,
removing all authentication and removing binary protocol seems to have fixed my probs. I can now connect and operate against the default bucket.
... now to continue testing.
thanks for your help.
-Corey
Thanks for your patience Corey, we'll be documenting these things as we go along.
Perry
Have they been? They look disabled in my install of beta2.
Some have, some have not. We enabled Monitor->Data Buckets to allow you to view statistics, but due to time and testing constraints we had to leave some other things out. Beta 3 is planned to allow multiple buckets to be created.
Thanks for your patience!
Perry
Jakarl is specialized in providing the work and life consults as well as the corresponding services for foreign friends. With our service, you are not only no longer worried about your trifle things on life, but also not be bothered with communicating
problems. Apart from that, there are well-designed tourist track around China we recommended and nostalgia gatherings as well as making-friends parties with local color.
Jakarl’s patience does not limit to these. As long as you come across any problem in your life and work in China, please don’t hesitate to contact us. We are very pleased to give our best suggestions and resolutions according to your needs for your reference. Trust us, you will not be disappointed!
http://www.jakarl.com
You haven't configured anything wrong. The disabled options will be enabled in the next beta. Presently there's a default data bucket that will receive the entire quota of storage and be spread across all your nodes. If you connect to port 11211 with a memcached client and do some sets, that's where the data will go.