Support Topics Documentation Slack YouTube Blog

Npm run debug errors out: Unable to register Runner

Backendless Version (3.x / 5.x, Online / Managed / Pro )

Online

Application ID

53CA60C1-87D8-49ED-9374-63A251B05366

Expected Behavior

Please describe the expected behavior of the issue, starting from the first action.

  1. npm run debug
  2. CodeRunner connects correctly.

Actual Behavior

Please provide a description of what actually happens, working from the same starting point.

  1. npm run debug
  2. I get this error:

Unable to register Runner. Backendless encountered an error while handling the request. An internal trouble ticket with ID 7678DF70-C76C-0E0D-FF07-8708B827B700 has been created and we will be investigating the issue.
Runner registration failed. Please copy Code Runner ID from console, press Attach and run CodeRunner with Code Runner ID
com.backendless.servercode.exceptions.ServerCodeException: Runner registration failed. Please copy Code Runner ID from console, press Attach and run CodeRunner with Code Runner ID
at controllers.ServerCodeModel.registerRunner(ServerCodeModel.java:113)
at router.Routes$$anonfun$routes$1.$anonfun$applyOrElse$1016(Routes.scala:13962)
at play.core.routing.HandlerInvokerFactory$$anon$6.resultCall(HandlerInvoker.scala:134)
at play.core.routing.HandlerInvokerFactory$$anon$6.resultCall(HandlerInvoker.scala:133)
at play.core.routing.HandlerInvokerFactory$JavaActionInvokerFactory$$anon$3$$anon$4$$anon$5.invocation(HandlerInvoker.scala:108)
at play.core.j.JavaAction$$anon$1.call(JavaAction.scala:88)
at play.http.DefaultActionCreator$1.call(DefaultActionCreator.java:31)
at com.backendless.old.security.ValidateApplication.call(ValidateApplication.java:57)
at com.backendless.old.security.ApplicationExistenceAndUseAction.call(ApplicationExistenceAndUseAction.java:38)
at com.backendless.old.security.ConsiderApiCallAction.call(ConsiderApiCallAction.java:29)
at com.backendless.TimeOutAction.call(TimeOutAction.java:26)
at com.backendless.SimultaneousApiCallLimitAction.call(SimultaneousApiCallLimitAction.java:25)
at com.backendless.StaticHttpResponseHeadersAction.call(StaticHttpResponseHeadersAction.java:18)
at com.backendless.StackOverflowHandlerAction.call(StackOverflowHandlerAction.java:19)
at com.backendless.CloseEntityManagerAction.call(CloseEntityManagerAction.java:36)
at com.backendless.CurrentRequestsNumberAction.call(CurrentRequestsNumberAction.java:30)
at play.core.j.JavaAction.$anonfun$apply$8(JavaAction.scala:138)
at scala.concurrent.Future$.$anonfun$apply$1(Future.scala:658)
at scala.util.Success.$anonfun$map$1(Try.scala:255)
at scala.util.Success.map(Try.scala:213)
at scala.concurrent.Future.$anonfun$map$1(Future.scala:292)
at scala.concurrent.impl.Promise.liftedTree1$1(Promise.scala:33)
at scala.concurrent.impl.Promise.$anonfun$transform$1(Promise.scala:33)
at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:64)
at play.core.j.HttpExecutionContext$$anon$2.run(HttpExecutionContext.scala:56)
at play.api.libs.streams.Execution$trampoline$.execute(Execution.scala:70)
at play.core.j.HttpExecutionContext.execute(HttpExecutionContext.scala:48)
at scala.concurrent.impl.CallbackRunnable.executeWithValue(Promise.scala:72)
at scala.concurrent.impl.Promise$KeptPromise$Kept.onComplete(Promise.scala:372)
at scala.concurrent.impl.Promise$KeptPromise$Kept.onComplete$(Promise.scala:371)
at scala.concurrent.impl.Promise$KeptPromise$Successful.onComplete(Promise.scala:379)
at scala.concurrent.impl.Promise.transform(Promise.scala:33)
at scala.concurrent.impl.Promise.transform$(Promise.scala:31)
at scala.concurrent.impl.Promise$KeptPromise$Successful.transform(Promise.scala:379)
at scala.concurrent.Future.map(Future.scala:292)
at scala.concurrent.Future.map$(Future.scala:292)
at scala.concurrent.impl.Promise$KeptPromise$Successful.map(Promise.scala:379)
at scala.concurrent.Future$.apply(Future.scala:658)
at play.core.j.JavaAction.apply(JavaAction.scala:138)
at play.api.mvc.Action.$anonfun$apply$2(Action.scala:96)
at scala.concurrent.Future.$anonfun$flatMap$1(Future.scala:307)
at scala.concurrent.impl.Promise.$anonfun$transformWith$1(Promise.scala:41)
at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:64)
at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:55)
at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:91)
at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:85)
at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:91)
at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:40)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: redis.clients.jedis.exceptions.JedisDataException: MASTERDOWN Link with MASTER is down and slave-serve-stale-data is set to ‘no’.
at redis.clients.jedis.Protocol.processError(Protocol.java:131)
at redis.clients.jedis.Protocol.process(Protocol.java:165)
at redis.clients.jedis.Protocol.read(Protocol.java:219)
at redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:309)
at redis.clients.jedis.Connection.getIntegerReply(Connection.java:260)
at redis.clients.jedis.Jedis.exists(Jedis.java:208)
at com.backendless.servercode.CodeRunnerDebugStatus.getConnectionStatusFromRedis(CodeRunnerDebugStatus.java:65)
at com.backendless.servercode.CodeRunnerDebugStatus.getConnectionStatusFromRedis(CodeRunnerDebugStatus.java:72)
at com.backendless.servercode.processManagement.RunnerRegistrationService.onRunnerConnected(RunnerRegistrationService.java:102)
at controllers.ServerCodeModel.registerRunner(ServerCodeModel.java:100)
… 51 more

Other Details

Deploying using the npm run deploy works great for this application. Only the debug command gives that error.

Debugging a couple of weeks ago worked correctly.

Sometimes it just hangs at this point
image

Hi Ricardo,

Thank you for the problem report. We will investigate and report back to you our findings.

Regards,
Mark

Thanks a lot Mark! I think you did something because it just started working.

image

Thank you for confirming, @rmaturi. Our devops team has fixed the problem.

Regards,
Mark