We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Webhook 2.8.0 on alpine linux, I am seeing this in the logs:
time="2023-01-19T22:55:57Z" level=info msg="[webhook] 2023/01/19 22:55:57 [327c11] incoming HTTP GET request from 10.191.146.98:48272" job=webhook pid=19 time="2023-01-19T22:55:57Z" level=info msg="[webhook] 2023/01/19 22:55:57 [327c11] health got matched" job=webhook pid=19 time="2023-01-19T22:55:57Z" level=info msg="[webhook] 2023/01/19 22:55:57 [327c11] error parsing body payload due to unsupported content type header: " job=webhook pid=19 time="2023-01-19T22:55:57Z" level=info msg="[webhook] 2023/01/19 22:55:57 [327c11] health hook triggered successfully" job=webhook pid=19 time="2023-01-19T22:55:57Z" level=info msg="[webhook] 2023/01/19 22:55:57 [327c11] executing /app/webhook-linux-amd64/hooks/health.sh (/app/webhook-linux-amd64/hooks/health.sh) with arguments ["/app/webhook-linux-amd64/hooks/health.sh"] and environment [] using as cwd" job=webhook pid=19 time="2023-01-19T22:55:57Z" level=info msg="[webhook] 2023/01/19 22:55:57 [327c11] command output: cat: /tmp/curl-response: No such file or directory" job=webhook pid=19 time="2023-01-19T22:55:57Z" level=info msg="http error: 000" job=webhook pid=19 time="2023-01-19T22:55:57Z" level=info msg=" reason: " job=webhook pid=19 time="2023-01-19T22:55:57Z" level=info msg=" " job=webhook pid=19 time="2023-01-19T22:55:57Z" level=info job=webhook pid=19 time="2023-01-19T22:55:57Z" level=info msg="[webhook] 2023/01/19 22:55:57 [327c11] error occurred: exit status 1" job=webhook pid=19 time="2023-01-19T22:55:57Z" level=info msg="[webhook] 2023/01/19 22:55:57 [327c11] finished handling health" job=webhook pid=19 time="2023-01-19T22:55:57Z" level=info msg="[webhook] 2023/01/19 22:55:57 [327c11] 500 | 91 B | 12.190129ms | 10.191.145.179:40202 | GET /health" job=webhook pid=19
Observing logs on server running in docker container on flatcar-linux (like coreos) 2905.2.5
time="2023-01-20T06:52:04Z" level=info msg="[webhook] 2023/01/20 06:52:04 [fb01d1] health got matched" job=webhook pid=17 time="2023-01-20T06:52:04Z" level=info msg="[webhook] 2023/01/20 06:52:04 [fb01d1] health hook triggered successfully" job=webhook pid=17 time="2023-01-20T06:52:04Z" level=info msg="[webhook] 2023/01/20 06:52:04 [fb01d1] executing /app/webhook-linux-amd64/hooks/health.sh (/app/webhook-linux-amd64/hooks/health.sh) with arguments ["/app/webhook-linux-amd64/hooks/health.sh"] and environment [] using as cwd" job=webhook pid=17 time="2023-01-20T06:52:04Z" level=info msg="[webhook] 2023/01/20 06:52:04 [fb01d1] finished handling health" job=webhook pid=17 time="2023-01-20T06:52:04Z" level=info msg="[webhook] 2023/01/20 06:52:04 [fb01d1] 200 | 4 B | 27.804287ms | 10.195.84.172:40202 | GET /health" job=webhook pid=17
Any clues on what is happening here?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Webhook 2.8.0 on alpine linux, I am seeing this in the logs:
Observing logs on server running in docker container on flatcar-linux (like coreos) 2905.2.5
Any clues on what is happening here?
The text was updated successfully, but these errors were encountered: