Re: syslog setup

On 21/6/24 22:19, Paul Coviello wrote:

Chris Townley wrote:

On 19/06/2024 13:08, Simon Clubley wrote:

On 2024-06-18, Paul Coviello <pcoviello@gmail.com> wrote:

Lawrence D'Oliveiro wrote:

On Wed, 12 Jun 2024 16:47:11 -0400, Paul Coviello wrote:
>

I do have a call with VSI tomorrow, though I'm not sure what yet will
come out of it.

>
How did it go?
>

well...  I was asked if I would like professional services in helping to
set this up, since we need to have this for some auditing purpose, I
said yes, but I asked them to check to see if anyone knew how before
they sent over a quote, I thought it was a fair question :-)

>
:-)
>
And did they confirm someone at VSI knows how to set it up ? :-)
>
Simon.
>

>
and perhaps they should document it!
>

no confirmation yet, and absolutely agree there should be something telling you how to set it up instead of leading you to believe just by adding in the opcom section it works... it doesn't there is some other setting I don't know.

Silly question, but can you describe what you're expecting to happen that doesn't?
I built this from the source included in the zip file and there are certainly a few quirks with it, but I don't know if the same are present in the prebuilt executables in the zip.
I suggest running the executable with debug like so after setting default to where ever you have it:
$ mcr []syslogd -d
This will produce a number of messages, the first of interest to me was "Can't open SYSLOGD_CONFIG", note not TCPIP$SYSLOGD_CONFIG as the PDF tells you to define.  So you may need to define a logical SYSLOGD_CONFIG to where you have the config file (or change the source code to include the TCPIP$ prefix and rebuild).
Note the example defines the logical as SYS$LOGIN:SYSLOGD_CONFIG.CFG, which is useless unless you are logged in as TCPIP$SYSLOG, per the PDF.
Define it to point at the actual directory.
This is what a proper startup looks like (apologies for line wrap):
$ define tcpip$syslogd_config sys$sysroot:[tcpip$syslog]syslogd.cfg
$ mcr []syslogd -d
Binding to SYSLOG           on port 514
init
cfline(*.err            /sys$login:err.log)
Opening Log file sys$login:err.log
cfline(*.debug          /sys$login:debug.log)
Opening Log file sys$login:debug.log
cfline(local0.*,user.*  /sys$login:local.log)
Opening Log file sys$login:local.log
cfline(*.err    XXXXX)
cfline(*.*              @node.domain.name)
cfline(local1.err       %CENTRAL)
OPCOM Class CENTRAL decoded as 1
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X FILE: sys$login:err.log
7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 X FILE: sys$login:debug.log
X 8 X X X X X X X X X X X X X X 8 X X X X X X X X FILE: sys$login:local.log
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X USERS: XXXXX,
8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 X FORW: node.domain.name
X X X X X X X X X X X X X X X X X 3 X X X X X X X CONSOLE: 1
logmsg: pri 56, flags 4, from node, msg syslogd: restart
Priority skip fac:5, 3 < 6
Logging to FILE sys$login:debug.log
Priority skip fac:5, 16 < 6
Priority skip fac:5, 3 < 6
Logging to FORW node.domain.name
Priority skip fac:5, 16 < 6
syslogd: restarted
Selecting 3
Once you have that out of the way, everything seems to work.  You can test it with the logger command as described in the PDF.  Note you can specify priorities with the logger command, which is sadly not documented in the PDF, but which any man page will happily tell you about.
$ logger -p local1.err "test central"
$
Message from syslogd@node at Jun 22 07:44:31 ...
test central
$
%%%%%%%%%%%  OPCOM  22-JUN-2024 07:44:31.11  %%%%%%%%%%%
Message from user XXXXX on NODE
Message from syslogd@node at Jun 22 07:44:31 ...
test central
HTH
Jim
--
eight-cubed.com