[Bug]: Amoro start error

[zhangwl9]

What happened?

After deploying Amoro and running {AMORO_HOME}/bin/ams.sh start, the following error message appears:

2025-01-09 19:33:30,765 ERROR [main] [org.apache.amoro.server.AmoroServiceContainer] [] - AMS start error
io.javalin.core.util.JavalinException: Static resource directory with path: '/static' does not exist. Depending on your setup, empty folders might not get copied to classpath.
at io.javalin.jetty.ConfigurableHandler.getResourceBase(JettyResourceHandler.kt:96) ~[javalin-4.6.8.jar:4.6.8]
at io.javalin.jetty.ConfigurableHandler.(JettyResourceHandler.kt:70) ~[javalin-4.6.8.jar:4.6.8]
at io.javalin.jetty.JettyResourceHandler.addStaticFileConfig(JettyResourceHandler.kt:33) ~[javalin-4.6.8.jar:4.6.8]
at io.javalin.core.JavalinConfig.addStaticFiles(JavalinConfig.java:134) ~[javalin-4.6.8.jar:4.6.8]
at org.apache.amoro.server.AmoroServiceContainer.lambda$initHttpService$2(AmoroServiceContainer.java:249) ~[amoro-ams-0.8-SNAPSHOT.jar:0.8-SNAPSHOT]
at io.javalin.core.JavalinConfig.applyUserConfig(JavalinConfig.java:205) ~[javalin-4.6.8.jar:4.6.8]
at io.javalin.Javalin.create(Javalin.java:93) ~[javalin-4.6.8.jar:4.6.8]
at org.apache.amoro.server.AmoroServiceContainer.initHttpService(AmoroServiceContainer.java:247) ~[amoro-ams-0.8-SNAPSHOT.jar:0.8-SNAPSHOT]
at org.apache.amoro.server.AmoroServiceContainer.startService(AmoroServiceContainer.java:172) ~[amoro-ams-0.8-SNAPSHOT.jar:0.8-SNAPSHOT]
at org.apache.amoro.server.AmoroServiceContainer.main(AmoroServiceContainer.java:123) [amoro-ams-0.8-SNAPSHOT.jar:0.8-SNAPSHOT]

Affects Versions

master(amoro-0.8-SNAPSHOT)

What table formats are you seeing the problem on?

No response

What engines are you seeing the problem on?

AMS

How to reproduce

1. Update the Amoro master branch to the latest version and compile Amoro (in a Windows 10 environment).
2. Deploy Amoro on Linux.
3. Configure the password and database (for MySQL) in {AMORO_HOME}/conf/config.yaml.
4. Execute {AMORO_HOME}/bin/ams.sh start.

Relevant log output

