UPS shutdown
-
you were right… error while reading...
it's the 24 cable...
but after reinstalling it does still not work :-(
-
you were right… error while reading...
it's the 24 cable...
but after reinstalling it does still not work :-(
I'm really confused. I have both cables 940-0024C and 940-0095B sitting here in front of me and they both work. I have an APC SmartUPS 700. Are you sure the cable is good? Have you tested it with the APC monitoring software by chance?
Also if the nut status screen shows wait, refresh your browser as its still negotiating with the UPS.
-
How can I check, why the service won't start ?
any idea ? -
How can I check, why the service won't start ?
any idea ?Configure nut via the webgui. Then go to the console and run
/usr/local/libexec/nut/upsdrvctl start
You should see something like
Detected SMART-UPS 700 [serialnum] on /dev/ttyd0
Otherwise it will give you an error message. The config files are stored in /usr/local/etc/nut/ If you get it working let me know what you changed to make it work.
After you get that far then you run the following commands. Be sure to replace myups with the name you gave your ups in the nut config.
/usr/local/sbin/upsd
/usr/local/sbin/upsmon myups@localhostBoth the above commands should tell you they were successfully executed.
-
so… the error was some "spaces" in the UPS name...
just use [a-z],[A-Z],[0-9]
sometime later there will be some update by
@rsw686;D now it works !!! ;D
-
so… the error was some "spaces" in the UPS name...
just use [a-z],[A-Z],[0-9]
sometime later there will be some update by
@rsw686;D now it works !!! ;D
I put the necessary checks in place so this shouldn't happen to anybody else. :) I also improved the status page. To get the latest reinstall the package via the webgui.
-
jepp… looks nice now :-)
alpha status should be changed to beta soon, I think ;-) -
Has anyone else tried to get NUT going on a Nokia IP330? I have the package installed but it will not recognize any cable I throw at it. I have an APC Back-UPS Pro 650, which connects fine to my pc via the 2 different cables I have.
-
Has anyone else tried to get NUT going on a Nokia IP330? I have the package installed but it will not recognize any cable I throw at it. I have an APC Back-UPS Pro 650, which connects fine to my pc via the 2 different cables I have.
How many serial ports on your IP330. The bottom one is always the console port. If that is all you have you will have to add a second serial port above it. All IP330s have the hole in the metal, just the sticker on the front is different. Find or buy one of the below serial port adapters. On the board there is a jumper to move from the modem to the serial port. Then you just plug the ribbon cable in and screw it in the front of the IP330.
Here is a pic from a website I found showing the jumper. I did this mod on mine as it originally had the modem exposed. I have not tested out NUT on it, but will try it in the next day or so and let you know.
http://criggie.dyndns.org/tech/ip330/images/jumper1.jpg
My IP330 is shown below. The pic is before I rearranged the rack. I painted it black as the sticker on the front was peeling off and it matches everything else I have. As you can see the modem is on the far right.
-
thanks for your response, I didnt even notice the cutout was already there, but will def. try this.
-
thanks for your response, I didnt even notice the cutout was already there, but will def. try this.
Hmm I just hooked up a ups to my ip330 on com2, and I couldn't get it to work. I have an embedded install on there so that might be part of the issue. When I try and start the driver control I get the error
Can't uu_lock ttyd1: creat error: No such file or directory
I'll have to look into this some more and see if I can get it to work. The IP330 is my main box and I don't really plan on switching to the full install to test this. Let me know if you find out anything different.
EDIT:
I'm making progress, I had to mkdir /var/spool/lock and set the permissions as this was missing on the embedded installs. There might be something missing from the embedded install to get this to work. I would be interested in seeing how it works out for you since you have a full install.
-
I noticed that the NUT service will NOT start after a firmware upgrade…
after hitting "change" button in NUT settings it runs again...
perhaps that should be fixed... ;)
-
I noticed that the NUT service will NOT start after a firmware upgrade…
after hitting "change" button in NUT settings it runs again...
perhaps that should be fixed... ;)
I don't have the slightest clue why that is happening. Any errors in the logs? Do any packages start? Feel free to submit a fix.
-
As far as getting my APC UPS to work with the ip330 I have only gotten it to work in simple signaling mode, meaning I'm using APC Back-UPS as the UPS type. Either my serial ribbon cable going to the board is bad or the IP330 has some issue with serial communication.
-
Hmm I just hooked up a ups to my ip330 on com2, and I couldn't get it to work. I have an embedded install on there so that might be part of the issue. When I try and start the driver control I get the error
Can't uu_lock ttyd1: creat error: No such file or directory
I installed the NUT package on a fresh hard drive based SNAPSHOT-02-14-2007 and get a similar error (for ttyd0) on a box that worked fine under win32 (com1) for an APC BackUPS Pro with the 95B cable in full signal mode. I tried all the various permutations from the webgui with no go. Went to the shell and hand ran the various nut binaries to see what I could figure out. At first I thought it had to do with settings in /etc/ttys for the various ttydX, especially ttyd0 due to the console definitions. But after eliminating that and a few other things, I'm still at a loss.
I'll try hand editing the ups.conf and try setting it to simple signaling like you did to see what happens.
-
Hmm I just hooked up a ups to my ip330 on com2, and I couldn't get it to work. I have an embedded install on there so that might be part of the issue. When I try and start the driver control I get the error
Can't uu_lock ttyd1: creat error: No such file or directory
I installed the NUT package on a fresh hard drive based SNAPSHOT-02-14-2007 and get a similar error (for ttyd0) on a box that worked fine under win32 (com1) for an APC BackUPS Pro with the 95B cable in full signal mode. I tried all the various permutations from the webgui with no go. Went to the shell and hand ran the various nut binaries to see what I could figure out. At first I thought it had to do with settings in /etc/ttys for the various ttydX, especially ttyd0 due to the console definitions. But after eliminating that and a few other things, I'm still at a loss.
I'll try hand editing the ups.conf and try setting it to simple signaling like you did to see what happens.
Does the /var/spool/lock directory exist? If you create that directory and run chown uucp:dialer /var/spool/lock does it work? If so I will put a check to make sure that directory exists and if not create it. All the full installs I've seen have already had it, but something might have changed.
From your post you have the console running on ttyd0. The only thing I can think of is that there is some conflict when the console is being directed to a serial port and using other serial ports.
-
Does this package work with a USB type interface…..I can't seem to get it to work. I have a APC Back-UPS 1500 XS/RS.
-
I commited a fix that will ensure that /var/spool/lock is present and create the directory if it is not. Please reinstall the package and try again. If it still does not work run
/usr/local/libexec/nut/upsdrvctl start
from the console and let me know the error message. Also do you have the console redirected to the serial port or no?
-
Does this package work with a USB type interface…..I can't seem to get it to work. I have a APC Back-UPS 1500 XS/RS.
Supposedly it does, but I have no USB UPS's to test with. On the settings page select APC Back-UPS LS USB. Configure the port as auto. If you still can't get it to work run
/usr/local/libexec/nut/upsdrvctl start
from the console and let me know the error message.
The LS and RS use the same driver. I will add the RS to the drop down list.
-
I get this in my logs…......Feb 19 12:10:27 last message repeated 7 times
Feb 19 12:10:27 last message repeated 7 times
Feb 19 12:09:52 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connected
Feb 19 12:09:52 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connected
Feb 19 12:09:47 upsmon[20333]: UPS apc1500@localhost is unavailable
Feb 19 12:09:47 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connected
Feb 19 12:09:47 upsmon[20333]: UPS apc1500@localhost is unavailable
Feb 19 12:09:47 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connected
Feb 19 12:09:42 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connected
Feb 19 12:09:42 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connected
Feb 19 12:09:41 upsd[20329]: Can't connect to UPS [apc1500] (apc1500): Permission denied
Feb 19 12:09:37 last message repeated 6 times
Feb 19 12:09:41 upsd[20329]: Can't connect to UPS [apc1500] (apc1500): Permission denied
Feb 19 12:09:37 last message repeated 5 times
Feb 19 12:09:12 last message repeated 24 times
Feb 19 12:09:07 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connectedAnd this is what this says….....$ /usr/local/libexec/nut/upsdrvctl start
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5)Network UPS Tools - UPS driver controller 2.0.5