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

HAProxy cannot be started. #165

Open
wkaiser22 opened this issue Feb 12, 2025 · 3 comments
Open

HAProxy cannot be started. #165

wkaiser22 opened this issue Feb 12, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@wkaiser22
Copy link

Package version (if known): 0.5.3

Describe the bug

I was trying to install Invenio, but unfortunately, HAProxy cannot be started. Through my research, I found that in the haproxy template in the ConfigMap.yaml file under backend apps, the following line :

server web web:80 check fall 2 inter 5000 maxconn {{ .Values.haproxy.maxconn }}
and under backend static:
server web web:80 check fall 2 inter 5000 maxconn {{ .Values.haproxy.maxconn_static }}

Additionally, the following setting is missing:
{{ include "invenio.fullname" . }}-web

The server is no longer named web, but invenio-web. This is why HAProxy couldn't be started. Could you please adjust it

Steps to Reproduce

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

Screenshots (if applicable)

Image
Image
Image

Additional context

@wkaiser22 wkaiser22 added the bug Something isn't working label Feb 12, 2025
@lindhe
Copy link
Contributor

lindhe commented Feb 13, 2025

I'm not using HAProxy, so it's not so strange that I haven't ran into this issue. It's pretty uncommon for applications to come with their own proxy, usually that's provided by the Kubernetes platform (in form of an ingress controller, for example).

I would have to understand the use-case first, to determine if HAProxy should be included at all. Do you have a use-case in mind, or did you just run with the default values and ran into the error?

@wkaiser22
Copy link
Author

Yes, I ran it with the default values and encountered this issue

@lindhe
Copy link
Contributor

lindhe commented Feb 13, 2025

I see. Do you have an Ingress controller available in your environment? If so, I recommend running with haproxy.enabled=false.

I'll bring this up with other maintainers to see if we should keep haproxy or scrap it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants