System syslog configuration

Started by Nagav, July 20, 2015, 11:42:00 AM

Previous topic - Next topic

Nagav

As far as I understood

Setting
EnableSyslogDaemon - to 1;
SyslogListenPort - port for syslog server to listen on (default is 514)
SyslogRetentionTime - (default is 90).

and restarting netxms server/agent should allow the netXMS console user to see syslog message in menu -> syslog
is my understanding correct ? but I do not see any message ? why it is so, I hope syslog parser configuration is not required to see all message in menu -> syslog


In netxmsd.conf file I have set
LogFile = /apps/uspsqa1/ntxms/netxms/log/netxmsd.log
I could see logs being written in netxmsd.log file
Is it not possible to see logs being written in netxmsd.log file in menu -> syslog screen ?


In netxmsd.conf file I tried to set
LogFile = {syslog}
and restarted server, I do not see any syslog message being created anywhere under netXMS folder
Where syslog will be written ? what configuration is required to write netxmsd message into syslog file ?

I read that syslog will be written in var folder, but I could not see it being created.

uspsqa1@mkeux805n-z1-76-SWITCH>> ls -ltra
total 12
drwxr-xr-x   4 uspsqa1  uspsqa1        4 Jan 14  2014 .
drwxr-xr-x   2 uspsqa1  uspsqa1        3 Jan 14  2014 netxms
drwxr-xr-x   9 uspsqa1  uspsqa1        9 May 26 03:24 ..
drwxr-xr-x   2 uspsqa1  uspsqa1        3 Jul 20 02:43 run
/apps/uspsqa1/ntxms/netxms/var

tomaskir

I think you are confusing a few things here.

1) application logs (nxagentd or netxmsd) are NOT syslog
2) You can read up on syslog here http://www.networkmanagementsoftware.com/what-is-syslog

Application logs (nxagentd or netxmsd) are written as configured in the (nxagentd or netxmsd) conf files.
Syslog messages can be sent from any of your devices to NetXMS syslog server.

You can of course direct the application logs to be sent over syslog as well (using the {syslog} setting), but correct syslog deamon configuration on your Linux box is needed.

On Windows, {syslog} means to use the Windows System Log - which is not syslog at all.