<?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 monitoring syslog in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439774#M6899</link>
    <description>Hi,&lt;BR /&gt;can any one suggest what is the best way to monitor syslog everyday for several server.&lt;BR /&gt;I am not using ITO.&lt;BR /&gt;Thanx&lt;BR /&gt;animesh</description>
    <pubDate>Fri, 25 Aug 2000 00:35:46 GMT</pubDate>
    <dc:creator>Animesh Chakraborty</dc:creator>
    <dc:date>2000-08-25T00:35:46Z</dc:date>
    <item>
      <title>monitoring syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439774#M6899</link>
      <description>Hi,&lt;BR /&gt;can any one suggest what is the best way to monitor syslog everyday for several server.&lt;BR /&gt;I am not using ITO.&lt;BR /&gt;Thanx&lt;BR /&gt;animesh</description>
      <pubDate>Fri, 25 Aug 2000 00:35:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439774#M6899</guid>
      <dc:creator>Animesh Chakraborty</dc:creator>
      <dc:date>2000-08-25T00:35:46Z</dc:date>
    </item>
    <item>
      <title>Re: monitoring syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439775#M6900</link>
      <description>I run a script that remsh's to each server and grep's for keywords such as "error fail full unable terminat restart" etc... The context is fairly easy;&lt;BR /&gt;#############################&lt;BR /&gt;#!/usr/bin/sh&lt;BR /&gt;for server in `cat server.list`&lt;BR /&gt;do&lt;BR /&gt;for error in `cat error.list`&lt;BR /&gt;do&lt;BR /&gt;remsh $server "grep $error /var/adm/syslog/syslog.log" &amp;gt;&amp;gt; a.out&lt;BR /&gt;done&lt;BR /&gt;done&lt;BR /&gt;#######################&lt;BR /&gt;Don't forget to put a entry in each .rhosts file on each server including the one the script runs from for the machine and the uid that will run it. example:&lt;BR /&gt;myhp myuid&lt;BR /&gt;&lt;BR /&gt;Do not use any plus + signs in the .rhosts file unless you don't care about security.&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Aug 2000 00:56:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439775#M6900</guid>
      <dc:creator>Jeremiah Campbell</dc:creator>
      <dc:date>2000-08-25T00:56:18Z</dc:date>
    </item>
    <item>
      <title>Re: monitoring syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439776#M6901</link>
      <description>I run a script that remsh's to each server and grep's for keywords such as "error fail full unable terminat restart" etc... The context is fairly easy;&lt;BR /&gt;#############################&lt;BR /&gt;#!/usr/bin/sh&lt;BR /&gt;for server in `cat server.list`&lt;BR /&gt;do&lt;BR /&gt;for error in `cat error.list`&lt;BR /&gt;do&lt;BR /&gt;remsh $server "grep $error /var/adm/syslog/syslog.log" &amp;gt;&amp;gt; a.out&lt;BR /&gt;done&lt;BR /&gt;done&lt;BR /&gt;#######################&lt;BR /&gt;Don't forget to put a entry in each .rhosts file on each server including the one the script runs from for the machine and the uid that will run it. example:&lt;BR /&gt;myhp myuid&lt;BR /&gt;&lt;BR /&gt;Do not use any plus + signs in the .rhosts file unless you don't care about security.&lt;BR /&gt;&lt;BR /&gt;You need to put all your servers one-per-line in the server.list file, and any keywords you want to look for in error.list.</description>
      <pubDate>Fri, 25 Aug 2000 00:58:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439776#M6901</guid>
      <dc:creator>Jeremiah Campbell</dc:creator>
      <dc:date>2000-08-25T00:58:39Z</dc:date>
    </item>
    <item>
      <title>Re: monitoring syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439777#M6902</link>
      <description>you could set it up so that the syslogd on one system will send the messages to another system. Then you could monitor one system's syslog for multiple systems.&lt;BR /&gt;&lt;BR /&gt;Use the @host option in the /etc/syslog.conf file then execute:  kill -HUP `cat /etc/syslog.pid`  to reread the changes made to syslog.conf&lt;BR /&gt;&lt;BR /&gt;# man 1M syslogd</description>
      <pubDate>Fri, 25 Aug 2000 00:58:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439777#M6902</guid>
      <dc:creator>Denver Osborn</dc:creator>
      <dc:date>2000-08-25T00:58:57Z</dc:date>
    </item>
    <item>
      <title>Re: monitoring syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439778#M6903</link>
      <description>I would rather go with Denver's option - and in addition to that, you can have a script that greps for particular keywords "fail|error|warn|alert|" and send an e-mail to you.&lt;BR /&gt;&lt;BR /&gt;eg.  &lt;BR /&gt;egrep -i 'fail|error|warn|alert|' | mail -s "syslog error/fail messages" yourself@your.domain.com&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Aug 2000 01:35:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439778#M6903</guid>
      <dc:creator>Kofi ARTHIABAH</dc:creator>
      <dc:date>2000-08-25T01:35:58Z</dc:date>
    </item>
    <item>
      <title>Re: monitoring syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439779#M6904</link>
      <description>I would rather go with Denver's option - and in addition to that, you can have a script that greps for particular keywords "fail|error|warn|alert|" and send an e-mail to you.&lt;BR /&gt;&lt;BR /&gt;eg.  &lt;BR /&gt;egrep -i 'fail|error|warn|alert|' | mail -s "syslog error/fail messages" yourself@your.domain.com&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Aug 2000 01:44:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439779#M6904</guid>
      <dc:creator>Kofi ARTHIABAH</dc:creator>
      <dc:date>2000-08-25T01:44:55Z</dc:date>
    </item>
    <item>
      <title>Re: monitoring syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439780#M6905</link>
      <description>I would rather go with Denver's option - and in addition to that, you can have a script that greps for particular keywords "fail|error|warn|alert|" and send an e-mail to you.&lt;BR /&gt;&lt;BR /&gt;eg.  &lt;BR /&gt;egrep -i 'fail|error|warn|alert|' /var/adm/syslog/syslog.log | mail -s "syslog error/fail messages" yourself@your.domain.com&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Aug 2000 02:52:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-syslog/m-p/2439780#M6905</guid>
      <dc:creator>Kofi ARTHIABAH</dc:creator>
      <dc:date>2000-08-25T02:52:53Z</dc:date>
    </item>
  </channel>
</rss>

