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][Script] In 1.11 single-machine deployment, the agent module cannot be started #10125

Closed
2 tasks done
tangyungteng opened this issue May 6, 2024 · 0 comments · Fixed by #10175
Closed
2 tasks done
Assignees
Labels
type/bug Something is wrong
Milestone

Comments

@tangyungteng
Copy link

What happened

Symptom In single-node deployment 1.11, the agent cannot be started and logs are waiting agent to start, sleep 3s...
image

What you expected to happen

1.11 can be successfully deployed on a single server

How to reproduce

  1. download the binary package of version 1.11 from the official website
  2. add mysql-connector-java-8.0.28.jar
  3. change the mysql database address in the configuration file
  4. Run the bin/inlong-daemon start standalone command to start

Environment

SMP Debian 5.10.178-3 (2023-04-22) x86_64
java version "1.8.0_371"

InLong version

1.11.0

InLong Component

InLong Agent

Are you willing to submit PR?

  • Yes, I am willing to submit a PR!

Code of Conduct

@tangyungteng tangyungteng added the type/bug Something is wrong label May 6, 2024
@dockerzhang dockerzhang added this to the 1.13.0 milestone May 10, 2024
@fuweng11 fuweng11 changed the title [Bug] In 1.11 single-machine deployment, the agent module cannot be started [Bug][Script] In 1.11 single-machine deployment, the agent module cannot be started Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something is wrong
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants