Incorrect syslog port
Bug #1325870 reported by
Stuart Bishop
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pgbadger (Juju Charms Collection) |
Fix Released
|
Critical
|
Stuart Bishop | ||
| postgresql (Juju Charms Collection) |
Fix Released
|
High
|
Stuart Bishop | ||
Bug Description
The PostgreSQL charm originally copied the rsyslog-forwarder charm for the syslog interface. This seems to be incorrect, with the rsyslog aggregator now just listening on port 514.
Switch the PostgreSQL charm and pgbadger charm to use UDP and port 514 and match the current syslog interface.
Related branches
lp:~stub/charms/precise/postgresql/bug-1325870-syslog-port
- Jorge Niedbalski (community): Needs Information
- charmers: Pending requested
-
Diff: 28 lines (+4/-4) 2 files modifiedapitemplates/rsyslog_forward.conf (+1/-1)
test.py (+3/-3)
lp:~stub/charms/precise/pgbadger/devel
- Marco Ceppi (community): Approve
-
Diff: 43 lines (+6/-6) 2 files modifiedapifiles/05-juju-pgbadger-rsyslog.conf (+2/-3)
tests/10-basic (+4/-3)
Changed in postgresql (Juju Charms Collection):
status:
New → In Progress
importance:
Undecided → High
assignee:
nobody → Stuart Bishop (stub)
no longer affects:
pgbadger (Ubuntu)
Changed in pgbadger (Juju Charms Collection):
status:
New → In Progress
importance:
Undecided → Critical
assignee:
nobody → Stuart Bishop (stub)
Changed in pgbadger (Juju Charms Collection):
status:
In Progress → Fix Released
Changed in postgresql (Juju Charms Collection):
status:
In Progress → Fix Released
To post a comment you must log in.