<?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: Whats the correct way to restart inetd in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415326#M663355</link>
    <description>&lt;!--!*#--&gt;There are some cases where you have to restart inetd. A bug that caused a memory leak causing ssh to fail as inetd approaches its maximum allowable memory allocation for example.&lt;BR /&gt;&lt;BR /&gt;The correct way to restart would be:&lt;BR /&gt;&lt;BR /&gt;/sbhin/init.d/inetd stop; /sbin/init.d/inetd start&lt;BR /&gt;&lt;BR /&gt;in single line, yes, to minimize the time when it remains down. And then ensure it started. &lt;BR /&gt;&lt;BR /&gt;It is critical to start inetd immediately upon stopping it because many services are dependent on it. Particularly when you have clustered nodes, a failure of inetd beyond time out periods can spell disaster.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Anoop</description>
    <pubDate>Fri, 08 May 2009 02:31:08 GMT</pubDate>
    <dc:creator>Anoop P_2</dc:creator>
    <dc:date>2009-05-08T02:31:08Z</dc:date>
    <item>
      <title>Whats the correct way to restart inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415318#M663347</link>
      <description>&lt;BR /&gt;Hi, &lt;BR /&gt;&lt;BR /&gt;Can anyone help.. I am getting a  error when telneting to my HP-UX server, (I'm trying to telnet to port 3872 on HP-UX server from  aremote server, I get connection refusted. I'ce checked firewall, The rules are in palce and the port 3872 is enabled, it doesnt look like its firewall. I've checked /etc/inetd.conf and found the line with telnet commented out. So I have un commented and would like to know the correct way to restart inetd. And hoping that will fix it.&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Thu, 07 May 2009 14:02:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415318#M663347</guid>
      <dc:creator>amreek bansal</dc:creator>
      <dc:date>2009-05-07T14:02:15Z</dc:date>
    </item>
    <item>
      <title>Re: Whats the correct way to restart inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415319#M663348</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Just run #inetd -c to reread the configuration file. that's enough. No need to restart inetd daemon.</description>
      <pubDate>Thu, 07 May 2009 14:04:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415319#M663348</guid>
      <dc:creator>Ganesan R</dc:creator>
      <dc:date>2009-05-07T14:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: Whats the correct way to restart inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415320#M663349</link>
      <description>"port 3872 is enabled"&lt;BR /&gt;&lt;BR /&gt;What process should answer port 3872 requests?&lt;BR /&gt;&lt;BR /&gt;This is normally used by oracle.</description>
      <pubDate>Thu, 07 May 2009 14:06:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415320#M663349</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-05-07T14:06:41Z</dc:date>
    </item>
    <item>
      <title>Re: Whats the correct way to restart inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415321#M663350</link>
      <description>&lt;BR /&gt;Yes I have tried inetd -c, it probably has re read the file, but hasnt fixed th etelent connection refused issue.</description>
      <pubDate>Thu, 07 May 2009 14:08:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415321#M663350</guid>
      <dc:creator>amreek bansal</dc:creator>
      <dc:date>2009-05-07T14:08:08Z</dc:date>
    </item>
    <item>
      <title>Re: Whats the correct way to restart inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415322#M663351</link>
      <description>&lt;BR /&gt;yes should be oracle using port 3872</description>
      <pubDate>Thu, 07 May 2009 14:09:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415322#M663351</guid>
      <dc:creator>amreek bansal</dc:creator>
      <dc:date>2009-05-07T14:09:03Z</dc:date>
    </item>
    <item>
      <title>Re: Whats the correct way to restart inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415323#M663352</link>
      <description>Hi Amreek,&lt;BR /&gt;&lt;BR /&gt;By default telnet will listen on port no 23. If you want to configure to listen on some other port comment out the existing line on /etc/inetd.conf and /etc/services and put the new entries like this...&lt;BR /&gt;&lt;BR /&gt;#vi /etc/inetd.conf&lt;BR /&gt;&lt;BR /&gt;newtelnet    stream tcp nowait root /usr/lbin/telnetd  telnetd&lt;BR /&gt;&lt;BR /&gt;#vi /etc/services&lt;BR /&gt;&lt;BR /&gt;newtelnet     3872/tcp                 # new telnet with port no 3872&lt;BR /&gt;&lt;BR /&gt;then reread the inetd daemon by #inetd -c&lt;BR /&gt;&lt;BR /&gt;Make sure that port 3872 is not used by any other service or application.</description>
      <pubDate>Thu, 07 May 2009 14:17:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415323#M663352</guid>
      <dc:creator>Ganesan R</dc:creator>
      <dc:date>2009-05-07T14:17:29Z</dc:date>
    </item>
    <item>
      <title>Re: Whats the correct way to restart inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415324#M663353</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;in my opinion port 3872 is not in listen currently, you can check that by&lt;BR /&gt;&lt;BR /&gt;netstat -an|grep 3872&lt;BR /&gt;&lt;BR /&gt;You're getting connection refused not for telnet issues, the reason is that port is not on listen. Just for a try, issue&lt;BR /&gt;&lt;BR /&gt;netstat -an &lt;BR /&gt;&lt;BR /&gt;and&lt;BR /&gt;&lt;BR /&gt;telnet &lt;LOCALHOST&gt; &lt;ONE of="" the="" port="" on="" netstat="" list=""&gt;&lt;BR /&gt;&lt;BR /&gt;HTH.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Fabio&lt;/ONE&gt;&lt;/LOCALHOST&gt;</description>
      <pubDate>Thu, 07 May 2009 14:22:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415324#M663353</guid>
      <dc:creator>Fabio Ettore</dc:creator>
      <dc:date>2009-05-07T14:22:49Z</dc:date>
    </item>
    <item>
      <title>Re: Whats the correct way to restart inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415325#M663354</link>
      <description>I'm not a oracle expert at all, but I guess this certain application is not using inetd.</description>
      <pubDate>Thu, 07 May 2009 14:23:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415325#M663354</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-05-07T14:23:54Z</dc:date>
    </item>
    <item>
      <title>Re: Whats the correct way to restart inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415326#M663355</link>
      <description>&lt;!--!*#--&gt;There are some cases where you have to restart inetd. A bug that caused a memory leak causing ssh to fail as inetd approaches its maximum allowable memory allocation for example.&lt;BR /&gt;&lt;BR /&gt;The correct way to restart would be:&lt;BR /&gt;&lt;BR /&gt;/sbhin/init.d/inetd stop; /sbin/init.d/inetd start&lt;BR /&gt;&lt;BR /&gt;in single line, yes, to minimize the time when it remains down. And then ensure it started. &lt;BR /&gt;&lt;BR /&gt;It is critical to start inetd immediately upon stopping it because many services are dependent on it. Particularly when you have clustered nodes, a failure of inetd beyond time out periods can spell disaster.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Anoop</description>
      <pubDate>Fri, 08 May 2009 02:31:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415326#M663355</guid>
      <dc:creator>Anoop P_2</dc:creator>
      <dc:date>2009-05-08T02:31:08Z</dc:date>
    </item>
    <item>
      <title>Re: Whats the correct way to restart inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415327#M663356</link>
      <description>I don't know anything about this, but based on what I have found there is an apache daemon "behind" this port; likely not started by inetd but running "static".&lt;BR /&gt;&lt;BR /&gt;So you may test with telnet, but modify the inetd.conf will create other problems and isn't a solution.</description>
      <pubDate>Fri, 08 May 2009 02:55:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415327#M663356</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-05-08T02:55:21Z</dc:date>
    </item>
    <item>
      <title>Re: Whats the correct way to restart inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415328#M663357</link>
      <description>&lt;!--!*#--&gt;To check whether port is being listened to:&lt;BR /&gt;&lt;BR /&gt;telnet &lt;SERVERNAME&gt; 3872 (Fabio's method)&lt;BR /&gt;&lt;BR /&gt;and also&lt;BR /&gt;&lt;BR /&gt;lsof -i tcp:3872&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Anoop&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SERVERNAME&gt;</description>
      <pubDate>Fri, 08 May 2009 02:55:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415328#M663357</guid>
      <dc:creator>Anoop P_2</dc:creator>
      <dc:date>2009-05-08T02:55:42Z</dc:date>
    </item>
    <item>
      <title>Re: Whats the correct way to restart inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415329#M663358</link>
      <description>Check the telent first, is it working or not. Login locally on the machine and try "telnet 0". If it returns the login prompt then telnet is ok else you need to fix this first.</description>
      <pubDate>Fri, 08 May 2009 04:39:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/whats-the-correct-way-to-restart-inetd/m-p/4415329#M663358</guid>
      <dc:creator>Mridul Shrivastava</dc:creator>
      <dc:date>2009-05-08T04:39:04Z</dc:date>
    </item>
  </channel>
</rss>

