org.eclipse.che.api.machine.server.exception.MachineException

Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web48

  • via GitHub by moifort
    , 1 year ago
    Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.
  • via GitHub by Blacktiger
    , 1 year ago
    Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.
  • Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.
  • Stack trace

    • org.eclipse.che.api.machine.server.exception.MachineException: Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout. at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:416)[che-core-api-machine-4.6.2.jar:4.6.2] at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:340)[che-core-api-machine-4.6.2.jar:4.6.2] at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:166)[che-core-api-machine-4.6.2.jar:4.6.2] at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:582)[che-core-api-workspace-4.6.2.jar:4.6.2] at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startQueue(WorkspaceRuntimes.java:458)[che-core-api-workspace-4.6.2.jar:4.6.2] at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:216)[che-core-api-workspace-4.6.2.jar:4.6.2] at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:533)[che-core-api-workspace-4.6.2.jar:4.6.2] at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28)[che-core-commons-lang-4.6.2.jar:4.6.2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[na:1.8.0_92-internal] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[na:1.8.0_92-internal] at java.lang.Thread.run(Thread.java:745)[na:1.8.0_92-internal] Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout. at org.eclipse.che.api.machine.server.wsagent.WsAgentLauncherImpl.startWsAgent(WsAgentLauncherImpl.java:107)[che-core-api-machine-4.6.2.jar:4.6.2] at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:386)[che-core-api-machine-4.6.2.jar:4.6.2] ... 10 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.