Jammy B
-
Posts
125 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Jammy B
-
-
7 minutes ago, Rysz said:
Thanks for getting back to me, honestly I'm at a loss as to what the problem with your UPS could be. It really does seem like nothing is working as it should (even in their own software, judging by the screenshot). NUT is trying to bring up the driver as it should, but it fails to do so when your system boots for reasons beyond my understanding - especially when considering that the configuration itself doesn't change between the system boot and you manually starting NUT.
A wild guess would be that the UPS takes a long time to get ready for a USB connection once noticing that there's something active on the other end of its USB connection. Meaning that the NUT driver startup at system boot might be happening at a stage where the UPS is not ready for a connection yet. But that would be the first time that I'm seeing something like this and I'm also wondering why this wasn't a problem for you before and has become one now... what's changed except for your batteries?
Honestly after all this trouble and at this stage, if it were my UPS, I would scrap that UPS because I would not be able to trust it after the mess with the batteries not holding their load, voltages all over the place and now the software parts acting up as well - the software remains a big part of the equation after all. I mean a good UPS should be a device you can trust to protect your data and not burn down your house while at it, definitely something to not have to worry about every day.
Used but good condition UPS can be found for cheap and even brand new UPS from reputable brands are not out of this world expensive. Personally I'd invest in a proper Eaton UPS, they have great support as far as NUT is concerned (having sponsored and contributed developing the NUT project for many years) and I personally use them with zero problems - the 5P series being my go-to UPS for almost all applications. I don't want this to be a sales pitch but something to consider from my experience.
If you must keep using your current UPS, have you tried using it with APCUPSD (the in-built "UPS Settings")? If not, it might be worth a try - just make sure to stop the NUT services first. Maybe it'll be the solution to all your problems. 🙂
its a cheap UPS, its just had new batteries put into it.
when they "fail" in a couple years i will look at it then.
in the meantime, is there a script i can make/run that runs 5 minutes after startup to restart Nut?
odd that the NUT starting issue only started after i removed the battery voltage and nominal voltage in the ups.conf, i might re-instate the nominal voltage today to see if it "cures" the issue, then if need be, reinstate the battery voltages and reduce "on battery" runtime to 1 minute instead of 2 minutes.
thanks for looking at it.
-
-
hi @Rysz
new issue now, Server turns off at midnight each night as per sleep scehdule. at 6am it then turns back on via BIOS alarm. but now NUT will not start. when i go into NUT settings and say "Yes" to Start NUT service.
it then starts and runs.
i attach diag prior to manually starting NUT and after i have started NUT.
what have i busted this time?
nut-debug-20240327091949 post.zip nut-debug-20240327091532 pre.zip
-
1 hour ago, Rysz said:
Nothing. NUT will by default show all the variables it can read from the UPS, but there's nothing more that can be done to increase the amount of those variables if the UPS driver does not support reading more. I'd just remove the custom voltage settings if they are not needed anymore and I think you're good. 🙂
[ups] driver = nutdrv_qx port = auto vendorid = 0001 productid = 0000 protocol = hunnox langid_fix = 0x0409 novendor noscanlangid default.battery.voltage.high = 27.50 default.battery.voltage.low = 21.40 default.battery.voltage.nominal = 24.00 default.input.voltage.nominal = 230 runtimecal = 900,100,1800,50removed:
default.battery.voltage.high = 27.50
default.battery.voltage.low = 21.40
default.battery.voltage.nominal = 24.00Then Nut would not start.
changed the attribute to runtime.low and then it loaded.
see how that fares i guess.
-
1
-
-
On 3/19/2024 at 1:01 PM, Rysz said:
Yeah that seems like a multifaceted problem there, perhaps your UPS battery is degraded and couldn't even hold the battery load long enough for NUT to kick in and even begin with the shutdown. From experience 2 minutes can be a very long time depending on your power draw and if your UPS battery is not able to sustain it you'll have a shutdown. That might also be the root problem with the battery voltages inside NUT, so perhaps a new battery would be worth trying and it'll also resolve your voltage situation for those voltage directives to no longer be required. Just an idea... 🙂
Good morning!
i have now replaced the 2no batteries within the Powercool UPS and it is now functioning correctly.
running the UPS directly connected to my laptop via USB and running the software that came with the Powercool doesn't tell me anything about the battery health. As far as it is concerned, the batteries within the unit are fine.
now that i have replaced the batteries, the 2 minute process is working fine.
What do i need to do [besides remove my custom battery voltages] to enable NUT to accurately read from the UPS?
edit to add - the "battery capacity" doesn't change even with new batteries. i think the software is a bit "universal" as it has options to do tests that do not do anything.
-
11 minutes ago, Rysz said:
Sure, no problem, still can you post the NUT Debug Package? Just want to make sure your configuration is good too because that shouldn't have happened even if you didn't see the settings anymore. Did you have to do a parity check when you started the server again or how are you not sure that it didn't shutdown the system as it should have?
yeah its doing a parity check.
looks like the power cut has revealed other issues as when i cut the power to the UPS, the UPS just goes off.
so i've directly connected to the UPS with a laptop via USB and the battery is 0%. i don't know if its just because it has been flattened and needs time to re-charge or if its f##ked. its only as old as my posts on here asking if NUT could get it!
i've disabled sleep/shutdown on the server as it won't finish a Parity check by midnight. when i get back home from work tonight i will have a look at battery % again.
worrying part is the SOC on NUT is dictated by the battery voltages i've manually entered. seems i need to do some further investigation on this as NUT won't know the battery is flat either.
will update this evening. thanks again.
-
5 minutes ago, Rysz said:
No it's not been removed, it's only visible in "Enable Manual Configuration Mode": "No" or "for UPS Driver" because those settings are misleading in manual configuration mode "Yes" as they won't function if you're using a different notification script directive in upsmon.conf (which some people do). If your UPS requires specific configuration lines to work with NUT (as I remember yours does) you'll have to set "Enable Manual Configuration Mode:" to "for UPS Driver" - it'll then respect your manual configuration for the UPS driver but let you configure the shutdowns and other settings at the same time.
Regardless if you didn't make any changes in upsmon.conf (especially to the line: NOTIFYCMD "/usr/sbin/nut-notify") it should've shut down as before even if the settings weren't directly visible anymore. In fact I just tested it from my server with your exact same configuration and it shut down after 2 minutes just fine. Do you perhaps have logs from before the shutdown and are you sure NUT registered that your UPS is on battery correctly? Did you get any notifications that the UPS is on battery?
you are the best!
that fixed it and re-instated my old settings.
thank you.
no notifcations as i wasn't home when it lost power so it couldn't get the messages out.
thanks for remembering how "cool" my Powercool was!
-
running == nut-2.8.1-x86_64-2stable.ssl11
has something been updated to remove the settings on NUT to set
Battery level to initiate shutdown (%):
Runtime left to initiate shutdown (minutes):
Time on battery before shutdown (seconds):
as i seem to have lost those options in NUT settings and we have had two power cuts in the last 12 hours and the server has not switched off due to not being told to.
i had it set 2 minutes after noticing a power cut, shut down.
how do i put that back?
-
9 hours ago, Rysz said:
I see you're using these UPS.CONF settings in your old post:
default.battery.voltage.high = 27.50 default.battery.voltage.low = 21.40 default.battery.voltage.nominal = 24.00If you do this then the driver will guess the battery charge based on the battery voltage. Particularly older batteries cannot hold their maximum voltage well anymore and have sags in voltage (possibly causing frequent re-charges). It's possible this mechanism causes your battery to look as "charging" when fluctuations or changes in voltage occur.
It's also possible that when the UPS sees an increased load when you start up your server it'll start topping up the battery from a lower voltage to a higher voltage (to ensure providing as much battery time as possible), as opposed to times when the UPS load is minimal and the battery can rest with a lower voltage.
Normally the UPS itself provides information about the battery charge, so these settings are not needed and the charge provided is an estimation at best. Please try removing these settings from the UPS.CONF and see if the UPS then provides the actual and not voltage-based estimation of the UPS battery charge.
This is in part related to what this user was warning about here in the old topic:
removing those 3 lines of code causes NUT to not function.
whilst they aren’t necessarily correct, the config works enough that when on battery it then powers off after 2 minutes.
what do you recommend I do next?
-
6 hours ago, Jammy B said:
no screen on my basic UPS - https://www.cclonline.com/pc-1000va-powercool-smart-ups-1000va-3-x-uk-plug-2-x-iec-rj45-x-2-usb-led-display/
the charging indicator is solid green which means charged and that doesn't change unless i have a powercut or manually kill power to it.
it powers my Unraid machine, UDMPRO, switch and CCTV NVR no problem. its never switched off and we don't get many powercuts and when we have its been flawless in signalling the Unraid machine to switch off.
its now on 52% charged as well. it was on 3% when i posted this morning
is there a setting i might have put in to it that it is reading the wrong thing, but what would increase over time?
my 3 year old thread -
Now “charged”
-
2 hours ago, Rysz said:
Does the UPS itself show as 100% charge (on the UPS display/LEDs) when this happens or does it show any indication that it's maybe really charging the battery? This is very very weird, especially that it "charges itself up" over time is usually really only seen when the UPS is in fact charging the battery somehow. I can't picture any programmatic problem that would make the driver increase the charge from 0% to 100% over time unless that's what the UPS also does... 😕
no screen on my basic UPS - https://www.cclonline.com/pc-1000va-powercool-smart-ups-1000va-3-x-uk-plug-2-x-iec-rj45-x-2-usb-led-display/
the charging indicator is solid green which means charged and that doesn't change unless i have a powercut or manually kill power to it.
it powers my Unraid machine, UDMPRO, switch and CCTV NVR no problem. its never switched off and we don't get many powercuts and when we have its been flawless in signalling the Unraid machine to switch off.
its now on 52% charged as well. it was on 3% when i posted this morning
is there a setting i might have put in to it that it is reading the wrong thing, but what would increase over time?
my 3 year old thread -
-
i've had NUT running a couple years now and one thing it does i still cannot solve.
the UPS runs 24/7.
my Unraid server does not, its on from 6am to midnight each day. When Unraid first boots, the battery % is at 0%. some point this afternoon, it have steadily "charged" itself up and got to 100%. i don't understand why it does this when it is 100% already as it is fully charged and on 24/7!
any suggestions on what i need to check/alter to make it display correctly? or am i totally misinterpreting something?
-
i've just seen the reddit post about the current installs expiring 1/1/24.
i'm running controller 5.14.23 with 12 or so sites on it.
can i migrate to this reborn or do i need to do something else?
edit - went for it to 8.0.24. it went without a hitch and is working great.
thank you.
-
2
-
-
40 minutes ago, Malfurious said:
That looks like what normally appears on the screen when I boot a Windows 11 VM booting from a passed through NVME drive. Shouldn't be an issue unless its not booting past this?
Yeah it’s loading up fine. Just normally a blank screen on boot. Only change is updating to 6.11.5
-
done the update, updated virtio drivers.
VM works but curious what to do to clear the messages.
-
3 hours ago, jojo345 said:
Since some time it`s not 100% working anymore. It does not detect array. You can add all your array discs to " monitor discs outside array" and it will work.
thanks for the tip, I have added the array disks to the outside setting. will report back how it fares.
-
Dynamix S3 Sleep
running latest stable unraid.
Can someone help me please?
i've setup S3 Sleep and so far was working fine.
but now it seems to ignore its own rules and turns itself off.
by that, i have it set to switch off from midnight onwards. typically it might stay on till around 1am then switch off due to activity on the server.
now it switches off bang on 12:10am every night [as the 10 minutes is the "extra delay" set on the plugin]
it aborted my parity check to switch itself off last night.
if people are watching Plex, it switches itself off.
it didn't do this before.
i attach a screenshot of my settings in hope that someone tells me i've ticked something!
-
5 hours ago, SimonF said:
None that I can think off what does the NUT detail show?
nothing jumps out at me.
-
had read errrors last night so done the usual power off, pull the drive, power up, start/stop array. turn off, reconnect and power on and re-build.
but i noticed NUT reporting 0% and charging. [its now on 1%]
i didn't touch the UPS, nor turn it off.
any ideas? normally a power cycle wouldn't mess with that.
-
4 minutes ago, SimonF said:
Guess should be 900,100,1800,50 for 15 mins full load. but i would go with values you are hsppy with.
thanks, the figures don’t make sense. I’m glad I asked.
Don’t worry. I’m not going to hold you to figures. UnRAID will power off 5 minutes after being told it’s on battery.
I just didn’t want it to panic it only had 5 minutes of capacity when the load is only 20-25%!
-
6 minutes ago, SimonF said:
Works for me
This is my config. I have Powercool 2000VA. Guessing you did update once you change the ups.conf and it takes a min or so before it appears + you need to refresh page.
[ups] driver = nutdrv_qx port = auto default.battery.voltage.high = 40.40 default.battery.voltage.low = 31.20 default.battery.voltage.nominal = 36.0 runtimecal=300,100,600,50
nice! just logged back in and it has it now.
What do you think to my 450,100,900,50?should I reduce it to match yours?
-
entered what you said but it still doesn't display anything in Runtime Left.
i've tried runtimecal=300,100,600,50
then i thought, go further with runtimecal=450,100,900,50 [based on 15 minutes]
but it still doesn't display anything.
-
4 hours ago, SimonF said:
Looks like Powercool doesn't report runtime so it needs to be calculated, So I looked at the driver source and documentation and found the way to get it display. I am struggling to find estimate runtime for the UPS on full load and half load. as does seem to be in Powercool documentation.
You need to add this to ups.conf
runtimecal=300,100,600,50
First number is duration in seconds, next is load 100%, Value for next load value in Seconds and finally load, i.e. half.
if it helps. It says 15-20 minutes at full load on battery.
-
this is my NUT config.
re-reading your question, no. i haven't got "Runtime Left" working.
its the last part of my puzzle to enable my Powercool 1000 to be fully displayed.
[Plugin] NUT v2 - Network UPS Tools
in Plugin Support
Posted
thanks for the script. i've put that in as even after adding the nominal voltage in yesterday, NUT failed this morning.
will report back tomorrow if the script does the job.
thank you for the assistance on all this as always.