I have a Dell PE 2850 connected via 940-0024C cable to serial port on the UPS
mentioned above.
I've used apt-get to install nut-2.0.2-3 and attempted to configure based on
the documentation.
So far I'm getting the following when I try to start ups daemon:
server:/etc/ups # /etc/init.d/ups start
Starting service NUT:
-> Starting UPS driver:
Network UPS Tools - UPS driver controller 2.0.2
Network UPS Tools (version 2.0.2) - APC Smart protocol driver
Driver version 1.99.7, command table version 2.0
Detected Smart-UPS RT 3000 XL [NS0545001690 ] on /dev/ttyS0
done
-> Starting upsd:
Network UPS Tools upsd 2.0.2
done
-> Starting upsmon:
Network UPS Tools upsmon 2.0.2
UPS: myups@10.133.1.51 (master) (power value 1)
Using power down flag file /etc/killpower
stat /etc/ups/upsd.conf: No such file or directory
Broadcast Message from nobody@server
(somewhere) at 15:35 ...
Communications with UPS myups@10.133.1.51 lost
done
server:/etc/ups #
Broadcast Message from nobody@server
(somewhere) at 15:35 ...
UPS myups@10.133.1.51 is unavailable
When I try upsc I get the following:
server:/etc/ups # upsc myups@10.133.1.51:3493
Error: Connection failure: Connection refused
I'm not sure if it's permissions:
server:/etc/ups # ls -la /etc/ups/
total 39
drwxr-xr-x 2 root root 184 Aug 31 14:56 .
drwxr-xr-x 68 root root 7208 Aug 31 14:54 ..
-rw-r----- 1 nut nut 3827 Aug 31 14:56 ups.conf
-rw-r----- 1 nut nut 11144 Aug 31 14:56 upsmon.conf
and...
ls -la /dev |grep ttyS0
crw-rw-rw- 1 nut nut 4, 64 Aug 31 15:35 ttyS0
Heres' the confs
ups.conf
MONITOR myups@10.133.1.51 1 nut password master
[myups]
driver = apcsmart
port = /dev/ttyS0
sdtype = 0
desc = "automatically configured device"
upsmon:
MONITOR myups@10.133.1.51 1 nut password master
...and the rest defaults
-----------------------------------------------------------------
This email message is intended only for the addressee(s)
and contains information that may be confidential and/or
copyrighted. If you are not the intended recipient please
notify the sender by reply email and immediately delete
this email. Use, disclosure or reproduction of this email
by anyone other than the intended recipient(s) is strictly
prohibited. USIT has scanned this email for viruses and
dangerous content and believes it to be clean. However,
virus scanning is ultimately the responsibility of the recipient.
-----------------------------------------------------------------
On 9/4/06, Chris Boyd <chris@usit.ie> wrote:> stat /etc/ups/upsd.conf: No such file or directoryThis is key. ups.conf configures the drivers, whereas upsd.conf controls access to the driver from the network. If you are setting up a standalone system, you can use this as a starting point for upsd.conf: #=====================ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all #===================== For more details, run 'man upsd.conf' -- - Charles Lepple
OK I've changed to a different machine as I don't think it install all
of nut. Now I'm working with nut-1.2.2
I changed the driver to newapc and it's now finding the RT 3000 correctly.
I'm still getting the reject TCP in messages:
upsd[17078]: Rejecting TCP connection from 10.133.1.49
Sep 5 15:00:35 usit-hq-s03 upsmon[17077]: Poll UPS [myups@10.133.1.49] failed -
Read error: No such file or directory
I've set the owner to nobody after trying to creating a user and setting it
as owner on the conf files as well as /dev/ttyS0.
Here is the message I get when starting ups:
Starting service NUT:
Network UPS Tools - UPS driver controller 1.2.2
Network UPS Tools (version 1.2.2) - APC Smart protocol driver
Driver version 1.4, command table version 1.2
Detected Smart-UPS RT 3000 XL [NS0545001690 ] on /dev/ttyS0
Network UPS Tools - UPS driver controller 1.2.2
Network UPS Tools upsd 1.2.2
/var/lib/ups is world readable
Read data for UPS [myups] successfully
Data source for UPS [myups]: newapc-ttyS0
Network UPS Tools upsmon 1.2.2
UPS: myups@10.133.1.49 (master) (power value 1)
Using power down flag file /etc/killpower
done
Broadcast Message from nobody@usit-hq-s03
(somewhere) at 15:00 ...
UPS myups@10.133.1.49 is unavailable
Here are the changes to the conf files:
ups.conf
[myups]
driver = newapc
port = /dev/ttyS0
cable = 940-0024C
sdtype = 0
upsd.conf
ACL all 0.0.0.0/0
ACL localhost 127.0.0.1/32
ACL usit 10.133.0.0/16
ACCESS grant monitor localhost usit
ACCESS deny all all
upsd.users
[monuser]
password = password
allowfrom = usit
upsmon master
upsmon.conf
RUN_AS_USER nobody
MONITOR myups@10.133.1.49 1 monuser password master
>>> "Charles Lepple" <clepple@gmail.com> 09/04/06 4:41
>>>
On 9/4/06, Chris Boyd <chris@usit.ie> wrote:> stat /etc/ups/upsd.conf: No such file or directory
This is key.
ups.conf configures the drivers, whereas upsd.conf controls access to
the driver from the network.
If you are setting up a standalone system, you can use this as a
starting point for upsd.conf:
#=====================ACL all 0.0.0.0/0
ACL localhost 127.0.0.1/32
ACCEPT localhost
REJECT all
#=====================
For more details, run 'man upsd.conf'
--
- Charles Lepple
-----------------------------------------------------------------
This email message is intended only for the addressee(s)
and contains information that may be confidential and/or
copyrighted. If you are not the intended recipient please
notify the sender by reply email and immediately delete
this email. Use, disclosure or reproduction of this email
by anyone other than the intended recipient(s) is strictly
prohibited. USIT has scanned this email for viruses and
dangerous content and believes it to be clean. However,
virus scanning is ultimately the responsibility of the recipient.
-----------------------------------------------------------------
Anyone have any ideas? Sorry I'm just stuck at this point.>>> "Chris Boyd" <chris@usit.ie> 09/05/06 3:09 >>>OK I've changed to a different machine as I don't think it install all of nut. Now I'm working with nut-1.2.2 I changed the driver to newapc and it's now finding the RT 3000 correctly. I'm still getting the reject TCP in messages: upsd[17078]: Rejecting TCP connection from 10.133.1.49 Sep 5 15:00:35 usit-hq-s03 upsmon[17077]: Poll UPS [myups@10.133.1.49] failed - Read error: No such file or directory I've set the owner to nobody after trying to creating a user and setting it as owner on the conf files as well as /dev/ttyS0. Here is the message I get when starting ups: Starting service NUT: Network UPS Tools - UPS driver controller 1.2.2 Network UPS Tools (version 1.2.2) - APC Smart protocol driver Driver version 1.4, command table version 1.2 Detected Smart-UPS RT 3000 XL [NS0545001690 ] on /dev/ttyS0 Network UPS Tools - UPS driver controller 1.2.2 Network UPS Tools upsd 1.2.2 /var/lib/ups is world readable Read data for UPS [myups] successfully Data source for UPS [myups]: newapc-ttyS0 Network UPS Tools upsmon 1.2.2 UPS: myups@10.133.1.49 (master) (power value 1) Using power down flag file /etc/killpower done Broadcast Message from nobody@usit-hq-s03 (somewhere) at 15:00 ... UPS myups@10.133.1.49 is unavailable Here are the changes to the conf files: ups.conf [myups] driver = newapc port = /dev/ttyS0 cable = 940-0024C sdtype = 0 upsd.conf ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACL usit 10.133.0.0/16 ACCESS grant monitor localhost usit ACCESS deny all all upsd.users [monuser] password = password allowfrom = usit upsmon master upsmon.conf RUN_AS_USER nobody MONITOR myups@10.133.1.49 1 monuser password master>>> "Charles Lepple" <clepple@gmail.com> 09/04/06 4:41 >>>On 9/4/06, Chris Boyd <chris@usit.ie> wrote:> stat /etc/ups/upsd.conf: No such file or directoryThis is key. ups.conf configures the drivers, whereas upsd.conf controls access to the driver from the network. If you are setting up a standalone system, you can use this as a starting point for upsd.conf: #=====================ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all #===================== For more details, run 'man upsd.conf' -- - Charles Lepple ----------------------------------------------------------------- This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyrighted. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. USIT has scanned this email for viruses and dangerous content and believes it to be clean. However, virus scanning is ultimately the responsibility of the recipient. ----------------------------------------------------------------- _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ----------------------------------------------------------------- This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyrighted. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. USIT has scanned this email for viruses and dangerous content and believes it to be clean. However, virus scanning is ultimately the responsibility of the recipient. -----------------------------------------------------------------
On 9/7/06, Chris Boyd <chris@usit.ie> wrote:> Anyone have any ideas?Not for NUT 1.2, no. That version is very old, and a number of fundamental changes have been made since then. -- - Charles Lepple
I suspected as much. For some reason installing nut using apt didn't dl all the config files. SuSE isn't the greatest with apt (nor YAST). Anyway I copied over the old config files from 1.2.2 server to the 2.0.2 server, changed ACCESS to ACCEPT and shangri la. Thanks a milion>>> "Charles Lepple" <clepple@gmail.com> 09/07/06 2:14 >>>On 9/7/06, Chris Boyd <chris@usit.ie> wrote:> Anyone have any ideas?Not for NUT 1.2, no. That version is very old, and a number of fundamental changes have been made since then. -- - Charles Lepple ----------------------------------------------------------------- This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyrighted. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. USIT has scanned this email for viruses and dangerous content and believes it to be clean. However, virus scanning is ultimately the responsibility of the recipient. -----------------------------------------------------------------