2025-01-09 19:33:30,365 INFO [main] [org.apache.amoro.server.table.executor.DataExpiringExecutor] [] - Table executor DataExpiringExecutor initialized
2025-01-09 19:33:30,365 INFO [main] [org.apache.amoro.server.table.executor.SnapshotsExpiringExecutor] [] - Table executor SnapshotsExpiringExecutor initialized
2025-01-09 19:33:30,365 INFO [main] [org.apache.amoro.server.table.executor.OrphanFilesCleaningExecutor] [] - Table executor OrphanFilesCleaningExecutor initialized
2025-01-09 19:33:30,365 INFO [main] [org.apache.amoro.server.table.executor.DanglingDeleteFilesCleaningExecutor] [] - Table executor DanglingDeleteFilesCleaningExecutor initialized
2025-01-09 19:33:30,365 INFO [main] [org.apache.amoro.server.table.executor.OptimizingCommitExecutor] [] - Table executor OptimizingCommitExecutor initialized
2025-01-09 19:33:30,365 INFO [main] [org.apache.amoro.server.table.executor.OptimizingExpiringExecutor] [] - Table executor OptimizingExpiringExecutor initialized
2025-01-09 19:33:30,365 INFO [main] [org.apache.amoro.server.table.executor.BlockerExpiringExecutor] [] - Table executor BlockerExpiringExecutor initialized
2025-01-09 19:33:30,365 INFO [main] [org.apache.amoro.server.table.executor.TableRuntimeRefreshExecutor] [] - Table executor TableRuntimeRefreshExecutor initialized
2025-01-09 19:33:30,365 INFO [main] [org.apache.amoro.server.table.executor.TagsAutoCreatingExecutor] [] - Table executor TagsAutoCreatingExecutor initialized
2025-01-09 19:33:30,365 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - AMS table service have been initialized
2025-01-09 19:33:30,366 INFO [table-explorer-scheduler-0] [org.apache.amoro.server.table.DefaultTableService] [] - Syncing external catalogs:
2025-01-09 19:33:30,366 INFO [table-explorer-scheduler-0] [org.apache.amoro.server.table.DefaultTableService] [] - Syncing external catalogs took 1 ms.
2025-01-09 19:33:30,370 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - Initializing thrift service...
2025-01-09 19:33:30,370 INFO [terminal-session-gc] [org.apache.amoro.server.terminal.TerminalManager] [] - Terminal Session Clean Task started
2025-01-09 19:33:30,370 INFO [terminal-session-gc] [org.apache.amoro.server.terminal.TerminalManager] [] - Terminal Session Clean Task, check interval: 300000 ms
2025-01-09 19:33:30,370 INFO [terminal-session-gc] [org.apache.amoro.server.terminal.TerminalManager] [] - Terminal Session Timeout: 30 minutes
2025-01-09 19:33:30,380 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - Initializing thrift server: TableMetastore
2025-01-09 19:33:30,380 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - Starting TableMetastore thrift server on port: 1262
2025-01-09 19:33:30,385 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - The number of selector threads for the TableMetastore thrift server is: 2
2025-01-09 19:33:30,385 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - The size of per-selector queue for the TableMetastore thrift server is: 4
2025-01-09 19:33:30,389 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - Initializing thrift server: OptimizeManager
2025-01-09 19:33:30,389 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - Starting OptimizeManager thrift server on port: 1261
2025-01-09 19:33:30,389 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - The number of selector threads for the OptimizeManager thrift server is: 2
2025-01-09 19:33:30,389 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - The size of per-selector queue for the OptimizeManager thrift server is: 4
2025-01-09 19:33:30,390 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - thrift-table-management-server-thread has been started
2025-01-09 19:33:30,390 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - thrift-optimizing-server-thread has been started
2025-01-09 19:33:30,566 INFO [main] [org.eclipse.jetty.util.log] [] - Logging initialized @1755ms to org.eclipse.jetty.util.log.Slf4jLog
2025-01-09 19:33:30,587 ERROR [main] [org.apache.amoro.server.AmoroServiceContainer] [] - AMS start error
io.javalin.core.util.JavalinException: Static resource directory with path: '/static' does not exist. Depending on your setup, empty folders might not get copied to classpath.
        at io.javalin.jetty.ConfigurableHandler.getResourceBase(JettyResourceHandler.kt:96) ~[javalin-4.6.8.jar:4.6.8]
        at io.javalin.jetty.ConfigurableHandler.<init>(JettyResourceHandler.kt:70) ~[javalin-4.6.8.jar:4.6.8]
        at io.javalin.jetty.JettyResourceHandler.addStaticFileConfig(JettyResourceHandler.kt:33) ~[javalin-4.6.8.jar:4.6.8]
        at io.javalin.core.JavalinConfig.addStaticFiles(JavalinConfig.java:134) ~[javalin-4.6.8.jar:4.6.8]
        at org.apache.amoro.server.AmoroServiceContainer.lambda$initHttpService$2(AmoroServiceContainer.java:249) ~[amoro-ams-0.8-SNAPSHOT.jar:0.8-SNAPSHOT]
        at io.javalin.core.JavalinConfig.applyUserConfig(JavalinConfig.java:205) ~[javalin-4.6.8.jar:4.6.8]
        at io.javalin.Javalin.create(Javalin.java:93) ~[javalin-4.6.8.jar:4.6.8]
        at org.apache.amoro.server.AmoroServiceContainer.initHttpService(AmoroServiceContainer.java:247) ~[amoro-ams-0.8-SNAPSHOT.jar:0.8-SNAPSHOT]
        at org.apache.amoro.server.AmoroServiceContainer.startService(AmoroServiceContainer.java:172) ~[amoro-ams-0.8-SNAPSHOT.jar:0.8-SNAPSHOT]
        at org.apache.amoro.server.AmoroServiceContainer.main(AmoroServiceContainer.java:123) [amoro-ams-0.8-SNAPSHOT.jar:0.8-SNAPSHOT]
