[Bug][Agent] The data file cannot be fetched

[byhuwei]

What happened

I configure all procedures and start a job of flink successfully, but the data in localhost cannot be written into mysql as i configured.
The state of data source is "waiting to add". There was no error logs in all of components.

What you expected to happen

The task of Inlong Agent was not created by Inlong Manager.

How to reproduce

The version of Inlong is 1.3.0 and I establish it by docker compose. The configuration of data source as follow. The name of data source is "local", the ip is "127.0.0.1", the path is "/data/collect-data/*.csv". Then i create a file named "1.csv" under the path /data/collect-data/ in the Inlong Agent container. However, it doesnot seem to work.

Environment

docker 20.10.17
docker compose v2.6.0

InLong version

1.3.0

InLong Component

InLong Manager, InLong Agent

Are you willing to submit PR?

• Yes, I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Thanks a lot for opening your first issue with us! 🧡 We'll get back to you shortly! ⏳

[dockerzhang]

@lucaspeng12138 PTAL, thanks.

[lucaspeng12138]

@byhuwei could you please package logs in manager and send to me? I cannot find a same env with your problem. My email 171575146@qq.com. Thanks!

[lucaspeng12138]

@byhuwei and agent logs too, please.

[byhuwei]

@byhuwei and agent logs too, please.

@lucaspeng12138 I have sent to u

[lucaspeng12138]

@byhuwei I find an error log in agent, is it network from agent to manager ok? I think agent can't access manager.

[byhuwei]

@lucaspeng12138 I start inlong service with docker compose, so i think maybe the agent start before manager which cause this error. I start the task at 08:17 and this error occured at 08:07. Also, there are no errors of agent after 08:07. So i think this error has no relation to this situation

[lucaspeng12138]

@byhuwei OK, I'm checking and trying to reproduce this problem.

[lucaspeng12138]

@byhuwei I find an environment which can reproduce this problem. I found agent report heartbeat to manager use instance ip 172.19.0.6 which is the agent container ip. When I using 127.0.0.1 on data source to tell manager agent ip is localhost, this problem will happen. You can confirm agent ip in mysql->apache_inlong_manager->component_heartbeat.

[lucaspeng12138]

@byhuwei Please let me know any progress if you have tried again.

[byhuwei]

@lucaspeng12138 I'm really sorry for responding u so late. I have retried again as u mentioned and i got a correct status when i use the agent container ip. So, the cause of this situation is the wrong ip of datasource which i configured. Thanks very much!