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

Execution failed for task ':startCorda'. #90

Open
jmahmud opened this issue Aug 24, 2024 · 1 comment
Open

Execution failed for task ':startCorda'. #90

jmahmud opened this issue Aug 24, 2024 · 1 comment

Comments

@jmahmud
Copy link

jmahmud commented Aug 24, 2024

Hi

I am trialling Corde 5.2, but cloning the repo (running on macOS Sonoma 14.5) with:

  • Java SDK Azul 17
  • Intelli J CE

When I rung the gradle task startCorda I am getting this error:
`Execution failed for task ':startCorda'.

net.corda.gradle.plugin.exception.CordaRuntimeGradlePluginException: Corda process did not start successfully, please check the logs.

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.2.1/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD FAILED in 705ms
2 actionable tasks: 2 executed`

I have attempted to remove all references to corda in home directory and the repo but I am simply unable to get it to simply start the Corda service. In addition, I have been able to clone the CSDE-cordapp-template-java repo and I was able to run the startCorda service there - but I am unclear as to what the difference is.

If I could have a suggestion as to what the issue may be that would be appreciated.

Thanks
Josh

@jmahmud
Copy link
Author

jmahmud commented Aug 24, 2024

It seems this is very similar to #88 - therefore will raise a PR in order to address this. However, ran into a secondary issue of FlowManagementUI failing due to attempting to bind to port 5000 which is usually in use (particularly on macOS). Therefore adjusted this to a non-standard port (5001) in order to resolve this....

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

1 participant