config-changed: fails when global_maxconns is not set
Bug #1231768 reported by
Dave Cheney
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| haproxy (Juju Charms Collection) |
Fix Released
|
High
|
Jorge Niedbalski | ||
Bug Description
What the hell ...
config.yaml
global_maxconn:
default: 4096
type: int
description: |
Sets the maximum per-process number of concurrent connections to
<number>.
p1/0:config-changed % config-get --format json global_maxconn
""
Revision history for this message
| Dave Cheney (dave-cheney) wrote | #1 |
| tags: | added: openstack |
Revision history for this message
| Jorge Niedbalski (niedbalski) wrote | #2 |
| Changed in haproxy (Juju Charms Collection): | |
| assignee: | nobody → Jorge Niedbalski (niedbalski) |
| status: | Triaged → Fix Released |
To post a comment you must log in.
Possibly fixed by https:/