GangLiCN commented on issue #8227: URL: https://github.com/apache/seatunnel/issues/8227#issuecomment-2594980788
In previous version, I started seatunnel server via below command, it looks like still working on latest version: > java -Dseatunnel.config=F:\Apache\seatunnel\apache-seatunnel-2.3.8\config\seatunnel.yaml -Dhazelcast.config=f:\apache\seatunnel\apache-seatunnel-2.3.8\config\hazelcast.yaml -Dlog4j2.contextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector -Dlog4j2.configurationFile=f:\apache\seatunnel\apache-seatunnel-2.3.8/config/log4j2.properties -Dseatunnel.logs.path=f:\apache\seatunnel\apache-seatunnel-2.3.8/logs -Dseatunnel.logs.file_name=seatunnel-engine-server -Xms2g -Xmx2g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/seatunnel/dump/zeta-server -cp F:\Apache\seatunnel\apache-seatunnel-2.3.8\lib\* org.apache.seatunnel.core.starter.seatunnel.SeaTunnelServer > After executed this command, Seatunnel server is runnong on port 5801, but unfortunately this service crashed.  But, I still can't submit job via below command as mentioned before: cd %seatunnel_home% call bin/seatunnel.cmd -c ./config/v2.batch.config.template -m local From the log, it fails to connect to 5802 port, I'm wondering why the seatunnel client don't try to connect to 5801 port(seatunner server is using) ???  -- 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]
