log forwarding subject to clock skew
Bug #1598292 reported by
Ian Booth
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned |
Bug Description
The log forward feature uses timestamp of stored log messages to determine which ones should be sent to the syslog server. This though makes the determination of which messages have not been sent affected by clock skew and some messages may not be forwarded.
tags: | added: 2.0 |
tags: | added: log-forwarding |
Changed in juju-core: | |
milestone: | 2.0-beta12 → 2.0-beta13 |
Changed in juju-core: | |
milestone: | 2.0-beta13 → 2.0-beta14 |
Changed in juju-core: | |
milestone: | 2.0-beta14 → 2.0-beta15 |
Changed in juju-core: | |
milestone: | 2.0-beta15 → 2.0.0 |
Changed in juju-core: | |
milestone: | 2.0.0 → 2.1.0 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.1.0 → none |
milestone: | none → 2.1.0 |
Changed in juju: | |
milestone: | 2.2-beta1 → 2.2-beta2 |
Changed in juju: | |
milestone: | 2.2-beta2 → 2.2-beta3 |
Changed in juju: | |
milestone: | 2.2-beta3 → 2.2-beta4 |
Changed in juju: | |
milestone: | 2.2-beta4 → 2.2-rc1 |
Changed in juju: | |
milestone: | 2.2-rc1 → 2.3.0 |
Changed in juju: | |
milestone: | 2.3.0 → 2.4-beta1 |
importance: | High → Medium |
Changed in juju: | |
milestone: | 2.4-beta1 → none |
To post a comment you must log in.
Fixing this is going to be a fairly major undertaking which is not going to get done for 2.1.