Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stethoscope on can't connect to database without monetdbd (discovery enabled) #2944

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2011-12-07 14:06:19 +0100
From: Viktor Rosenfeld <<24hesk>>
To: clients devs <>
Version: 11.5.9 (Aug2011-SP3) [obsolete]

Last updated: 2012-01-26 15:31:58 +0100

Comment 16612

Date: 2011-12-07 14:06:19 +0100
From: Viktor Rosenfeld <<24hesk>>

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2
Build Identifier:

Connecting to database with stethoscope using the -d option results in an error message.

Reproducible: Always

Steps to Reproduce:

  1. start monetdbd process
  2. run "stethoscope -d ... -u ... -P ..." with valid connection details

Actual Results:

Stethoscope exits with the following error message:

stethoscope: no databases found for '...'

Comment 16622

Date: 2011-12-07 17:17:26 +0100
From: @grobian

confirmed on Linux, i.e. it's not platform specific.

Comment 16623

Date: 2011-12-07 17:36:46 +0100
From: @grobian

Changeset ed417790216c made by Fabian Groffen fabian@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ed417790216c

Changeset description:

stethoscope: fix connecting without monetdbd

Make sure we can connect directly to mservers, and that we don't print
garbage if making a connection actually failed.  Fixes bug #2944.

Comment 16624

Date: 2011-12-07 17:37:09 +0100
From: @grobian

Thanks for reminding me. Fixed for the Dec2011 release.

Comment 16819

Date: 2012-01-26 15:31:58 +0100
From: @sjoerdmullender

The Dec2011 version has been release, so declaring this bug as FIXED.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant