- Community Home
- >
- Servers and Operating Systems
- >
- Servers - General
- >
- HP Power Trust UPS
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-03-2002 08:43 AM
12-03-2002 08:43 AM
HP Power Trust UPS
Dec 3 15:54:09 swhlbu01 /usr/lbin/ups_mond[4120]: /usr/lbin/ups_mond: UPS Moni
tor daemon starting; using configuration file /etc/ups_conf
Dec 3 15:54:09 swhlbu01 /usr/lbin/ups_mond[4120]: /usr/lbin/ups_mond: Failed to
create the named fifo (/var/stm/data/tools/monitor/ups_mond.fifo) to be used as
communication channel with the UPS monitor(EMS). The mkfifo failed with errno
= 2.
Dec 3 15:54:12 swhlbu01 /usr/lbin/ups_mond[4120]: /usr/lbin/ups_mond: UPS /dev/tty1p1 read failed: File exists; Uninterruptable Power Supply has not been connected correctly; loss of power would not be detectible
Dec 3 15:54:18 swhlbu01 /usr/lbin/ups_mond[4120]: /usr/lbin/ups_mond: UPS /dev/tty1p1 read of status failed: File exists
Dec 3 16:03:23 swhlbu01 /usr/lbin/ups_mond[4120]: /usr/lbin/ups_mond: terminated by signal 15
Any help would be greatly appreciated.
- Tags:
- UPS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-03-2002 02:18 PM
12-03-2002 02:18 PM
Re: HP Power Trust UPS
DocID=UCMDSKBRC00010861
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000065140754
Hope this helps ..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-04-2002 01:31 AM
12-04-2002 01:31 AM
Re: HP Power Trust UPS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-04-2002 01:58 AM
12-04-2002 01:58 AM
Re: HP Power Trust UPS
Here's the same document accessible for us Europeans :-)
http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000065140754&admit=-938907319+1038995884055+28353475
HTH,
Vince
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-04-2002 02:31 AM
12-04-2002 02:31 AM
Re: HP Power Trust UPS
You are right, the UPS does not communicate with the server.
The following cookbook should do the trick
1. Verify the ups_mond program is not running. Enter the following to
see if it is.
ps -ef|grep ups
If it is still running, copy the inittab file:
cp /etc/inittab /etc/inittab.backup
2. Edit the /etc/inittab file and look for a line like the following:
ups1::respawn:rtprio 0 /etc/ups_mond -f /etc/ups_conf
Insert a # in front of the line so it looks like the following:
#ups1::respawn:rtprio 0 /etc/ups_mond -f /etc/ups_conf
3. Save your changes and then enter:
init q
Verify with "ps -ef|grep ups" that the /etc/ups_mond program is not
running.
4. Look in /etc/ups_conf and check for the port this program uses. It
is most likely /dev/tty0p1. Use this port for all subsequent commands
where the word PORTNAME is shown.
5. Enter the following command:
kermit
6. At the "C-Kermit>" prompt, enter the following commands:
set line PORTNAME <-----Remember to use name from above!! (I assume it's tty1p1 in your case)
set speed 1200
connect
If ?? displays from ups, it is working fine and you can exit kermit
by skipping to Step 9.
7. If ?? is not displayed, enter the following:
set speed 9600
connect
If ?? is not displayed, try 2400 or 4800 baud. If these baud rates
don't work, the problem may be bad or wrong cable, a device file or mux
board problem, bad UPS, or another process is using the port.
Go to step 9 to exit kermit. This procedure will not work.
8. When ?? is displayed, enter the following:
N <-----------NO Carriage return. You will see NM
set speed 1200
connect
?? should be displayed. If 'CM' is displayed instead, press
to display ??.
9. Enter the following commands:
exit
10. Copy the original inittab file back by entering the following:
cp /etc/inittab.backup /etc/inittab
init q
Verify that the ups_mond program is running.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP