Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

livenessProbe and readinessProbe cause errors in log #296

Open
horakmar opened this issue Apr 18, 2019 · 1 comment
Open

livenessProbe and readinessProbe cause errors in log #296

horakmar opened this issue Apr 18, 2019 · 1 comment
Assignees
Labels

Comments

@horakmar
Copy link

Kubernetes livenessProbe and readinessProbe cause that ubiquity container logs errors every readinessProbe period (default 5 secs). Probes are defined as default as:

readinessProbe:
  tcpSocket:
    port: 9999

Probes make these lines in ubiquity pod log:

2019/04/18 10:48:18 http: TLS handshake error from 172.28.112.162:48322: EOF
2019/04/18 10:48:23 http: TLS handshake error from 172.28.112.162:48334: EOF
2019/04/18 10:48:28 http: TLS handshake error from 172.28.112.162:48368: EOF
2019/04/18 10:48:33 http: TLS handshake error from 172.28.112.162:48380: EOF
2019/04/18 10:48:35 http: TLS handshake error from 172.28.112.162:48392: EOF
2019/04/18 10:48:38 http: TLS handshake error from 172.28.112.162:48414: EOF
...

Similarly probes cause errors in ubiquity-db pod log every 2 second:

LOG:  incomplete startup packet
LOG:  incomplete startup packet
LOG:  incomplete startup packet
LOG:  incomplete startup packet
LOG:  incomplete startup packet
@AnjanaAK
Copy link

@horakmar Any updates on this? I'm also experiencing the same issue.

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

No branches or pull requests

4 participants