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

Getting an IPC error: Access is denied #4

Open
psyantyst opened this issue Feb 20, 2018 · 3 comments
Open

Getting an IPC error: Access is denied #4

psyantyst opened this issue Feb 20, 2018 · 3 comments

Comments

@psyantyst
Copy link

Thanks for providing the config files for the PoA tutorial.

However, compared to the tutorial, the following two lines are missing in your node1.toml:
[ipc]
disable = true

So after starting node0, attempting to start node1 fails with the following error:
IPC error: Access is denied. (os error 5)

Adding the above two lines fixes the error. Are these lines missing on purpose, or is it simply by accident?

Thanks!

@sahar-fehri
Copy link

@psyantyst ,
Indeed i had the same issue, my node0.toml file was missing the above two lines you have mentioned which produced the same error. However they existed in the node1.toml file.

I wonder why were they missing in the documentation...

Thanks,

@xiaods
Copy link

xiaods commented Dec 25, 2018

the ipc is not useful for common case.

@ltfschoen
Copy link

ltfschoen commented Mar 5, 2020

Another inconsistency, is that file's in this repo only include the websockets option in the node1.toml file

node1.toml

[websockets]
port = 8547

whereas in the tutorial here https://wiki.parity.io/Demo-PoA-tutorial.html#2-setting-up-the-two-nodes, the example node0.toml and node1.toml code snippets suggest including the following websockets options in both files, and using different ports:

node0.toml

[websockets]
port = 8450

node1.toml

[websockets]
port = 8451

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

4 participants