Not accepting syslog messages

Bug #1323627 reported by Stuart Bishop on 2014-05-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rsyslog (Juju Charms Collection)
Undecided
Unassigned
rsyslog-forwarder (Juju Charms Collection)
High
Jorge Niedbalski

Bug Description

With the local provider, I am unable to send syslog messages to the rsyslog service:

juju deploy ubuntu
juju deploy rsyslog
juju deploy rsyslog-forwarder
juju add-relation ubuntu rsyslog-forwarder
juju add-relation rsyslog-forwarder:syslog rsyslog:aggregator

The rsyslog unit is happily logging local syslog messages:

juju run --unit rsyslog/0 'logger -p local0.error This is a local message'
juju run --unit rsyslog/0 'sudo tail -1 /var/log/syslog'

However, sending messages from the remote unit does nothing:

juju run --unit ubuntu/0 'logger -p local0.error This is a remote message'
juju run --unit rsyslog/0 'sudo tail -1 /var/log/syslog'

Related branches

Stuart Bishop (stub) wrote :

I also get this behavior on Canonistack.

Stuart Bishop (stub) wrote :

There are several problems with the rsyslog and rsyslog-forwarder charms:

- The rsyslog-forwarder is attempting to send to rsyslog via TCP to port 10514
- The rsyslog aggregator is listening for UDP messages on port 514
- TCP would be nice, but rsyslogd is crashing when a TCP listener is configured (precise LXC container). This is possibly why it was removed from the last commit to the rsyslog charm.

For now, I think rsyslog is fine and the forwarder needs to be updated to talk UDP to port 514.

Changed in rsyslog (Juju Charms Collection):
status: New → Invalid
Changed in rsyslog-forwarder (Juju Charms Collection):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Jorge Niedbalski (niedbalski)
Jorge Niedbalski (niedbalski) wrote :

OK, i fixed this by forwarding all the forwarder rsyslog messages to UDP port 514.

Changed in rsyslog-forwarder (Juju Charms Collection):
status: In Progress → Fix Committed
Jorge Niedbalski (niedbalski) wrote :

environment: local
machines:
  "0":
    agent-state: started
    agent-version: 1.19.1.1
    dns-name: localhost
    instance-id: localhost
    series: trusty
    state-server-member-status: has-vote
  "1":
    agent-state: started
    agent-version: 1.19.1.1
    dns-name: 10.0.3.15
    instance-id: niedbalski-local-machine-1
    series: precise
    hardware: arch=amd64
  "2":
    agent-state: started
    agent-version: 1.19.1.1
    dns-name: 10.0.3.32
    instance-id: niedbalski-local-machine-2
    series: precise
    hardware: arch=amd64
services:
  mysql:
    charm: cs:precise/mysql-45
    exposed: false
    relations:
      cluster:
      - mysql
      juju-info:
      - rsyslog-forwarder
    units:
      mysql/0:
        agent-state: started
        agent-version: 1.19.1.1
        machine: "1"
        public-address: 10.0.3.15
        subordinates:
          rsyslog-forwarder/0:
            upgrading-from: local:precise/rsyslog-forwarder-10
            agent-state: started
            agent-version: 1.19.1.1
            public-address: 10.0.3.15
  rsyslog:
    charm: cs:precise/rsyslog-3
    exposed: false
    relations:
      aggregator:
      - rsyslog-forwarder
    units:
      rsyslog/0:
        agent-state: started
        agent-version: 1.19.1.1
        machine: "2"
        open-ports:
        - 514/tcp
        - 514/udp
        public-address: 10.0.3.32
  rsyslog-forwarder:
    charm: local:precise/rsyslog-forwarder-10
    exposed: false
    relations:
      juju-info:
      - mysql
      syslog:
      - rsyslog
    subordinate-to:
    - mysql

Then i sent a message using logger on mysql/0

logger -p local0.error Testing message

Received message on rsyslog/0:

Jun 3 11:11:51 niedbalski-local-machine-1 ubuntu: Testing message

Changed in rsyslog-forwarder (Juju Charms Collection):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers