<?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 Syslog getting full in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-getting-full/m-p/2497446#M20296</link>
    <description>I am getting the following error messages in the syslog table every minute which eventually is making my system to crash after few weeks. My question is:&lt;BR /&gt;&lt;BR /&gt;1. What does this error message mean?&lt;BR /&gt;&lt;BR /&gt;2. How do we make the syslog  to not log this error?&lt;BR /&gt;&lt;BR /&gt;3. How to trim the syslog automatically?&lt;BR /&gt;&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc last message repeated 2 times&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_ACCEPT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_PEERADDR snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_ACCEPT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_PEERADDR snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc last message repeated 4 times&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_ACCEPT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:30:03 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:30:03 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -&amp;gt; snpair&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
    <pubDate>Thu, 22 Feb 2001 20:03:16 GMT</pubDate>
    <dc:creator>Alex Hose</dc:creator>
    <dc:date>2001-02-22T20:03:16Z</dc:date>
    <item>
      <title>Syslog getting full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-getting-full/m-p/2497446#M20296</link>
      <description>I am getting the following error messages in the syslog table every minute which eventually is making my system to crash after few weeks. My question is:&lt;BR /&gt;&lt;BR /&gt;1. What does this error message mean?&lt;BR /&gt;&lt;BR /&gt;2. How do we make the syslog  to not log this error?&lt;BR /&gt;&lt;BR /&gt;3. How to trim the syslog automatically?&lt;BR /&gt;&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc last message repeated 2 times&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_ACCEPT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_PEERADDR snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_ACCEPT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_PEERADDR snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:29:04 udcpdc last message repeated 4 times&lt;BR /&gt;Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_ACCEPT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:30:03 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -&amp;gt; snpair&lt;BR /&gt;Feb 22 02:30:03 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -&amp;gt; snpair&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Thu, 22 Feb 2001 20:03:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-getting-full/m-p/2497446#M20296</guid>
      <dc:creator>Alex Hose</dc:creator>
      <dc:date>2001-02-22T20:03:16Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog getting full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-getting-full/m-p/2497447#M20297</link>
      <description>These messages come from some third party software in your kernel and are not generated by hp-ux. I would contact the 3rd s/w supplier.</description>
      <pubDate>Thu, 22 Feb 2001 23:56:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-getting-full/m-p/2497447#M20297</guid>
      <dc:creator>Andy Monks</dc:creator>
      <dc:date>2001-02-22T23:56:39Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog getting full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-getting-full/m-p/2497448#M20298</link>
      <description>I can't help with first 2 questions but for trimming syslog , try putting the following script in the root cron file&lt;BR /&gt;&lt;BR /&gt;#!/bin/sh&lt;BR /&gt;cat /var/adm/syslog/syslog.log | grep -v udcpdc &amp;gt; /tmp/tmpsyslog&lt;BR /&gt;cp /tmp/tmpsyslog /var/adm/syslog.log&lt;BR /&gt;rm /tmp/tmpsyslog&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;This will display all lines which do not contain the string udcpdc to a seperate file which then can be coppied over the original syslog file.  &lt;BR /&gt;&lt;BR /&gt;You need to be careful not to delete the original file with the rm command as this does not delete the space just the inode entry until the systlogd process is killed.</description>
      <pubDate>Fri, 23 Feb 2001 11:37:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-getting-full/m-p/2497448#M20298</guid>
      <dc:creator>John Waller</dc:creator>
      <dc:date>2001-02-23T11:37:30Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog getting full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-getting-full/m-p/2497449#M20299</link>
      <description>Just to add to John's response.  I do almost exactly the same script, except I add -v -e &lt;REMOVE_THIS&gt; -e &lt;REMOVE_THIS2&gt; -e &lt;REMOVE_THIS3&gt;&lt;BR /&gt;So I can get rid of a few bothersome messages I don't need to read from syslog....I set this little script up and cron it in the morning before I generally do a quick check of my logs....  I cron this script every morning to keep my syslog manageable.&lt;BR /&gt;&lt;BR /&gt;/rcw&lt;/REMOVE_THIS3&gt;&lt;/REMOVE_THIS2&gt;&lt;/REMOVE_THIS&gt;</description>
      <pubDate>Fri, 23 Feb 2001 14:38:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-getting-full/m-p/2497449#M20299</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2001-02-23T14:38:49Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog getting full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-getting-full/m-p/2497450#M20300</link>
      <description>As stated previously, having a script to trim the syslog is going to work - I do it myself. But as another alternative you could go the the HP archive center and get a program called "trimlog". This will do the syslog file as well as any other log file you may have trouble with. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 23 Feb 2001 15:50:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-getting-full/m-p/2497450#M20300</guid>
      <dc:creator>Rick Garland</dc:creator>
      <dc:date>2001-02-23T15:50:51Z</dc:date>
    </item>
  </channel>
</rss>

