SUMMARY: binlogd logging to remote hosts

From: Tim Mooney <mooney_at_dogbert.cc.ndsu.NoDak.edu>
Date: Wed, 19 Mar 1997 13:10:55 -0600 (CST)

All-

I never actually asked this question on the list (but I was close), but I
thought I would summarize the problem and the solution to hopefully save
others some time and trouble.

After setting up DecEvent 2.2 on some of our hosts last week, I decided that
it might be nice to configure `binlogd' to log binary "events" to both a file
and a central host that was also running DecEvent.

I proceeded to modify /etc/binlog.conf as documented in the binlogd(8) man
page, adding a line like:

*.* _at_some.other.host

Unfortunately, it didn't work (no events showed up in the
/var/adm/binary.errlog on the remote host). After some debugging I managed
to discover the problem.

Basically, there is a minor error in the /etc/services file that's shipped
with all versions of Digital Unix that I currently have access to. When
binlogd starts up, it tries to look up the service:

        binlog/udp

but /etc/services only contains an entry for

        binlogd/udp

If you modify /etc/services to add the alias `binlog' on the binlogd line
and restart binlogd, the problem is fixed. This needs to be done on both
the client and server hosts.

I discovered the problem using the `-d' option to binlogd, in conjunction with
`logger -b'.

Hope this helps someone,

Tim
-- 
Tim Mooney                              mooney_at_dogbert.cc.ndsu.NoDak.edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J1, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
Received on Wed Mar 19 1997 - 20:33:22 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:36 NZDT