App does not start on AKS (Azure Kubernetes Service) - Java subprocess takes too long to start

0
Hello,   I am deploying an app on AKS (Azure Kubernetes Service). The CI/CD deployment process runs without any error.   However the app is not started. In the application log, right after the normal message "Trying to start the MxRuntime...", something happens which prevents the app from starting. The error message is very vague. What exactly is done in the startup process here? What Java subprocess takes too long?  Is there any way to get more detailed log messages? Timeout: Java subprocess takes too long to start.   7/30/2024, 2:28:00.071 PM INFO: Executing export_industrial_edge_config_variable... 7/30/2024, 2:28:00.277 PM INFO: Mendix Cloud Foundry Buildpack v5.0.16 [e9a6e09] starting... 7/30/2024, 2:28:00.283 PM INFO: Fixing up permissions of directory 'model' with mode 700 7/30/2024, 2:28:00.284 PM INFO: Fixing up permissions of directory 'web' with mode 755 7/30/2024, 2:28:00.284 PM INFO: Fixing up permissions of directory 'data' with mode 700 7/30/2024, 2:28:00.286 PM INFO: Using external file store configured by user-defined settings. See https://github.com/mendix/cf-mendix-buildpack for file store configuration details. 7/30/2024, 2:28:00.286 PM INFO: JVM garbage collector is set to [Serial] 7/30/2024, 2:28:00.287 PM INFO: get_java_major_version : major_version - 11 7/30/2024, 2:28:00.287 PM INFO: checking is micrometer metrics enabled 7/30/2024, 2:28:00.287 PM INFO: checking is micrometer metrics enabled 7/30/2024, 2:28:00.563 PM INFO: checking is micrometer metrics enabled 7/30/2024, 2:28:00.564 PM INFO: MENDIX-LOGGING-HEARTBEAT: Heartbeat number 1 7/30/2024, 2:28:00.622 PM INFO: Using Java version: 7/30/2024, 2:28:00.622 PM INFO: openjdk version "11.0.24" 2024-07-16 LTS 7/30/2024, 2:28:00.622 PM INFO: OpenJDK Runtime Environment (Red_Hat-11.0.24.0.8-2) (build 11.0.24+8-LTS) 7/30/2024, 2:28:00.622 PM INFO: OpenJDK 64-Bit Server VM (Red_Hat-11.0.24.0.8-2) (build 11.0.24+8-LTS, mixed mode, sharing) 7/30/2024, 2:28:00.622 PM INFO: The buildpack is starting the runtime... 7/30/2024, 2:28:00.622 PM INFO: Trying to start the MxRuntime... 7/30/2024, 2:29:01.000 PM ERROR: Timeout: Java subprocess takes too long to start. 7/30/2024, 2:29:01.048 PM ERROR: Starting the JVM process did not succeed... 7/30/2024, 2:29:01.048 PM ERROR: Starting application failed: Cannot start the Mendix runtime. Most likely, the runtime is already active or still active 7/30/2024, 2:29:01.049 PM INFO: Waiting for the application to shutdown... 7/30/2024, 2:29:11.054 PM WARNING: The application did not shutdown by itself... Columns 1s 354ms   (Mendix version 8.18.29)   Kind regards, Elco Fransen
asked
1 answers
2

By the looks of the logs, you are using mendix-docker-buildpack. With Java process it means the main process that will run your app. The start up sequence is that JVM is first started with a basic "admin container". Then there's a sequence of commands issued to this container to load your app model, configure it with database, constants, and other tasks.

 

Since you are deploying to AKS, can you share the pod events and the deployment yaml spec? It's possible your resource limits are too low causing the JVM to not start at all.

 

answered