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

Error on healthCheck: x509: Can't parse "NaN" as a number #381

Open
quasarblue opened this issue Mar 14, 2022 · 3 comments
Open

Error on healthCheck: x509: Can't parse "NaN" as a number #381

quasarblue opened this issue Mar 14, 2022 · 3 comments

Comments

@quasarblue
Copy link

running
symbol-bootsrap healthCheck

The command output on the log is:
2022-03-13T08:35:42.590Z info User for docker resolved: 1000:1000
2022-03-13T08:35:42.591Z info Running image using Exec: symbolplatform/symbol-server:gcc-10-1.0.3.1 openssl x509 -enddate -noout -in node.crt.pem -checkend NaN
2022-03-13T08:35:43.393Z info
2022-03-13T08:35:43.394Z error x509: Can't parse "NaN" as a number
x509: Invalid number "NaN" for -checkend
x509: Use -help for summary.

To Reproduce
mainnet node: conrad.symbolnode.ninja
testnet node: pequod.cola-potatochips.net

Desktop (please complete the following information):

  • OS: Debian 11
  • Tool Version: 1.1.5 linux-x64 node-v17.2.0
  • Docker Version: 20.10.13
  • Node Version: 17.2.0
@24309
Copy link

24309 commented Apr 4, 2022

same problem, running

symbol-bootstrap healthCheck

2022-04-04T19:31:52.363Z info User for docker resolved: 1000:1000
2022-04-04T19:31:52.365Z info Running image using Exec: symbolplatform/symbol-server:gcc-10-1.0.3.1 openssl x509 -enddate -noout -in node.crt.pem -checkend NaN
2022-04-04T19:31:52.718Z info
2022-04-04T19:31:52.718Z error x509: Can't parse "NaN" as a number
x509: Invalid number "NaN" for -checkend
x509: Use -help for summary.

Error: Cannot validate node.crt.pem certificate expiration. Expiration Date cannot be resolved. Check the logs!

after running

symbol-bootstrap renewCertificates

2022-04-04T19:31:13.693Z info Generating config from preset 'mainnet'
2022-04-04T19:31:13.693Z info Using assembly 'dual'
2022-04-04T19:31:13.707Z info User for docker resolved: 1000:1000
2022-04-04T19:31:13.707Z info Running image using Exec: symbolplatform/symbol-server:gcc-10-1.0.3.3 openssl x509 -enddate -no out -in node.crt.pem -checkend 2592000
2022-04-04T19:31:32.936Z info The node.crt.pem certificate for node node will expire on Nov 30 23:24:23 2022 GMT. No need to renew it yet.
2022-04-04T19:31:32.936Z info
2022-04-04T19:31:32.936Z info The SSL certificates are up-to-date. There is nothing to upgrade.
2022-04-04T19:31:32.936Z info

OS: CentOS8
Version: symbol-bootstrap/1.1.6 linux-x64 node-v12.20.1

@fboucquez
Copy link
Owner

Have you done a

symbol-bootstrap config --upgrade -p mainnet -a dual -c customPreset.yml

Before running healthCheck?

@quasarblue
Copy link
Author

Doing symbol-bootstrap config --upgrade solves the problem

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