-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nut-upsmon broken - tmpfs configuration files not created #6644
Comments
Will look into it; it was working for me, but I don't remember if I did upsmon standalone...will review. I may have had a PR for that that I closed. |
@petvoigt For your work around you also need It looks like I missed submitting the fix for upsmon on it's own. Will create a PR and and backport PR and we'll see if the backport gets accepted for 18.06. |
@petvoigt Also, after the chmod of '$UPSMON_C' and '/var/etc/nut.conf' you need
I know how I missed it now...didn't test upsmon alone and the way I was using nut-server it took care of this business. |
Will test the above PR and submit. |
@cshoredaniel, ah, sounds good. Thank your for your quick reply and many thanks for the quickly updated NUT documentation under https://openwrt.org/docs/guide-user/services/ups/software.nut. UID nut and GID nut are present on my system:
However, I dont' know what to do with $UPSMON_C - in fact it is empty. I tried:
|
Accidently closed issue (wrong button), reopened immetiately. |
@petvoigt Sorry for not being clear: that needs to be in the initscript |
@cshoredaniel, thanks for clarifying. After the above mentioned changes to /etc/init.d/nut-monitor I further have to do after every reboot:
Could you please tell me, which NUT packages are affected by your patch and could you please report here, when I can update the affected packages to test your changes? |
Only package nut-upsmon will be affected and it's just updating the initscript appropriately Ah, I caught /var/etc/nut in my PR, will check nut.conf. And I wouldn't count on updates to the packages a downloads.openwrt.com until the .1 release (but that probably won't be that long as there are already errata being corrected in core too). |
I'll post the final initscript revision here (after testing) so you can at least have that on-router until the updated package is available. |
Thanks a lot. I will keep this issue open until I have tested at least the updated initscript. |
If you could leave it until PR is merged that would be best! That way others can find it. |
OK, if I understand correctly, this will be after testing the .1 release. |
Oh, no worries, it'll autoclose when the PR is merged due to commit message. |
OK, did not know this;-) |
Ok, put the script below in /etc/init.d/nut-monitor on the device and you ought to be good on reboot.
|
nut-monitor failed to create required dir /var/etc/nut, as well as failing to set appropriate user on the directory and conf files. Fixing this closes openwrt#6644 Signed-off-by: Daniel F. Dickinson <cshored@thecshore.com> (cherry picked from commit 98fdf16)
Script runs like a charm, thanks a lot. |
Excellent! And thank you for your helping get this fixed! |
On 2018-08-02 02:22 PM, Dr. Peter Voigt wrote:
Script runs like a charm, thanks a lot.
Just FYI, because of a CVE it looks like 18.06.1 is going to be built
and may be available this weekend. If it includes packages you may get
the nice present of the updated NUT a lot sooner than expected!
Also, I've updated the Wiki page for NUT with proper UCI documentation.
Regards,
Daniel
|
On Wed, 08 Aug 2018 10:31:27 -0700
Daniel Dickinson <notifications@github.com> wrote:
On 2018-08-02 02:22 PM, Dr. Peter Voigt wrote:
> Script runs like a charm, thanks a lot.
>
Just FYI, because of a CVE it looks like 18.06.1 is going to be built
and may be available this weekend. If it includes packages you may
get the nice present of the updated NUT a lot sooner than expected!
Also, I've updated the Wiki page for NUT with proper UCI
documentation.
Regards,
Daniel
Thanks for this hint. I have scheduled upgrade time this weekend for
18.06.1. The NUT documentation has become valuable and comprehensive -
nice.
Regards,
Peter
|
Maintainer: @cshoredaniel
Environment: AMD GX-412TC SOC, PC Engines APU2, OpenWrt 18.06.0, x86_64)
Description:
Today I performed a sysupgrade via LUCI webGUI from 17.01.4 to 18.06.0.
Installed NUT packages:
I have configured NUT as slave to monitor a master in my LAN, e.g. MODE=netclient in /etc/nut.conf.
/etc/init.d//etc/init.d/nut-monitor cannot be started as it complains about missing /var/etc/nut directory and files in it.
I can manually configure and start nut-upsmon:
As a partial workaround I added to start_service() of /etc/init.d//etc/init.d/nut-monitor the following code:
This partial workaround preserves the subdirectory "nut" under /var/etc during a reboot. However, nut-upsmon does not start automatically during boot.
The text was updated successfully, but these errors were encountered: