.NET SDK 2.0 Beta, Could not bootstrap, Github tester app


#1

I was trying to test new .NET SDK 2.0 Beta, so I downloaded from GitHub master version and ran tester app with “beer-sample” (default), but I had the following messages:

Could not bootstrap - check inner exceptions for details.
 is this a Memcached bucket?

Call stack:

Couchbase.dll!Couchbase.Configuration.Server.Providers.CarrierPublication.CarrierPublicationProvider.GetConfig(string bucketName = {unknown}, string password = {unknown})	C#

Line 48: var operationResult = ioStrategy.Execute(new Config(Converter));

Couchbase.dll!Couchbase.IO.Strategies.DefaultIOStrategy.Execute(Couchbase.IO.Operations.IOperation operation = {unknown})	C#

Line 45: var result = Execute(operation, connection); 

result =
{
Cas = 0
Durability = Satisfied
Exception = null
Message = "??\0\0\0\0\0?\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"
Status = UnknownCommand
Success = false
Value = null
}

Env: Couchbase Version: 2.2.0 community edition (build-837-rel), Win 8, x32

Execution log file:

2014-09-22 19:42:22,283 [8] DEBUG Couchbase.Core.ClusterManager - Trying to boostrap with Couchbase.Configuration.Server.Providers.CarrierPublication.CarrierPublicationProvider.
2014-09-22 19:42:25,279 [8] DEBUG Couchbase.Configuration.Server.Providers.ConfigProviderBase - Getting config for bucket beer-sample
2014-09-22 19:42:25,296 [8] DEBUG Couchbase.Core.ClusterManager - Creating DefaultIOStrategy
2014-09-22 19:42:25,297 [8] DEBUG Couchbase.IO.Strategies.DefaultIOStrategy - Creating DefaultIOStrategy cb7ac9ed-ce45-4191-b56c-117a25fffb76
2014-09-22 19:42:25,588 [8] DEBUG Couchbase.IO.ConnectionPool`1 - Acquire new: 8dd71cdf-c982-4eed-bf0d-9cf0f5a45377 | 127.0.0.1:11210 | [0, 0] - 4894544a-fa36-423c-b5ae-28e00d3c7135 - Disposed: False
2014-09-22 19:42:25,600 [8] INFO Couchbase.IO.ConnectionBase - Sending key  using 0 on 127.0.0.1:11210
2014-09-22 19:42:31,188 [8] DEBUG Couchbase.IO.ConnectionPool`1 - Acquire new: 4fe3f704-8554-4637-908b-1106ddcd7e92 | 127.0.0.1:11210 | [0, 1] - 4894544a-fa36-423c-b5ae-28e00d3c7135 - Disposed: False
2014-09-22 19:42:31,191 [8] DEBUG Couchbase.Authentication.SASL.CramMd5Mechanism - Authenticating socket 4fe3f704-8554-4637-908b-1106ddcd7e92
2014-09-22 19:42:31,193 [8] INFO Couchbase.IO.ConnectionBase - Sending key CRAM-MD5 using 0 on 127.0.0.1:11210
2014-09-22 19:42:31,215 [8] INFO Couchbase.IO.ConnectionBase - Sending key CRAM-MD5 using 0 on 127.0.0.1:11210
2014-09-22 19:42:31,215 [8] DEBUG Couchbase.Authentication.SASL.CramMd5Mechanism - Authentication for socket 4fe3f704-8554-4637-908b-1106ddcd7e92 succeeded.
2014-09-22 19:42:31,216 [8] DEBUG Couchbase.IO.Strategies.DefaultIOStrategy - Authenticated beer-sample using Couchbase.Authentication.SASL.CramMd5Mechanism - cb7ac9ed-ce45-4191-b56c-117a25fffb76.
2014-09-22 19:42:31,218 [8] INFO Couchbase.IO.ConnectionBase - Sending key  using 0 on 127.0.0.1:11210
2014-09-22 19:42:31,220 [8] DEBUG Couchbase.IO.ConnectionPool`1 - Releasing: 4fe3f704-8554-4637-908b-1106ddcd7e92 on 127.0.0.1:11210 - 4894544a-fa36-423c-b5ae-28e00d3c7135
2014-09-22 19:42:31,314 [8] WARN Couchbase.Core.ClusterManager - Couchbase.Configuration.ConfigException:  is this a Memcached bucket?
   at Couchbase.Configuration.Server.Providers.CarrierPublication.CarrierPublicationProvider.GetConfig(String bucketName, String password) in d:\couchbase-net-client-master\Src\Couchbase\Configuration\Server\Providers\CarrierPublication\CarrierPublicationProvider.cs:line 84
   at Couchbase.Core.ClusterManager.CreateBucket(String bucketName, String password) in d:\couchbase-net-client-master\Src\Couchbase\Core\ClusterManager.cs:line 160
2014-09-22 19:42:31,317 [8] DEBUG Couchbase.Core.ClusterManager - Trying to boostrap with Couchbase.Configuration.Server.Providers.Streaming.HttpStreamingProvider.
2014-09-22 19:42:33,147 [8] INFO Couchbase.Configuration.Server.Providers.Streaming.HttpServerConfig - Bootstrapping from http://127.0.0.1:8091/pools
2014-09-22 19:42:33,858 [2] DEBUG Couchbase.IO.Strategies.DefaultIOStrategy - Finalizing DefaultIOStrategy for 127.0.0.1:11210 - cb7ac9ed-ce45-4191-b56c-117a25fffb76
2014-09-22 19:42:33,859 [2] DEBUG Couchbase.IO.ConnectionPool`1 - Disposing ConnectionPool for 127.0.0.1:11210 - 4894544a-fa36-423c-b5ae-28e00d3c7135
2014-09-22 19:42:33,860 [2] DEBUG Couchbase.IO.ConnectionBase - Disposing connection for 127.0.0.1:11210 - 8dd71cdf-c982-4eed-bf0d-9cf0f5a45377
2014-09-22 19:42:33,861 [2] DEBUG Couchbase.IO.ConnectionBase - Disposing connection for 127.0.0.1:11210 - 4fe3f704-8554-4637-908b-1106ddcd7e92
2014-09-22 19:42:34,042 [8] INFO Couchbase.Configuration.Server.Providers.Streaming.HttpServerConfig - Bootstrapped from http://127.0.0.1:8091/pools
2014-09-22 19:42:34,042 [8] DEBUG Couchbase.Configuration.Server.Providers.ConfigProviderBase - Starting provider on main thread: 8
2014-09-22 19:42:34,066 [8] WARN Couchbase.Core.ClusterManager - System.UriFormatException: Invalid URI: Invalid port specified.
   at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
   at System.Uri..ctor(String uriString)
   at Couchbase.Configuration.Server.Serialization.BucketConfig.GetTerseUri(Node node, Boolean useSsl) in d:\couchbase-net-client-master\Src\Couchbase\Configuration\Server\Serialization\BucketConfig.cs:line 187
   at Couchbase.Configuration.Server.Providers.Streaming.HttpStreamingProvider.GetConfig(String bucketName, String password) in d:\couchbase-net-client-master\Src\Couchbase\Configuration\Server\Providers\Streaming\HttpStreamingProvider.cs:line 67
   at Couchbase.Core.ClusterManager.CreateBucket(String bucketName, String password) in d:\couchbase-net-client-master\Src\Couchbase\Core\ClusterManager.cs:line 160

