haproxy / keepalived logs needed
Bug #1231584 reported by
Chris Ricker
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cisco Openstack |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
haproxy and keepalived need logging configured and enabled during install to facilitate troubleshooting of HA installations
This likely requires adoption of appropriate puppet modules to manage syslog configurations
| Changed in openstack-cisco: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| Changed in openstack-cisco: | |
| milestone: | none → h.1 |
Revision history for this message
| Chris Ricker (chris-ricker) wrote | #1 |
| Changed in openstack-cisco: | |
| milestone: | h.1 → h.2 |
| Changed in openstack-cisco: | |
| milestone: | h.2 → h.3 |
| Changed in openstack-cisco: | |
| milestone: | h.3 → i.0 |
| Changed in openstack-cisco: | |
| milestone: | i.0 → i.1 |
| Changed in openstack-cisco: | |
| milestone: | i.1 → none |
To post a comment you must log in.
haproxy logging notes
- haproxy only logs over the network due to its early chroot
- need to turn up remote syslogging on the server we target to receive
- need to set a facility and priority in haproxy.conf
- need to add a selection filter for that facility:priority in rsyslog conf on the log-receiving server
- need to add a logrotate for that new log file