Skip to content
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

Geoerver not getting UP while deploying as StatefulSet in Kubernetes #111

Closed
saingithub opened this issue Jul 26, 2022 · 6 comments
Closed

Comments

@saingithub
Copy link

I was trying to deploy geoserver as a StatefulSet in Kubernetes. When we mount the data directory geoserver is not getting up.

I was getting the error in the logs as waiting for the geoserver to be up and running.

I was able to deploy without mounting the directory and there is no persistance for the data in that case.

Could you please guide as in deploying as a StatefulSet

@saingithub
Copy link
Author

I had given /var/geoserver/datadir as the mountpath

@randomorder
Copy link
Member

Hi @saingithub

From what you say it doesn't look like a problem with the docker image itself, maybe with the statefulset or persistent volume and claim definitions in kubernetes...

Check the permissions on the directory to make sure it writable by the user that is running tomcat (and geoserver) in the container

There is also an HELM Chart readily available for the deployment of a geoserver cluster or to inspect and see how we have defined volumes and mounts for the data directory here

@saingithub
Copy link
Author

When we give /var/geoserver/ or /var/geoserver/datadir as the mount path. The geoserver is not getting Up.

Do you have a Statefulset yaml file

@randomorder
Copy link
Member

it's templated in the Helm chart here. Hope it helps

@saingithub
Copy link
Author

We have deployed using the helm chart you have shared. The pod is Up and running , but there is no persistance for the data .

I created a test workspace and restarted the pod. The workspace got deleted when the pod got up.

All the volume claims are still there.

@randomorder
Copy link
Member

Sorry for the late reply. In case you are still facing this problem please create an issue in the Chart implementation repository. This repo is for the docker image itself. Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants