Closed Triple5soul89ny closed 4 years ago
Hi,
the problem seems to be that the assist-server cannot check the Elasticsearch database mappings and thus will fail to start. Without a running assist-server the teach and chat server will not be able to validate the cluster and will refuse to start as well.
Can you see another error description before the "TRACE" part begins? It might give some more info about whats going on.
Another thing is that the Elasticsearch database usually does not like to run in admin mode, in Linux it will even refuse to start at all with "sudo". Can you try the run-script in a non-admin console?
Thanks for you quick answer. Now I found my mistake. I have to start the elasticserver with admin rights, and than the run-sepia without admin rights. Now it works like first setup
strange this shouldn't be the case ... but glad it works now :smile:
Hello Florian,
sorry for disturbing again, but I have a little problem. First I installed SEPIA on my Windows 2016 Server. Everything went really well and easy. Than I had to restart the machine. After restart I opend "cmd" with admin, switched to the SEPIA directory and run-sepia. Check of Elasticserver Fail, than Elasticserver started automaticly. After that I only get FAIL
than I checked the Logs and get these errors:
sepia-assist-server:
2020-02-18 19:18:54 ERROR - TRACE: net.b07z.sepia.server.assist.server.Setup.testAndUpdateElasticsearchMapping(Setup.java:359) 2020-02-18 19:18:54 ERROR - TRACE: net.b07z.sepia.server.assist.server.Config.testDatabases(Config.java:356) 2020-02-18 19:18:54 ERROR - TRACE: net.b07z.sepia.server.assist.server.Start.main(Start.java:366)
sepia-teach-server:
2020-02-18 19:18:59 ERROR - Could not reach AssistAPI at http://localhost:20721/ Exception in thread "main" java.lang.RuntimeException: Core-tools are NOT set properly! AssistAPI could not be reached! at net.b07z.sepia.server.teach.server.Start.main(Start.java:128)
Could you please tell me what do I do wrong?