The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
Jobagent not connecting properly to server
I'm experimenting a bit with user agents on different machines / operating systems to allow for better scaling, but I get an issue trying to do so.
My server instance is running on a Ubuntu server, my agent on a windows 10 machine. While the server notices the agent is running (orange light) the agent itself keeps spawning the following error statement :
2019-06-16 16:57:00.380 ERROR 6020 --- [taskScheduler-3] c.r.e.jobagent.scheduled.SyncTasks : Sync cannot be completed. Cause: Failed to check whether sync service is enabled. HTTP response code was: 401
Anything specific I would need to allow on my server / agent host to get it running?
My server instance is running on a Ubuntu server, my agent on a windows 10 machine. While the server notices the agent is running (orange light) the agent itself keeps spawning the following error statement :
2019-06-16 16:57:00.380 ERROR 6020 --- [taskScheduler-3] c.r.e.jobagent.scheduled.SyncTasks : Sync cannot be completed. Cause: Failed to check whether sync service is enabled. HTTP response code was: 401
Anything specific I would need to allow on my server / agent host to get it running?
0
Best Answer
-
aschaferdiek Employee-RapidMiner, Member Posts: 76 RM EngineeringHi kayman,this behavior is caused by a clock difference on both machines. The agent's clock is probably not the same as the clock on the machine where RapidMiner Server is running. The agent will create a Json Web Token (JWT) to access RapidMiner Server and if the clocks are not synchronized the JWT which has been created in the agent to access RapidMiner Server is invalid because basically the time comparison fails.There are two possible solutions to the problem1. Synchronize the clocks so they are exactly the same on both machines2. Use today's released 9.3.1 version of RapidMiner Server which has introduced a clock offset tolerance mechanismTo see the entire changelog of the new version of RapidMiner Server, please visit https://docs.rapidminer.com/latest/server/releases/changes-9.3.1.htmlI hope this helps.6
Answers