Technical article 107650

Forwarding /dev/error output to another system via syslogd silently fails, syslogd core dumps.

OpenServer 5.0.0OpenServer 5.0.2

Written · Last revised

Problem

I have added the entry:
*.debug    @remotehost

to /etc/syslog.conf on the local host where 'remotehost' is the host name of the system to which error messages should be forwarded. However, the forwarding does not occur and I cannot find any error message.

Solution

Every line in the /etc/syslog.conf file that starts with a '#' sign is a comment and will be ignored by syslogd.

Similarly, every blank line in /etc/syslog.conf will be ignored by syslogd.

Any other line must have the following format:

selector   action

So in the example above, *.debug is in the selector field and @remotehost is in the action field.

The entries in the selector field MUST be separated from the
entries in the action field by one or more Tabs.  If, instead
of tab(s), you put in one or more spaces entered with the space
bar, the line will not have the appropriate format and syslogd
will fail to perform the action.
If you use SCOTerm Edit-Paste to transfer your /etc/syslog.conf
file from one system to another, SCOTerm will convert the tab(s)
to blank spaces.  Make sure you convert these blank spaces back
to one or more tabs.

Next, check that syslogd is running. Then signal it to reread syslog.conf:

# kill -1 `cat /etc/syslog.pid`
Enter the command:
# nohup tail -f /usr/adm/messages | /usr/bin/logger &
Every entry that /etc/logger writes to /usr/adm/messages will now
also be logged in /usr/adm/syslog on the remote host.  This is in
addition to the usual debugging information from daemons, such
as /etc/ftpd (note that /etc/logger and /usr/bin/logger are two
distinct commands).

See also

error(M) logger(TC) syslog(SLIB) syslogd(ADMN)

From the Xinuos technical article database, record 107650. Reproduced with permission. The original is at www.sco.com/ta/107650, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.