-
Notifications
You must be signed in to change notification settings - Fork 531
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
Comments
I think you should be creating the pem file without a passphrase (just press enter when prompted). |
Thank you very much! Thisa. Redis sets the connection password. How does dynomite set the corresponding password? |
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'> |
That's great! |
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
The text was updated successfully, but these errors were encountered: