Talk:Syslog-NG Installation
(unfortunately) |
(Not so much Syslog-NG but...) |
||
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. |
Revision as of 04:13, 7 June 2008
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.
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! --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.