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

Use 'ssh-keygen-t rsa-f' to generate the 'dynomite. Pem' file. Once the password is set, the startup fails #680

Closed
YeChuang opened this issue Jul 5, 2019 · 5 comments

Comments

@YeChuang
Copy link

YeChuang commented Jul 5, 2019

system info : centos 6.5 dynomite 0.5.9

Use 'ssh-keygen-t rsa-f' to generate the 'dynomite. Pem' file. Once the password is set, the startup fails and the error message is as follows:


[2019-07-05 11:35:29.249] conf_datastore_transform:188 Created <DATASTORE 0xc0c520 110.80.141.51:9856:1>
[2019-07-05 11:35:29.249] load_private_rsa_key_by_file:57 Error: could NOT read RSA pem key file at /usr/local/dynomite/conf/dynomite.pem
[2019-07-05 11:35:29.249] load_private_rsa_key:118 failed load_private_rsa_key_by_file(&sp->pem_key_file)
[2019-07-05 11:35:29.249] crypto_init:165 failed load_private_rsa_key(sp)
[2019-07-05 11:35:29.249] core_crypto_init:226 failed crypto_init(&ctx->pool)
[2019-07-05 11:35:29.249] core_start:334 mbuf_size not in YAML: using deprecated way 16384
[2019-07-05 11:35:29.249] core_start:341 max_msgs not in YAML: using deprecated way 200000
[2019-07-05 11:35:29.249] dn_run:578 failed core_start(nci)
[2019-07-05 11:35:29.249] dn_print_done:219 done, rabbit done

@thias
Copy link

thias commented Jul 8, 2019

I think you should be creating the pem file without a passphrase (just press enter when prompted).

@YeChuang
Copy link
Author

YeChuang commented Jul 9, 2019

Thank you very much! Thisa.

Redis sets the connection password. How does dynomite set the corresponding password?

@YeChuang
Copy link
Author

YeChuang commented Jul 9, 2019

By the way, through the dynomite operation redis (with the password set), the error is reported as follows:

[2019-07-09 14:53:52.470] proxy_accept:213 <PROXY 0x1c70420 8 listening on '10.0.2.15:8102'> accepted <CLIENT 0x1c726c0 12 from '10.0.2.15:54180'>
[2019-07-09 14:53:52.470] redis_parse_req:1232 parsed unsupported command 'AUTH'
[2019-07-09 14:53:52.470] redis_parse_req:1836 parsed bad req 5 res 1 type 0 state 5
00000000 2a 32 0d 0a 24 34 0d 0a 41 55 54 48 0d 0a 24 38 |*2..$4..AUTH..$8|
00000010 0d 0a 31 71 61 7a 32 77 73 78 0d 0a |..1qaz2wsx..|
[2019-07-09 14:53:52.470] core_close_log:406 close <CLIENT 0x1c726c0 12 from '10.0.2.15:54180'> on event FFFF eof 0 done 0 rb 28 sb 0: Invalid argument
[2019-07-09 14:53:52.470] client_unref_internal_try_put:95 <CLIENT 0x1c726c0 -1 from '10.0.2.15:54180'> unref owner <POOL 0x1c64400 'dyn_o_mite'>

@smukil
Copy link
Contributor

smukil commented Jul 9, 2019

@YeChuang The AUTH command is in review. Once it's merged, it will be supported.
#576

@YeChuang
Copy link
Author

That's great!
thanks!

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

No branches or pull requests

3 participants