<?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: Errors in syslog.log in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587490#M32483</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Logging enabled means that inetd sends SIGQUIT to inetd, but inetd is already running, which causes it ti toggle the state of connection logging. &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 01 Oct 2001 14:52:10 GMT</pubDate>
    <dc:creator>Marcin Wicinski</dc:creator>
    <dc:date>2001-10-01T14:52:10Z</dc:date>
    <item>
      <title>Errors in syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587483#M32476</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;I am getting a load of errors in my syslog.log every couple of minutes saying....&lt;BR /&gt;&lt;BR /&gt;Oct  1 15:59:03 hostname inetd[29631]: bpcd/tcp: Connection from hostname (ip address) at Mon Oct  1 15:59:03 2001&lt;BR /&gt;&lt;BR /&gt;and....&lt;BR /&gt;&lt;BR /&gt;Oct  1 16:00:04 hostname inetd[29956]: registrar/tcp: Connection from hostname (ip address) at Mon Oct  1 16:00:04 2001&lt;BR /&gt;&lt;BR /&gt;Anybody know what these mean?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance,&lt;BR /&gt;&lt;BR /&gt;Colin.&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Oct 2001 14:14:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587483#M32476</guid>
      <dc:creator>Warren griggs</dc:creator>
      <dc:date>2001-10-01T14:14:22Z</dc:date>
    </item>
    <item>
      <title>Re: Errors in syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587484#M32477</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;It simply means that inetd was enabled with logging (the -l argument). Man inetd for details. If you wish to turn it off, you will need to go to the console and login. Edit the /sbin/init.d/inetd script. If the -l arg to inetd  is specified in the 'start)' section,&lt;BR /&gt;remove it there. It may have been specified in an /etc/rc.config.d/inetd file. &lt;BR /&gt;After you make the changes:&lt;BR /&gt;/sbin/init.d/inetd stop&lt;BR /&gt;/sbin/init.d/inetd start&lt;BR /&gt; &lt;BR /&gt;Regards, Clay</description>
      <pubDate>Mon, 01 Oct 2001 14:27:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587484#M32477</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-10-01T14:27:52Z</dc:date>
    </item>
    <item>
      <title>Re: Errors in syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587485#M32478</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;From those messages it looks like that inetd is running in logging mode i.e inetd -l.&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Oct 2001 14:27:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587485#M32478</guid>
      <dc:creator>Rajeev Tyagi</dc:creator>
      <dc:date>2001-10-01T14:27:57Z</dc:date>
    </item>
    <item>
      <title>Re: Errors in syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587486#M32479</link>
      <description>The '-l' option can also be set in /etc/rc.config.d/netdaemons.  If you do not find it in one place, look to the other.&lt;BR /&gt;&lt;BR /&gt;It is not necessarily a bad thing to have logging turned on, every once in a while you may see a machine or address connecting that you do not think should be....</description>
      <pubDate>Mon, 01 Oct 2001 14:31:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587486#M32479</guid>
      <dc:creator>John Payne_2</dc:creator>
      <dc:date>2001-10-01T14:31:32Z</dc:date>
    </item>
    <item>
      <title>Re: Errors in syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587487#M32480</link>
      <description>Hi Colin,&lt;BR /&gt;&lt;BR /&gt;bpcd is the Veritas Netbackup service name,&lt;BR /&gt;registrar is the Resource Monitor broker.&lt;BR /&gt;&lt;BR /&gt;If these messages are valid, perhaps it simply means inetd logging has been switched on for some reason.&lt;BR /&gt;&lt;BR /&gt;Rgds, Robin&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Oct 2001 14:34:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587487#M32480</guid>
      <dc:creator>Robin Wakefield</dc:creator>
      <dc:date>2001-10-01T14:34:05Z</dc:date>
    </item>
    <item>
      <title>Re: Errors in syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587488#M32481</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Thanks for the speedy replies.&lt;BR /&gt;&lt;BR /&gt;What I don't understand is that the machine seems to be connecting to itself.&lt;BR /&gt;&lt;BR /&gt;i.e. Oct  1 16:00:04 host1 inetd[29956]: registrar/tcp: Connection from host1 (&lt;BR /&gt;ip address of host1) at Mon Oct  1 16:00:04 2001&lt;BR /&gt;&lt;BR /&gt;Why is it connecting to itself so often and through the night when the machine is supposed to be quiet?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Colin.</description>
      <pubDate>Mon, 01 Oct 2001 14:37:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587488#M32481</guid>
      <dc:creator>Warren griggs</dc:creator>
      <dc:date>2001-10-01T14:37:55Z</dc:date>
    </item>
    <item>
      <title>Re: Errors in syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587489#M32482</link>
      <description>Hi Colin,&lt;BR /&gt;&lt;BR /&gt;Is this machine acting as server + client for these applications?  If there is an underlying problem, perhaps the application logs show the real reason for the multiple reconnects.&lt;BR /&gt;&lt;BR /&gt;Rgds, Robin.</description>
      <pubDate>Mon, 01 Oct 2001 14:44:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587489#M32482</guid>
      <dc:creator>Robin Wakefield</dc:creator>
      <dc:date>2001-10-01T14:44:11Z</dc:date>
    </item>
    <item>
      <title>Re: Errors in syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587490#M32483</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Logging enabled means that inetd sends SIGQUIT to inetd, but inetd is already running, which causes it ti toggle the state of connection logging. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Oct 2001 14:52:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog-log/m-p/2587490#M32483</guid>
      <dc:creator>Marcin Wicinski</dc:creator>
      <dc:date>2001-10-01T14:52:10Z</dc:date>
    </item>
  </channel>
</rss>

