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

[Bug]: Running a Chainlink Node | CLI Param Ordering for V2 Nodes #1278

Closed
patrickhuie19 opened this issue May 4, 2023 · 0 comments · Fixed by #1279
Closed

[Bug]: Running a Chainlink Node | CLI Param Ordering for V2 Nodes #1278

patrickhuie19 opened this issue May 4, 2023 · 0 comments · Fixed by #1279
Labels
bug Something isn't working triage

Comments

@patrickhuie19
Copy link
Contributor

Describe the bug

In https://docs.chain.link/chainlink-nodes/v1/running-a-chainlink-node , step #4:

Chainlink Nodes running 2.0.0 and later require the -config and -secrets flags after the node start part of the command. Versions 1.13.1 and earlier require the -config and -secrets flags to be placed before node start.

However, I was unable to start a v2 node without putting the -config and -secrets flags before node start. The expected behavior is to put the flags after node.

To Reproduce

Follow https://docs.chain.link/chainlink-nodes/v1/running-a-chainlink-node up to step 4

URLs

https://docs.chain.link/chainlink-nodes/v1/running-a-chainlink-node

Expected behavior

The documentation should clarify that in v2 of the node, the flags can be placed after node, not node start.

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage
Projects
None yet
1 participant