similar to: megatec driver floods syslog with "UPS lost/re-established" messages

Hi there! I'm a n00b NUT user trying to get it running on RHEL5 and actually do something useful for me. Few questions: 1) I want it to notify me by email on power loss and power back events. I can't find any sample scripts for this purpose... Where shall I look for them? 2) So far, I've backported the package from Fedora and got my Ablerex running (previously used with Upsilon /

Hi Alexander, > I've UPS named PowerMan RealSmart 1000, it is not listed in > compatibility list. I found that it works with "fentonups" driver and > have ups.model "Unknown S163-1000". Ithink "1000" is from capacity - > I've seen in Internet someone have RealSmart 800 identified "S163-800". > Also PowerMan have

I recently upgradeded dovecot on one of our servers from version 1.0.10 to version 1.1.3. Ever since, we've been seeing occasional errors similar to this sequence (with the username and IP addresses elided): Sep 30 00:09:56 alcor dovecot: pop3-login: Login: [4954], XXXX, NNN.NNN.NN.NNN Sep 30 00:09:56 alcor dovecot: wrapper[5006]: pop3, XXXX, NNN.NNN.NN.NNN Sep 30 00:09:56 alcor

Hello List, I've upgraded to dovecot from FreeBSD ports, changed the config from previous 0.99 version, but meet a problem with %d variable beeing empty in userdb static configuration directive. Our server supports multiple domains, e.g. 'mxc.ru' and 'mail.mxc.ru'. Users can log into using their full e-mail address like antonm at mxc.ru or antonm at mail.mxc.ru, but the

Hi again, I tested several times using the Megatec driver from nut 2.2.2 to no avail, as it definitely never "sees" the UPS. Always getting : # drivers/megatec -DDD -a Alpha Network UPS Tools 2.2.2 - Megatec protocol driver 1.5.14 [megatec] Carlos Rodrigues (c) 2003-2008 debug level is '3' Starting UPS detection process... Asking for UPS status [Q1]... Q1 => FAILED

Hi there, A couple years ago, I had patched the "fentonups" nut driver to allow it to work with my Unitek Alpha 500 UPS. My patch had been accepted and incorporated in the standard fentonups driver. I have had no time to stay involved in the "nut" project since (and besides this I'm not a developper...). 2 days ago I upgraded from Ubuntu Gutsy to Ubuntu Hardy and got

NUT recently stopped working on my debian. I'm not sure which upgrade broke it. ups.conf: [mustek] driver = megatec port = /dev/ttyS0 desc = "mustek ups" # upsd -DDDD Network UPS Tools upsd 2.4.1 listen_add: added ::1:3493 listen_add: added 127.0.0.1:3493 setuptcp: try to bind to 127.0.0.1 port 3493 listening on 127.0.0.1 port 3493 setuptcp: try to bind

On Mon, Oct 20, 2008 at 1:35 PM, Arjen de Korte <nut+devel at de-korte.org> wrote: > Citeren Carlos Rodrigues <cefrodrigues at gmail.com>: > >> BTW, the patch has a small typo in one of the comments: "applied to >> battery.volage" :) > > I'll leave that up to you to correct. Since it is only a comment, it won't > be visible to innocent users

Ubuntu 8.04 Nut : Version: 2.2.1-2.1ubuntu7.2 Hello, I choose the megatec driver and I connect through a serial cable. I receive a "This UPS has an unsupported combination of battery voltage/number of batteries" message. I know this is not an error but I don't really what I have to do next. Here is the result of /lib/nut/megatec -a infosec -DDD debug level is '3'

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but

2010/10/13 Vitaly Lavrov > I found bug in nut/drivers/megatec.c - force shutdown may dont work. > See patch. > could you please give a try to blazer, since it is set to replace megatec with 2.6.0. Arjen will quite probably comment on your patch usefulness within the blazer scope. thanks for your contrib. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton -

Hi to all, I am new on the lists but using nut on megatec for last two and half years. Looking at archives I saw that there is a lot of people confused about battery voltage and I want to help them to clear out some stuff in their heads. This story is based on my experience with UPS devices from 600VA to 20kVA, from single phase systems to three phase systems, with battery packs from 1

Hi all, Currently, the "megatec" driver only supports UPSes which have a serial (RS232) interface. However, I'm under the impression that most of the models that speak the megatec protocol, and have an USB interface, just have a standard serial-to-USB converter inside. This being the case, there should be a "/dev/ttyUSBx" device which the megatec driver could use just as

Hi all, Currently, the "megatec" driver only supports UPSes which have a serial (RS232) interface. However, I'm under the impression that most of the models that speak the megatec protocol, and have an USB interface, just have a standard serial-to-USB converter inside. This being the case, there should be a "/dev/ttyUSBx" device which the megatec driver could use just as

I had some free time this weekend, and made some long overdue changes to "megatec". The thing is, these changes lead to a couple of questions that I must ask before I go on and "svn commit" them: 1) The blazer, fentonups, esupssmart, ippon, sms and mustek drivers are now completely covered and all of their functionality should now be present in megatec, and also every model

On Feb 11, 2008 5:30 PM, Marcio Gomes <mpg at microlink.com.br> wrote: > I change the if in [OFF] detect state to, in original way, if you send a > reset.watchdog, the UPS goes > to OFF state in clients, but it is not correct, because UPS is OL and > Shutdown are in progress, but > the power is not OFF First of all, thanks for the patch. But I have a few comments: Are you

Greetings! Thanks to all the developers who have made this project so far. Searching for a Linux based Belkin UPS monitor led me straight to the Network UPS Tools. I have bought a Belkin F6C900-UNV (900VA) for use on a Slackware 10.2 server to replace an older APC model that died suddenly. So far I have successfully managed to get NUT 2.0.5 compiled and configured and found that this Belkin

Hi Alexander, thanks for your good work on the megatec_usb driver. I have made a few more (cosmetic) changes. Is the driver now working stably for your device? In particular, do the instant commands (and particularly "upsdrvctl -k") work properly? In this case, we could hopefully mark the device as "supported" and merge the driver to the main branch. There is still the

Hi folks! We have a Powercom Vanguard 6000 running here. It seems to be supported by the megatec driver within nut. So I get everything out of it exept the battery status. When I run Nut, it says: Megatec protocol UPS detected [UPS Model 6K Ver Y1.3]. This UPS has an unsupported combination of battery voltage/number of batteries. The "battery.charge" value will be bogus. So I would