You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0
Build Identifier:
When mclient tries to connect to a remote database, but provides an invalid user or password, the server will have a connection that stays in CLOSE_WAIT state.
Reproducible: Always
Steps to Reproduce:
create (empty) db on remote server
access from client: mclient -hremote.server -dremotedb -p50000
provide an incorrect password (or username) to get
InvalidCredentialsException:checkCredentials:invalid credentials for user 'monetdb'
Actual Results:
On the server it shows (netstat -ap):
tcp 1 0 remote.server:50000 client:42231 CLOSE_WAIT 30210/mserver5 t
Expected Results:
No entry
This also happens when another schema/user/pw than the default sys/monetdb is in place
for now solved by closing the streams properly after login failures. This gives slightly different time_waits then normal (successfull) connections as those
are first closed by the client.
The text was updated successfully, but these errors were encountered:
Date: 2013-09-04 09:11:45 +0200
From: @bartscheers
To: SQL devs <>
Version: 11.15.11 (Feb2013-SP3)
CC: @njnes
Last updated: 2013-09-27 13:47:18 +0200
Comment 19118
Date: 2013-09-04 09:11:45 +0200
From: @bartscheers
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0
Build Identifier:
When mclient tries to connect to a remote database, but provides an invalid user or password, the server will have a connection that stays in CLOSE_WAIT state.
Reproducible: Always
Steps to Reproduce:
InvalidCredentialsException:checkCredentials:invalid credentials for user 'monetdb'
Actual Results:
On the server it shows (netstat -ap):
tcp 1 0 remote.server:50000 client:42231 CLOSE_WAIT 30210/mserver5 t
Expected Results:
No entry
This also happens when another schema/user/pw than the default sys/monetdb is in place
Comment 19125
Date: 2013-09-04 14:37:45 +0200
From: @njnes
for now solved by closing the streams properly after login failures. This gives slightly different time_waits then normal (successfull) connections as those
are first closed by the client.
The text was updated successfully, but these errors were encountered: