Re: [syslog-ng] Tracking down a failure between NG and FIFO
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Antonín Faltýnek wrote:
there is option log_fifo_size(); for syslog-ng that defines size of log queue in number o messages, couldn't be you logserver overloaded?
Yah possibly; in the absence of any other changes, some Event that spiked the volume would be what I expected to find. But i can't find anything in that time frame.
for mysql I'm not using fifo that's mentioned everywhere on inet by I call mysql as program (I've different table layout):
What version does that start appearing in? I've still got 1.6.9 - i was considering upgrading to the 2.0 branch, but not until I understand what happened here. Thanks for the info. It's working now; took down stunnel, syslog, and mysql, stared hard at all the configs for a bit, brought it all back up. Started working again. I'd feel better if i knew why it is working now, even more than finding out what broke before.
Tonda Faltynek ------------------------------------------------------------ You can do that without any technological mambo-jumbo...
- -- Rob Munsch Solutions For Progress IT www.solutionsforprogress.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFCDbhBvBcJFK6xYURAtz2AJ90qQYUQn9sgPLfYawnjk2e97C1agCaApT1 Abv2dUK1DWHHcK2e+J8KD14= =EM0z -----END PGP SIGNATURE-----
participants (1)
-
Rob Munsch