[Bug] setaunnel web 1.0.1 can not work with seatunnel engine 2.3.7
Search before asking
- [X] I had searched in the issues and found no similar issues.
What happened
Refer to the link https://github.com/apache/seatunnel-web/tree/main?tab=readme-ov-file#33-install to deploy seatunnel-web-1.0.1. However, after starting seatunnel-web, the port 8801 of seatunnel-web is normally listening, but the page reports a 404 error.
SeaTunnel Version
2.3.7
SeaTunnel Config
The hazelcast-master.yaml for Zeta Engine:
hazelcast:
cluster-name: seatunnel
network:
rest-api:
enabled: true
endpoint-groups:
CLUSTER_WRITE:
enabled: true
DATA:
enabled: true
join:
tcp-ip:
enabled: true
member-list: # 添加所有 Master 节点、Worker 节点,注意端口的区别
- h142:5801 # Master Role
- h143:5801 # Master Role
- h149:5801 # Master Role
- h144:5802 # Worker Role
- h145:5802 # Worker Role
port:
auto-increment: false
port: 5801
properties:
hazelcast.invocation.max.retry.count: 20
hazelcast.tcp.join.port.try.count: 30
hazelcast.logging.type: log4j2
hazelcast.operation.generic.thread.count: 50
hazelcast.heartbeat.failuredetector.type: phi-accrual
hazelcast.heartbeat.interval.seconds: 2
hazelcast.max.no.heartbeat.seconds: 180
hazelcast.heartbeat.phiaccrual.failuredetector.threshold: 10
hazelcast.heartbeat.phiaccrual.failuredetector.sample.size: 200
hazelcast.heartbeat.phiaccrual.failuredetector.min.std.dev.millis: 100
The application.yml for SeaTunnel-Web:
```yml
server:
port: 8801
spring:
application:
name: seatunnel
jackson:
date-format: yyyy-MM-dd HH:mm:ss
datasource:
driver-class-name: com.mysql.cj.jdbc.Driver
url: jdbc:mysql://10.0.6.144:3306/seatunnel?useSSL=false&useUnicode=true&characterEncoding=utf-8&allowMultiQueries=true&allowPublicKeyRetrieval=true
username: seatunnel
password: seatunnel
mvc:
pathmatch:
matching-strategy: ant_path_matcher
jwt:
expireTime: 86400
# please add key when deploy
secretKey:
algorithm: HS256
---
spring:
config:
activate:
on-profile: h2
sql:
init:
schema-locations: classpath*:script/seatunnel_server_h2.sql
datasource:
driver-class-name: org.h2.Driver
url: jdbc:h2:mem:seatunnel;MODE=MySQL;DB_CLOSE_DELAY=-1;DATABASE_TO_LOWER=true
username: sa
password: sa
h2:
console:
enabled: true
path: /h2
settings:
trace: false
web-allow-others: false
### Running Command
```shell
sh bin/seatunnel-backend-daemon.sh start
Error Exception
404 error for web ui
Zeta or Flink or Spark Version
Zeta 2.3.7
Java or Scala Version
openjdk1.8
Screenshots
Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
the error in logfile:
2024-09-13 14:24:48.128 seatunnel h142 INFO [main] [ClientLoggingService$DefaultLogger.log():104] - hz.client_1 [seatunnel] [5.1] Authenticated with server [h143]:5801:2035e838-9458-4998-b5ed-800e8a8294ac, server version: 5.1, local address: /10.0.6.142:57679
2024-09-13 14:24:48.129 seatunnel h142 INFO [main] [ClientLoggingService$DefaultLogger.log():104] - hz.client_1 [seatunnel] [5.1] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
2024-09-13 14:24:48.137 seatunnel h142 INFO [hz.client_1.event-3] [ClientLoggingService$DefaultLogger.log():104] - hz.client_1 [seatunnel] [5.1]
Members [5] {
Member [h142]:5801 - 89794f46-e124-4250-8761-a9ca3fab0e60
Member [h143]:5801 - 2035e838-9458-4998-b5ed-800e8a8294ac
Member [h149]:5801 - dee88345-054b-42bc-afa4-f4086531377f
Member [h144]:5802 - 6f699cb2-8930-4fda-b4f4-9a9c5914de00 lite
Member [h145]:5802 - 308ead1c-7cad-4ac1-bc89-967b353b0f59 lite
}
2024-09-13 14:24:48.140 seatunnel h142 INFO [main] [ClientLoggingService$DefaultLogger.log():104] - hz.client_1 [seatunnel] [5.1] Authenticated with server [h142]:5801:89794f46-e124-4250-8761-a9ca3fab0e60, server version: 5.1, local address: /10.0.6.142:60376
2024-09-13 14:24:48.143 seatunnel h142 INFO [main] [ClientLoggingService$DefaultLogger.log():104] - hz.client_1 [seatunnel] [5.1] Authenticated with server [h149]:5801:dee88345-054b-42bc-afa4-f4086531377f, server version: 5.1, local address: /10.0.6.142:56315
2024-09-13 14:24:48.146 seatunnel h142 INFO [main] [ClientLoggingService$DefaultLogger.log():104] - hz.client_1 [seatunnel] [5.1] Authenticated with server [h144]:5802:6f699cb2-8930-4fda-b4f4-9a9c5914de00, server version: 5.1, local address: /10.0.6.142:33305
2024-09-13 14:24:48.148 seatunnel h142 INFO [main] [ClientLoggingService$DefaultLogger.log():104] - hz.client_1 [seatunnel] [5.1] Authenticated with server [h145]:5802:308ead1c-7cad-4ac1-bc89-967b353b0f59, server version: 5.1, local address: /10.0.6.142:49540
2024-09-13 14:24:48.179 seatunnel h142 INFO [main] [AbstractLogger.info():69] - Client statistics is enabled with period 5 seconds.
2024-09-13 14:24:48.232 seatunnel h142 WARN [main] [GroovyTemplateAutoConfiguration$GroovyMarkupConfiguration.checkTemplateLocationExists():86] - Cannot find template location: classpath:/templates/ (please add some templates, check your Groovy configuration, or set spring.groovy.template.check-template-location=false)
2024-09-13 14:24:48.502 seatunnel h142 INFO [main] [ContextHandler$Context.log():2368] - Initializing Spring DispatcherServlet 'dispatcherServlet'
2024-09-13 14:24:48.502 seatunnel h142 INFO [main] [FrameworkServlet.initServletBean():525] - Initializing Servlet 'dispatcherServlet'
2024-09-13 14:24:48.503 seatunnel h142 INFO [main] [FrameworkServlet.initServletBean():547] - Completed initialization in 1 ms
2024-09-13 14:24:48.511 seatunnel h142 INFO [main] [AbstractConnector.doStart():333] - Started ServerConnector@576b7c74{HTTP/1.1, (http/1.1)}{0.0.0.0:8801}
2024-09-13 14:24:48.512 seatunnel h142 INFO [main] [JettyWebServer.start():172] - Jetty started on port(s) 8801 (http/1.1) with context path '/'
2024-09-13 14:24:48.513 seatunnel h142 INFO [main] [DocumentationPluginsBootstrapper.start():120] - Context refreshed
2024-09-13 14:24:48.530 seatunnel h142 INFO [main] [DocumentationPluginsBootstrapper.start():123] - Found 1 custom documentation plugin(s)
2024-09-13 14:24:48.543 seatunnel h142 INFO [main] [ApiListingReferenceScanner.scan():41] - Scanning for api listing references
2024-09-13 14:24:48.674 seatunnel h142 INFO [main] [CachingOperationNameGenerator.startingWith():40] - Generating unique operation named: listAllTransformUsingGET_1
2024-09-13 14:24:48.682 seatunnel h142 INFO [main] [CachingOperationNameGenerator.startingWith():40] - Generating unique operation named: listSinkUsingGET_1
2024-09-13 14:24:48.688 seatunnel h142 INFO [main] [CachingOperationNameGenerator.startingWith():40] - Generating unique operation named: listSourceUsingGET_1
2024-09-13 14:24:48.692 seatunnel h142 INFO [main] [CachingOperationNameGenerator.startingWith():40] - Generating unique operation named: syncUsingGET_1
2024-09-13 14:24:48.747 seatunnel h142 INFO [main] [CachingOperationNameGenerator.startingWith():40] - Generating unique operation named: getJobDefinitionUsingGET_1
2024-09-13 14:24:49.056 seatunnel h142 INFO [main] [StartupInfoLogger.logStarted():61] - Started SeatunnelApplication in 5.257 seconds (JVM running for 5.538)
2024-09-13 14:24:53.513 seatunnel h142 INFO [qtp2122225197-15] [AuthenticationInterceptor.preHandle():70] - user does not exist
What is the URL of the Seatunnel web UI you are accessing?
http://10.0.6.142:8801/ui/, 10.0.6.142 is the ip of the seatunnel-web host
Try http://10.0.6.142:8801/ui/#
you can build latest seatunnel-web code to see it working with seatunnel 2.3.7
Try http://10.0.6.142:8801/ui/#
The same error as before
you can build latest seatunnel-web code to see it working with seatunnel 2.3.7
Is it the main branch of seatunnel-web in git repository?
yes
@chenyz1984 Need to configure the secretKey in application.yml
have you find any solution?
have you find any solution?
have not
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.