You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am facing a problem in which Orion is deployed on AKS (Azure Kubernetes Service) Cluster. For some reasons when the containers are restarted or redeployed on some other nodes due to autoscaling or AKS Automatic upgrade scheduling, the Orion API gives 502 Bad Gateway Error.
This resolves with helm upgrade orion fiware/orion . But do you know why Orion API gives 502 error when the containers are restarted? Since the containers were restarted, I could not find any useful logs.
Thank you
The text was updated successfully, but these errors were encountered:
Hi,
I'm not sure what happens, but if the container crashes, please create an issue in the fiware/orion. Container crashes do not belong to the chart. @sbanoeon To get the logs of crashed containers, I recommend to use a log-aggregator in your cluster. You will be able to see the logs of crashed containers with such.
Best
I am facing a problem in which Orion is deployed on AKS (Azure Kubernetes Service) Cluster. For some reasons when the containers are restarted or redeployed on some other nodes due to autoscaling or AKS Automatic upgrade scheduling, the Orion API gives 502 Bad Gateway Error.
This resolves with
helm upgrade orion fiware/orion
. But do you know why Orion API gives 502 error when the containers are restarted? Since the containers were restarted, I could not find any useful logs.Thank you
The text was updated successfully, but these errors were encountered: