NSLU2-Linux
view · edit · print · history

HowTo.InstallAndConfigureSyslog-ng History

Hide minor edits - Show changes to markup

January 14, 2007, at 07:28 PM by fcarolo -- Warning about outdated info
Added lines 1-4:

Better instructions about running syslog-ng under Unslug and other Optware platforms is available at the syslog-ng for Optware page. There you can also find links to the original documentation for syslog_ng.

Warning:: the rest of this page is about an older version of the syslog-ng package. The errors in the original config file are corrected in the current version. It is strongly recommended that you use the current Optware package for syslog-ng instead of this older version.

Changed lines 6-7 from:
to:
Changed lines 66-67 from:

Farhan Yousaf

to:

Farhan Yousaf

December 25, 2006, at 03:35 AM by Farhan Yousaf --
Changed lines 56-59 from:

If you'd like to capture log messages via a remote device (udp/514), add this to your /opt/etc/syslog-ng/syslog-ng.conf:

  log { source(net); destination(pix); };
to:

If you'd like to capture log messages via a remote device, e.g. a Cisco PIX 501 (udp/514), add these lines to your /opt/etc/syslog-ng/syslog-ng.conf:

  destination net_all { file("/opt/var/log/net_all.log"); };
  log { source(net); destination(net_all); };
December 25, 2006, at 03:32 AM by Farhan Yousaf --
Changed lines 52-60 from:

Jerome

to:

Jerome


If you'd like to capture log messages via a remote device (udp/514), add this to your /opt/etc/syslog-ng/syslog-ng.conf:

  log { source(net); destination(pix); };

Farhan Yousaf

May 31, 2006, at 03:51 AM by Jerome --
Changed lines 44-52 from:

to:

Just add in the configuration file those two lines: destination console { file("/opt/var/log/console"); }; destination console_all { file("/opt/var/log/console_all"); };

They will redirect the console messages to those 2 files and you will be sure to get them.

Jerome

August 25, 2005, at 08:42 AM by Niko_K --
Changed line 44 from:

---

to:

August 25, 2005, at 08:42 AM by Niko_K --
Changed lines 40-44 from:

Same problem here...

to:

Same problem here...

Niko_K

---

August 25, 2005, at 08:41 AM by Niko_K --
Changed lines 38-40 from:

to:

Same problem here...

July 04, 2005, at 06:50 AM by Dutch --
Changed lines 1-4 from:
to:

June 22, 2005, at 03:47 AM by Dutch -- HowTo....InstallAndConfigureSyslog-ng
Added lines 1-40:

How to... InstallAndConfigureSyslog?-ng

I got this error message when trying to run syslog-ng with the default config file that came with it in the ipkg install:


17-Jun-2005_21:51:11
root@DVZ_NET_FS
/share/hdd/conf/unslung :^> syslog-ng -d -v
binding fd 3, inetaddr: 0.0.0.0, port: 514
io.c: Preparing fd 3 for reading
io.c: Preparing fd 4 for reading
binding fd 5, unixaddr: /dev/log
io.c: listening on fd 5
unresolved reference: console
Error initializing configuration, exiting.

I then grepped the syslog-ng.conf file to see what the problem reference might be, and got this:


17-Jun-2005_21:51:57
root@DVZ_NET_FS
/share/hdd/conf/unslung :^> cat /opt/etc/syslog-ng/syslog-ng.conf |grep console
log { source(src); filter(f_emergency); destination(console); };
log { source(src); destination(console_all); };

I was able to get syslog-ng working (as far as I can tell) by simply commenting out the two lines that contained references to console and console_all, but I am concerned that I won't be getting the f_emergency messages that I'm supposed to be getting.

Anyone who wants to add to this, please do! I'm just barely on the cusp between n00bie and novice at this.... :^)


view · edit · print · history · Last edited by fcarolo.
Based on work by Farhan Yousaf, Jerome, Niko_K, and Dutch.
Originally by Dutch.
Page last modified on January 14, 2007, at 07:28 PM