similar to: mge-shut driver fails almost after every reboot

Hello Arno, Thanks for the quick reply. FreeNAS is FreeBSD-based. Yes, I could test a patch. As I have mentioned, this behavior is not seen at every single reboot but after most reboots. Also, some times, the connectivity can be lost without even rebooting. That is not very often can have happened a few times. Best regards, Panagiotis On 2/4/2015 5:44 ??, Arnaud Quette wrote: > Hello

Hello Panagiotis 2015-04-01 16:28 GMT+02:00 Panagiotis Kritikakos < panagiotis.kritikakos at nikitec.gr>: > Hello all, > > OS name: FreeNAS 9.3 > NUT version: 2.7.2 > NUT installed method: Bundled with FreenNAS 9.3 > Device: EATON 5SC 1000 (http://powerquality.eaton. > com/Products-services/Backup-Power-UPS/5SC.aspx?cx=5& >

Hello Arno, Can apply the patch directly or should I recompile nut? Best regards, Panagiotis On 3/4/2015 5:06 ??, Arnaud Quette wrote: > Hello Panagiotis > > 2015-04-03 14:28 GMT+02:00 Panagiotis Kritikakos > <panagiotis.kritikakos at nikitec.gr > <mailto:panagiotis.kritikakos at nikitec.gr>>: > > Hello Arno, > > Question: have you also

Hello Arno, > Question: have you also tested oldmge-shut? > Otherwise, that might be interesting to do so and send back the > results of these tests... Yes, I've tried this as well with worse results unfortunately. This driver seems to be even more unstable. When it gets able to set communication with the UPS (which is not always the case), it usually lost it again after a while.

Hello Arno, FreeNAS doesn't come with a compiler and I had to compile with the patch on FreebBSD-9.3 and then copy the produced mge-shut. Unfortunately it didn't work out. For every try I was getting "Connection Refused" and when I tried /usr/local/libexec/nut/mge-shut -D -a <ups_name> I was always getting 'No matching HID UPS found'. I returned back to the

Hi all, I just changed my old MGE ellipse for a evolution 850 (now eaton). I can connect using mge-shut (newmge-shut doesn't work). But I have a few issues. I lloked around on NUT web-site and googled with no luck. Using debian lenny on 2.6.18 kernel (due to some ISDN driver that doesn't work with earlier kernels) 1) the most annoying is that I cannot shutdown the UPS. here is a trace :

Hi Panagiotis 2015-04-06 9:13 GMT+02:00 Panagiotis Kritikakos < panagiotis.kritikakos at nikitec.gr>: > Hello Arno, > > Can apply the patch directly or should I recompile nut? > not sure to fully understand your comment, but... this is a source code patch, so you indeed have to apply it to the NUT source code (from within the source tree, "patch -p1 <

I have trouble in getting communication work with MGE Ellipse 500. I bought it second hand and I don't have the cable for it. How do I know if it's the Serial or USB model? The serial number of the unit is: 769B16015. I suspect it is the serial version as the label next to the RJ11 stands "com port", but I can't be 100% sure. MGE Ellipse serial cable pinout can be found

Hello Panagiotis 2015-04-03 14:28 GMT+02:00 Panagiotis Kritikakos < panagiotis.kritikakos at nikitec.gr>: > Hello Arno, > > Question: have you also tested oldmge-shut? >> Otherwise, that might be interesting to do so and send back the results >> of these tests... >> > Yes, I've tried this as well with worse results unfortunately. This driver > seems to

Hi, I have the above UPS connected to a FreeBSD 6.2 box and it shows 'data stale' very frequently (every few minutes). I have tried the usual trick of setting maxage, poll interval, etc etc but to no avail. When I wind up logging I see (on mge-shut) entering shut_get_report(id: 0d, len: 1800) shut_wait_ack(): ACK received entering shut_get_report(id: 16, len: 1800) shut_wait_ack():

We have several systems in remote locations and I have found that the ones in the US are having issues.. We are an Australian company and can't source a 110V UPS locally so we arrange to have one bought for the site when it's installed. It seems that in the US we are getting "Pulsar EX 1500" UPSs but locally we buy "Pulsar 1500". NUT seems to work find with the

Hi, I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the mge-shut driver but I'm having some problems. It appears to init OK but I can't, say, turn the outlets off, eg.. harrow:~>upsc mge@localhost battery.charge: 78 battery.charge.low: 20 battery.runtime: 05760 driver.name: mge-shut driver.parameter.port: /dev/cuad1 driver.version: 2.0.3 driver.version.internal: 0.65

Hi, I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the mge-shut driver but I'm having some problems. It appears to init OK but I can't, say, turn the outlets off, eg.. harrow:~>upsc mge@localhost battery.charge: 78 battery.charge.low: 20 battery.runtime: 05760 driver.name: mge-shut driver.parameter.port: /dev/cuad1 driver.version: 2.0.3 driver.version.internal: 0.65

Dear Andreas, some googling revealed, you created a driver for the xanto series of online-usv.de. In what state it is currently? I've to manage a S2000 and would like to use nut for it, is it usable by now? Do you need another tester? TIA, Pete

Hello, I'm trying to install FreeBSD 9.1 amd64 on an IBM x3550 M3 server. Installation went smoothly, RAID controller and network cards were successfully recognised. But, after the installation, the server fails to boot from disk. There were some posts, about two years ago, in this list implying that the problem lies in UEFI but I couldn't find any clear solution. Any suggestions would

Sorry for a bit longer delay than I anticipated, I was stuffed with the work. This is the next iteration of the patch adding some functionality to apcsmart driver, and relying on 'ignorelb' recently added. Follow up from previous thread: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02331.html Main differences is that V3 is split into many small patches, so the

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.

This is 2nd version of the earlier patch featuring a few new features and fixes to the apcsmart driver, following the remarks in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html Major changes from v1: - handle battery.charge and battery.runtime checks at main.c level - handle "immutable but writable" conflict gracefully at driver level -

Is it just me, or freebsd-update isn't yet shipping the openssl updates? I'm trying (on an SMP machine) to fetch them, but there seem to be none available. I'd like to confirm that sleep deprivation isn't the culprit here, so I've checked in /usr/local/freebsd-update/work/ and the subdirectory with the highest number contains the SA-06:21 files. Anyone seen that clue bat

Hi, my UPS is a Best Fortress LI1420 with the monitoring master running fedora 7. I have to replace the manufacturer's software "Checkups II" because it's not working with releases after fc4. My choice is the nut package. But it isn't just installing rpm's and configure the parameter files. ? The first hurdle to take was realising the UPS doesn't send a prompt.