Open defyjoy opened 3 years ago
Does your Kubernetes cluster allow creating of unix domain sockets? Can you post a response form query to /api/status
?
Unrelated to your original question, but I am also trying to deploy on Kubernetes. Can you share your deployment.yaml? From the README, after initialization the Docker container stops — how did you start it up again? Kubernetes doesn't have anything like docker start
Yep I'm having the same issue saying the dispatcher is turned off. Helppppp ;( Can't seem to find anyone who has found a solution to this.
I have the same issue I prepare data in pvc osm-data-pvc2
apiVersion: apps/v1
kind: Deployment
metadata:
annotations:
meta.helm.sh/release-name: overpass-api-server
meta.helm.sh/release-namespace: osm
labels:
app.kubernetes.io/instance: overpass-api-server
app.kubernetes.io/name: overpass-api-server
name: overpass-api-server
namespace: osm
spec:
replicas: 1
selector:
matchLabels:
app.kubernetes.io/instance: overpass-api-server
app.kubernetes.io/name: overpass-api-server
template:
metadata:
labels:
app.kubernetes.io/instance: overpass-api-server
app.kubernetes.io/name: overpass-api-server
spec:
containers:
- name: overpass-api-server
image: wiktorn/overpass-api
imagePullPolicy: IfNotPresent
securityContext:
allowPrivilegeEscalation: true
runAsUser: 0
resources:
limits:
cpu: "4"
memory: "16Gi"
requests:
cpu: "4"
memory: "16Gi"
env:
- name: OVERPASS_META
value: "yes"
- name: OVERPASS_MODE
value: init
- name: OVERPASS_PLANET_URL
value: http://download.geofabrik.de/north-america/us-latest.osm.bz2
- name: OVERPASS_RULES_LOAD
value: "10"
volumeMounts:
- mountPath: "/db"
name: osm-datadb
volumes:
- name: osm-datadb
persistentVolumeClaim:
claimName: osm-data-pvc2
error
I successful deployed overpass-api in k8s cluster(aws eks). maybe overpass-api create unix domain sockets in /db/ dir. So s3 pvc is not work for overpass-api server I recomand to use efs pvc in aws eks cc @wiktorn
I was able to run the container for australia region and the docker container restarted after downloading entire db and the pod showed 1/1 on kubernetes . However when I check the logs and query for the api . I get strange error as -
Below are the logs from the pod
Can you please guide how and why is this happening and how to resolve this ?