DanielLeens commented on issue #11595:
URL: https://github.com/apache/seatunnel/issues/11595#issuecomment-5137560998

   Thanks for the report and the extra note about FTP connectivity.
   
   I read the stack trace. This fails during source initialization, before the 
Flink job starts reading records: `BaseFileSourceConfig` discovers the 
configured path, the FTP source calls `listStatus/listFiles`, and the final 
`Connection reset` is raised while the FTP client is closing/logging out after 
that file-list operation. So this is not a plugin discovery problem; it is in 
the FTP directory listing/control-channel lifecycle for this path.
   
   A few details are still needed before we can tell whether this is a 
SeaTunnel bug or an FTP server/network-mode compatibility issue:
   
   1. Please confirm the exact FTP host used by the failing run. The config 
snippet shows one host, but the log line says SeaTunnel connected to a 
different FTP server address.
   2. From the same machine/container that runs the Flink client, please verify 
a directory listing of `/pathimages/pdfbg/2023-03/` using the same FTP mode, 
not only login/connect. For this issue, `LIST`/directory listing behavior is 
the important part.
   3. Please provide the FTP server log around the failed `LIST` and 
`QUIT/logout` time, if available.
   4. Please try both supported SeaTunnel FTP modes, `passive_local` and 
`active_local`, and report whether the failure changes.
   5. If possible, include the number of entries under that directory and 
whether any file name uses non-UTF-8 or unusual characters.
   
   Please redact passwords, access keys, internal tokens, and other credentials 
in any follow-up. Also, since the SeaTunnel project tracks issues in English, 
please provide the follow-up details in English if possible so more maintainers 
can help review it.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to