Apcupsd NUT Wrapper Script issues with WebNUT Container #5
Comments
|
Hi, thx for opening the issue. Is WebNUT not showing any value at all, or did it just miss the Ciao |
|
@TechaNima hi, i have uploaded a new version in the "test" branch. can you try that out please and paste the LOG again here? It should at least now get one step further. The question is, if WebNUT is requesting the description later on for each and every variable. You can get the updated version here: https://raw.githubusercontent.com/gitmachtl/various/test/upsnutwrapper/upsnutwrapper.sh |
Nada. It doesn't see any UPS info coming from the Proxmox host. I'll have a look at the updated script tomorrow after work. Apcupsd is working normally. I can see all the info correctly on the host and on its built in web page. I have verified that the WebNUT port is open on the Container host VM and docker-compose is fine as well. |
|
I can see both UPSs on WebNUT with the updated script. However, now I'm getting an internal server error when I click either of them in WebNUT. Here's the log from the script: |
|
ok, now WebNUT tries to request have to implement the its just a bit strange, that WebNUT cannot handle such things well. i would also open up a issue on the WebNUT github repo. because my script is returning an i will get back to you when the |
Honestly, all the interactions between your script and WebNUT goes way above my understanding. You'd be much better at explaining this to them. I'm a bit surprised that the script picked up my QNAP at all. It's not setup as a UPS master atm. Honestly, I had forgotten I had even plugged the other UPS into it. Thank you for taking your time to make the script work with WebNUT. I definitely would not be able to. |
|
@TechaNima please check the updated version 1.7 ! The QNAP is not picked up. The script is originally made to be used with Synology and QNAP nas devices. And those devices need a specific name on the Nut-Server. I don't know your setup. The script should be run on the machine that has the |
|
Alrighty. It mostly works now. I don't know if these are reported in the first place, but these values are empty on WebNUT:
|
|
ah... can you edit the lines 213 and 216 in the script and change them from
UPS_ups_timer_start"-1"
UPS_ups_timer_shutdown"-1"
to
UPS_ups_timer_start="-1"
UPS_ups_timer_shutdown="-1"
there are only values if 'apcaccess' reports them.Can you attach a log again?
|
|
Looks clean at a glance |
|
Fixed some stuff that I noticed: Line 83 Those 2 fixed the missing descriptions. |
|
@TechaNima yea thx, i did a super rush implementation for the DESC command so you can check it out. Can you run the |
|
|
thx, your ups is not reporting a value for the apparent power [VA] via the |
|
@TechaNima i have uploaded a new version 1.9. In that version i also included your ups "Back-UPS RS 1500G" with the apparent power value. |
Sure is https://gyazo.com/3e8dbf900bfcd623a07b6be234ebff67 Would be nice if non-reported values didn't show up in WebNUT, but that sounds like a problem for WebNUT devs and I don't care enough to bug them about it tbh. Thank you for updating everything to work with WebNUT <3 |
The logfile would grow and grow. Is only ment to be used for troubleshooting, but not very useful in the longturm. You can also remove the "qnapups" entry in this line various/upsnutwrapper/upsnutwrapper.sh Line 67 in 649ffa3 If you have a QNAP nas, you can directly point it to the IP if your pve host, which is running this wrapper script and it will see your ups. Glad i works for you. Best regards, Martin |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to get it to work with WebNUT container and I'm getting this kind of a log from the script:
The text was updated successfully, but these errors were encountered: