<?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: syslog.log in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log/m-p/3035964#M133490</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Check with "netstat -a" if bootps port is being used, and who is using it, probably another instance of the same program.&lt;BR /&gt;Kill the daemon and restart "inetd -c".&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Zigor</description>
    <pubDate>Tue, 29 Jul 2003 10:52:05 GMT</pubDate>
    <dc:creator>Zigor Buruaga</dc:creator>
    <dc:date>2003-07-29T10:52:05Z</dc:date>
    <item>
      <title>syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log/m-p/3035960#M133486</link>
      <description>I'm getting the following message every ten minutes in my syslog.log and don't know where to look to fix the problem.&lt;BR /&gt;&lt;BR /&gt;Jul 29 07:14:06 Avenger inetd[13805]: bootps/udp: bind: Address already in use&lt;BR /&gt;Jul 29 07:14:06 Avenger inetd[13805]: bootps/udp: Service enabled&lt;BR /&gt;Jul 29 07:24:06 Avenger inetd[13805]: bootps/udp: bind: Address already in use&lt;BR /&gt;Jul 29 07:24:06 Avenger inetd[13805]: bootps/udp: Service enabled&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Jul 2003 10:34:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log/m-p/3035960#M133486</guid>
      <dc:creator>Jim Spencer_1</dc:creator>
      <dc:date>2003-07-29T10:34:56Z</dc:date>
    </item>
    <item>
      <title>Re: syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log/m-p/3035961#M133487</link>
      <description>This almost certainly means that the inetd daemon is trying to bind to the bootp port but some other process has already opened it.&lt;BR /&gt;If you have lsof installed you can use it to find the process.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Michael.</description>
      <pubDate>Tue, 29 Jul 2003 10:46:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log/m-p/3035961#M133487</guid>
      <dc:creator>Michael Kelly_5</dc:creator>
      <dc:date>2003-07-29T10:46:46Z</dc:date>
    </item>
    <item>
      <title>Re: syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log/m-p/3035962#M133488</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Try&lt;BR /&gt;&lt;BR /&gt;a:Comment out the bootp entry in inetd.conf&lt;BR /&gt;b:inetd -c&lt;BR /&gt;c:Then kill the bootpd that is running&lt;BR /&gt;d:inetd -c&lt;BR /&gt;e:Reverse the first step and remove the        comment on the bootp entry in inetd.conf&lt;BR /&gt;f:inetd -c&lt;BR /&gt;&lt;BR /&gt;Look for the latest patch&lt;BR /&gt;&lt;BR /&gt;        Steve Steel</description>
      <pubDate>Tue, 29 Jul 2003 10:47:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log/m-p/3035962#M133488</guid>
      <dc:creator>Steve Steel</dc:creator>
      <dc:date>2003-07-29T10:47:52Z</dc:date>
    </item>
    <item>
      <title>Re: syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log/m-p/3035963#M133489</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;If inetd was killed with a -k option while bootpd was running, this&lt;BR /&gt;is the result.  Inetd will start a bootpd process on demand and that&lt;BR /&gt;process will service new bootpd requests for a set period of time&lt;BR /&gt;before it exits due to no more bootp requests. This causes the&lt;BR /&gt;UDP port for bootpd to be held "open" by the running bootpd process,&lt;BR /&gt;even after you have killed the inetd process with the "inetd -k".&lt;BR /&gt;If you kill running bootpd, then run #inetd -c, it should stop.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Jerome</description>
      <pubDate>Tue, 29 Jul 2003 10:49:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log/m-p/3035963#M133489</guid>
      <dc:creator>Jerome Baron</dc:creator>
      <dc:date>2003-07-29T10:49:56Z</dc:date>
    </item>
    <item>
      <title>Re: syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log/m-p/3035964#M133490</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Check with "netstat -a" if bootps port is being used, and who is using it, probably another instance of the same program.&lt;BR /&gt;Kill the daemon and restart "inetd -c".&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Zigor</description>
      <pubDate>Tue, 29 Jul 2003 10:52:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log/m-p/3035964#M133490</guid>
      <dc:creator>Zigor Buruaga</dc:creator>
      <dc:date>2003-07-29T10:52:05Z</dc:date>
    </item>
    <item>
      <title>Re: syslog.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log/m-p/3035965#M133491</link>
      <description>Might be an address being served by bind and bootps.&lt;BR /&gt;&lt;BR /&gt;The bootps service lets you boot other boxes off your system into Ignite Disaster Recovery and lets you push or pull Ignite images.&lt;BR /&gt;&lt;BR /&gt;You might try /opt/ignite/bin/ignite and reconfigure the IP address assigned to the process.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 29 Jul 2003 10:53:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log/m-p/3035965#M133491</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-07-29T10:53:15Z</dc:date>
    </item>
  </channel>
</rss>

