Mojave Terminal not starting nodes from runnodes (Corda deployNodes)

Viewed 412

When starting ./build/nodes/deployNodes in macOS Mojave 10.14.1, the terminal opens but does not start up the tabs corresponding to each node defined in the deployNodes task in Gradle.

Specifically looking at the tutorial section here.

Anyone have a solution?

5 Answers

To fix this, go to System Preferences -> Security and Privacy -> Privacy -> Accessibility and make sure that Terminal is in the list and checked (enabled).

If you are running nodes from IntelliJ terminal you have to add it and Terminal to Accessibility and Automation sections.

Accessibility: Accessibility Automation: Automation

I am facing the same issue (on Mojave) even after adding Intellij and terminal to accessibility and automation.

The work around is to manually start the nodes via; java -jar corda.jar in each nodes directory.

I managed to fix this issue by resetting security permissions on OSX. I could not work out how to add Java into the Accessability group.

Conditions apply in this paragraph! If you type 'tccutil reset AppleEvents' in a Terminal then this will clear all the security associations. Then when you run applications again you'll get prompted to allow or block. So if you do this, then try ./runnodes again you should see a bunch of dialogs which you can click yes to. The nodes should now start ok.

Also, in your security settings you should see 'Java' appear in the Accessibility group.

Instead of accessibility and automation, to make this work on Catalina 10.15.7 I had to add terminal to the Developer Tools section instead of accessibility and automation:

enter image description here

Related