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

Not able to get the smtp-relay pod in ready state #174

Closed
tardich opened this issue Jan 9, 2024 · 5 comments
Closed

Not able to get the smtp-relay pod in ready state #174

tardich opened this issue Jan 9, 2024 · 5 comments

Comments

@tardich
Copy link

tardich commented Jan 9, 2024

Running the mail relay from the provided helm chart, I'm facing an issue which do not let the pod reach the ready state.

In the pod logs, everything seems normal, but describing the pod, I'm getting:

Readiness probe failed: command "sh -c [ ! -f /tmp/container_is_terminating ] && printf "EHLO healthcheck\nquit\n" | { while read l ; do sleep 1; echo $l; done } | nc -w 2 127.0.0.1 587 | grep -qE "^220.*ESMTP Postfix"" timed out

Any clue on where to look at?

Nice work, by the way!

@tardich
Copy link
Author

tardich commented Jan 9, 2024

In case you ask, I'm using mail-4.0.4, using default image from it

@tardich
Copy link
Author

tardich commented Jan 9, 2024

As I can see, the error is the script itself. Running it in a shell all by itself returns:

!: line 1: [: missing `]'

I haven't found out yet the issue with it....

@bokysan
Copy link
Owner

bokysan commented Jan 9, 2024

Yeah, this is all connected to #171 -- I'll need to fix the issue and test it out thorougly.

bokysan added a commit that referenced this issue Jan 9, 2024
Default timeout for healthcheck by kubernetes is too low. As we wait up
for 2 seconds for the Postfix and DKIM to respond, this exceeds the
threshold and the healthcheck fails with:

```
Readiness probe failed: command "sh -c /scripts/healthcheck.sh" timed out
```

By simply increasing `timeoutSeconds` this issue is resolved.
@bokysan
Copy link
Owner

bokysan commented Jan 9, 2024

I believe issue has been fixed. Can you please try edge image?

You'll also need to do helm ... --set readinessProbe.timeoutSeconds=8 to test this. This will be the default in release v4.1.0.

@tardich
Copy link
Author

tardich commented Jan 9, 2024

Yes, it now works! Great !

In fact, I was looking at putting single quotes around the script but it was still failing, because of the timeout being too small, I guess :-)

@bokysan bokysan closed this as completed Jan 11, 2024
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