Hey community, we are running TypeSense 27.1 on Az...
# community-help
m
Hey community, we are running TypeSense 27.1 on Azure AKS and after a server node update the TypeSense server is in a crash-loop. terminate called after throwing an instance of 'std::invalid_argument' │ │ what(): stoi The node image was updated to "AKSUbuntu-2204gen2containerd-202411.03.0". Do you have any clue why TypeSense is not starting?
j
Could you provide the full stack trace?
m
That is the complete output of the TypeSense pod on our Kubernetes cluster.
BTW we found and fixed the problem. Within our kubernetes namespace we had a Kubernetes service called "typesense-api" this named caused that the TypeSense pod crashed. We have no clue how this is possible. Do you have any idea? Once we renamed the service to something else than typesense-api it worked again
j
No idea why that would happen 🤔