ESQuery Errors

EventStoreDB
1

I just downloaded the windows 3.0.0.0 version. The documentation references a tool called esquery, I did not see any binary named esquery. I do however have an EventStore.Query.exe tool. When I try running that tool it fails with the following information. I have tried creating different users and not even specifying a user / password and nothing seems to work for me.

C:\opt\eventstore> .\eventstore.query.exe

No server set defaulting to http://127.0.0.1:2113/

username:admin

password:

Unhandled Exception: System.Net.ProtocolViolationException: You must provide a request body if you set ContentLength>0 or Send

Chunked==true. Do this by calling [Begin]GetRequestStream before [Begin]GetResponse.

at System.Net.HttpWebRequest.GetResponse()

at esquery.Program.TryValidatePassword(Uri baseuri, NetworkCredential cred) in c:\EventStore\src\esquery\Program.cs:line 12

4

at esquery.Program.GetValidatedNetworkCredential(Uri baseuri) in c:\EventStore\src\esquery\Program.cs:line 101

at esquery.Program.ReadArgs(String[] args) in c:\EventStore\src\esquery\Program.cs:line 83

at esquery.Program.Main(String[] args) in c:\EventStore\src\esquery\Program.cs:line 199

Thanks,

Adam

2

That’s not very good as an error message.

Are you actually running the server on 127.0.0.1:2113?

Cheers,

James

3

Yes, I am running a cluster on 127.0.0.1:1113,2113,3113

I don’t think its even making the http request, using fiddler I can’t see any requests going out.

Adam

4

I’ll try to repro.

5

Thanks. From git blame it looks like the Content Length was changed from 0 to 10 in this commit [https://github.com/EventStore/EventStore/commit/60fbd603a3509d364d18ccb5a4a3c592e1d58723#diff-93b06b23d607a60cf920d163f1906f7eL105]

I don’t see any body being sent in the request so I would assume the length should be 0 not 10, maybe the MS-Clr and Mono have different implementations here so its not causing an issue on linux.

Adam

6

That looks like a fat finger but this code has been used since then perhaps it’s a framework difference

7

I suspect Mono is rather more forgiving in this kind of case than .NET. Either way, we’ll have it fixed and in 3.0.1 (arriving shortly with numerous small fixes).

Cheers,

James

8

This is being tracked here: https://github.com/EventStore/EventStore/issues/283

James