MonitorWare Knowledge Base

Seems the facility/priority do not map like the old sysklod did. Is there a doc to explain this?

Thanks

• Custom written rsyslog.conf?
• Maintenance Contract?
• Installation support?

They should be the same - can you explain where you see the troubles. Eventually a bug...

Rainer

well, hopefully it isnt sysklogd-sql changing things.. But I had a table set like so:

`facility` enum('auth','authpriv','cron','daemon','kern','lpr','mail','mark','news','security','syslog','user','uucp','local0','local1','local2','local3','local4','local5','local6','local7') collate latin1_general_ci NOT NULL default 'syslog',
`priority` enum('debug','info','notice','warning','warn','err','error','crit','alert','emerg','panic') collate latin1_general_ci NOT NULL default 'notice',

And its mapping user stuff under auth.. Just all over.. I dont really know if your wrong, or sysklogd-sql.. But if you contend your right, I just need some sort of mapping thing so I can set my table up right..

I am not sure about the MySQL enum. What does it expect in the insert statement- a string of this name or a numerical value? Please be advised that rsyslogd uses numerical values and decodes them with the same calls than sysklogd does. The codes can be found in rfc 3164 (http://www.ietf.org/rfc/rfc3164.txt) in section 4.1.1.

Rainer

It would appear sysklog-sql. (which is a modified version of sysklod to log to mysql) seems to have mucked up the numbers..

Thanks for this link this is what I was looking for.

Glad I could help!

Rainer