Hello, This is my first message to the Flink mailing list.
I previously had a Flink job jar that worked flawlessly on my old Debian machine about six months ago. Recently, I migrated to a new Debian PC and deployed the same jar file using the same version of Flink. Although the job appears to run in the Flink dashboard without any errors, it fails to write data to the PostgreSQL database, but the job itself is not stopping. Notably, when I run the jar file directly using the Java command on the new PC, it works as expected. I also updated to the latest Flink version and rebuilt the jar with the updated dependencies, but the issue persists. Has anyone encountered a similar problem or have suggestions on what might be causing this discrepancy when running via the Flink cluster? Thank you for your assistance. Best regards, Vishnu
