[Nut-upsuser] Various NUT issues/questions+NEW ONE

[Scott Tuc Ellentuch at T-B-O-H]

> > 20060512 080139 100 NA 0 [OL CHRG] NA NA
> > 20060512 080639 100 NA 0 [OL CHRG] NA NA
> > 20060512 081139 100 NA 0 [OL CHRG] NA NA
> > 20060512 081639 90 NA 4 [OB DISCHRG] NA NA
> > 20060512 082139 74 NA 0 [OB DISCHRG] NA NA
> > 20060512 082639 57 NA 0 [OB DISCHRG] NA NA
> > 20060512 083139 40 NA 0 [OB DISCHRG] NA NA
> 
> That was 20 minutes from 100% to 40%. Does not look unusual. 
>
	No, not at all, and that it went to 0 pretty soon 
after that isn't either. What I'm finding unsual is the fact it
ran *3 hours* after that point.
> 
> > 	I guess I wasn't defining the scenerio correctly.
> > 
> > 	1) Power goes out
> > 	2) UPS on Battery
> > 	3) UPS gets to 30% battery
> > 	4) System realizes it, does a "shutdown -h now"
> > 	5) UPS gets to 1% battery 
> > 	6) Power comes back on
> > 
> > 	During the entire time, there was never a power loss to the
> > system
> 
> You did not configure your shutdown scripts correctly; see item 11
> under "Configuring shutdowns for low battery events" in INSTALL.  Your
> computer is supposed to power off (after going through the usual
> shutdown procedure) by letting the UPS know to shut down its
> load. This will cause the UPS to cut power to the computer, and then
> sit there until power comes back on. In the event that the power
> returns while the shutdown is already in progress, the UPS will cut
> power to the computer for a few seconds, then come back on. This
> ensures that your computer will never be in a bad state. 
>
	AH, ok, I thought I saw something about that. I need to 
reinvestigate, thank you.
> 
> > > > [outlet.0.desc]
> > > > [outlet.1.autoswitch.charge.low]
> > > > [outlet.1.desc]
> > > > [outlet.1.switch]
> > > > [ups.delay.shutdown]
> > > > 
> > > > Is that the ONLY items I can get besides :
> > > > 
> > > > battery.charge: 0
> > > > battery.charge.low: 30
> > > > battery.runtime: 00000
> > > > driver.name: mge-shut
> > > > driver.parameter.port: /dev/cuaa0
> > > > driver.version: 2.0.3
> > > > driver.version.internal: 0.65
> > > > outlet.0.desc: Main Outlet
> > > > outlet.0.switchable: 0
> > > > outlet.1.autoswitch.charge.low: 0
> > > > outlet.1.desc: PowerShare Outlet 1
> > > > outlet.1.id: 2
> > > > outlet.1.switch: 1
> > > > outlet.1.switchable: 1
> > > > ups.delay.shutdown: -1
> > > > ups.load: 6
> > > > ups.mfr: MGE UPS SYSTEMS
> > > > ups.serial: unknown
> > > > ups.status: OB DISCHRG LB
> > > 
> > > Hard to say without comparing it to another similar device, but
> > > doesn't look unusual to me. -- Peter
> > > 
> > 	So why isn't UPSLOG not atleast showing the "ups.load"?
> 
> I don't know. Anybody? 
> 
> > May 12 10:26:27 soekris upsd[498]: Client upsmon at 127.0.0.1 set FSD on UPS [ellip
> > se]
> > May 12 10:26:27 soekris upsmon[519]: UPS ellipse at localhost on battery
> > May 12 10:26:27 soekris upsmon[519]: Executing automatic power-fail shutdown
> > May 12 10:26:27 soekris kernel: May 12 10:26:27 soekris upsmon[519]: Executing a
> > utomatic power-fail shutdown
> > May 12 10:26:27 soekris upsmon[519]: Auto logout and shutdown proceeding
> > 
> > 	And it shut it down! It wasn't on battery, I know it.
> 
> Looks like your UPS went on battery at 10:26, about 25 minutes after
> you restarted your computer. Maybe there was a short power outage, or
> you yanked the cable accidentally, or there was a UPS malfunction. In
> any case, since NUT saw that your battery had not yet reached 30
> percent, it shut down immediately, which is what it is supposed to do
> in this situation.
> 
	I've been VERY aware of power conditions here, unless it was
a fluctuation that caused it, or a UPS malfunction, it wasn't me.  I guess I
have to put it down to "fluke".

			Thanks, Tuc