SchedulerX:Connection issues

"no worker available" error

Issue description:

You receive a "no worker available" error.

Cause:

This error typically indicates a configuration issue.

Solution:

1. Log on to the worker and check SchedulerX logs at /${user.home}/logs/schedulerx/worker.log.

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

   • If you started the process as root, the log path is /root/logs/schedulerx/worker.log.

2. Search for WorkerConfig and verify the endpoint, namespace, and group ID are correct.

DomainNotFoundException error during application deployment

Issue description:

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

org.springframework.beans.factory.BeanCreationException Create breakpoint : Error creating bean with name 'schedulerxWorker' defined in class path resource [com/alibaba/schedulerx/SchedulerxAutoConfigure.class]: Invocation of init
	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)
	at org.zendure.core.launch.BladeApplication.run(BladeApplication.java:49)
	at org.zendure.Application.main(Application.java:46)
Caused by: java.io.IOException Create breakpoint : 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 Create breakpoint : Not found domainName.
	at com.alibaba.schedulerx.worker.SchedulerxWorker.init(SchedulerxWorker.java:151)
	... 19 common frames omitted

Cause:

The endpoint does not match the deployment environment.

Solution:

Verify that your application uses the correct endpoint for its deployment environment. Local machines can only connect to Internet endpoints. For supported values, see Endpoints.

cannot find namespaceId error during application deployment

Issue description:

The application throws this error on startup:

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

Cause:

• The namespace parameter in the access configuration may be incorrect.

• The application region differs from the namespace region.

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

Solution:

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

Test local connections

In the SchedulerX console, switch the region to Internet, then create and connect an application. Access the Internet environment from a local machine.

Internet appears under Others in the top navigation bar region selector.

Troubleshoot proxy connections

If you can connect directly but not through a proxy, verify that the endpoint matches your deployment region. For details, see Endpoints.

DNS resolution failure over a direct connect

After establishing a direct connect, configure forwarding management to forward DNS requests for VPC internal domain names to an external DNS system so that your IDC or office network can resolve them correctly.