Ai Hub Process Execution Currently Not Available Error
star2021
New Altair Community Member
Hi everyone! I encounter problems whereby I can login into my rapidminer ai hub account. But, there are errors where the process execution currently not available, page could not load and I cannot execute my process on rapidminer hub. Everything was fine during installation day but after I shutdown my computer and I want to continue my work on the next day, these problems always happen.
All pages in my ai hub home look like this:
I've checked my logs file but cannot understand much. I think the error said that job service is offline but I don't know how to solve it. I hope anyone can help me please as I need to complete my task as soon as possible. Thank you
I attached here the log file.
All pages in my ai hub home look like this:
I've checked my logs file but cannot understand much. I think the error said that job service is offline but I don't know how to solve it. I hope anyone can help me please as I need to complete my task as soon as possible. Thank you
I attached here the log file.
Tagged:
0
Best Answer
-
Thanks for the info. To give it a fast try, you could try out 8.0.22 or below?
1
Answers
-
Someone please help this question.0
-
Hi. We're on it to reproduce. Thanks for your input.Two questions upfront:- Which MySQL JConnector have you used @star2021 ?- Have you tried using a different MySQL JConnector?
0 -
Hi aschaferdiek , thank you for your reply,
1. I used mysql-connector-java-8.0.24.
2. I have not try using any different mysql jconnector yet. Should I try different version of mysql jconnector?
0 -
Thanks for the info. To give it a fast try, you could try out 8.0.22 or below?
1 -
Hi ascaferdiek!
Thanks a lot for your help. I try mysql-connector-java-5.1.47 and it works.
I shutdown my laptop after installation. Then, the error did not show up anymore after I turn on my laptop back. Now, I can run process on rapidminer ai hub again.
Thank you for your help! I really appreciate it a lot!1 -
We could reproduce the problem. The root cause is related to an internal software we use to manage database migration which has a bug with any MySQL JDBC connector greater than 8.0.22.Please use 8.0.22 for now as MySQL JDBC connector where we could not reproduce the problem. We'll update our documentation for pointing that out in our current release cycle.Thanks again for reporting @star2021 !0
-
Ohhh that's why I got those error before this.
You're welcome aschaferdiek! I'm glad you help me.0