Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hi folks, I've been trying to install the Network UPS Tools (http://dns323.kood.org/howto:nut_ups) for a couple of days now, without success... help would be appreciated...
So far, I've installed the 3 packages required, created "nut" gorup and "nutmon" user. Now I'm trying to configure everything, by editing files ups.conf, upsd.conf & upsd.users. Weird thing, it seems like my box is trying to read info from files in /usr/local/ups/etc/ and not /ffp/etc. Problem is, the 3 files at /usr/local/ups/etc seem to be recreated if I reboot the box... The only way I can make upsdrvctl work, is by cp all 3 files to /usr/local/ups/etc . upsdrvctl was able to load correctly, but upsd was not... was stating a few line like ACCEPT no longer supported.... If I checked the process, I could not find a process related to upsd. The command upsd -c stop did not work either. Frankly, I don't konw where to go from here... can anyone help? thanks!
If I delete the info in /usr/local/ups/etc I get this error :
root@serveur_bkp:/mnt/HD_a2/ffp/etc# upsdrvctl start Network UPS Tools - UPS driver controller 2.2.0- Can't open /usr/local/ups/etc/ups.conf: Can't open /usr/local/ups/etc/ups.conf: No such file or directory root@serveur_bkp:/mnt/HD_a2/ffp/etc#
elseif I cp the files from /ffp/etc to /usr/local/ups/etc/ (but then I loose them at a reboot) :
root@serveur_bkp:/mnt/HD_a2/ffp/etc# upsdrvctl start Network UPS Tools - UPS driver controller 2.2.0- Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) Using subdriver: APC HID 0.92 root@serveur_bkp:/mnt/HD_a2/ffp/etc# upsd Network UPS Tools upsd 2.4.1 ACL in upsd.conf is no longer supported - switch to LISTEN ACL in upsd.conf is no longer supported - switch to LISTEN ACL in upsd.conf is no longer supported - switch to LISTEN ACCEPT in upsd.conf is no longer supported - switch to LISTEN ACCEPT in upsd.conf is no longer supported - switch to LISTEN REJECT in upsd.conf is no longer supported - switch to LISTEN not listening on 127.0.0.1 port 3493 root@serveur_bkp:/mnt/HD_a2/ffp/etc#
root@serveur_bkp:/mnt/HD_a2/ffp/etc# ps PID USER COMMAND 2270 root /web/webs 2279 root crond 2305 root sshd: root@pts/0 2325 root -sh 2376 root /usr/local/ups/bin/usbhid-ups -a usbhid 2412 root /usr/local/ups/bin/usbhid-ups -a usbhid -u root 3165 root /usr/local/ups/bin/usbhid-ups -a APC_UPS 3185 root /usr/local/ups/bin/usbhid-ups -a APC_UPS 3289 root ps root@serveur_bkp:/mnt/HD_a2/ffp/etc#
root@serveur_bkp:/mnt/HD_a2/ffp/etc# upsd -c stop Network UPS Tools upsd 2.4.1 fopen /ffp/var/state/ups/upsd.pid: No such file or directory root@serveur_bkp:/mnt/HD_a2/ffp/etc#
root@serveur_bkp:/mnt/HD_a2/ffp/etc# ls -al -rwxr--r-- 1 root root 3754 Jun 9 2010 ups.conf -rwxr--r-- 1 root nut 2054 Jun 9 2010 upsd.conf -rwxr--r-- 1 root nut 2166 Jun 9 2010 upsd.users root@serveur_bkp:/mnt/HD_a2/ffp/etc#
Last edited by seth889 (2010-06-09 04:39:30)
Offline
Whenever you see a reference to 2.2.0, it is the older version contained in the DNS firmware. You need to stop those processes before you start the ones in the ffp package. I put this in my fun_plug.local file:
/usr/sbin/upsd -c stop /usr/sbin/upsdrvctl stop
Then make sure you specifically start the newer release by including the full path:
/ffp/bin/upsdrvctl start /ffp/sbin/upsd /ffp/sbin/upsmon
Offline
Good, thank you very much, I realized indeed that it was running 2.2.0 and not the 2.4.1. Solved the problem. thanks
Offline
By the way, I tried to test NUT by pulling out the plug of the power outlet, UPS took over, but DNS323 did not shutdown... I also installed cleanboot (from another post on a forum, for a clea shutdown) but still did not do anything. Am I missing something? Search info on the wiki and the NUT homepage, but did not find anything usefull.... any idea why it is not shuthing down? or how I can investigate? I can shutdown via ssh with "shutdown" command without problem...
thanks
Last edited by seth889 (2010-06-10 23:29:23)
Offline
NUT will not start a shutdown until the UPS reaches a low battery state. Depending on the UPS you can control where this threshold is. If you want to test the shutdown process, you can simulate a low battery status with upsmon to make sure the shutdown works as you want.
/ffp/sbin/upsmon -c fsd
This signals upsmon to perform a forced shutdown. I have cleanboot installed as well and it all works very smoothly. I also have my PC set up as a slave so that it gets shutdown too.
Offline
Yes thanks, just found out a few hours earlier that I had an error in the name of my hostname in upsd.conf ... was preventing upsmon to monitor the UPS thus not reacting to critical battery... now works like a charm ;-)
I tried to set up my winxp machine with Winut... I can'T get it to connect to my dns323 ... always says it is not capable of connecting... I did create a user in upsd.users (with pass, allow and slave) and in upsd.conf with ACL and ACCEPT, but nothing... any toughts?
Offline
The later versions of upsd don't use the ACL, ACCEPT, and REJECT parameters. You have to use LISTEN instead. My upsd.conf simply contains:
LISTEN 0.0.0.0 3493
Offline
I see... thank I fixed it... and for WinNUT ? are you using it?
Offline
Yes I use WinNUT and it can connect and be a slave with that upsd config.
Offline
What did you use in the upsd.conf file for winnut itself? I can't get it to connect... I use the winmonuser I created on the dns323 with password, but keep getting Connection lost blablabla as soon as I hit the "start winnut"...
Offline
In WinNUT's upsmon.conf I have:
MONITOR usbhid@dns323 1 monuser monpass slave
In my case "dns323" is the host name and "usbhid" is the UPS name from /ffp/etc/ups.conf:
[usbhid] driver = usbhid-ups port = auto
Offline