2025-01-09 19:33:30,592 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - Stopping table management server...
2025-01-09 19:33:30,592 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - Stopping optimizing server...
2025-01-09 19:33:30,592 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - Stopping table service...
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.TagsAutoCreatingExecutor] [] - dispose thread pool for threads tags-auto-creating-executor
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.TableRuntimeRefreshExecutor] [] - dispose thread pool for threads table-runtime-refresh-executor
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.BlockerExpiringExecutor] [] - dispose thread pool for threads blocker-expiring-executor
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.OptimizingExpiringExecutor] [] - dispose thread pool for threads optimizing-expiring-executor
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.OptimizingCommitExecutor] [] - dispose thread pool for threads optimizing-commit-executor
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.DanglingDeleteFilesCleaningExecutor] [] - dispose thread pool for threads dangling-delete-files-cleaning-executor
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.OrphanFilesCleaningExecutor] [] - dispose thread pool for threads orphan-files-cleaning-executor
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.SnapshotsExpiringExecutor] [] - dispose thread pool for threads snapshots-expiring-executor
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.DataExpiringExecutor] [] - dispose thread pool for threads data-expiring-executor
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - Stopping terminal manager...
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - Stopping optimizing service...
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.TagsAutoCreatingExecutor] [] - dispose thread pool for threads tags-auto-creating-executor
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.TableRuntimeRefreshExecutor] [] - dispose thread pool for threads table-runtime-refresh-executor
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.BlockerExpiringExecutor] [] - dispose thread pool for threads blocker-expiring-executor
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.OptimizingExpiringExecutor] [] - dispose thread pool for threads optimizing-expiring-executor
2025-01-09 19:33:30,593 INFO [main] [org.apache.amoro.server.table.executor.OptimizingCommitExecutor] [] - dispose thread pool for threads optimizing-commit-executor
2025-01-09 19:33:30,594 INFO [main] [org.apache.amoro.server.table.executor.DanglingDeleteFilesCleaningExecutor] [] - dispose thread pool for threads dangling-delete-files-cleaning-executor
2025-01-09 19:33:30,594 INFO [main] [org.apache.amoro.server.table.executor.OrphanFilesCleaningExecutor] [] - dispose thread pool for threads orphan-files-cleaning-executor
2025-01-09 19:33:30,594 INFO [main] [org.apache.amoro.server.table.executor.SnapshotsExpiringExecutor] [] - dispose thread pool for threads snapshots-expiring-executor
2025-01-09 19:33:30,594 INFO [main] [org.apache.amoro.server.table.executor.DataExpiringExecutor] [] - dispose thread pool for threads data-expiring-executor
2025-01-09 19:33:30,593 ERROR [terminal-session-gc] [org.apache.amoro.server.terminal.TerminalManager] [] - Interrupted when sleep
java.lang.InterruptedException: sleep interrupted
        at java.lang.Thread.sleep(Native Method) ~[?:1.8.0_352]
        at java.lang.Thread.sleep(Thread.java:342) ~[?:1.8.0_352]
        at java.util.concurrent.TimeUnit.sleep(TimeUnit.java:386) ~[?:1.8.0_352]
        at org.apache.amoro.server.terminal.TerminalManager$SessionCleanTask.run(TerminalManager.java:419) [amoro-ams-0.8-SNAPSHOT.jar:0.8-SNAPSHOT]
        at java.lang.Thread.run(Thread.java:750) [?:1.8.0_352]
2025-01-09 19:33:30,594 INFO [main] [org.apache.amoro.server.HighAvailabilityContainer] [] - Waiting to become the leader of AMS
2025-01-09 19:33:30,594 INFO [main] [org.apache.amoro.server.HighAvailabilityContainer] [] - Became the leader of AMS
2025-01-09 19:33:30,595 INFO [main] [org.apache.amoro.server.manager.AbstractPluginManager] [] - initializing plugin configuration for: event-listeners
2025-01-09 19:33:30,596 INFO [main] [org.apache.amoro.server.manager.AbstractPluginManager] [] - initializing plugin configuration for: metric-reporters
2025-01-09 19:33:30,634 INFO [main] [org.apache.amoro.server.AmoroServiceContainer] [] - Setting up AMS table executors...
2025-01-09 19:33:30,638 INFO [main] [org.apache.amoro.server.DefaultOptimizingService] [] - OptimizerManagementService begin initializing
2025-01-09 19:33:30,641 INFO [main] [org.apache.amoro.server.DefaultOptimizingService] [] - SuspendingDetector for Optimizer has been started.
2025-01-09 19:33:30,641 INFO [main] [org.apache.amoro.server.DefaultOptimizingService] [] - OptimizerManagementService initializing has completed
2025-01-09 19:33:30,641 INFO [main] [org.apache.amoro.server.table.executor.DataExpiringExecutor] [] - Table executor DataExpiringExecutor initialized
2025-01-09 19:33:30,641 INFO [main] [org.apache.amoro.server.table.executor.SnapshotsExpiringExecutor] [] - Table executor SnapshotsExpiringExecutor initialized

Anything else

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

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

[ihadoop]

it seems not a bug. if you complie by you self , you should using dist package and then unpackage it.

[zhangwl9]

it seems not a bug. if you complie by you self , you should using dist package and then unpackage it.
I am using a tar package as shown in pat（amoro\dist\target \apache-amoro-0.8-SNAPSHOT-bin.tar.gz）and this is also under the dist directory. Are the packages under this path right, or do I need to add other jar or files to the tar package

[zhoujinsong]

Hi, it seems that the installation package is missing static resource jars. Did you perhaps not package all components completely, or did you enable the skip-dashboard-build profile?

Can you provide the package command to help us find the cause?