Issue with Docker Startup

I am trying to follow the instructions in https://docs.appian.com/suite/help/20.2/Installing_Appian_in_Docker_Containers.html and when i go to startup after installing the license, I get stuck in the waiting for services to start loop:

c:\appian-docker>docker-compose up
Creating network "appian-docker_default" with the default driver
Creating rdbms         ... done
Creating base  ... done
Creating search-server   ... done
Creating service-manager ... done
Creating data-server     ... done
Creating web-application ... done
Attaching to base, rdbms, search-server, service-manager, web-application, data-server
base               | No command specified, exiting
data-server        | Waiting for these containers to start: service-manager
data-server        | Currently waiting for service-manager
rdbms              | 2020-07-31T02:04:57.244600Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
rdbms              | 2020-07-31T02:04:57.253776Z 0 [Note] mysqld (mysqld 5.7.21) starting as process 1 ...
rdbms              | 2020-07-31T02:04:57.263177Z 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
rdbms              | 2020-07-31T02:04:57.266031Z 0 [Note] InnoDB: PUNCH HOLE support available
rdbms              | 2020-07-31T02:04:57.266079Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
rdbms              | 2020-07-31T02:04:57.266086Z 0 [Note] InnoDB: Uses event mutexes
rdbms              | 2020-07-31T02:04:57.266091Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
rdbms              | 2020-07-31T02:04:57.266096Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
rdbms              | 2020-07-31T02:04:57.266100Z 0 [Note] InnoDB: Using Linux native AIO
rdbms              | 2020-07-31T02:04:57.266470Z 0 [Note] InnoDB: Number of pools: 1
rdbms              | 2020-07-31T02:04:57.266603Z 0 [Note] InnoDB: Using CPU crc32 instructions
rdbms              | 2020-07-31T02:04:57.269403Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
rdbms              | 2020-07-31T02:04:57.282438Z 0 [Note] InnoDB: Completed initialization of buffer pool
rdbms              | 2020-07-31T02:04:57.285481Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
rdbms              | 2020-07-31T02:04:57.325097Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
rdbms              | 2020-07-31T02:04:57.553665Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
rdbms              | 2020-07-31T02:04:57.559393Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
rdbms              | 2020-07-31T02:04:57.790942Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
rdbms              | 2020-07-31T02:04:57.803321Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
rdbms              | 2020-07-31T02:04:57.803379Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
rdbms              | 2020-07-31T02:04:57.805154Z 0 [Note] InnoDB: 5.7.21 started; log sequence number 12320425
rdbms              | 2020-07-31T02:04:57.806550Z 0 [Note] Plugin 'FEDERATED' is disabled.
rdbms              | 2020-07-31T02:04:57.811193Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
rdbms              | 2020-07-31T02:04:57.917936Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
rdbms              | 2020-07-31T02:04:57.946489Z 0 [Warning] CA certificate ca.pem is self signed.
rdbms              | 2020-07-31T02:04:57.949611Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
rdbms              | 2020-07-31T02:04:57.949688Z 0 [Note] IPv6 is available.
rdbms              | 2020-07-31T02:04:57.949706Z 0 [Note]   - '::' resolves to '::';
rdbms              | 2020-07-31T02:04:57.949729Z 0 [Note] Server socket created on IP: '::'.
rdbms              | 2020-07-31T02:04:57.978643Z 0 [Note] InnoDB: Buffer pool(s) load completed at 200731  2:04:57
rdbms              | 2020-07-31T02:04:58.055148Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
rdbms              | 2020-07-31T02:04:58.055199Z 0 [Warning] 'user' entry 'mysql.session@localhost' ignored in --skip-name-resolve mode.
rdbms              | 2020-07-31T02:04:58.055213Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
rdbms              | 2020-07-31T02:04:58.055237Z 0 [Warning] 'user' entry 'appian@localhost' ignored in --skip-name-resolve mode.
rdbms              | 2020-07-31T02:04:58.060184Z 0 [Warning] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.
rdbms              | 2020-07-31T02:04:58.060211Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
rdbms              | 2020-07-31T02:04:58.061054Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
rdbms              | 2020-07-31T02:04:58.382243Z 0 [Warning] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.
rdbms              | 2020-07-31T02:04:58.389684Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
rdbms              | 2020-07-31T02:04:59.554193Z 0 [Note] Event Scheduler: Loaded 0 events
rdbms              | 2020-07-31T02:04:59.558044Z 0 [Note] mysqld: ready for connections.
rdbms              | Version: '5.7.21'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
search-server      | No containers to wait for, starting now
search-server      | Executing start command: /usr/local/appian/ae/search-server/bin/start.sh
search-server      | SS_JAVA_OPTS: -Xms1024m -Xmx1024m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Duser.timezone=GMT
search-server      | Attempt 1/6: Waiting 5 seconds for Appian Search Server to start ...
service-manager    | Unable to find build.info
web-application    | Waiting for these containers to start: search-server service-manager
web-application    | Currently waiting for search-server
base exited with code 0
search-server      | Appian Search Server process has been started.
search-server      | Advertising as ready on 9355
search-server      | Logfiles: /usr/local/appian/ae/logs/search-server/search-server.log
search-server      | [2020-07-31T02:04:07,464][INFO ][org.elasticsearch.plugins.PluginsService] [%node_name] loaded plugin [org.elasticsearch.index.reindex.ReindexPlugin]
search-server      | [2020-07-31T02:04:07,465][INFO ][org.elasticsearch.plugins.PluginsService] [%node_name] loaded plugin [org.elasticsearch.painless.PainlessPlugin]
search-server      | [2020-07-31T02:04:07,465][INFO ][org.elasticsearch.plugins.PluginsService] [%node_name] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
search-server      | [2020-07-31T02:04:14,641][DEBUG][org.elasticsearch.action.ActionModule] [%node_name] Using REST wrapper from plugin com.appian.es.auth.BasicAuthPlugin
search-server      | [2020-07-31T02:04:17,159][INFO ][com.appian.es.bootstrap.NodeInit] [%node_name] Successful initialization of Elasticsearch node on [search-server:9301].
search-server      | [2020-07-31T02:04:17,181][INFO ][com.appian.es.logging.HealthStatusLoggingListener] [%node_name] Cluster health changed for [cluster name=appian-search-cluster]. Status changed from [none] to [RED]. Current cluster information: [status=RED], [timed out=false], [nodes=1], [data nodes=1], [active primary shards=0], [active shards=0], [relocating shards=0], [initializing shards=0], [unassigned shards=0]
search-server      | [2020-07-31T02:04:17,199][INFO ][com.appian.es.logging.HealthStatusLoggingListener] [%node_name] Cluster health changed for [cluster name=appian-search-cluster]. Status changed from [RED] to [GREEN]. Current cluster information: [status=GREEN], [timed out=false], [nodes=1], [data nodes=1], [active primary shards=0], [active shards=0], [relocating shards=0], [initializing shards=0], [unassigned shards=0]
search-server      | [2020-07-31T02:05:01,939][INFO ][com.appian.es.bootstrap.NodeInit] [%node_name] The following settings will be used to start the ElasticSearch node:
search-server      | {"action.auto_create_index":"false","cluster.name":"appian-search-cluster","cluster.routing.allocation.disk.watermark.flood_stage":"500mb","cluster.routing.allocation.disk.watermark.high":"500mb","cluster.routing.allocation.disk.watermark.low":"500mb","indices.fielddata.cache.size":"15%","path.data":"/usr/local/appian/ae/search-server/data","path.home":"/usr/local/appian/ae/search-server","path.logs":"/usr/local/appian/ae/logs/search-server","thread_pool.write.queue_size":"500","transport.type":"netty4"}
search-server      | [2020-07-31T02:05:01,963][INFO ][com.appian.es.bootstrap.NodeInit] [%node_name] Attempting initialization of Elasticsearch node on [search-server:9301].
service-manager    | Password successfully changed!
service-manager    | No containers to wait for, starting now
service-manager    | Executing start command: /usr/local/appian/ae/passwordWrapper.sh start.sh -s all
search-server      | [2020-07-31T02:05:03,006][INFO ][org.elasticsearch.plugins.PluginsService] [%node_name] no modules loaded
search-server      | [2020-07-31T02:05:03,013][INFO ][org.elasticsearch.plugins.PluginsService] [%node_name] loaded plugin [http-basic-auth]
search-server      | [2020-07-31T02:05:03,014][INFO ][org.elasticsearch.plugins.PluginsService] [%node_name] loaded plugin [org.elasticsearch.analysis.common.CommonAnalysisPlugin]
search-server      | [2020-07-31T02:05:03,014][INFO ][org.elasticsearch.plugins.PluginsService] [%node_name] loaded plugin [org.elasticsearch.index.reindex.ReindexPlugin]
search-server      | [2020-07-31T02:05:03,015][INFO ][org.elasticsearch.plugins.PluginsService] [%node_name] loaded plugin [org.elasticsearch.painless.PainlessPlugin]
search-server      | [2020-07-31T02:05:03,015][INFO ][org.elasticsearch.plugins.PluginsService] [%node_name] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
web-application    | search-server is up!
web-application    | Currently waiting for service-manager
service-manager    | Unable to find build.info
service-manager    | Starting Distributed Transaction Log
service-manager    | Executing command: '[/usr/local/appian/ae/services/zookeeper-3.5.6/bin/zkServer.sh, start, /usr/local/appian/ae/services/conf/zookeeper.properties]' in /usr/local/appian/ae/services/zookeeper-3.5.6/bin with environment [JVMFLAGS:-Xms128m -Xmx256m -Duser.timezone=GMT, ZOO_LOG_DIR:/usr/local/appian/ae/logs/service-manager/zookeeper, ZOO_LOG4J_PROP:INFO,CONSOLE,ROLLINGFILE]
service-manager    | Starting QuorumPeerMain...
search-server      | [2020-07-31T02:05:10,153][DEBUG][org.elasticsearch.action.ActionModule] [%node_name] Using REST wrapper from plugin com.appian.es.auth.BasicAuthPlugin
service-manager    | process QuorumPeerMain running
service-manager    | Zookeeper connected, root child count of [1]
service-manager    | QuorumPeerMain started in 2680 ms
service-manager    | Service Zookeeper successfully started
search-server      | [2020-07-31T02:05:12,385][INFO ][org.elasticsearch.monitor.jvm.JvmGcMonitorService] [%node_name] [gc][1] overhead, spent [417ms] collecting in the last [1s]
search-server      | [2020-07-31T02:05:12,793][INFO ][com.appian.es.bootstrap.NodeInit] [%node_name] Successful initialization of Elasticsearch node on [search-server:9301].
search-server      | [2020-07-31T02:05:12,828][INFO ][com.appian.es.logging.HealthStatusLoggingListener] [%node_name] Cluster health changed for [cluster name=appian-search-cluster]. Status changed from [none] to [RED]. Current cluster information: [status=RED], [timed out=false], [nodes=1], [data nodes=1], [active primary shards=0], [active shards=0], [relocating shards=0], [initializing shards=0], [unassigned shards=0]
search-server      | [2020-07-31T02:05:12,931][INFO ][com.appian.es.logging.HealthStatusLoggingListener] [%node_name] Cluster health changed for [cluster name=appian-search-cluster]. Status changed from [RED] to [GREEN]. Current cluster information: [status=GREEN], [timed out=false], [nodes=1], [data nodes=1], [active primary shards=0], [active shards=0], [relocating shards=0], [initializing shards=0], [unassigned shards=0]
service-manager    | Using emulated InjectSessionExpiration
service-manager    | Starting
service-manager    | Default schema
service-manager    | State change: CONNECTED
service-manager    | New config event received: {}
service-manager    | New config event received: {}
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.analytics00-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.analytics00-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.analytics01-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.analytics01-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.analytics02-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.analytics02-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.channels-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.channels-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.content-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.content-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.download-stats-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.download-stats-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.execution00-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.execution00-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.execution01-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.execution01-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.execution02-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.execution02-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.forums-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.forums-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.groups-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.groups-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.notifications-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.notifications-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.notifications-email-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.notifications-email-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.portal-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.portal-0/00000000000000000000.log
service-manager    | Walking /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.process-design-0 to recover Kafka cluster state
service-manager    | Recovering data from /usr/local/appian/ae/services/data/kafka-logs/serviceManager.transaction.process-design-0/00000000000000000000.log
service-manager    | Waiting for all configured Kafka nodes to report Kafka state.
service-manager    | Finished reporting Kafka state for all configured Kafka nodes.
service-manager    | Initializing partition assignments
service-manager    | backgroundOperationsLoop exiting
service-manager    | local Kafka broker is not registered in Zookeeper
service-manager    | Executing command: '[/usr/local/appian/ae/services/kafka_2.12-2.2.0-appian-1/bin/kafka-server-start.sh, /usr/local/appian/ae/services/conf/kafka-server.properties, --override, log.dirs=/usr/local/appian/ae/services/data/kafka-logs, --override, min.insync.replicas=1, --override, listeners=PLAINTEXT://engines:9092, --override, zookeeper.connect=engines:2181, --override, advertised.listeners=PLAINTEXT://engines:9092, --override, broker.id=0, --override, zookeeper.connection.timeout.ms=40000, --override, zookeeper.session.timeout.ms=40000, --override, offsets.topic.replication.factor=1]' in /usr/local/appian/ae/services/kafka_2.12-2.2.0-appian-1/bin with environment [KAFKA_HEAP_OPTS:-Xms512m -Xmx1024m, KAFKA_OPTS:-Duser.timezone=GMT, KAFKA_JMX_OPTS: , LOG_DIR:/usr/local/appian/ae/logs/service-manager/kafka, CLASSPATH:, KAFKA_LOG4J_OPTS:-Dlog4j.configuration=file:///usr/local/appian/ae/services/conf/kafka-log4j.properties]
service-manager    | Starting Kafka...
service-manager    | process Kafka running
service-manager    | local Kafka broker is not registered in Zookeeper
service-manager    | Waiting for local Kafka broker to be registered with Zookeeper
service-manager    | local Kafka broker is not registered in Zookeeper
service-manager    | Waiting for local Kafka broker to be registered with Zookeeper
service-manager    | local Kafka broker is not registered in Zookeeper
service-manager    | Waiting for local Kafka broker to be registered with Zookeeper
service-manager    | local Kafka broker 0 : (EndPoint(engines,9092,ListenerName(PLAINTEXT),PLAINTEXT)) : null registered in Zookeeper
service-manager    | Local Kafka broker is registered with Zookeeper...checking topics
service-manager    | Waiting for the following topics listed in Zookeeper to become available: List(serviceManager.transaction.notifications, serviceManager.transaction.download-stats, serviceManager.transaction.groups, serviceManager.transaction.forums, serviceManager.transaction.notifications-email, serviceManager.transaction.execution01, serviceManager.transaction.execution00, serviceManager.transaction.portal, serviceManager.transaction.channels, serviceManager.transaction.execution02, serviceManager.transaction.content, serviceManager.transaction.process-design, serviceManager.transaction.analytics02, serviceManager.transaction.analytics00, serviceManager.transaction.analytics01)
service-manager    | Waiting for topic serviceManager.transaction.forums to be available
service-manager    | Topic serviceManager.transaction.forums available.
service-manager    | Waiting for topic serviceManager.transaction.notifications to be available
service-manager    | Topic serviceManager.transaction.notifications available.
service-manager    | Waiting for topic serviceManager.transaction.notifications-email to be available
service-manager    | Topic serviceManager.transaction.notifications-email available.
service-manager    | Waiting for topic serviceManager.transaction.channels to be available
service-manager    | Topic serviceManager.transaction.channels available.
service-manager    | Waiting for topic serviceManager.transaction.content to be available
service-manager    | Topic serviceManager.transaction.content available.
service-manager    | Waiting for topic serviceManager.transaction.download-stats to be available
service-manager    | Topic serviceManager.transaction.download-stats available.
service-manager    | Waiting for topic serviceManager.transaction.groups to be available
service-manager    | Topic serviceManager.transaction.groups available.
service-manager    | Waiting for topic serviceManager.transaction.portal to be available
service-manager    | Topic serviceManager.transaction.portal available.
service-manager    | Waiting for topic serviceManager.transaction.process-design to be available
service-manager    | Topic serviceManager.transaction.process-design available.
service-manager    | Waiting for topic serviceManager.transaction.analytics00 to be available
service-manager    | Topic serviceManager.transaction.analytics00 available.
service-manager    | Waiting for topic serviceManager.transaction.analytics01 to be available
service-manager    | Topic serviceManager.transaction.analytics01 available.
service-manager    | Waiting for topic serviceManager.transaction.analytics02 to be available
service-manager    | Topic serviceManager.transaction.analytics02 available.
service-manager    | Waiting for topic serviceManager.transaction.execution00 to be available
service-manager    | Topic serviceManager.transaction.execution00 available.
service-manager    | Waiting for topic serviceManager.transaction.execution01 to be available
service-manager    | Topic serviceManager.transaction.execution01 available.
service-manager    | Waiting for topic serviceManager.transaction.execution02 to be available
service-manager    | Topic serviceManager.transaction.execution02 available.
service-manager    | __consumer_offsets has not been created yet, this may be caused by no consumers being initialized yet
service-manager    | All topics accessible...local Kafka broker engines:9092 successfully launched
service-manager    | Kafka started in 6921 ms
service-manager    | Service Kafka successfully started
service-manager    | Distributed Transaction Log Started
service-manager    | Starting Service Manager
service-manager    | Executing command: '[/usr/local/appian/ae/services/lib/scripts/service-manager.sh]' in /usr/local/appian/ae/services/lib/scripts with environment [JAVA_OPTS:-XX:ErrorFile=/usr/local/appian/ae/logs/service-manager/service_manager_error_pid%p.log -XX:MaxDirectMemorySize=8g -Xms64m -Xmx8g -XX:+CrashOnOutOfMemoryError ]
service-manager    | Waiting for Service Manager to launch
service-manager    | Service Manager started in 5767 ms
service-manager    | Starting forums
service-manager    | forums: Start initiated
service-manager    | Starting notifications
service-manager    | notifications: Start initiated
service-manager    | Starting notifications-email
service-manager    | notifications-email: Start initiated
service-manager    | Starting channels
service-manager    | channels: Start initiated
service-manager    | Starting content
service-manager    | content: Start initiated
service-manager    | Starting download-stats
service-manager    | download-stats: Start initiated
service-manager    | Starting groups
service-manager    | groups: Start initiated
service-manager    | Starting portal
service-manager    | portal: Start initiated
service-manager    | Starting process-design
service-manager    | process-design: Start initiated
service-manager    | Starting analytics00
service-manager    | analytics00: Start initiated
service-manager    | Starting analytics01
service-manager    | analytics01: Start initiated
service-manager    | Starting analytics02
service-manager    | analytics02: Start initiated
service-manager    | Starting execution00
service-manager    | execution00: Start initiated
service-manager    | Starting execution01
service-manager    | execution01: Start initiated
service-manager    | Starting execution02
service-manager    | execution02: Start initiated
service-manager    |
service-manager    | Waiting for services to start...
service-manager    |   analytics00 in STARTING state, REPLICA mode
service-manager    |   analytics01 in STARTING state, REPLICA mode
service-manager    |   analytics02 in STARTING state, REPLICA mode
service-manager    |   channels in STARTING state, REPLICA mode
service-manager    |   content in STARTING state, REPLICA mode
service-manager    |   download-stats in STARTING state, REPLICA mode
service-manager    |   execution00 in STARTING state, REPLICA mode
service-manager    |   execution01 in STARTING state, REPLICA mode
service-manager    |   execution02 in STARTING state, REPLICA mode
service-manager    |   forums in STARTING state, REPLICA mode
service-manager    |   groups in STARTING state, REPLICA mode
service-manager    |   notifications in STARTING state, REPLICA mode
service-manager    |   notifications-email in STARTING state, REPLICA mode
service-manager    |   portal in STARTING state, REPLICA mode
service-manager    |   process-design in STARTING state, REPLICA mode
service-manager    |
service-manager    | Waiting for services to start...
service-manager    |   analytics00 in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   analytics01 in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   analytics02 in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   channels in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   content in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   download-stats in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   execution00 in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   execution01 in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   execution02 in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   forums in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   groups in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   notifications in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   notifications-email in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   portal in CRASHLOOPBACKOFF state, REPLICA mode
service-manager    |   process-design in CRASHLOOPBACKOFF state, REPLICA mode

  Discussion posts and replies are publicly visible

Parents Reply
  • OK issue was using a win license when I have a linux VM.  Got that resolved, but now there is an issue starting the rmdbs container.

    web-application    | 2020-08-05 19:03:49 WARNING [wait-for-component] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference
    web-application    |    com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Access denied for user 'appian'@'%' to database 'AppianPrimaryDS'

    Any ideas?

Children