<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: messages in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/messages/m-p/3881586#M25618</link>
    <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;The message is not very meaningful to me. &lt;BR /&gt;&lt;BR /&gt;The cause of the hang should also be in /var/log/messages and that could be a hardware issue.&lt;BR /&gt;&lt;BR /&gt;I'd boot the box of the diagnostics cd and run all hardware diagnostics.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Tue, 17 Oct 2006 11:52:23 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2006-10-17T11:52:23Z</dc:date>
    <item>
      <title>messages</title>
      <link>https://community.hpe.com/t5/operating-system-linux/messages/m-p/3881585#M25617</link>
      <description>I am getting the following message in the messages file.&lt;BR /&gt;syslog-ng[4357]: STATS: dropped 0&lt;BR /&gt;The messages repeats over and over again. Also this machine was hung and i had to reboot the box, this machine does not have the netdump enabled so i am unable to find the root cause. does the bove message point to anything? this is redhat AS3.&lt;BR /&gt;&lt;BR /&gt;THanks&lt;BR /&gt;&lt;BR /&gt;Brian</description>
      <pubDate>Tue, 17 Oct 2006 09:43:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/messages/m-p/3881585#M25617</guid>
      <dc:creator>brian_31</dc:creator>
      <dc:date>2006-10-17T09:43:33Z</dc:date>
    </item>
    <item>
      <title>Re: messages</title>
      <link>https://community.hpe.com/t5/operating-system-linux/messages/m-p/3881586#M25618</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;The message is not very meaningful to me. &lt;BR /&gt;&lt;BR /&gt;The cause of the hang should also be in /var/log/messages and that could be a hardware issue.&lt;BR /&gt;&lt;BR /&gt;I'd boot the box of the diagnostics cd and run all hardware diagnostics.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 17 Oct 2006 11:52:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/messages/m-p/3881586#M25618</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-10-17T11:52:23Z</dc:date>
    </item>
    <item>
      <title>Re: messages</title>
      <link>https://community.hpe.com/t5/operating-system-linux/messages/m-p/3881587#M25619</link>
      <description>Brian,&lt;BR /&gt;&lt;BR /&gt;Syslog-ng has a built-in buffer for TCP and FIFO/named pipe destinations. When the remote end (TCP or local named pipe) can't keep up with the amount of messages that syslog-ng is trying to send in, the buffer can overflow. syslog-ng reports the number of dropped message LINES in the STATS messages. The "STATS: dropped 0" message is syslog-ng notice message, which tell you it hasn't drop any /dev/log packets.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Ross</description>
      <pubDate>Tue, 17 Oct 2006 11:53:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/messages/m-p/3881587#M25619</guid>
      <dc:creator>Ross Minkov</dc:creator>
      <dc:date>2006-10-17T11:53:59Z</dc:date>
    </item>
  </channel>
</rss>

