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] [Master] Got Argument list too long error when starting standalone server #9575

Closed
3 tasks done
paul8263 opened this issue Apr 19, 2022 · 1 comment
Closed
3 tasks done
Assignees
Labels
backend bug Something isn't working

Comments

@paul8263
Copy link
Contributor

paul8263 commented Apr 19, 2022

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

Start Dolphinscheduler in standalone mode:
./dolphinscheduler-daemon.sh start standalone-server
And then got an error:
/opt/username/dolphinscheduler/apache-dolphinscheduler-dev-SNAPSHOT-bin/standalone-server/bin/start.sh: line 37: /usr/jdk64/java/bin/java: Argument list too long

What you expected to happen

It seems that the following code in dolphinscheduler-standalone-server/src/main/bin/start.sh:
CP=$DOLPHINSCHEDULER_HOME/libs/standalone-server/* for d in alert-server api-server master-server worker-server; do for f in $DOLPHINSCHEDULER_HOME/../$d/libs/*.jar; do CP=$CP:$f done done

returns a very long classpath that exceeds Linux command line limit.

How to reproduce

Put dolphinscheduler executables in a folder within a deep folder hierarchy or a long name and then start the standalone server.

Anything else

No response

Version

dev

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@paul8263 paul8263 added bug Something isn't working Waiting for reply Waiting for reply labels Apr 19, 2022
@github-actions
Copy link

Thank you for your feedback, we have received your issue, Please wait patiently for a reply.

  • In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
  • If you haven't received a reply for a long time, you can join our slack and send your question to channel #troubleshooting

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

No branches or pull requests

3 participants