Talk:Syslog-NG Installation - Revision history

DrModiford: Sometimes the simplest way..

2008-06-09T21:29:43Z

Sometimes the simplest way..

DrModiford: Perhaps this will do it

2008-06-07T21:45:11Z

Perhaps this will do it

DrModiford: Mea culpa, mea culpa, mea maxima culpa...

2008-06-07T21:28:57Z

Mea culpa, mea culpa, mea maxima culpa...

Jimbo: what I don't see is...

2008-06-07T12:22:30Z

what I don't see is...

Jimbo: oh. THAT, I can answer:

2008-06-07T12:16:45Z

oh. THAT, I can answer:

212.30.5.135: Not so much Syslog-NG but...

2008-06-07T08:13:49Z

Not so much Syslog-NG but...

Jimbo: unfortunately

2008-06-07T01:32:58Z

unfortunately

DrModiford: Call for assistance

2008-06-06T20:57:32Z

Call for assistance

New page

The Syslog / MySQL Pipe script is the best I could do from what I could gather from examples. It does however drop-out and require restarting. My fix was to use a cron job to restart it daily. Could any fellow Wiki member here care to expand on what I have missed in order to improve it?

There is just a few more things to add to the Syslog-NG article before it's finished, but any help on the above issue would be greatly beneficial.

Best regards,

DrModiford.

← Older revision		Revision as of 21:29, 9 June 2008
Line 53:		Line 53:

	I suspect the original while-loop checks to see if there is anything in the pipe before continuing the process, so it may only get busy when a set of network-originating Syslog events are sent through to the pipe itself. While simply running as is (following the update to the code) it is not noticeable using 'top'.		I suspect the original while-loop checks to see if there is anything in the pipe before continuing the process, so it may only get busy when a set of network-originating Syslog events are sent through to the pipe itself. While simply running as is (following the update to the code) it is not noticeable using 'top'.
		+
		+	== Sometimes the simplest way.. ==
		+
		+	...is to crib off someone else ;-)
		+
		+	As noted on the main article, I found a good method for piping directly to MySQL (still using the [[mkfifo]] command method) but without the external script on a Gentoo guide of a similar nature to this one.
		+
		+	Having implemented it on my production box its working fine, the script method would have dropped out by now!

← Older revision		Revision as of 21:45, 7 June 2008
Line 41:		Line 41:

	Thanks for the tip on the script - I shall update my server soon and let you know the utilization is, if any at all.		Thanks for the tip on the script - I shall update my server soon and let you know the utilization is, if any at all.
		+
		+	== Perhaps this will do it ==
		+
		+	I did a search and found the following page (sorry for the Google Cache, the servers were "down for maintenance" at the time)
		+
		+	http://64.233.183.104/search?q=cache:O_RZM0qyDiQJ:www.ibm.com/developerworks/forums/thread.jspa%3FthreadID%3D120023%26tstart%3D0+sh+script+continuous+loop&hl=en&ct=clnk&cd=1&gl=uk
		+
		+	(the original http://www.ibm.com/developerworks/forums/thread.jspa?threadID=120023&tstart=0)
		+
		+	The last posting on the cached page had some good pointers, including a 'sleep' command to reduce CPU over-usage.
		+
		+	I suspect the original while-loop checks to see if there is anything in the pipe before continuing the process, so it may only get busy when a set of network-originating Syslog events are sent through to the pipe itself. While simply running as is (following the update to the code) it is not noticeable using 'top'.

← Older revision		Revision as of 21:28, 7 June 2008
Line 33:		Line 33:

	What actually writes ''to'' mysql.pipe? I see a couple scripts (your rc.d script, and the /usr/local/bin script) that create the fifo and/or dump its contents into the mysql db, but I don't see any config stuff that would cause things to go INTO mysql.pipe to begin with. What am I missing? --[[User:Jimbo\|Jimbo]] 08:22, 7 June 2008 (EDT)		What actually writes ''to'' mysql.pipe? I see a couple scripts (your rc.d script, and the /usr/local/bin script) that create the fifo and/or dump its contents into the mysql db, but I don't see any config stuff that would cause things to go INTO mysql.pipe to begin with. What am I missing? --[[User:Jimbo\|Jimbo]] 08:22, 7 June 2008 (EDT)
		+
		+	== Mea culpa, mea culpa, mea maxima culpa... ==
		+
		+	...alright - perhaps maybe, just maybe, I missed a vital piece of configuration file for the Syslog-NG service itself!
		+
		+	Hopefully that clarifies how A gets to B now!
		+
		+	Thanks for the tip on the script - I shall update my server soon and let you know the utilization is, if any at all.

← Older revision		Revision as of 12:22, 7 June 2008
Line 29:		Line 29:

	What does this continuously looping shell script running in the background do to your CPU usage, btw? --[[User:Jimbo\|Jimbo]] 08:16, 7 June 2008 (EDT)		What does this continuously looping shell script running in the background do to your CPU usage, btw? --[[User:Jimbo\|Jimbo]] 08:16, 7 June 2008 (EDT)
		+
		+	== what I don't see is... ==
		+
		+	What actually writes ''to'' mysql.pipe? I see a couple scripts (your rc.d script, and the /usr/local/bin script) that create the fifo and/or dump its contents into the mysql db, but I don't see any config stuff that would cause things to go INTO mysql.pipe to begin with. What am I missing? --[[User:Jimbo\|Jimbo]] 08:22, 7 June 2008 (EDT)

← Older revision		Revision as of 12:16, 7 June 2008
Line 20:		Line 20:

	DrModiford.		DrModiford.
		+
		+	== oh. THAT, I can answer: ==
		+
		+	# Loop MySQL pipe function
		+	while [ -e /var/log/mysql.pipe ]
		+
		+	As soon as you hit EOF one time on your pipe, the script breaks out of your while loop and is done. Try an infinite while with an if statement nested inside, instead of the conditional while you're using now.
		+
		+	What does this continuously looping shell script running in the background do to your CPU usage, btw? --[[User:Jimbo\|Jimbo]] 08:16, 7 June 2008 (EDT)

← Older revision		Revision as of 08:13, 7 June 2008
Line 10:		Line 10:

	Unfortunately, I haven't messed with syslog-ng at all and thus can't be of any assistance... but it's an interesting topic and I very much appreciate your sharing your experience here! --[[User:Jimbo\|Jimbo]] 21:32, 6 June 2008 (EDT)		Unfortunately, I haven't messed with syslog-ng at all and thus can't be of any assistance... but it's an interesting topic and I very much appreciate your sharing your experience here! --[[User:Jimbo\|Jimbo]] 21:32, 6 June 2008 (EDT)
		+
		+	== Not so much Syslog-NG but... ==
		+
		+	...the redirection script under the 'Syslog-NG Piping' section called 'syslog-pipe.sh'. All it does is constantly loop taking anything sent to the pipe in '/var/log/mysql.pipe' to MySQL. However it drops out for no apparent reason. I have used a cron-job to restart it, because (somewhat thankfully) the pipe queues up information so nothing is lost during this downtime. Not ideal but it's a work-around.
		+
		+	Thanks for the feedback Jimbo, hopefully it will be of use to others.
		+
		+	Best regards,
		+
		+	DrModiford.

← Older revision		Revision as of 01:32, 7 June 2008
Line 6:		Line 6:

	DrModiford.		DrModiford.
		+
		+	== unfortunately ==
		+
		+	Unfortunately, I haven't messed with syslog-ng at all and thus can't be of any assistance... but it's an interesting topic and I very much appreciate your sharing your experience here! --[[User:Jimbo\|Jimbo]] 21:32, 6 June 2008 (EDT)