Re: [Nut-upsuser] Sweex 1000VA UPS
On 11/11/06, Arjen de Korte [EMAIL PROTECTED] wrote: The problem was the serial cable. That why I recommended to try it under Windows with the bundled software, to rule out a problem like this. I see. For contact closure type UPSes, they almost never are. Ok, I will remember that! I don't know if the ups will actually shutdown the system now on low battery. Assuming that the monitoring works (which looks like it), it probably will, as you already found out during earlier tests where your system kept on rebooting when the serial cable was not connected. This is essentially the same as OB LB for upstype=7. Yes, but I just want to be sure tht the state LB is going to show up. When this happens I'm pretty sure the thing will do what it's supposed to do. I'm also wondering if the system will boot up when the powerline comes online again. That would be very nice! upsc ain't showing much information on the battery status here, but as far as I remember I've read somewhere in the docs that this is normal with genericups drivers, not? On Battery and Low Battery are the only two status signals available, so no fancy voltage readings, load percentages and battery charge. If you want that, you need a smarter UPS. I don't really care about those fancy readings. I'm not watching those stats all day :-) If it does what it should do and protect my system in a decent way on powerfails, I'm more then happy! [...] Good! I'm glad that in the end things worked out for you. So am I, Thanks again for all your help and pointings in the redirection. Kind regards, Yves ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
On 11/12/06, Sergiy Kazakov [EMAIL PROTECTED] wrote: To prevent system shutdown on LB while testing you may set powervalue value in MONITOR line (in upsmon.conf) to 0 (zero). But don't forget to set MINSUPPLIES to zero too. See comments in upsmon.conf and man upsmon.conf for further details. Whith this one you can check if the other parts of nut getting read on LB. Also you can setup non-critical workstation as slave (even MS Windows workstation) and check whether upsmon sends shutdown instruction. Interesting for my testing! Tnx for telling me. Kind Regards, Yves ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
On 11/10/06, Arjen de Korte [EMAIL PROTECTED] wrote:[...] If you're willing to try a few more things, comment out the part in theNUT startup script where 'upsmon' is started/stopped and fire it up. With'upsc [EMAIL PROTECTED]' you should be able to see the status of the UPS, without the risk of shutting down your system when things are notconfigured properly. Try at least /dev/ttyS[0-3] with the UPS in differentserial ports on your server. Remember to stop the script before modifying and starting it again. Good luck!Kind regards,ArjenOk, I 've done some more testing. I did comment out the upsmon entry in /etc/default/nutThen loaded the driver like: /lib/nut/genericups -x upstype=7 /dev/ttyS0It loaded and according syslog:Nov 11 10:19:47 radius1 genericups[8469]: Startup successfulHowever when I tried: radius1:/etc/nut# upsc [EMAIL PROTECTED] Error: Connection failure: Connection refusedradius1:/etc/nut# I've done this for ttyS0 ttyS1 (there are no more, 2 results in an error at fire up)I also changed the permissions on ttyS1 like radius1:/etc/nut# ls -al /dev/ttyS0crw-rw 1 root nut 4, 64 2005-02-26 07:39 /dev/ttyS0radius1:/etc/nut# Same problem.The only things left here are.1. There is a problem with the serial cable. (I tried 2 of them) How will I know if the cable that came with the UPS is the right one?2. That thing just won't ever work for linux.The new series of MGE are Ellipse ASR I hope someone can confirm these things work as they should with NUT running on debian stable.Many tnxYves ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
Ok, I 've done some more testing. I did comment out the upsmon entry in /etc/default/nut Then loaded the driver like: /lib/nut/genericups -x upstype=7 /dev/ttyS0It loaded and according syslog:Nov 11 10:19:47 radius1 genericups[8469]: Startup successfulHowever when I tried: radius1:/etc/nut# upsc [EMAIL PROTECTED] Error: Connection failure: Connection refusedradius1:/etc/nut# I've done this for ttyS0 ttyS1 (there are no more, 2 results in an error at fire up)I also changed the permissions on ttyS1 like radius1:/etc/nut# ls -al /dev/ttyS0crw-rw 1 root nut 4, 64 2005-02-26 07:39 /dev/ttyS0radius1:/etc/nut# Same problem.The only things left here are.1. There is a problem with the serial cable. (I tried 2 of them) How will I know if the cable that came with the UPS is the right one?2. That thing just won't ever work for linux.The new series of MGE are Ellipse ASR I hope someone can confirm these things work as they should with NUT running on debian stable.Many tnxYves Woops forget it!I've noticed a typo in /etc/default/nut # start upsdSTART_UPSD=yed (instead of yes!)Ok, now I gotradius1:/etc/default# upsc [EMAIL PROTECTED] driver.name: genericupsdriver.parameter.port: /dev/ttyS0driver.parameter.upstype: 7driver.version: 2.0.1driver.version.internal: 1.30ups.mfr: CyberPowerups.model: Power99ups.status: OL We move on... ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
On 11/11/06, YvesDM [EMAIL PROTECTED] wrote: [...] We move on... Ok, I think it's working. The problem was the serial cable. I had 2, one came with the ups, the other came with another ups. During my tests I changed the original cable with the other one. I never changed it back, thinking they were exactly the same. Now I changed it back and used the serial cabel that came with the ups again.So now we've got:1. On powerline, so status OLradius1:/etc/default# upsc [EMAIL PROTECTED]driver.name: genericupsdriver.parameter.port: /dev/ttyS0driver.parameter.upstype: 7driver.version: 2.0.1driver.version.internal: 1.30ups.mfr: CyberPower ups.model: Power99ups.status: OL2. I pulled the powerplug of the UPS, so OBradius1:/etc/default# upsc [EMAIL PROTECTED]driver.name: genericupsdriver.parameter.port : /dev/ttyS0driver.parameter.upstype: 7driver.version: 2.0.1driver.version.internal: 1.30ups.mfr: CyberPowerups.model: Power99ups.status: OB3. I plugged the powerline back in, again OL :-) radius1:/etc/default# upsc [EMAIL PROTECTED]driver.name: genericupsdriver.parameter.port: /dev/ttyS0driver.parameter.upstype: 7driver.version: 2.0.1driver.version.internal : 1.30ups.mfr: CyberPowerups.model: Power99ups.status: OLradius1:/etc/default# I don't know if the ups will actually shutdown the system now on low battery.upsc ain't showing much information on the battery status here, but as far as I remember I've read somewhere in the docs that this is normal with genericups drivers, not?It's not the right time now to check if the system really is shutdown when the battery is getting low.(live system) I will test this asap and keep this list informed. Many tnxYves ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
On 11/11/06, YvesDM [EMAIL PROTECTED] wrote: I don't know if the ups will actually shutdown the system now on low battery. If the status changes to OB LB, then it should shut your system down (assuming everything else is still configured properly). upsc ain't showing much information on the battery status here, but as far as I remember I've read somewhere in the docs that this is normal with genericups drivers, not? Yes, the UPS monitors the battery level internally, and sets the serial pins to a certain state. Because genericups is only looking at the levels of two pins, there are only 4 states that the UPS can report (online vs. on battery, battery OK vs. battery low). There is still the possibility that the UPS can report more status over the serial data lines (including battery charge level, voltages, load, etc.) but it sounds like you have tried a number of different drivers already. It's not the right time now to check if the system really is shutdown when the battery is getting low. (live system) I will test this asap and keep this list informed. Remember that you can also test things with the UPS powering a dummy load, like an old monitor or a lamp. Then, if you simply do not start upsmon, you can discharge the battery completely without shutting down the system which is monitoring the UPS. 'upsc' only needs the driver and 'upsd', as you found out. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
YvesDM wrote: Ok, I think it's working. The problem was the serial cable. That why I recommended to try it under Windows with the bundled software, to rule out a problem like this. I had 2, one came with the ups, the other came with another ups. During my tests I changed the original cable with the other one. I never changed it back, thinking they were exactly the same. For contact closure type UPSes, they almost never are. Now I changed it back and used the serial cabel that came with the ups again. [...] I don't know if the ups will actually shutdown the system now on low battery. Assuming that the monitoring works (which looks like it), it probably will, as you already found out during earlier tests where your system kept on rebooting when the serial cable was not connected. This is essentially the same as OB LB for upstype=7. upsc ain't showing much information on the battery status here, but as far as I remember I've read somewhere in the docs that this is normal with genericups drivers, not? On Battery and Low Battery are the only two status signals available, so no fancy voltage readings, load percentages and battery charge. If you want that, you need a smarter UPS. It's not the right time now to check if the system really is shutdown when the battery is getting low. That would be a recommendation indeed. See the notes on this in the genericups man page. (live system) I will test this asap and keep this list informed. Good! I'm glad that in the end things worked out for you. Kind regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
Disconnecting a UPS from a live server and testing it at a separate workstation is a MUST if you're not absolutely sure the configuration is correct. I would never use an UPS on a production system without double checking that monitoring works. Otherwise your investment gives you a false sense of security. [...] But anyway, I will do it in a free day next week and test things out on a spare proliant server I 'm lucky to have right now. While you're at it, try the UPS on a Windows machine with the bundled software to exclude that the UPS or serial cable are the culprits. It's a long shot, but you wouldn't be the first to find out that there is a problem in that area. It also guarantees that the UPS is indeed compatible to the UPSmart software. [...] I definately will complain to sweex! I will ask them to send me the manage software for linux. As they claim on their website it's supported. Don't hold your breath. And chances are that they direct you to a shoddy binary only package for RedHat 6.2 or some other ancient Linux version, which isn't very useful anymore. If it should 'just work' and you don't find enjoyment in trying to make it work, do yourself a favor and indeed swap it for one that is better supported by the manufacturer (MGE indeed comes to mind, since they officially sponsor NUT). Don't get me wrong. I enjoy searching for things and trying to make things work the right way. I would never use opensource if I didn't enjoy this, would I? But this time it's just to critical and I'm to much in a rush to get this working. That's exactly what I meant. Personally I enjoyed reverse engineering the SafeNet protocol and writing a driver for it. And I don't feel too bad about Sweex providing erronous information on their website and not willing to provide the details on the device needed to write a driver. However, as a professional I would be outraged if I had to spend hours and hours on a 75 UPS trying to make it work because I need it so badly. In that case, you'd better invest a few euros more and buy a device that is really supported by the manufacturer (MGE for instance). [...] That version is already quite old, we're at 2.0.4 already, with 2.0.5 lurking just around the corner. Yes I know, but I tried to keep the system as much as possible with the stable brand. But If it wouls solve my problems I could of course grab nut from unstable or testing. Don't bother. Although there were some changes in genericups, the're not major and unlikely to be the root cause of your problems. If you're willing to try a few more things, comment out the part in the NUT startup script where 'upsmon' is started/stopped and fire it up. With 'upsc [EMAIL PROTECTED]' you should be able to see the status of the UPS, without the risk of shutting down your system when things are not configured properly. Try at least /dev/ttyS[0-3] with the UPS in different serial ports on your server. Remember to stop the script before modifying and starting it again. Good luck! Kind regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
radius1:/etc/nut# /lib/nut/genericups -a ups_name Network UPS Tools - Generic UPS driver 1.30 (2.0.1) No upstype set - see help text / man page! The last line should ring a bell, don't you think so? radius1:/etc/nut# /lib/nut/genericups upstype=7 -a ups_name Network UPS Tools - Generic UPS driver 1.30 (2.0.1) No upstype set - see help text / man page! Honestly, you didn't read the genericups man page, did you? You can't specify an upstype like this (the correct way is explained in the man page). My ups.conf looks like this: radius1:/etc/nut# cat ups.conf # Network UPS Tools: example ups.conf # user = nut [ups_name] driver = genericups upstype=7 port = /dev/ttyS0 desc = Sweex 1000VA UPS In short, each configuration parameter in this file should be on a separate line, like the following: [ups_name] driver = genericups upstype = 7 port = /dev/ttyS0 desc = Sweex 1000VA UPS Also make sure that NUT is able to access the serial port, so you may want to check permissions: ls -l /dev/ttyS0 Kind regards, Arjen PS Please keep the mailinglist posted. Others may benefit from problems (and solutions) you have with configuring NUT to get your UPS working. -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
On 11/9/06, Arjen de Korte [EMAIL PROTECTED] wrote: radius1:/etc/nut# /lib/nut/genericups -a ups_name Network UPS Tools - Generic UPS driver 1.30 (2.0.1) No upstype set - see help text / man page!The last line should ring a bell, don't you think so? Yes so I've tried man nut :-) Honestly, you didn't read the genericups man page, did you? You can't specify an upstype like this (the correct way is explained in the manpage).See above...ok now I did. In short, each configuration parameter in this file should be on aseparate line, like the following:[ups_name]driver = genericupsupstype = 7port = /dev/ttyS0desc = Sweex 1000VA UPS Ok, I tried this.The driver was loaded and. the server shutdown immediately.I had to attach a screen and a keyboard to the server and boot it in single user modeto disable nut in /etc/default/ Also make sure that NUT is able to access the serial port, so you may want to check permissions:ls -l /dev/ttyS0This gives me:radius1:/var/log# ls -l /dev/ttyS0crw-rw 1 root dialout 4, 64 2005-02-26 07:39 /dev/ttyS0So, I guess not good. What is the correct chown? chown root:nut /dev/ttyS0 ? Could this be the reason of the instant shutdown? I don't want this to happen again. (radius) Kind regards,ArjenPSPlease keep the mailinglist posted. Others may benefit from problems(and solutions) you have with configuring NUT to get your UPS working.Of course.Many tnx Yves ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
PS Some logfiles from the instant shutdowns:The ups was NOT running on battery power. Nov 9 14:37:16 radius1 genericups[1640]: Startup successfulNov 9 14:37:16 radius1 upsd[1641]: /etc/nut/upsd.conf is world readable Nov 9 14:37:16 radius1 upsd[1641]: Connected to UPS [ups_name]: genericups-ttyS0Nov 9 14:37:16 radius1 upsd[1641]: /etc/nut/upsd.users is world readableNov 9 14:37:16 radius1 upsd[1642]: Startup successful Nov 9 14:37:16 radius1 upsmon[1644]: Startup successfulNov 9 14:37:16 radius1 upsd[1642]: Connection from 127.0.0.1Nov 9 14:37:16 radius1 upsd[1642]: Client [EMAIL PROTECTED] logged into UPS [ups_name]Nov 9 14:37:16 radius1 upsmon[1645]: UPS [EMAIL PROTECTED] battery is lowNov 9 14:37:16 radius1 upsmon[1645]: UPS [EMAIL PROTECTED] on batteryNov 9 14:37:16 radius1 upsd[1642]: Client [EMAIL PROTECTED] set FSD on UPS [ups_name]Nov 9 14:37:16 radius1 upsmon[1645]: Executing automatic power-fail shutdownNov 9 14:37:16 radius1 upsmon[1645]: Auto logout and shutdown proceeding Nov 9 14:37:21 radius1 upsd[1642]: Host 127.0.0.1 disconnected (read failure)Nov 9 14:37:27 radius1 upsd[1642]: Signal 15: exitingNov 9 14:37:27 radius1 genericups[1640]: Signal 15: exiting Nov 9 14:40:22 radius1 kernel: groups: 01Nov 9 14:40:22 radius1 kernel: groups: 01 02Nov 9 14:40:22 radius1 kernel: groups: 02Nov 9 14:40:22 radius1 kernel: groups: 02 01Nov 9 14:40:27 radius1 genericups[1640]: Startup successful Nov 9 14:40:27 radius1 upsd[1641]: /etc/nut/upsd.conf is world readableNov 9 14:40:27 radius1 upsd[1641]: Connected to UPS [ups_name]: genericups-ttyS0Nov 9 14:40:27 radius1 upsd[1641]: /etc/nut/upsd.users is world readable Nov 9 14:40:27 radius1 upsd[1642]: Startup successfulNov 9 14:40:27 radius1 upsmon[1644]: Startup successfulNov 9 14:40:27 radius1 upsd[1642]: Connection from 127.0.0.1Nov 9 14:40:27 radius1 upsd[1642]: Client [EMAIL PROTECTED] logged into UPS [ups_name]Nov 9 14:40:27 radius1 upsmon[1645]: UPS [EMAIL PROTECTED] battery is lowNov 9 14:40:27 radius1 upsmon[1645]: UPS [EMAIL PROTECTED] on batteryNov 9 14:40:27 radius1 upsd[1642]: Client [EMAIL PROTECTED] set FSD on UPS [ups_name]Nov 9 14:40:27 radius1 upsmon[1645]: Executing automatic power-fail shutdown Nov 9 14:40:27 radius1 upsmon[1645]: Auto logout and shutdown proceedingNov 9 14:40:32 radius1 upsd[1642]: Host 127.0.0.1 disconnected (read failure)Nov 9 14:40:39 radius1 upsd[1642]: Signal 15: exiting ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
[ups_name] driver = genericups upstype = 7 port = /dev/ttyS0 desc = Sweex 1000VA UPS Ok, I tried this. The driver was loaded and. the server shutdown immediately. Lesson #1: Always first test whether the driver is producing good results (you must be able to read the status from your UPS correctly), before using it to shutdown a system. I had to attach a screen and a keyboard to the server and boot it in single user mode to disable nut in /etc/default/ Lesson #2: Unless you're sure of #1, don't put NUT in scripts that are started automatically to prevent deadlocks... :-) [...] This gives me: radius1:/var/log# ls -l /dev/ttyS0 crw-rw 1 root dialout 4, 64 2005-02-26 07:39 /dev/ttyS0 So, I guess not good. What is the correct chown? chown root:nut /dev/ttyS0 ? Could this be the reason of the instant shutdown? No, not really. When the genericups driver fails to lock the serial port (because of wrong permissions or it is locked by another process) it will fail to startup. Are you absolutely sure that the UPS is connected to /dev/ttyS0? For 'upstype=7' the signals for 'on battery' and 'low battery' are -CTS and -DCD (both zero). I wouldn't be surprized at all if this is the same as nothing connected to the port you're monitoring (although I can't test that right now). Note that the genericups driver is not able to detect whether or not something is connected to the port it is monitoring, unlike many other (somewhat) smarter protocols that are used by other drivers. This is due to the limitations of the contact closure protocol used, not by the driver. I don't want this to happen again. (radius) Lesson #3: You really, REALLY, shouldn't experiment with a UPS on a live system... :-) When in doubt, it is always better to follow the instructions from the genericups man page under the chapter 'TESTING COMPATIBILITY' to prevent inadvertent shutdowns of your system. Kind regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
YvesDM wrote: On 11/8/06, *Udo van den Heuvel* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Try Powermust. radius1:/etc/nut# cat ups.conf # Network UPS Tools: example ups.conf # user = nut [ups_name] driver = powermust port = /dev/ttyS0 desc = Sweex 1000VA UPS radius1:/etc/nut# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon. radius1:/etc/nut# I see: [EMAIL PROTECTED] ~]# service ups restart Stopping UPS monitor: [ OK ] Stopping upsd: [ OK ] Shutting down powermust: [ OK ] Starting powermust: Network UPS Tools - Mustek PowerMust UPS driver 1.1 (2.0.3) Carlos Rodrigues (c) 2003, 2004 Mustek PowerMust UPS, or compatible, detected. [ OK ] Starting upsd: Network UPS Tools upsd 2.0.3 Connected to UPS [myups]: powermust-ttyS1 Synchronizing...done [ OK ] Starting UPS monitor (master): Network UPS Tools upsmon 2.0.3 UPS: [EMAIL PROTECTED] (master) (power value 1) Using power down flag file /etc/killpower [ OK ] So what is your upsdrvctl problem? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
YvesDM wrote: So what is your upsdrvctl problem? Are we talking the same UPS here? I have a Sweex, 800VA or so? If yes, I wish I knew ! Maybe try the source to see what the function does that is mentioned in the error? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
YvesDM wrote: Are you absolutely sure that the UPS is connected to /dev/ttyS0? For 'upstype=7' the signals for 'on battery' and 'low battery' are -CTS and -DCD (both zero). I wouldn't be surprized at all if this is the same as nothing connected to the port you're monitoring (although I can't test that right now). The machine kept rebooting, even with no serial cable to the UPS connected anymore, so I guess that's a yes? I would say that if it doesn't make a difference whether the serial cable is attached or not, that would be a safe bet, yes. I just checked with genericups monitoring a serial port without anything connected and as expected, it showed LB OB (low battery and on battery), which would force a system shutdown had upsmon been running: # upsc [EMAIL PROTECTED] driver.name: genericups driver.parameter.port: /dev/ttyS1 driver.parameter.upstype: 7 driver.version: 2.0.3 driver.version.internal: 1.31 ups.mfr: CyberPower ups.model: Power99 ups.status: LB OB (Shame on me, even I'm not using the lastest NUT version) How can I be absolutely sure it's connected to /dev/ttyS0? I don't know. The trouble with contact closure type UPSes is, there is no way to determine if the correct UPS is connected and in many cases, no way to check if something is connected at all. Short of a couple of ones that support serial PnP (I know of at least APC has a model that does), but that's not used by NUT (should be handled at a different level). That proliant server has a serial A and a serial B RS232, I took serial A. If you have a serial loopback plug (or a breakout box), you could check if you can access that port, but looking at your past replies I fear that you even don't know what I'm talking about right now (no pun intended). I'm not familiar with proliant servers, so I can't offer much more help here. [...] Lesson #3: You really, REALLY, shouldn't experiment with a UPS on a live system... :-) Yes, Easy to say when the system is already operational. I didn't have that much choice. Disconnecting a UPS from a live server and testing it at a separate workstation is a MUST if you're not absolutely sure the configuration is correct. I would never use an UPS on a production system without double checking that monitoring works. Otherwise your investment gives you a false sense of security. Bottom line is that a UPS should make a power loss to your system predictable, it can't prevent it always, so you MUST check if that works. Even when monitoring the status of the UPS works, you must still make sure the system shuts down cleanly and reboots when power returns. There is no better way to guarantee that, than to yank the mains cable from the UPS and see what happens (at a convenient time, that is). When in doubt, it is always better to follow the instructions from the genericups man page under the chapter 'TESTING COMPATIBILITY' to prevent inadvertent shutdowns of your system. Yes, I guess you're right, but I start to get sick of it. You have every reason to. You expected something to work (and if your UPS indeed would have used the SafeNet software, it would, or else give you an error message that the configuration was not OK) and instead it is giving you all sorts of trouble. Please complain to the company that sold you the UPS (or better yet, to Sweex for providing incorrect information on their website). As I said before this is a live system and I can't mess with it to much. I really hope someone can give me the link I 'm missing here. Otherwise it's better to stop waisting my time on that ups and look for another one better supported. MGE? If it should 'just work' and you don't find enjoyment in trying to make it work, do yourself a favor and indeed swap it for one that is better supported by the manufacturer (MGE indeed comes to mind, since they officially sponsor NUT). Suggestions from recent models working without problems are welcome. I use the stable debian package, nut 2.0.1-4 That version is already quite old, we're at 2.0.4 already, with 2.0.5 lurking just around the corner. Kind regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
On 11/9/06, Arjen de Korte [EMAIL PROTECTED] wrote: YvesDM wrote: Are you absolutely sure that the UPS is connected to /dev/ttyS0? For 'upstype=7' the signals for 'on battery' and 'low battery' are -CTS and -DCD (both zero). I wouldn't be surprized at all if this is the same as nothing connected to the port you're monitoring (although I can't test that right now). The machine kept rebooting, even with no serial cable to the UPS connected anymore, so I guess that's a yes? I would say that if it doesn't make a difference whether the serialcable is attached or not, that would be a safe bet, yes. I just checkedwith genericups monitoring a serial port without anything connected and as expected, it showed LB OB (low battery and on battery), which wouldforce a system shutdown had upsmon been running:So, this might have happened here :-)[...] That proliant server has a serial A and a serial B RS232, I took serial A.If you have a serial loopback plug (or a breakout box), you could checkif you can access that port, but looking at your past replies I fear that you even don't know what I'm talking about right now (no punintended). I'm not familiar with proliant servers, so I can't offer muchmore help here.[...]As you feared, I have no idea... Lesson #3: You really, REALLY, shouldn't experiment with a UPS on a live system... :-) Yes, Easy to say when the system is already operational. I didn't have that much choice.Disconnecting a UPS from a live server and testing it at a separateworkstation is a MUST if you're not absolutely sure the configuration is correct. I would never use an UPS on a production system without doublechecking that monitoring works. Otherwise your investment gives you afalse sense of security.Yes I know, the ups gives me some kind of secure feeling when I'm around and awake, but there it ends of course. That's why I started looking for a solution to make this more easy for me.If I remove the ups in front of the server I feel even less secure then now (as we all know murphy)But anyway, I will do it in a free day next week and test things out on a spare proliant server I 'm lucky to have right now. Bottom line is that a UPS should make a power loss to your systempredictable, it can't prevent it always, so you MUST check if that works. Even when monitoring the status of the UPS works, you must stillmake sure the system shuts down cleanly and reboots when power returns.There is no better way to guarantee that, than to yank the mains cable from the UPS and see what happens (at a convenient time, that is).Yes, I know, but I'm scared to screw my raid during unclean shutdowns. When in doubt, it is always better to follow the instructions from the genericups man page under the chapter 'TESTING COMPATIBILITY' to prevent inadvertent shutdowns of your system. Yes, I guess you're right, but I start to get sick of it.You have every reason to. You expected something to work (and if yourUPS indeed would have used the SafeNet software, it would, or else give you an error message that the configuration was not OK) and instead itis giving you all sorts of trouble. Please complain to the company thatsold you the UPS (or better yet, to Sweex for providing incorrectinformation on their website). I definately will complain to sweex! I will ask them to send me the manage software for linux.As they claim on their website it's supported. As I said before this is a live system and I can't mess with it to much. I really hope someone can give me the link I 'm missing here. Otherwise it's better to stop waisting my time on that ups and look for another one better supported. MGE?If it should 'just work' and you don't find enjoyment in trying to makeit work, do yourself a favor and indeed swap it for one that is bettersupported by the manufacturer (MGE indeed comes to mind, since they officially sponsor NUT).Don't get me wrong. I enjoy searching for things and trying to make things work the right way. I would never use opensource if I didn't enjoy this, would I?But this time it's just to critical and I'm to much in a rush to get this working. Suggestions from recent models working without problems are welcome. I use the stable debian package, nut 2.0.1-4That version is already quite old, we're at 2.0.4 already, with 2.0.5lurking just around the corner.Yes I know, but I tried to keep the system as much as possible with the stable brand. But If it wouls solve my problems I could of course grab nut from unstable or testing. Kind regards,ArjenI wish to thank you for the time you spent writing those answers and explaining this to me. It's very appreciated, tnx! Again, if anyone can recommend me an easy-setup MGE ups with nut I'll be glad to hear. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
I'm trying to get a sweex ups working with nut on debian sarge. Good luck! Sweex is notorious for changing their products internally, without telling you. Have you noticed that their online documentation still mentions the SafeNet software? And that they even have the guts to mention that their UPS is 'fully compatible with Unix'. Upon asking, they boldly stated that you can power a Unix box from it, but you can't monitor it. Yeah, right! This one: http://www.sweex.com/producten.php?lang=1%20sectie=item=59artikel=95 It's shipped with UPSmart and according to the compatibility list it should work with the genericups upstype=7 driver. But it doesn't. I have one unit that does. But that doesn't neccessarily mean that yours does too (unfortunately, see above). I get: mybox:/etc/nut# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl failed). mybox:/etc/nut# This could be a configuration problem. Can you post the contents of the /etc/ups/ups.conf file here and also the permissions on the serial port you configured in there? Checking out with the bundled (Windows) software on a Windows box may be worthwile too, to rule out problems in the serial cable and/or UPS. So I guess I'm using the wrong driver. I'm not ready to jump to that conclusion yet. I already tried the savenet driver too, but no succes. That one for sure won't work, since that one is only good for devices that were shipped with the SafeNet 1.0 for Windows software. Yours apparently wasn't. I found on the net someone using the ippon driver with a 500VA sweex ups, but this doesn't work for me. All help is very appreciated. Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
On 11/7/06, YvesDM [EMAIL PROTECTED] wrote: Hi, I'm trying to get a sweex ups working with nut on debian sarge. This one: http://www.sweex.com/producten.php?lang=1%20sectie=item=59artikel=95 It's shipped with UPSmart and according to the compatibility list it should work with the genericups upstype=7 driver. But it doesn't. I get: mybox:/etc/nut# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl failed). mybox:/etc/nut# genericups does not have very many ways to fail. What if you try starting the driver directly, such as: /lib/nut/genericups -a ups_name You can also check the system logs for error messages. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sweex 1000VA UPS
On 11/8/06, Charles Lepple [EMAIL PROTECTED] wrote: genericups does not have very many ways to fail. What if you trystarting the driver directly, such as: /lib/nut/genericups -a ups_nameHi,When I do:radius1:/etc/nut# /lib/nut/genericups -a ups_name Network UPS Tools - Generic UPS driver 1.30 (2.0.1)No upstype set - see help text / man page!radius1:/etc/nut# /lib/nut/genericups upstype=7 -a ups_nameNetwork UPS Tools - Generic UPS driver 1.30 ( 2.0.1)No upstype set - see help text / man page!My ups.conf looks like this:radius1:/etc/nut# cat ups.conf# Network UPS Tools: example ups.conf#user = nut[ups_name] driver = genericups upstype=7 port = /dev/ttyS0 desc = Sweex 1000VA UPS You can also check the system logs for error messages.I don't get any messages in syslog from trying this.I received data stale and/or connection problems when I tried other drivers before. Maybe it's time to start looking out for another ups? I leave for holidays on 20/11 and I want this of my back by that time.Sincerely, Yves ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
