similar to: Shutdown Problem

Hi I am running FC5 with nut coming from the fc5 extras repositories. I am trying to configure a Gamatronic D-Compact ups. The cable that came with the ups has a serial connector on one end and a usb on the other. cat /proc/bus/usb/devices produces T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P:

On Fri, 13 Jul 2018 16:55:23 +0300 Eli Wapniarski via samba <samba at lists.samba.org> wrote: > Opensuse > > Everything is there. > Are you sure, I thought OpenSUSE suffered from the same problem as red-hat, i.e. MIT kerberos, and there wasn't a distro AD DC package available. Rowland

Regards I am installing NUT for the UPS Skate UPS-2200D, the UPS have conection with USB to PC and i have problems to configure nut the ups is conected and Linux report this config Aug 19 23:34:56 dakota kernel: [22393.099595] usb 2-2: new low speed USB device using uhci_hcd and address 7 Aug 19 23:35:06 dakota kernel: [22403.186326] usb 2-2: Product: MEC0002 Aug 19 23:35:06 dakota kernel:

Hi all - I'm new to both UPS setup and SNMP on linux - so I'd appreciate any help I can get....I'm stuck! I'm running fedora core 5, and have installed net-snmp and nut. I'm trying to get my network connected UPS to this linux machine. My /etc/ups/ups.conf looks like this: [upsnetwork] driver = snmp-ups port = 172.31.254.7 community = public desc="Network

I have a Gamatronic Smart Compact 750. I have it connected to my linux machine via serial cable and am running nut 2.0.3. There is no interruption in power, but the ups is reporting OB (on battery). Is there a configuration option I am missing? The relevant ups.conf entry is: [Gamatronic] port = /dev/ttyS1 desc = "Home Gamatronic UPS" driver = genericups

Hi, I have an HPML150 using fedora4 and am attempting to use nut tools with it's HP T700 UPS - Following this howto : http://fedoranews.org/contributors/kazutoshi_morioka/nut/ Attached are relevant configs. I've tried a whole bunch of ups drivers; apcsmart, fentonups, bestups, genericups type 1--> 16 Yet to try the remaining drivers Some genericups upstypes trigger immediate

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

Hi Patrick, 2006/4/2, Patrick Beard <p.beard@blueyonder.co.uk>: > Hi Arnaud, > > Just wanted to let you know the the Belkin F6H500ukUNV is working for me > with the fentonups driver. > > http://catalog.belkin.com/IWCatSectionView.process?IWAction=Load&Merchant_Id=&Section_Id=202840 > > I originally tried it with the genericups driver with upstype=7 but this

Hi list here is the patch to make fentonups recognize some PowerCOM's UPS's, and to setup terminal lines for them (at least for SMK-1500a) as powercom's original upsmon do. fentonups -x powercom works correctly with SMK-1500a (it screamed ''Communications with UPS lost - check cabling' or 'Short read during UPS id sequence' without this patch). Sorry for

Hi Henning, you should get in touch with Carlos, who his developing a generic megatec driver (available from svn: http://eu1.networkupstools.org/source.html) Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer -

Hi *Simon, i got a similar setup here (also a powercom-oem-product, but in my case labeled by a swiss "manufacturer") with the same problems, using powercom's upsmon works fine, while nut completely refuses to cooperate. after trying almost everything i somehow hopeless surfed on the official nut-page, when i saw that there are powercom-products which don't need the

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

Hi ups-devel, As I looked throw www.networkupstools.org site, haven't found any pointers where to send patches, so I hope this is the right place. (Please let me know weather this is the right place.) The patch contains a minor change in the logic of the driver, our Effekta MHD 3000 UPS continuously writes status data to the serial port, so one has to send a CR character and empty the

Hello everybody, this is my first post to this list - normally I take some time to read some messages first to get an impression of the List, but I have a pressing question to ask, so please forgive me if I miss the right tone... I just installed NUT 2.0.2 and try to get it working with our Effekta MT 1500. In the Drievers List I found this entry: "Effekta" "MI/MT/MH"

I finally got some time to implement a pair of options to upsc for listing all configured UPSes on a given upsd: http://boxster.ghz.cc/projects/nut/changeset?new=branches%2Fupsc_list%2Fclients%2Fupsc.c%40859&old=trunk%2Fclients%2Fupsc.c%40821 http://boxster.ghz.cc/projects/nut/browser/branches/upsc_list/clients/upsc.c?rev=859 I think this should work with the new functions for parsing IPv6

Carlos, Today I was browsing through the NUT Tracker and noticed an entry which linked to a message on nut-upsdev: http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-January/000559.html Although the fentonups driver is no longer in the tree (since it was replaced by the megatec driver), I think there is still some merit in this patch. Notice the following lines from this message: >

G'day. I have a UPS here that is driven by the Fenton UPS driver, and which requests that I report the ID string to the NUT developers: root@anu:~# upsdrvctl start smk800 Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - Fenton UPS driver 1.22 (2.0.4) Unknown ups - please report this ID string: #M+H SMK-800 2000 V6.2 Detected Unknown MK-800 on /dev/ttyS0 The

Hi! Trying to set up NUT on Centos 5 to monitor a CyberPower 1500AVR UPS. There seem to be many documents, all of which seem to be not fully consistent with each other, and most of them aren't up to date. I'm guessing I should be using udev rather than hal, but I'm somewhat stumped on how to figure out what device it should be monitoring. there are a bunch of udev rules installed

Hi There, Running on debian sarge. This was working a while ago, but here goes.. When viewing the upsstats.cgi page, im getting a message "Not Supported" in the Model column with a "ONLINE" message, but no other stats. Here is the syslog when booting nut: Oct 15 14:28:40 mx1 upsmon[4835]: Signal 15: exiting Oct 15 14:28:40 mx1 upsmon[4834]: upsmon parent: read: Success Oct

I am seeing a problem that I am not sure how to fix and since I have never had to use samba for anything major like this I am not sure where to go. So, here is goes! I have a few Gentoo systems that currently have a bunch of data on them. I have been tasked with getting data from some Windows machines to the Gentoo systems so that we can dump the Windows machines. So, the windows machines are