Do you have any ideas?

Thank you

  • tom

#2

Tomm -

The .NET 2.0 SDK targets Couchbase Server 2.5 and greater at the moment: http://docs.couchbase.com/prebuilt/net-sdk-2.0-beta/topics/compatibility.html

Try upgrading your couchbase server instance.

-Jeff


#3

I am experiencing the same problem running against Couchbase 3.0.1.

AggregateException: Could not bootstrap - check inner exceptions for details.

InnerException: JSON integer 2896300456 is too large or small for an Int32. Path ‘[0].basicStats.memUsed’, line 1, position 9763.

Not sure if it’s relevant, but this bucket has 516934 items. I do not see this error with smaller buckets.


#4

Sounds like an issue. It looks like your cluster’s memory used is incorrectly unpacking into an int32. I’m a little unsure why we’d get this at all during bootstrap. Could you file one at couchbase.com/issues ?


#5

@ingenthr @akmartin yes, this is a different issue. I created a Jira ticket for it: http://www.couchbase.com/issues/browse/NCBC-692

-Jeff


#6

There is another place where I’m seeing overflows, namely:

diff --git a/Src/Couchbase/Configuration/Server/Serialization/Hdd.cs b/Src/Couchbase/Configuration/Server/Serialization/Hdd.cs
index d599521..c241427 100644
--- a/Src/Couchbase/Configuration/Server/Serialization/Hdd.cs
+++ b/Src/Couchbase/Configuration/Server/Serialization/Hdd.cs
@@ -14,7 +14,7 @@ namespace Couchbase.Configuration.Server.Serialization
         public long Used { get; set; }

         [JsonProperty("usedByData")]
-        public int UsedByData { get; set; }
+        public long UsedByData { get; set; }

         [JsonProperty("free")]
         public long Free { get; set; }

#7

boingolover -

Ticket can be found here: http://www.couchbase.com/issues/browse/NCBC-715

Thanks!

-Jeff


#8

I created a pull request on github as well, #27 , but I can’t link to it since I just signed up. Thanks!


#9

The issue http://www.couchbase.com/issues/browse/NCBC-715 is marked as fixed, but I just encountered using the .NET SDK 2.0 Bucket connection. I downloaded the latest NuGet package about 1h ago (19/11/2014 13:00).
When will you deploy the latest package that includes this fix to NuGet?

Thanks


#10

@antonello

It’s fixed in github, but the affects version is Beta2 and the fix version is 2.0.0, which means that it won’t be packaged (on NuGet) until 2.0.0 is released on or around Dec 2nd.

Here is what is in Beta2: https://github.com/couchbase/couchbase-net-client/commits/2.0-beta2

You can clone and build from master to get the latest of what will be in 2.0.0, along with the fix for NCBC-715.

Thanks!

-Jeff