<?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: tftpd timeout errors in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/tftpd-timeout-errors/m-p/5141922#M452649</link>
    <description>This message is not an error. It is a normal message from tftpd. There is some other server in your network that makes a tftp request and triggers the tftp daemon this particular server to start up via inetd. If there are no other tftp connections to your server, the tftp daemon exits and you get this message.&lt;BR /&gt;&lt;BR /&gt;Do you need to have the tftp service running in your server? That is does your server provide any tftp files to other servers to boot up? Most likely not. IgniteUX users the tftp service to allow other servers to boot over the network. And it is igniteUX that probably enabled the tftp service in your server. If you don't need it you can disable it in /etc/inetd.conf and reload inetd by "inted -c".</description>
    <pubDate>Thu, 20 Nov 2008 03:57:59 GMT</pubDate>
    <dc:creator>TTr</dc:creator>
    <dc:date>2008-11-20T03:57:59Z</dc:date>
    <item>
      <title>tftpd timeout errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tftpd-timeout-errors/m-p/5141921#M452648</link>
      <description>I'm on an HP RP7420 server running HPUX 11.i. The syslog file is getting this error message every ten minutes.&lt;BR /&gt;tftpd[5533]: Timeout (no requests in 10 minutes)&lt;BR /&gt;I noticed this error after I killed an ignite tape backup two weeks ago.</description>
      <pubDate>Wed, 19 Nov 2008 23:47:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tftpd-timeout-errors/m-p/5141921#M452648</guid>
      <dc:creator>Vernita Hall</dc:creator>
      <dc:date>2008-11-19T23:47:23Z</dc:date>
    </item>
    <item>
      <title>Re: tftpd timeout errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tftpd-timeout-errors/m-p/5141922#M452649</link>
      <description>This message is not an error. It is a normal message from tftpd. There is some other server in your network that makes a tftp request and triggers the tftp daemon this particular server to start up via inetd. If there are no other tftp connections to your server, the tftp daemon exits and you get this message.&lt;BR /&gt;&lt;BR /&gt;Do you need to have the tftp service running in your server? That is does your server provide any tftp files to other servers to boot up? Most likely not. IgniteUX users the tftp service to allow other servers to boot over the network. And it is igniteUX that probably enabled the tftp service in your server. If you don't need it you can disable it in /etc/inetd.conf and reload inetd by "inted -c".</description>
      <pubDate>Thu, 20 Nov 2008 03:57:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tftpd-timeout-errors/m-p/5141922#M452649</guid>
      <dc:creator>TTr</dc:creator>
      <dc:date>2008-11-20T03:57:59Z</dc:date>
    </item>
    <item>
      <title>Re: tftpd timeout errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tftpd-timeout-errors/m-p/5141923#M452650</link>
      <description>The tftp service is running because we have Service Guard.</description>
      <pubDate>Thu, 20 Nov 2008 15:07:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tftpd-timeout-errors/m-p/5141923#M452650</guid>
      <dc:creator>Vernita Hall</dc:creator>
      <dc:date>2008-11-20T15:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: tftpd timeout errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tftpd-timeout-errors/m-p/5141924#M452651</link>
      <description>I have not done serviceguard since 2001. Are you sure serviceguard requires the tftp service? Serviceguard and tftp are so contradicting of each other.</description>
      <pubDate>Fri, 21 Nov 2008 12:46:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tftpd-timeout-errors/m-p/5141924#M452651</guid>
      <dc:creator>TTr</dc:creator>
      <dc:date>2008-11-21T12:46:39Z</dc:date>
    </item>
    <item>
      <title>Re: tftpd timeout errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tftpd-timeout-errors/m-p/5141925#M452652</link>
      <description>TTr,&lt;BR /&gt;&lt;BR /&gt;I'm not sure if Service Guard has anything to do with tftp. I noticed when I do "man tftpd" this is one of the statements:&lt;BR /&gt;&lt;BR /&gt;  -s   This option enables tftpd to work in the Service Guard environment.  This option is required for some ftp clients.  These clients reject the tftp reply received&lt;BR /&gt;from a different IP address than the one requested when the server's interface is configured with an alias IP address.&lt;BR /&gt;</description>
      <pubDate>Tue, 25 Nov 2008 15:53:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tftpd-timeout-errors/m-p/5141925#M452652</guid>
      <dc:creator>Vernita Hall</dc:creator>
      <dc:date>2008-11-25T15:53:18Z</dc:date>
    </item>
    <item>
      <title>Re: tftpd timeout errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tftpd-timeout-errors/m-p/5141926#M452653</link>
      <description>Thanks TTr,&lt;BR /&gt;&lt;BR /&gt;Upgrading the igniteUX software enabled&lt;BR /&gt;the tftp service in your server. I disable it in /etc/inetd.conf and reload inetd by "inted -c".&lt;BR /&gt;Everthing is fine now!!!</description>
      <pubDate>Tue, 02 Dec 2008 20:54:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tftpd-timeout-errors/m-p/5141926#M452653</guid>
      <dc:creator>Vernita Hall</dc:creator>
      <dc:date>2008-12-02T20:54:38Z</dc:date>
    </item>
  </channel>
</rss>

