-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication exception and Role "syncope" does not exist #89
Comments
Hi @lijin850591109, can you describe the kubernetes cluster you use to deploy SiteWhere? How many nodes? What resources each node has? From the exception you provided Instance Management is failing to authenticate, but this can be due to some other part of the system not being healthy or unavailable. |
As Jorge mentioned, the exception is probably due to a problem with Instance Management microservice startup. If you can provide the complete logs, we'll take a look. We've also seen an occasional issue with Istio where the microservices are running with no errors, but the connection between the REST API gateway and Instance Management takes a long time to become available. This has shown up on Docker for Windows and can be fixed by restarting the Docker engine. Also, which log has the |
my cluster has two nodes, Mem 96G CPU 24 Hard Disk 1T for each node password authentication failed for user "syncope" log is in sitewhere-postgresql container
the sitewhere-web-rest complete logs:
|
Can you also attach the logs for the |
Instance Management log:
|
The SiteWhere user management service is not able to interact with the Syncope REST services (basically getting a 404). It appears that the host is running (since no connection exception), but the REST services are not there. Does this happen even if you shut down the instance with |
yes, It happens every time when I restart the instance |
Is there a web ui,what is the url? or only can login from the administrative application ? Thanks! |
Hi @lijin850591109, there is a Admin UI you can download and install. |
@lijin850591109 We only support access via the admin application, though the system does expose REST services that allow other applications to use SiteWhere without the admin application. There is no embedded web app with the equivalent admin functionality though. |
Describe the bug
A clear and concise description of what the bug is.
On a fresh deployment, cannot access Administration dashboard because of failed login with default credentials: admin/password
Provide Information
Output of
helm version
:Output of
kubectl version
:Output of
helm ls sitewhere
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
None
SiteWhere App Version:
2.0.0
SiteWhere Chart Version:
Latest sitewhere from https://sitewhere.io/helm-charts
To Reproduce
https://github.com/sitewhere/sitewhere-k8s
https://sitewhere.io/docs/2.0.0/deployment/#monitor-sitewhere-services
Expected behavior
Authenticate successfully and see the dashboard
Additional context
The text was updated successfully, but these errors were encountered: