-
Notifications
You must be signed in to change notification settings - Fork 76
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
Dispatchers container causing my kamailio pod to CrashLoopBackOff in on-premise k8s cluster #22
Comments
Just change the command path for 'dispatchers' daemon image in '02-kamailio.yaml' file to '/go/bin/dispatchers':
|
Thank you Sergei! You rock!! All pods are up and running! I am seeing a couple errors in the container logs, wondering if you have any more magic bullets you can softly lob my way?
The only difference from the commands and editing that I enumerated above was your suggested change in 02-kamailio.yaml, and applying 00-rbac.yaml before applying 01-nats.yaml. Appreciate your time,
|
Hi, Results: ``[root@local live-demo]# kubectl get all --namespace=voip NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE NAME READY UP-TO-DATE AVAILABLE AGE NAME DESIRED CURRENT READY AGE |
[root@local live-demo]# kubectl logs kamailio-2lqwb --namespace=voip kamailio |
[root@local live-demo]# kubectl describe pod kamailio --namespace=voip Normal Scheduled 10m default-scheduler Successfully assigned voip/kamailio-2lqwb to node2 |
Hi,
Thanks very much for your demo - it's been the only thing I've found that may address my SIP routing issues!
Though, I've been stuck on one problem for a week... I'm hoping someone could help me over this hurdle.
I'm running minikube on a Centos 7 VM.
Everything is Running with the exception of the kamailio pod, which is in CrashLoopBackOff.
Kubectl describe says the pod can't find /app:
exec: "/app": stat /app: no such file or directory: unknown
Any debug help would be much appreciated!
Thank you,
DRE
Commands and editing done:
Results:
The text was updated successfully, but these errors were encountered: