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

monetdbd status and mserver properties have random values #2982

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

monetdbd status and mserver properties have random values #2982

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

Comments

@monetdb-team
Copy link

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

Date: 2012-01-23 10:11:40 +0100
From: @grobian
To: Merovingian devs <>
Version: 11.7.5 (Dec2011) [obsolete]

Last updated: 2012-02-29 10:34:29 +0100

Comment 16806

Date: 2012-01-23 10:11:40 +0100
From: @grobian

continuously running monetdbd get all dbfarm with a running monetdbd returns random values for status and mserver like so:

status monetdbd[54777] (unknown version) is serving this dbfarm
mserver /usr/local/monetdb/bin/mserver5

status monetdbd[54777] 1.6 (Dec2011) is serving this dbfarm
mserver /usr/local/monetdb/bin/mserver5

status monetdbd[54777] 1.6 (Dec2011) is serving this dbfarm
mserver unknown (unsupported monetdbd)

This is odd, merovingian.log doesn't report any problems.

Comment 16851

Date: 2012-01-30 18:24:17 +0100
From: @grobian

Changeset fd13abca7fc6 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=fd13abca7fc6

Changeset description:

monetdbd properties: mserver and version are multi-line responses

make sure we expect more output to follow after requesting mserver or
version properties
make sure we terminate the connection after sending the answer to
mserver and version properties

this solves a problem where the answer might not arrive, and monetdbd
eventually thinking more should have come, bug #2982

Comment 16852

Date: 2012-01-30 18:24:39 +0100
From: @grobian

Fixed per comment 1

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