Forum: Installation

Post: Failure to authenticate connection(/127.0.0.1:33413): wire protocol violation (messa

Failure to authenticate connection(/127.0.0.1:33413): wire protocol violation (messa
i_kruk
Jun 18, 2012
Hello everybody,
I'm newbie in VoltDB. So I have a problem installing this database.
I started enterprise manager on local server and added voter.jar to database. I want to test on local machine therefore my k-safety=0. I started database successfuly but when I try to connect via VoltDB Studio on port 21212 I get this message:
"Failure to authenticate connection(/127.0.0.1:33423): wire protocol violation (message length 1195725856 is too large)."
What shall I do to fix this problem?
Thanks in advance.
Use the JSON HTTP port
nshi
Jun 18, 2012
Hello,

VoltDB Studio uses JSON to interact with the database. Try connecting it to the JSON HTTP port, which is 8080 by default.

Port 21212 is for native clients which use the binary wire protocol to talk to the database.

Ning
Ning, thank you for fast
i_kruk
Jun 18, 2012
Hello,

VoltDB Studio uses JSON to interact with the database. Try connecting it to the JSON HTTP port, which is 8080 by default.

Port 21212 is for native clients which use the binary wire protocol to talk to the database.

Ning


Ning,

thank you for fast reply.

Unfortunately when I use 8080 port I have an exception:
"Thread Thread[Client authenticator 4,5,Client authentication threads] died"


JSON enabled, HTTP port= 8080. Also when I open in browser http://localhost:8080 this pages opens and I see some info about my voltdb.
log from the server
nshi
Jun 18, 2012
Ning,

thank you for fast reply.

Unfortunately when I use 8080 port I have an exception:
"Thread Thread[Client authenticator 4,5,Client authentication threads] died"

JSON enabled, HTTP port= 8080. Also when I open in browser http://localhost:8080 this pages opens and I see some info about my voltdb.


Can you post the log from the server? The log file should be in the "logs" directory in your "destination directory" as specified when you created the database in the enterprise manager.


Meanwhile, if you connect to http://localhost:8080/studio in the browser, does it connect successfully?


Ning
log.txt
i_kruk
Jun 18, 2012
Can you post the log from the server? The log file should be in the "logs" directory in your "destination directory" as specified when you created the database in the enterprise manager.

Meanwhile, if you connect to http://localhost:8080/studio in the browser, does it connect successfully?

Ning


Log.txt attached: attach13

When I open http://localhost:8080/studio I see vdb studio authentification window. I have the same error message:
"ERROR

Thread Thread[Client authenticator 11,5,Client authentication threads] died" etc
Also I'm not sure if the login/password is correct, cause i dunno where i define this log/pass :\
Low hardware threads
nshi
Jun 18, 2012
Log.txt attached: attach13

When I open http://localhost:8080/studio I see vdb studio authentification window. I have the same error message:
"ERROR

Thread Thread[Client authenticator 11,5,Client authentication threads] died" etc
Also I'm not sure if the login/password is correct, cause i dunno where i define this log/pass :\


Looking at the log, it seems like it's related to this forum post http://community.voltdb.com/node/1176 .

Ning
Thank you, Ning Hope it will
i_kruk
Jun 19, 2012
Looking at the log, it seems like it's related to this forum post http://community.voltdb.com/node/1176 .

Ning


Thank you, Ning
Hope it will be helpful
I had to put together a
aweisberg
Jun 19, 2012
Thank you, Ning
Hope it will be helpful


I had to put together a re-rolled version of 2.7.1 for someone else so I also put in the patch to fix the thread count issue on single core machines. It's unofficial, we should have another official release next week.


https://s3.amazonaws.com/com.voltdb.aweisberg/voltdb-ariel-2.7.1.tar.gz
https://s3.amazonaws.com/com.voltdb.aweisberg/changes-2.7.1.diff
bballard
Jun 10, 2013
For anyone getting this issue in the future, the WARN message indicates that something is sending messages to the client or admin port (21212 or 21211) that is not a valid wire protocol message. One typical cause of this is trying to connect to http://hostname:21212 rather than the default HTTP port http://hostname:8080. It could be any network traffic sent to the wire protocol ports, however, and it may be the case that different port number should be configured. The port numbers used by VoltDB and how to override them is documented in Managing VoltDB Appendix A.5 (http://voltdb.com/docs/MgtGuide/HostConfigPortOpts.php)