Connection and configuration FAQ - Microservices Engine

This topic lists common SchedulerX connection issues and their solutions.

My workers show as unavailable

The no worker available error typically indicates a mismatch in your Endpoint, Namespace, or GroupId configuration.

To diagnose:

Open the SchedulerX log on the worker machine: /${user.home}/logs/schedulerx/worker.log
- Admin account: /home/admin/logs/schedulerx/worker.log
- Root account: /root/logs/schedulerx/worker.log
Search for WorkerConfig and verify that the Endpoint, Namespace, and GroupId values match the values in the SchedulerX console.

My application throws a DomainNotFoundException at startup

Caused by: com.alibaba.schedulerx.worker.exception.DomainNotFoundException: Not found domainName

The endpoint does not match the deployment environment.

Online workers: Use the endpoint for the region where your SchedulerX instance is deployed.
Local workers: Use only the Internet region endpoint.

For the complete list of supported endpoints, see Endpoints.

My application reports "can not find namespaceId" at startup

can not find namespaceId, key: d783212a9c-5a00-4d00-b8ca-b7a68824c97f
source:schedulerx domain=schedulerx-test.console.aliyun.com

Two common causes:

Wrong namespace ID -- The Namespace value contains a typo or references a different namespace.
Region mismatch -- The namespace was created in one region (for example, China (Hangzhou)), but the application connects through a different region (for example, Internet).

To verify, open the MSE SchedulerX console, go to the Applications page, and click Access Config to check the namespace, endpoint, and region values.

How do I test SchedulerX connections from a local machine?

Switch the region to Internet in the SchedulerX console, create an application in that region, and connect to it.

For detailed steps, see Connect to SchedulerX over the Internet from an on-premises environment.

My local SchedulerX proxy cannot reach the internet

If the machine has a direct internet connection but proxy mode fails, specify the endpoint explicitly. For a list of regions and their endpoints, see Endpoints.

DNS resolution fails in my self-managed IDC or office network over a leased line

After connecting through a leased line, configure forwarding management to forward DNS requests for internal Alibaba Cloud VPC domain names to your external DNS system. This allows your self-managed Internet Data Center (IDC) or office network to resolve those domain names correctly.