<?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: ups_mond ups_cond dev file problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ups-mond-ups-cond-dev-file-problem/m-p/3881909#M280097</link>
    <description>Ooops, I forgot to report that upon starting ups_mond the syslog msg was:&lt;BR /&gt;/usr/lbin/ups_mond[1600]: /usr/lbin/ups_mond: UPS /dev/&lt;BR /&gt;tty1p0 write failed: Bad file number; ignoring that UPS&lt;BR /&gt;&lt;BR /&gt;Thanks in advance,&lt;BR /&gt;Doug</description>
    <pubDate>Tue, 17 Oct 2006 15:41:35 GMT</pubDate>
    <dc:creator>Doug_3</dc:creator>
    <dc:date>2006-10-17T15:41:35Z</dc:date>
    <item>
      <title>ups_mond ups_cond dev file problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ups-mond-ups-cond-dev-file-problem/m-p/3881908#M280096</link>
      <description>Our ups_mond and ems had been turned off for our power trust ups on an hp9000 (rp7400).  Upon restart we are seeing this messsage:&lt;BR /&gt;/usr/lbin/ups_mond: AC Power&lt;BR /&gt; to all recognized, system critical UPS's OK! System will not shutdown.&lt;BR /&gt;Oct 17 13:27:17 sd81hp9k /usr/lbin/ups_mond[22628]: /usr/lbin/ups_mond: UPS /dev&lt;BR /&gt;/tty1p0 interrupted but read of ups status failed - possible UPS hardware problem&lt;BR /&gt;&lt;BR /&gt;The ups_conf is pointing to tty1p0 and the character file exists with these rights:&lt;BR /&gt;crw--w--w- 1 bin bin 1 0x010000 Oct 17 12:18 /dev/tty1p0&lt;BR /&gt;&lt;BR /&gt;Ideas on why the ups_mond can claim the ups is ok but the second msg is claiming it can't read the status of the ups?&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Oct 2006 15:38:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ups-mond-ups-cond-dev-file-problem/m-p/3881908#M280096</guid>
      <dc:creator>Doug_3</dc:creator>
      <dc:date>2006-10-17T15:38:49Z</dc:date>
    </item>
    <item>
      <title>Re: ups_mond ups_cond dev file problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ups-mond-ups-cond-dev-file-problem/m-p/3881909#M280097</link>
      <description>Ooops, I forgot to report that upon starting ups_mond the syslog msg was:&lt;BR /&gt;/usr/lbin/ups_mond[1600]: /usr/lbin/ups_mond: UPS /dev/&lt;BR /&gt;tty1p0 write failed: Bad file number; ignoring that UPS&lt;BR /&gt;&lt;BR /&gt;Thanks in advance,&lt;BR /&gt;Doug</description>
      <pubDate>Tue, 17 Oct 2006 15:41:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ups-mond-ups-cond-dev-file-problem/m-p/3881909#M280097</guid>
      <dc:creator>Doug_3</dc:creator>
      <dc:date>2006-10-17T15:41:35Z</dc:date>
    </item>
    <item>
      <title>Re: ups_mond ups_cond dev file problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ups-mond-ups-cond-dev-file-problem/m-p/3881910#M280098</link>
      <description>I ran into something similar with a software &lt;BR /&gt;product that uses /dev/lan1. I had to change&lt;BR /&gt;the perms to 666. And I had to do that &lt;BR /&gt;everytime the system was rebooted.&lt;BR /&gt;What owner is ups_mond running as?</description>
      <pubDate>Tue, 17 Oct 2006 17:32:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ups-mond-ups-cond-dev-file-problem/m-p/3881910#M280098</guid>
      <dc:creator>jerry1</dc:creator>
      <dc:date>2006-10-17T17:32:22Z</dc:date>
    </item>
  </channel>
</rss>

