cloudfoundry / cloudfoundry/loggregator-agent-release

Windows Cells not sending logs to syslog drain when posted via https.

Open
#39 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

scheduled
Dominant language
Go
Stars
14
Forks
34
Avg merge
7h 6m
Merged PRs (30d)
2

Description

Since we upgraded from cf-deployment 12.45.0 up to 13.7.0 and up to present 13.10.0, our windows application and cell logs are not arriving at the syslog drains which use https post.

The loggr-syslog-agent-windows logs contain the following suspicious error:
2020/09/08 15:50:21 failed to write to syslogdain.cloud.pcftest.com, retrying in 15s, err: x509: certificate signed by unknown authority. syslogdain.cloud.pcftest.com does in fact have a valid cert signed by Digicert.

I can work around this by setting drain_skip_cert_verify, but that doesn't seem optimal or desired.

Here is how I reproduce the issue:

  1. Deploy an application which can accept posts like https://github.com/pusherofbrooms/syslogdrain (change manifest if you actually use this)
  2. setup the service with cf cups syslogdrain -l "https://MYLOGURL"
  3. setup a windows application like the one found at git@github.com:cloudfoundry-incubator/NET-sample-app.git and bind it to the syslog drain
  4. restart the windows application
  5. observe that no CELL or APP/PROC/WEB logs are sent to the drain application
  6. observe the above err: x509 cert error in the loggr-syslog-agent-windows logs

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the loggr-syslog-agent-windows logs and the HTTPS syslog-drain path described in the reproduction steps. Reproduce with an HTTPS drain and a Windows application, then investigate why the valid DigiCert certificate is reported as unknown; done means CELL and APP/PROC/WEB logs arrive without disabling certificate verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
observability-sre
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.