<?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: Stderr problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/stderr-problem/m-p/3312087#M567734</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The best way with unnneded log files is to cofigure them as /dev/null in appropriate config files. If this is impossible, run the following cron job, if you don't need to store the files:&lt;BR /&gt;&lt;BR /&gt;cd  /usr/sap/NA1 &lt;BR /&gt;ls -t stderr* | while read FNAME; do&lt;BR /&gt;echo &amp;gt; $FNAME&lt;BR /&gt;done&lt;BR /&gt;&lt;BR /&gt;Run this script according to the files growing.&lt;BR /&gt;&lt;BR /&gt;HTH</description>
    <pubDate>Tue, 22 Jun 2004 10:38:54 GMT</pubDate>
    <dc:creator>Victor Fridyev</dc:creator>
    <dc:date>2004-06-22T10:38:54Z</dc:date>
    <item>
      <title>Stderr problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/stderr-problem/m-p/3312085#M567732</link>
      <description>Currently, we are running oracle &amp;amp; SAP&lt;BR /&gt;There is directory /usr/sap/NA1 that create stderr log for SAP application&lt;BR /&gt;&lt;BR /&gt;The problem is stderr2 log is growing more than capacity of this file system&lt;BR /&gt;&lt;BR /&gt;Only solution is reboot the server &lt;BR /&gt;Right now we made null copy stderr log&lt;BR /&gt;&lt;BR /&gt;please check the following logs and give me solution&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;-rw-rw-rw-   1 na1adm     sapsys         160 Jun 20 15:10 stderr1&lt;BR /&gt;-rw-r--r--   1 root       sys              0 Jun 22 05:59 stderr2&lt;BR /&gt;-rw-rw-rw-   1 na1adm     sapsys     8177662481 Jun 22 11:02 stderr2.old&lt;BR /&gt;-rwxrwxrwx   1 na1adm     sapsys         174 Jun 20 15:10 stderr3&lt;BR /&gt;-rwxrwxrwx   1 na1adm     sapsys         174 Jun 20 15:10 stderr4&lt;BR /&gt;-rwxrwxrwx   1 na1adm     sapsys           0 Jun 20 15:10 stdout1&lt;BR /&gt;-rwxrwxrwx   1 na1adm     sapsys           0 Jun 20 15:10 stdout2&lt;BR /&gt;-rwxrwxrwx   1 na1adm     sapsys           0 Jun 20 15:10 stdout3&lt;BR /&gt;-rwxrwxrwx   1 na1adm     sapsys           0 Jun 20 15:10 stdout4&lt;BR /&gt;seauxsp1:/usr/sap/NA1/DVEBMGS00/work&amp;gt;du -sk&lt;BR /&gt;81372   .&lt;BR /&gt;seauxsp1:/usr/sap/NA1/DVEBMGS00/work&amp;gt;du -sk stderr2.old&lt;BR /&gt;5       stderr2.old&lt;BR /&gt;seauxsp1:/usr/sap/NA1/DVEBMGS00/work&amp;gt;bdf .&lt;BR /&gt;Filesystem          kbytes    used   avail %used Mounted on&lt;BR /&gt;/dev/vg07/lvol11   6144000  587819 5210018   10% /usr/sap/NA1&lt;BR /&gt;seauxsp1:/usr/sap/NA1/DVEBMGS00/work&amp;gt;</description>
      <pubDate>Tue, 22 Jun 2004 10:31:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/stderr-problem/m-p/3312085#M567732</guid>
      <dc:creator>Steve Lee_7</dc:creator>
      <dc:date>2004-06-22T10:31:04Z</dc:date>
    </item>
    <item>
      <title>Re: Stderr problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/stderr-problem/m-p/3312086#M567733</link>
      <description>the information you provide regarding the sizes, protections, etc.  of the log files does not appear to me to be relevant to solving your problem. If the log is too big for the filesystem you potential solutions are things like, a) decrease logging; b) increase filesystem space; c) truncate and or move the logfiles more frequently; etc...&lt;BR /&gt;&lt;BR /&gt;or perhaps I am misunderstanding the question or situation...</description>
      <pubDate>Tue, 22 Jun 2004 10:35:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/stderr-problem/m-p/3312086#M567733</guid>
      <dc:creator>John Kittel</dc:creator>
      <dc:date>2004-06-22T10:35:25Z</dc:date>
    </item>
    <item>
      <title>Re: Stderr problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/stderr-problem/m-p/3312087#M567734</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The best way with unnneded log files is to cofigure them as /dev/null in appropriate config files. If this is impossible, run the following cron job, if you don't need to store the files:&lt;BR /&gt;&lt;BR /&gt;cd  /usr/sap/NA1 &lt;BR /&gt;ls -t stderr* | while read FNAME; do&lt;BR /&gt;echo &amp;gt; $FNAME&lt;BR /&gt;done&lt;BR /&gt;&lt;BR /&gt;Run this script according to the files growing.&lt;BR /&gt;&lt;BR /&gt;HTH</description>
      <pubDate>Tue, 22 Jun 2004 10:38:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/stderr-problem/m-p/3312087#M567734</guid>
      <dc:creator>Victor Fridyev</dc:creator>
      <dc:date>2004-06-22T10:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: Stderr problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/stderr-problem/m-p/3312088#M567735</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I would first find the process that is using this file. If it is constantly growing, then run 'fuser stderr2' and it should list out the processes that opened this file and fix them.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Tue, 22 Jun 2004 10:40:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/stderr-problem/m-p/3312088#M567735</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2004-06-22T10:40:38Z</dc:date>
    </item>
  </channel>
</rss>

