Topic: NUT Configuration on SME7

[robertmcgill]

I am setting up a Belkin F6H650-SER on a fresh SME7 install.  This UPS works with NUT with the genericups driver.  I have read through the howto and other posts about configuring NUT under SME7.  The problem I am having is setting the upstype value (it's supposed to be set to upstype=7).  Does anyone know if there is a label for setting this value in the system configuration database and templating system?

The UPS has a serial interface and works when started manually (I followed the testing instructions for the genericups man page):

login as: root
root@gretel's password:
Last login: Mon Aug 21 15:37:08 2006 from pc-00106.robertmcgilllaw.com
[root@gretel ~]# genericups -x upstype=7 /dev/ttyS0
Network UPS Tools - Generic UPS driver 1.31 (2.0.3-pre2)
UPS type: CyberPower Power99
[root@gretel ~]#
Broadcast message from nut (Mon Aug 21 15:50:11 2006):

Communications with UPS UPS@localhost established

[root@gretel ~]# upsc UPS@localhost
driver.name: genericups
driver.parameter.upstype: 7
driver.version: 2.0.3-pre2
driver.version.internal: 1.31
ups.mfr: CyberPower
ups.model: Power99
ups.status: OL
[root@gretel ~]#

When I unplug the UPS, the system complains about it and when I do "genericups -x upstype=7 /dev/ttyS0" the computer shuts down like it's supposed to.

Any help would be much appreciated.

[brianr]

Have you tried editting in the upstype into the /etc/ups/ups.conf?  This would validate your parameters.  Remeber this is only a temporary fix though.

Not sure how to get the upstype in the ups.conf file "properly", possible a custom template?

[robertmcgill]

Brian--Thanks for offering your assistance.  I tried to manually edit the upstype in /etc/ups/ups.conf and it didn't seem to help.  That's okay, however, as I have a few other things keeping me busy for the time being.

[raem]

robertmcgill

> I tried to manually edit the upstype in /etc/ups/ups.conf and it didn't seem to help.  


Restart the nut service after making config changes
/etc/init.d/nut restart

[byte]

/etc/init.d/nut restart

Remember it's /etc/rc7.d/S**nut restart where ** is the number.

Come on Ray you should know that    

[brianr]

actually either will work, but the reccommended way to restart services in SME7 is:

svc -t /var/service/nut

[fern]

byte

>>> /etc/init.d/nut restart
>> /etc/rc7.d/S**nut restart where ** is the number.
> svc -t /var/service/nut

/etc/init.d is a link to /etc/rc.d/init.d
/etc/rc7.d is a link to /etc/rc.d/rc7.d
/service is a link to /var/service

If anyone can explain it better please do, I'm happy to be corrected.
As I read it the first command will be OK where the service is not supervised.
The other commands mentioned are more correct as they look to see if it is a supervised service & enabled or not in the db.
In this particular case of nut the svc command did not work as there is no nut service in /var/service.
The nitty gritty is in the dev guide Chapter 9.

/etc/init.d/nut status
newhidups is stopped
upsd is stopped
upsmon is stopped

/etc/rc7.d/S15nut status
newhidups is stopped
upsd is stopped
upsmon is stopped

svc -t /var/service/nut
svc: warning: unable to chdir to /var/service/nut: file does not exist

svc -t /service/nut
svc: warning: unable to chdir to /service/nut: file does not exist


On a system where nut is not enabled

/etc/init.d/nut restart

Stopping UPS monitor:                                      [FAILED]
Stopping upsd:                                             [FAILED]
Shutting down newhidups:                                   [FAILED]
Starting newhidups: Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3-pre2)
No matching USB/HID UPS found                 [FAILED]
Starting upsd:                                             [  OK  ]
Starting UPS monitor (master):                             [  OK  ]

Broadcast message from nut (Sun Sep 10 22:24:13 2006):
Communications with UPS UPS@localhost lost
Broadcast message from nut (Sun Sep 10 22:24:18 2006):
UPS UPS@localhost is unavailable

/etc/init.d/nut stop
Stopping UPS monitor:                                      [  OK  ]
Stopping upsd:                                             [  OK  ]
Shutting down newhidups:                                   [FAILED]


/etc/rc7.d/S15nut restart

This command gave no response as nut was not enabled therefore did not get (re)started.

[fern]

byte

> /etc/rc7.d/S15nut restart
> This command gave no response as nut was not enabled therefore did
> not get (re)started.

...and for completeness...

config show nut

nut=service
    Model=newhidups
    status=disabled


config setprop nut status enabled
config show nut

nut=service
    Model=newhidups
    status=enabled

/etc/rc7.d/S15nut restart
(which now gives a different response as nut was enabled in the db)

Stopping UPS monitor:                                      [FAILED]
Stopping upsd:                                             [FAILED]
Shutting down newhidups:                                   [FAILED]
Starting newhidups: Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3-pre2)

No matching USB/HID UPS found                 [FAILED]
Starting upsd:                                             [  OK  ]
Starting UPS monitor (master):                             [  OK  ]

Broadcast message from nut (Sun Sep 10 22:38:42 2006):

Communications with UPS UPS@localhost lost

Broadcast message from nut (Sun Sep 10 22:38:47 2006):

UPS UPS@localhost is unavailable


/etc/rc7.d/S15nut stop

Stopping UPS monitor:                                      [  OK  ]
Stopping upsd:                                             [  OK  ]
Shutting down newhidups:                                   [FAILED]