[Bug 1188435] [NEW] logger --udp does not work (sends AF_UNIX)

[Roy Smith]

Public bug reported:

Description:	Ubuntu 12.04.2 LTS
Release:	12.04

bsdutils:
  Installed: 1:2.20.1-1ubuntu3
  Candidate: 1:2.20.1-1ubuntu3
  Version table:
 *** 1:2.20.1-1ubuntu3 0
        500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

$ logger -n localhost --udp "this is my message"

What I expected to happen: my message would get sent to port 514 UDP.

What happened instead: nothing went to port 514, but it did get written
to /dev/log.

If I run:

$ tcpdump -i lo -s 0 -A port 514

while doing this, I get no output.  If I strace the logger process, I
can see it create a UDP socket, connect to the appropriate address and
port, then not send anything on that port.  I can also see it send to
/dev/log:

$ strace -e network logger -n localhost --udp "this is my message"
socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(514), sin_addr=inet_addr("127.0.0.1")}, 16) = 0
socket(PF_FILE, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 1
connect(1, {sa_family=AF_FILE, path="/dev/log"}, 110) = 0
sendto(1, "<13>Jun  7 01:06:49 logger: this"..., 46, MSG_NOSIGNAL, NULL, 0) = 46

** Affects: rsyslog (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1188435

Title:
  logger --udp does not work (sends AF_UNIX)

Status in “rsyslog” package in Ubuntu:
  New

Bug description:
  Description:	Ubuntu 12.04.2 LTS
  Release:	12.04

  bsdutils:
    Installed: 1:2.20.1-1ubuntu3
    Candidate: 1:2.20.1-1ubuntu3
    Version table:
   *** 1:2.20.1-1ubuntu3 0
          500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
          100 /var/lib/dpkg/status

  $ logger -n localhost --udp "this is my message"

  What I expected to happen: my message would get sent to port 514 UDP.

  What happened instead: nothing went to port 514, but it did get
  written to /dev/log.

  If I run:

  $ tcpdump -i lo -s 0 -A port 514

  while doing this, I get no output.  If I strace the logger process, I
  can see it create a UDP socket, connect to the appropriate address and
  port, then not send anything on that port.  I can also see it send to
  /dev/log:

  $ strace -e network logger -n localhost --udp "this is my message"
  socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
  socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
  socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
  connect(3, {sa_family=AF_INET, sin_port=htons(514), sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  socket(PF_FILE, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 1
  connect(1, {sa_family=AF_FILE, path="/dev/log"}, 110) = 0
  sendto(1, "<13>Jun  7 01:06:49 logger: this"..., 46, MSG_NOSIGNAL, NULL, 0) = 46

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1188435/+subscriptions