Incorrect syslog port

Bug #1325870 reported by Stuart Bishop
6
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

Stuart Bishop (stub)
Changed in postgresql (Juju Charms Collection):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Stuart Bishop (stub)
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)
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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.