Connection issues

"No worker available" error

Symptom:

The application reports a no worker available error.

Possible cause:

A configuration error.

Solution:

1. Log on to the worker to view the SchedulerX logs. The log path is /${user.home}/logs/schedulerx/worker.log.

   • If the process is started by the admin account, the log path is /home/admin/logs/schedulerx/worker.log.

   • If the process is started by the root account, the log path is /root/logs/schedulerx/worker.log.

2. Search for the WorkerConfig keyword and verify that the endpoint, namespace, and GroupId parameters are correct.

Application deployment fails with DomainNotFoundException

Symptom:

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

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'schedulerxWorker' defined in class path resource [com/alibaba/schedulerx/SchedulerxAutoConfigure.class]: Invocation of init method failed
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1786)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:602)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:524)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:944)
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145)
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:754)
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:434)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:338)
	at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:144)
	...
Caused by: java.io.IOException: Schedulerx WorkerConfig[domainName=]
	at com.alibaba.schedulerx.worker.SchedulerxWorker.init(SchedulerxWorker.java:223)
	at com.alibaba.schedulerx.worker.SchedulerxWorker.afterPropertiesSet(SchedulerxWorker.java:831)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1845)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1782)
	... 16 common frames omitted
Caused by: com.alibaba.schedulerx.worker.exception.DomainNotFoundException: Not found domainName.
	at com.alibaba.schedulerx.worker.SchedulerxWorker.init(SchedulerxWorker.java:151)
	... 19 common frames omitted

Possible cause:

The endpoint does not match the deployment environment.

Solution:

Verify that the endpoint matches your production environment. For local testing, use the Internet endpoint. For supported endpoints, see Endpoints.

Application deployment fails with "can not find namespaceId" error

Symptom:

The application fails to start and reports the following error:

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

Possible causes:

• The namespace parameter is configured incorrectly.

• The region of the deployment machine does not match the region where the namespace was created.

  For example, the namespace is created in the China (Hangzhou) region, but the application connects to the Internet region.

Solution:

Log on to the MSE SchedulerX console. On the Application Management page, click Access Configuration and verify the information.

Local connection test for SchedulerX

In the SchedulerX console, switch the region to Internet, create an application, and connect it. For details, see Connect to the Internet from a local environment.

Local SchedulerX proxy cannot connect to the internet

If a direct connection to the Internet succeeds but the proxy mode connection fails, explicitly specify the endpoint. For deployment regions and their endpoints, see Endpoints.

DNS resolution failure in self-managed networks

After the leased line is connected, configure forwarding management. This routes DNS resolution requests for internal Alibaba Cloud VPC domain names to an external DNS system, enabling correct resolution from your self-managed IDC or office network.