TASKCTL scheduler found after the server restart with no, afterwards just know because the service has not started, because TASKCTL after the installation is complete, the default is to start, so use so long time all don't know need to start the service, I find some information below is found in the boot method, my TASKCTL version is 4.1,
Service startup is divided into three large, EM node, Server nodes and the Agent (Agent) node,
EM node startup stop command is respectively: eminit and emshut
Start node and the node Agent Server, is divided into two steps:
(ctlinit) and start the initialization node (ctlstart)
Stop the service on the contrary the stop node (ctlstop) and remove the initialization information (ctlshut)
Among them when starting and em node after initialization, the start of the nodes can be on the client side admin,

CodePudding user response:

I solved the problem of

CodePudding user response:

Congratulations to you! It is good to solve!