Package: syslog-ng "Dec 1 01:57:22 somehost syslog-ng[314]: STATS: dropped 1"
Huh? "STATS" this is merely a statistic, not a serious error condition??? "dropped 1"? One what? One packet (obvious thing computers dropped)? One message? One bar of soap? What the heck is causing multiple messages like this? Despite <[EMAIL PROTECTED]>, I don't see it mentioned in the obvious places. Crucially the destination needs to be listed. From context that message immediately makes me check /var, since filling up that filesystem would be the favorite reason for the system logger to start dropping things. Once I see that isn't a problem, and see no cluster of messages to overflow the buffers one starts wondering WTF is going on. Knowing that the destination was /dev/xconsole would of avoided some panic and with more complex setups would greatly simplify debugging. Adding messages advising that buffers are filling up would also be helpful. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | [EMAIL PROTECTED] PGP 8881EF59 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ \___\_|_/82 04 A1 3C C7 B1 37 2A*E3 6E 84 DA 97 4C 40 E6\_|_/___/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]