similar to: timestamped debug output (was: upsd flapping in the breeze)

Hi, I have had a long standing problem with NUT talking to 110V MGE UPSs on FreeBSD, I was recently investigating again and noticed that upsd seems overly noisy, eg.. May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5

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 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, 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, 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-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

Hello, I forgot nut since more than a year because a lot of job with other application My server nut failed since severals months We had 3 electric failure so I must install a new server nut I work with ubuntu 10.04.4 (64bits) / I installed nut 2.4.3 with deposits I have a MGE Pulsar evolution 2200 connected on usb last week when I began my tests all was ok (communication etc etc ..)

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 <

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 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 :

Thanks for the help. I thought I'd solved the problem (setting the line number information in the instruction metadata) by inserting my own function for setting line number in llvm/Support/DebugLoc.h. I have added a function setLine(unsigned) in DebugLoc class. The function simply sets the LineCol variable as needed. But there is a problem. Whenever I'm checking the line number(calling

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 *, I'm running into a problem configuring bonding on an HP DL 360 G4p, running 4.3 + tg3 driver version 3.43f. I'm connecting eth0 and eth1 to a Cisco 2948 (CatOS 8.1(3)) and receiving flapping notices. The ethernet address is that of the primary interface. I have tried several different modes, including balance-rr (0), active-backup (1), and balance-alb (6). All have the

I just noticed that MDIClient windows do not automatically become current when they receive a mouse click, but only do so if the click happens inside of an enabled widget. This may very well be correct, but if so then what is the right way to handle it, if you want a more familiar window-manager behavior (click to focus)? For example, if you change the mditest.rb example like so... ---

Hi, all - I've searched the archives, and although I've come close to finding a few things that describe my problem, I haven't been able to nail it down. Basically I've got 8 TrippLite SU3000RTXR3U's (Couldn't it be a simple model number, like "4UPS"? hah!), and when I tap in to them with nutc, I see that the status flaps back and forth between OL and OB quite

On Wed, Mar 09, 2016 at 04:11:05PM +1300, Douglas Bagnall wrote: > We looked at this some more, and Andrew seemed to understand and wrote > the attached patch. > > We need to decide if the change in owner is enough reason to refuse > the open(), or if we should just continue. > > On the basis that the owner change is not significant, we reworked the > code to do the

Hey all, I'm running * (1.0.9) with some 7960's. When I pick up the handset it often will flap on and off hook eventually hanging up on me and not realizing that I am still holding the handset. These phones are running with the SIP 7.5.0 image on a LAN (no NAT). I am not sure if this is a phone issue or an Asterisk setting. Ideas?

Whilst tinkering with lvm (which now works great - thanks!), I made a typo which caused the domain to stop booting. I think it was just that I got the config file wrong in terms of which device mapped to which. Anyway, I had specified ''restart=True'' and so the domain was starting to boot, failing, then restarting again. This was the expected behaviour, but it was a pain to kill.

I had an odd situation yesterday, klibc 1.5.17 ipconfig was trying DHCP on all 3 NICs in the server, but one has a bad switch that causes the link on eth2 to go up/down every 10 seconds. IPconfig would just time out. If I tell ipconfig to only try eth0, then DHCP address is configured, and the netboot proceeds 100%. I'll take a peek at the code but maybe someone here is familiar with the

Hi all, I've got a device that seems to become unreachable for about 2 minutes, every hour. From what I can tell, it isn't due to network or server issues. Any ideas? TIA. -- Mike Diehl Diehlnet Communications, LLC. Voice: (505) 903-5700 Fax: (505) 903-5701