Barbican log not parsed correctly
Bug #1891343 reported by
Doug Szumski
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
Medium
|
Unassigned | ||
Train |
In Progress
|
Medium
|
Unassigned | ||
Ussuri |
In Progress
|
Medium
|
Unassigned | ||
Victoria |
In Progress
|
Medium
|
Unassigned | ||
Wallaby |
Fix Released
|
Medium
|
Unassigned |
Bug Description
On Train, Centos 8 I see in the Fluentd logs many entries like:
```
2020-08-12 16:52:47 +0200 [warn]: #0 got incomplete line before first line from /var/log/
es/252MB} {rss usage: 103350272 bytes/98MB} [pid: 32|app: 0|req: 3610/6099] 10.0.0.32 () {30 vars in 706 bytes} [Wed Aug 12 16:52:47 2020] GET /v1/secrets/f5a
ce1ac-7423-
```
To post a comment you must log in.
And we don't get anything from loadwsgi.py.log, which is where most of the useful barbican API logs end up.