Stuck with Trying to start the MxRuntime

0
I am just trying to deploy any app using mendix on kubernetes. I thoroughly followed the steps mentioned here: https://docs.mendix.com/developerportal/deploy/run-mendix-on-kubernetes.  All pods are running and everything but accessing the app using the nodeIP:nodePort, doesn’t show anything. The logs of the pod show the below: INFO: Setting CF_INSTANCE_INDEX to 0 based on hostname mendix-k8s-stateful-0 INFO: Adding uid to /etc/passwd INFO: Mendix Cloud Foundry Buildpack v4.14.1 [0d7828a] starting... ERROR: Unable to fixup permissions of directory 'model' with mode 700: [Errno 1] Operation not permitted: '/opt/mendix/build/model', Ignoring. ERROR: Unable to fixup permissions of directory 'web' with mode 755: [Errno 1] Operation not permitted: '/opt/mendix/build/web', Ignoring. ERROR: Unable to fixup permissions of directory 'data' with mode 700: [Errno 1] Operation not permitted: '/opt/mendix/build/data', Ignoring. WARNING: External file store not configured, uploaded files in the app will not persist across restarts. See https://github.com/mendix/cf-mendix-buildpack for file store configuration details. INFO: Using Java version: INFO: java version "1.8.0_261" INFO: Java(TM) SE Runtime Environment (build 1.8.0_261-b12) INFO: Java HotSpot(TM) 64-Bit Server VM (build 25.261-b12, mixed mode) INFO: The buildpack is starting the runtime... INFO: Trying to start the MxRuntime… could you please help? P.S: I have hashed everything related to license ID and key for the moment, could that be related?
asked
1 answers
0

It ran successfully thank you very much, but I get this when I try to login:
INFO: Setting CF_INSTANCE_INDEX to 0 based on hostname mendix-k8s-stateful-0
INFO: Adding uid to /etc/passwd
INFO: Mendix Cloud Foundry Buildpack v4.14.1 [0d7828a] starting...
ERROR: Unable to fixup permissions of directory 'model' with mode 700: [Errno 1] Operation not permitted: '/opt/mendix/build/model', Ignoring.
ERROR: Unable to fixup permissions of directory 'web' with mode 755: [Errno 1] Operation not permitted: '/opt/mendix/build/web', Ignoring.
ERROR: Unable to fixup permissions of directory 'data' with mode 700: [Errno 1] Operation not permitted: '/opt/mendix/build/data', Ignoring.
WARNING: External file store not configured, uploaded files in the app will not persist across restarts. See https://github.com/mendix/cf-mendix-buildpack for file store configuration details.
INFO: Using Java version:
INFO: java version "1.8.0_261"
INFO: Java(TM) SE Runtime Environment (build 1.8.0_261-b12)
INFO: Java HotSpot(TM) 64-Bit Server VM (build 25.261-b12, mixed mode)
INFO: The buildpack is starting the runtime...
INFO: Trying to start the MxRuntime...
INFO - Logging: Logging to file: /opt/mendix/build/log/out.log, max size: 1099511627776KiB, max rotation: 10
INFO - Core: Mendix Runtime 7.16.0 (build 36935). Copyright © 2003-2018 Mendix bv. All rights reserved.
INFO - M2EE: Setting MaxFormContentSize for Runtime Server to 10485760
INFO - Services: Adding 0 authority certificate(s)
INFO - ConnectionBus: Starting uniqueness constraint violation diagnostics...
INFO - ConnectionBus: Uniqueness constraint violation diagnostics has been successfully finished. No violations are found.
INFO - Core: Storage service: Local file system storage, uploaded files path: /opt/mendix/build/data/files
INFO - ConnectionBus: Database: PostgreSQL 11.13 (Debian 11.13-1.pgdg90+1), name: 'jdbc:postgresql://10.116.20.77:5432/db0?tcpKeepAlive=true'
Driver: PostgreSQL JDBC Driver 42.1.4
Oct 20, 2021 1:57:49 PM java.util.prefs.FileSystemPreferences$6 run
WARNING: Prefs file removed in background /opt/mendix/build/.java/.userPrefs/com/mendix/core/prefs.xml
WARNING - Core: The runtime has been started using a trial license, the framework will be terminated when the maximum time is exceeded!
INFO - Core: Mendix Runtime successfully started, the application is now available.
INFO: The MxRuntime is fully started now.
INFO: Ensuring admin user credentials
INFO: Model version: 1.0.0.2
INFO: MENDIX-INTERNAL: Metrics are disabled.
INFO: MENDIX-LOGGING-HEARTBEAT: Heartbeat number 1
INFO - WebUI: New login request from [Source-IP: 127.0.0.1, User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36]
INFO - WebUI: Login FAILED: unknown user 'admin'.
INFO - WebUI: New login request from [Source-IP: 127.0.0.1, User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36]
INFO - WebUI: Login FAILED: unknown user 'admin'.
INFO - WebUI: New login request from [Source-IP: 127.0.0.1, User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36]
INFO - WebUI: Login FAILED: unknown user 'admin'.

 

I declared the password in kubernetes secret file as mentioned in:  https://docs.mendix.com/developerportal/deploy/run-mendix-on-kubernetes. 

but no one mentioned anything about a username? and apparently admin is not it, any ideas?

answered