Jump to content

Rysz

Community Developer
 View Profile  See their activity

  • Posts

    470

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Posts posted by Rysz

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted · Edited by Rysz

    3 minutes ago, Masterwishx said:

    is also good ?

    upscmd shutdown.return - Turn off the load and return when power is back

     

    No, because this will also kill the power of the UPS instantly and result in an unclean shutdown on all your clients and server. Always use only this command to trigger the NUT shutdown routine: It ensures a clean shutdown of your clients and your server, will also disable the UPS power (if that is configured in the GUI) after the clean shutdown and start the UPS again when the power is back.

      

    upsmon -c fsd

     

    • Thanks 1

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted

    3 minutes ago, Masterwishx said:

    What the right command for fsd (shutdown) the ups and server and all connected pc ,if i dont want to wait 10 min 

    as i have in setting Time on Battery before Shutdown (Minutes): 10 ?

      

    /etc/rc.d/rc.nut shutdown 2>&1 | logger -t "rc.nut"

     

     

    Use this command to start the NUT shutdown routine now: 

    upsmon -c fsd

     

    The command you posted would result in an unclean shutdown because it would kill the power instantly.

    • Like 1

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted

    12 minutes ago, Puntoboy said:

    I've been trying to connect my Synology NAS to Unraid using this plugin without success. I have two options in Synology DSM to connect to a network UPS server, Synology NAS and SNMP. Obviously Unraid isn't a Synology NAS, so that doesn't work (I did try just in case). By default the NUT server doesn't seem to support SNMP either, anyone set this up?

     

    Is your UPS physically connected to your UNRAID server or your Synology NAS?

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted · Edited by Rysz

    15 hours ago, Tim_J said:

    Hi Everyone,

    I have question about Back-UPS XS 1300G Battery upgrades. My original batteries died and i replaced them with lead acid batteries different capacity ( much higher ) and same voltage. Is it possible to " explain" to UPS that need s to calculate estimated times for battery life time? It reports 1:15 minutes on 24V 130AH batteries. Also, what is the format of command in upc.conf that i can change battery manufacture date? i tried "battery.mfr.date : 2023/06/10" , battery.mfr.date = 2023/06/10 but that just disables plugin.

     

    Sorry, im new in all this and my programming skils are limited with copy and paste. However, i would like to extend UPS backup time .

    Any help is appreciated,

     

    Best Regards,

    Tim

    itjtower-diagnostics-20240508-1107.zip 162.07 kB · 0 downloads

     

    Sorry, I can't provide support for usage cases outside of manufacturer's specifications. For safety reasons and from experience I'd also strongly advise against using any different battery capacity than those your UPS was rated for by the UPS manufacturer. The electrical mechanisms in the UPS may not safely be able to charge and/or discharge the higher capacity battery you are using, which may be hazardous for several reasons (fire, electrical shock, ...)

     

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted · Edited by Rysz

    1 hour ago, luzfcb said:

     

    @Rysz Thanks again for generating the new build from the NUT master branch. The NUT fixes for Gamatronic Driver worked, and it's finally the first time I've been able to get NUT to start on my UPS "Nobreak NHS Premium PDV Senoidal 1500 VA" from Brazillian brand "NHS Sistemas de Energia"



    image.thumb.png.e2b190353a0e1c29bbf6c4bdcb8a22c5.png

     


    Hey, thanks for reporting back and glad it works for you now. I've just pushed an update to NUT where the "preview (latest build)" backend is now today's master including the fixes for your driver. So after updating NUT you just need to choose the "preview (latest build)" backend in NUT Settings and reboot your system afterwards, then you'll be on that driver natively (also surviving any system reboots).

     

    Thanks again for your help and patience investigating this issue. 🙂 

     

    Samba Worm VFS Module against Ransomware

    in Feature Requests

    Posted · Edited by Rysz

    It would be great if the Samba Worm VFS module could be configurable on a per-share basis through the Web GUI (as on TrueNAS). It's extremely simple to integrate into an individual share configuration and would help harden Samba shares against ransomware from Windows clients a bit, something I'm sure many users here would appreciate. It's really just an additional Samba layer that can be activated and deactivated without trace at any time, so it works cleanly and without messing with the Linux file permissions or actual files underneath.

     

    Most of the ransomware originates from Windows clients. What the Worm VFS module does (when activated) is allowing to put new files onto a read/write Samba share, but disallowing writes to those files after a certain amount of time has passed (the grace period). So you could set up a grace period of 24 hours, where you can still make changes to any new files from these last 24 hours and once that time has passed they're turned read-only on that Samba share. This could be very useful for media libraries, as an example, where later changes to the files by the user are not to be expected.

     

    It's just two lines in the share configuration: 

    vfs objects = worm
worm:grace_period = 86400     # 1 day

     

    https://wiki.samba.org/index.php/Using_the_worm_VFS_Module

     

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted

    19 hours ago, pcpai said:

    Need help

    some one uses a UPS from EuroTech?

    EuroTech UPS2000VA

     

    [nutdev1]
    driver = "nutdrv_qx"
    port = "auto"
    vendorid = "0001"
    productid = "0000"
    bus = "001"

      

    May  4 15:19:59 PCPAI-HOME ool www[28452]: /usr/local/emhttp/plugins/nut-dw/scripts/start
May  4 15:20:00 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:20:02 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:20:02 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:20:02 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:20:09 PCPAI-HOME rc.nut: Device not supported!
May  4 15:20:09 PCPAI-HOME rc.nut: Device not supported!
May  4 15:20:09 PCPAI-HOME rc.nut: Network UPS Tools - Generic Q* USB/Serial driver 0.39 (2.7.4.1)
May  4 15:20:09 PCPAI-HOME rc.nut: USB communication driver 0.43
May  4 15:20:09 PCPAI-HOME rc.nut: Driver failed to start (exit status=1)
May  4 15:20:09 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1


May  4 15:28:54 PCPAI-HOME ool www[56806]: /usr/local/emhttp/plugins/nut-dw/scripts/stop
May  4 15:28:55 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:28:57 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:28:57 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:28:57 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:28:58 PCPAI-HOME rc.nut: Stopping the NUT services... 
May  4 15:29:00 PCPAI-HOME rc.nut: Can't open /var/run/nut/blazer_ser-ups.pid: No such file or directory
May  4 15:29:00 PCPAI-HOME rc.nut: Can't open /var/run/nut/blazer_ser-auto.pid either: No such file or directory
May  4 15:29:00 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:29:06 PCPAI-HOME ool www[57804]: /usr/local/emhttp/plugins/nut-dw/scripts/start
May  4 15:29:07 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:29:09 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:29:09 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:29:09 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:29:10 PCPAI-HOME rc.nut: Network UPS Tools - Megatec/Q1 protocol serial driver 1.58 (2.7.4.1)
May  4 15:29:10 PCPAI-HOME rc.nut: 
May  4 15:29:10 PCPAI-HOME rc.nut: Fatal error: 'vendorid' is not a valid variable name for this driver.
May  4 15:29:10 PCPAI-HOME rc.nut: 
May  4 15:29:10 PCPAI-HOME rc.nut: Look in the man page or call this driver with -h for a list of
May  4 15:29:10 PCPAI-HOME rc.nut: valid variable names and flags.
May  4 15:29:10 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:29:11 PCPAI-HOME rc.nut: fopen /var/run/nut/upsd.pid: No such file or directory
May  4 15:29:11 PCPAI-HOME rc.nut: listening on 0.0.0.0 port 3493
May  4 15:29:11 PCPAI-HOME upsd[58162]: listening on 0.0.0.0 port 3493
May  4 15:29:11 PCPAI-HOME upsd[58162]: Can't connect to UPS [ups] (blazer_ser-ups): No such file or directory
May  4 15:29:11 PCPAI-HOME rc.nut: Can't connect to UPS [ups] (blazer_ser-ups): No such file or directory
May  4 15:29:11 PCPAI-HOME upsd[58163]: Startup successful
May  4 15:29:12 PCPAI-HOME rc.nut: fopen /var/run/nut/upsmon.pid: No such file or directory
May  4 15:29:12 PCPAI-HOME rc.nut: UPS: [email protected] (master) (power value 1)
May  4 15:29:12 PCPAI-HOME rc.nut: Using power down flag file /etc/nut/no_killpower
May  4 15:29:12 PCPAI-HOME upsmon[58166]: Startup successful
May  4 15:29:12 PCPAI-HOME upsmon[58166]: Warning: running as one big root process by request (upsmon -p)
May  4 15:29:12 PCPAI-HOME upsd[58163]: User [email protected] logged into UPS [ups]
May  4 15:29:12 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:12 PCPAI-HOME upsmon[58166]: Communications with UPS [email protected] lost
May  4 15:29:17 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:17 PCPAI-HOME upsmon[58166]: UPS [email protected] is unavailable
May  4 15:29:22 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:27 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:32 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:37 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:42 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:47 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:52 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:57 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:30:02 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:30:07 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:30:07 PCPAI-HOME ool www[57807]: /usr/local/emhttp/plugins/nut-dw/scripts/restart
May  4 15:30:07 PCPAI-HOME rc.nut: Stopping the NUT services... 
May  4 15:30:07 PCPAI-HOME upsmon[58166]: Signal 15: exiting
May  4 15:30:07 PCPAI-HOME rc.nut: Network UPS Tools upsmon 2.7.4.1
May  4 15:30:07 PCPAI-HOME upsd[58163]: User [email protected] logged out from UPS [ups]
May  4 15:30:07 PCPAI-HOME upsd[58163]: mainloop: Interrupted system call
May  4 15:30:07 PCPAI-HOME upsd[58163]: Signal 15: exiting
May  4 15:30:07 PCPAI-HOME rc.nut: Network UPS Tools upsd 2.7.4.1
May  4 15:30:09 PCPAI-HOME rc.nut: Can't open /var/run/nut/blazer_ser-ups.pid: No such file or directory
May  4 15:30:09 PCPAI-HOME rc.nut: Can't open /var/run/nut/blazer_ser-auto.pid either: No such file or directory
May  4 15:30:09 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:30:13 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:30:16 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:30:16 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:30:16 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:30:17 PCPAI-HOME rc.nut: Fatal error: unusable configuration
May  4 15:30:17 PCPAI-HOME rc.nut: Network UPS Tools - Megatec/Q1 protocol serial driver 1.58 (2.7.4.1)
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut: Unable to open auto: No such file or directory
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut: Things to try:
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut:  - Check 'port=' in ups.conf
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut:  - Check owner/permissions of all parts of path
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut: Driver failed to start (exit status=1)
May  4 15:30:17 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:31:59 PCPAI-HOME ool www[63635]: /usr/local/emhttp/plugins/nut-dw/scripts/start
May  4 15:32:00 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:32:02 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:32:02 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:32:02 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:32:05 PCPAI-HOME rc.nut: No supported UPS detected
May  4 15:32:05 PCPAI-HOME rc.nut: Network UPS Tools - Megatec/Q1 protocol USB driver 0.20 (2.7.4.1)
May  4 15:32:05 PCPAI-HOME rc.nut: Driver failed to start (exit status=1)
May  4 15:32:05 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:32:12 PCPAI-HOME ool www[64160]: /usr/local/emhttp/plugins/nut-dw/scripts/start
May  4 15:32:13 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:32:15 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:32:15 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:32:15 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:32:18 PCPAI-HOME rc.nut: No supported UPS detected
May  4 15:32:18 PCPAI-HOME rc.nut: Network UPS Tools - Megatec/Q1 protocol USB driver 0.20 (2.7.4.1)
May  4 15:32:18 PCPAI-HOME rc.nut: Driver failed to start (exit status=1)
May  4 15:32:18 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1

    dont know what to do

    tried on legacy and 2.8.2

     

    Sorry, it doesn't seem like this UPS manufacturer is supported by NUT at all.

    It's also not listed in the hardware compatibility list: https://networkupstools.org/stable-hcl.html

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted

    13 hours ago, luzfcb said:

     

    Thank you for generating the compiled version with DEBUG active, however unfortunately I still haven't been able to find out for sure the cause of the segmentation fault.

    However, I discovered some useful settings for debugging and extra configurations.
     

    In ups.conf , there are some additional settings that live outside the driver section, that is, they must be placed BEFORE the [driver-configuration-name] and are not valid to define inside the driver section.
    (https://github.com/networkupstools/nut/blob/ff045c089b362085ec0abd651da5e9216c49e281/conf/ups.conf.sample#L45-L80)

    In my case, I changed the "Enable Manual Configuration:" option in the Nut Unraid UI to "for UPS Driver" and my ups.conf looked like this:
      

    maxretry = 3
user = nut
group = nut
debug_min = 6
synchronous = yes

[nhs]
driver = gamatronic
port = /dev/ttyACM0
desc = "nhs_1500va"


    After that, I started the NUT driver directly (gamatronic) with some debug options and got this:

    > Note: In case anyone reads this and doesn't understand, each NUT driver is an independent executable, so I can use it directly instead of using `upsdrvctl`. The problem with using upsdrvctl for debugging is that not every driver has the same arguments and upsdrvctl can hide some of the error messages, which makes debugging difficult;

      

    root@f:~# /usr/libexec/nut/gamatronic -DDDDDDD -a nhs -u root
Network UPS Tools - Gamatronic UPS driver 0.03 (2.7.4.1)
   0.000000     [D5] send_to_all: SETINFO driver.parameter.port "/dev/ttyACM0"
   0.000019     [D1] debug level is '7'
   0.000296     [D5] send_to_all: SETINFO device.type "ups"
Connected to UPS on /dev/ttyACM0 baudrate: 2400
   2.209413     [D5] send_to_all: SETINFO driver.version "2.7.4.1"
   2.209425     [D5] send_to_all: SETINFO driver.version.internal "0.03"
   2.209430     [D5] send_to_all: SETINFO driver.name "gamatronic"
   2.209435     [D1] PC-->UPS: "^P003AP1"
   2.209506     [D1]  send returned: 8
   3.631085     [D1] UPS<--PC: "3,6,7,8,9,10,14,16,18,19,20,21,224,28,4,28,29,33,36,37,38,39,43"
   3.631097     [D1] PC-->UPS: "^P003AP2"
   3.631171     [D1]  send returned: 8
   5.130488     [D1] UPS<--PC: "47,51,54,55,56,57,58,59,61,62,63,64,65,68,69,776,77,80,81,82,84,87,88,7,88,89"
   5.130515     [D1]  Query 0 is ST5
   5.130518     [D1]  Querying varnum 3
   5.130522     [D1]  Querying varnum 6
   5.130526     [D1]  Querying varnum 7
   5.130530     [D1]  Querying varnum 8
   5.130535     [D1]  Querying varnum 9
   5.130543     [D1]  Querying varnum 10
   5.130548     [D1]  Querying varnum 14
   5.130552     [D1]  Query 1 is NOM
   5.130554     [D1]  Querying varnum 16
   5.130557     [D1]  Query 2 is ST1
   5.130559     [D1]  Querying varnum 18
   5.130564     [D1]  Querying varnum 19
   5.130568     [D1]  Querying varnum 20
   5.130570     [D1]  Querying varnum 21
Segmentation fault


    Apparently, the driver is able to initiate communication with the UPS, but fails at some point.

    That said, 4 hours ago some fixes for the gamatronic driver were merged into NUT ( gamatronic driver revised for safer memory operations. [#2427].
    I'm hoping this is a possible fix for the bug I'm experiencing.


    @Rysz  If it's not too much to ask, could you generate a new build from the current master branch of NUT?

     

    nut-2.8.2-x86_64-2debug.txz


    Here we go - current master with debug symbols, same procedure as before.

    Please do report back again with your findings - thanks in advance! 🙂 

     

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted

    20 minutes ago, luzfcb said:

     

    Thank you for generating the compiled version with DEBUG active, however unfortunately I still haven't been able to find out for sure the cause of the segmentation fault.

    However, I discovered some useful settings for debugging and extra configurations.
     

    In ups.conf , there are some additional settings that live outside the driver section, that is, they must be placed BEFORE the [driver-configuration-name] and are not valid to define inside the driver section.
    (https://github.com/networkupstools/nut/blob/ff045c089b362085ec0abd651da5e9216c49e281/conf/ups.conf.sample#L45-L80)

    In my case, I changed the "Enable Manual Configuration:" option in the Nut Unraid UI to "for UPS Driver" and my ups.conf looked like this:
      

    maxretry = 3
user = nut
group = nut
debug_min = 6
synchronous = yes

[nhs]
driver = gamatronic
port = /dev/ttyACM0
desc = "nhs_1500va"


    After that, I started the NUT driver directly (gamatronic) with some debug options and got this:

    > Note: In case anyone reads this and doesn't understand, each NUT driver is an independent executable, so I can use it directly instead of using `upsdrvctl`. The problem with using upsdrvctl for debugging is that not every driver has the same arguments and upsdrvctl can hide some of the error messages, which makes debugging difficult;

      

    root@f:~# /usr/libexec/nut/gamatronic -DDDDDDD -a nhs -u root
Network UPS Tools - Gamatronic UPS driver 0.03 (2.7.4.1)
   0.000000     [D5] send_to_all: SETINFO driver.parameter.port "/dev/ttyACM0"
   0.000019     [D1] debug level is '7'
   0.000296     [D5] send_to_all: SETINFO device.type "ups"
Connected to UPS on /dev/ttyACM0 baudrate: 2400
   2.209413     [D5] send_to_all: SETINFO driver.version "2.7.4.1"
   2.209425     [D5] send_to_all: SETINFO driver.version.internal "0.03"
   2.209430     [D5] send_to_all: SETINFO driver.name "gamatronic"
   2.209435     [D1] PC-->UPS: "^P003AP1"
   2.209506     [D1]  send returned: 8
   3.631085     [D1] UPS<--PC: "3,6,7,8,9,10,14,16,18,19,20,21,224,28,4,28,29,33,36,37,38,39,43"
   3.631097     [D1] PC-->UPS: "^P003AP2"
   3.631171     [D1]  send returned: 8
   5.130488     [D1] UPS<--PC: "47,51,54,55,56,57,58,59,61,62,63,64,65,68,69,776,77,80,81,82,84,87,88,7,88,89"
   5.130515     [D1]  Query 0 is ST5
   5.130518     [D1]  Querying varnum 3
   5.130522     [D1]  Querying varnum 6
   5.130526     [D1]  Querying varnum 7
   5.130530     [D1]  Querying varnum 8
   5.130535     [D1]  Querying varnum 9
   5.130543     [D1]  Querying varnum 10
   5.130548     [D1]  Querying varnum 14
   5.130552     [D1]  Query 1 is NOM
   5.130554     [D1]  Querying varnum 16
   5.130557     [D1]  Query 2 is ST1
   5.130559     [D1]  Querying varnum 18
   5.130564     [D1]  Querying varnum 19
   5.130568     [D1]  Querying varnum 20
   5.130570     [D1]  Querying varnum 21
Segmentation fault


    Apparently, the driver is able to initiate communication with the UPS, but fails at some point.

    That said, 4 hours ago some fixes for the gamatronic driver were merged into NUT ( gamatronic driver revised for safer memory operations. [#2427].
    I'm hoping this is a possible fix for the bug I'm experiencing.


    @Rysz  If it's not too much to ask, could you generate a new build from the current master branch of NUT?

     

    Thanks for the detailed write-up, I'll build a new debug package as soon as possible (most likely tonight). 🙂 

    • Like 1

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted

    4 minutes ago, SimonF said:

    Hi @Rysz

     

    Has a changed happend in the backend to report trim? Why is this amber and not green?

     

    On Line - Trimming Input

     

    There's three priorities in the GUI:

    • Green - nothing out of the ordinary is happening (OL, CHRG, CAL)
    • Orange - something out of the ordinary is happening (OB, BYPASS, DISCHRG, TRIM, BOOST)
    • Red - something critical is happening (LB, HB, RB, OVER, OFF, FSD)

    So orange is not necessarily bad, it's just that the UPS is doing something for the user to notice in the GUI.

     

    Unraid Forums Upgrade

    in Announcements

    Posted · Edited by Rysz

    grafik.thumb.png.2c3c41c5141c68b17249bd4301d38e12.png

     

    The last active topic seems too cramped in comparison to the huge part with the forum name (having lots of unused white-space).
    Removing the width: 100% on .ipsDataItem_main it'd look like this (better in my opinion):

     

    grafik.thumb.png.72850844bd73401bd502c1ae5639daf1.png

     

    I know it's a work in progress and I love the new forum software, but I'm not too happy about some changes myself. I think the light mode is too bold (better lower font-weight?) and bright (better light gray instead of full white?), while some layout (example see above), font and color choices still look a bit hacked together rather than feeling "native" yet (in lack for a better word). Perhaps a better choice would have been to keep the fonts and color palettes that people were used to, while upgrading mostly the forum software and the layout around it. Nonetheless thankful for all the (ongoing) hard work put into improving the website and community. 🙂 

     

    • Like 2

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted

    4 minutes ago, d3m3zs said:

    Sorry for weird question, but how can I change "Time on Battery before Shutdown " ? There is 5 minutes and all item are disabled.image.thumb.png.9ac96c7f8964cd986990859edc1c10ba.png

     

    You need to stop NUT, change the setting and then start NUT again - it cannot be changed when it's running.

    • Like 1

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted · Edited by Rysz

    2 hours ago, Mr.meowgi said:

    Ive been getting this error daily for as long as i can remember  

    usbhid-ups[14966]: nut_libusb_get_report: Input/Output Error
usbhid-ups[14966]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
usbhid-ups[14966]: nut_libusb_get_string: Pipe error

    But I don’t know how to set the pollonly flag. Any idea how?

     

    also i get lots of errors like this one that fills up and i dont know why. 

    nginx: 2024/04/30 12:35:07 [alert] 12245#12245: worker process 21789 exited on signal 6

     

      

    pollonly

    Just put this in UPS.CONF on line 8 using GUI configuration editor and restart NUT afterwards. But if all works as it should, I'd just ignore these messages in syslog and not mess around with extra settings.

     

    [PLUGIN] mergerFS for UNRAID (Support Topic)

    in Plugin Support

    Posted

    8 minutes ago, tazire said:

    I know nothing about mergerfs tbh but with the likely introduction of multiple arrays is this a good option for merging 2 array pools and then a cache pool as a single share, for want of a better word, assuming unraid doesnt introduce a solution for this themselves. 

     

    And also will your new snapraid plugin complement a setup like that?

     

    I have no information about multi array support or how it will be implemented, sorry about that. mergerFS basically can pool multiple disk mount-points together, so regardless where the data is residing physically it can then be accessed through one single folder (the mergerFS mount-point). Some users use this functionality to pool data on the array and data residing in the cloud together (e.g. for Plex), others use it to pool multiple disks mounted through Unassigned Devices together for better accessing through a single custom share/location on the server. I'm not sure how well it would perform pooling already pooled data (if I understood you correctly there, since array pools and cache pools already are pooled you'd be pooling pooled data) and if or how that would interfere with Unraid. Regarding SnapRAID, that's not really got anything to do with mergerFS. Basically SnapRAID provides parity for multiple individual disks (mounted in their individual disk mount-points), but doesn't pool array data by default (as Unraid does with the user shares). So mergerFS could be used to pool a SnapRAID array (consisting of a bunch of individual disk mount-points) into one folder (the mergerFS mount-point) for e.g. later sharing through a custom SMB/NFS share. Hope that makes sense a bit. 🙂 

    [Plugin] LLDP for UNRAID (6.10+ / Support Topic)

    in Plugin Support

    Posted · Edited by Rysz

    3 hours ago, AnnabellaRenee87 said:

    Weird problem, LLDP on the server looks to only be seeing my other LAN port on the server that's unplugged, I need it to be on the other one, It's only seeing eth1, not eth0.

     

     

    If that makes sense.

     

    Screenshots attached of what's being detected and what the settings are.image.thumb.png.025bfeee6db21bbd63ce4a05fb5da248.png

    image.png

    server-diagnostics-20240430-0759.zip 233.47 kB · 0 downloads

     

    PS,

     

    Here's my Routing Table if it's needed.

    image.png

     

    LLDP broadcasts on all eth* (so eth0, eth1, eth2 ...) interfaces, so both on eth0 and eth1 in your case. It seems to be advertising as the management IPs both the IPv6 IP of your eth0 interface (as you have IPv6 enabled there) and the IPv4 IP of your eth1 interface (as you have IPv6 disabled there). I think that it's doing what it should, considering you have two physical interfaces (eth0, eth1) and it's advertising both with the respective default IP of each respective interface. Would you have liked for it to advertise the IPv4 IP of eth0 (even if you're using IPv6)? I can try to add a setting to manually override the advertised management IPs, but I'll have to look how to implement that so might take a while.

     

    [PLUGIN] SnapRAID on UNRAID

    in Plugin Support

    Posted · Edited by Rysz

    SnapRAID on UNRAID

    A plugin for advanced users installing SnapRAID onto UNRAID systems.

     

    Possible Use-Cases:

    • Parity protection and a degree of corruption detection/repair for custom-mounted (e.g. using UD), possibly mergerFS-fused/pooled, unassigned disks outside of the primary Unraid array - either due to not always being online (cold backups) or exceeding the maximum possible array size of 30 disks, as commonly seen with large mixed disk JBOD/DAS solutions not wanting or being able to go full ZFS (primary use-case).
    • A degree of corruption detection/repair for rarely changing large file libraries (e.g. on media or backup servers) in conjunction with Unraid parity, sacrificing an Unraid array data disk for SnapRAID parity to leverage the advantages of both Unraid and SnapRAID (experimental use-case).
    • You tell me - post here if you have another exciting use case that worked well for your specific storage needs.


    General Usage Warning:

    As with any software interacting with your data, only ever use it on backed up data and in combination with a solid backup strategy.

    Read the manual and help-texts before acting and if you do not understand a 100% what you are doing, please just do not do it... 🙂 

     

    This thread is not really for teaching how to use SnapRAID. It is primarily intended for reporting and solving problems around the plugin itself. If the detailed SnapRAID manual and amply provided hover/F1 help-texts are not enough to bring clarity on using the software, this plugin will most likely have no real benefit for you (no offense). It was made for advanced users with very specific storage needs, not to just play around with without purpose (if you value your data).

     

    Installable via Community Applications

     

    • Like 6
    • Thanks 2

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted

    Just now, schalmers said:

    I appreciate all of the help,  I have been trying different USB ports with both of the 2 drivers "nutdrv_qx" and "blazer_usb" with all of your recommendations to keep commented out  but I have not had any luck.

     

    I guess I will have no other choice but to look for a different UPS for this server.    Thanks again

     

    Another thing to try apart from NUT would be the default "UPS Settings" (which use APCUPSD) if you haven't already tried that.

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted

    5 minutes ago, schalmers said:

    Changed UPS.CONF to:

     

    [ups]
        driver = "blazer_usb"
        port = "auto"
        vendorid = "0001"
        productid = "0000"
        product = "MEC0003"
        vendor = "MEC"
        bus = "003"

     

    Syslog shows the different driver but it still failed....

     

    Apr 25 21:16:26 HomeSrv ool www[24750]: /usr/local/emhttp/plugins/nut-dw/scripts/start
    Apr 25 21:16:27 HomeSrv rc.nut: Writing NUT configuration...
    Apr 25 21:16:29 HomeSrv rc.nut: Updating permissions for NUT...
    Apr 25 21:16:29 HomeSrv rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
    Apr 25 21:16:29 HomeSrv rc.nut: Disabling the NUT Runtime Statistics Module...
    Apr 25 21:16:35 HomeSrv rc.nut: No supported UPS detected
    Apr 25 21:16:35 HomeSrv rc.nut: Network UPS Tools - Megatec/Q1 protocol USB driver 0.20 (2.7.4.1)
    Apr 25 21:16:35 HomeSrv rc.nut: Driver failed to start (exit status=1)
    Apr 25 21:16:35 HomeSrv rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1

     

    I'm sorry, the only thing I can think of is going through these settings again with another USB port or cable (keep the bus, device, busport commented out though to not fix NUT on a specific USB port). Otherwise unfortunately we seem to be out of luck.

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted

    3 minutes ago, schalmers said:

     

    Ok I reset the UPS.CONF back to:

     

    [ups]
        driver = "nutdrv_qx"    # alternately: blazer_usb nutdrv_atcl_usb
        port = "auto"
        vendorid = "0001"
        productid = "0000"
        product = "MEC0003"
        vendor = "MEC"
        # bus = "003"
        # device = "002"
        # busport = "001"

     

    Then I changed the version back to "legacy (2.7.4 stable)" and closed down all VMs, Dockers, Array and restarted the server.

     

    Verified in NUT Settings were the proper version:  

    image.png.5f8f7085844105370c02bafb0fa8c7be.png

     

    and restarted the NUT service the syslog still shows error:

     

    Apr 25 20:45:10 HomeSrv ool www[10410]: /usr/local/emhttp/plugins/nut-dw/scripts/start
    Apr 25 20:45:11 HomeSrv rc.nut: Writing NUT configuration...
    Apr 25 20:45:13 HomeSrv rc.nut: Updating permissions for NUT...
    Apr 25 20:45:13 HomeSrv rc.nut: Adding UDEV lines to rc.6 for NUT...
    Apr 25 20:45:13 HomeSrv rc.nut: Adding UPS shutdown lines to rc.6 for NUT...
    Apr 25 20:45:13 HomeSrv rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
    Apr 25 20:45:13 HomeSrv rc.nut: Disabling the NUT Runtime Statistics Module...
    Apr 25 20:45:28 HomeSrv rc.nut: Device not supported!
    Apr 25 20:45:28 HomeSrv rc.nut: Device not supported!
    Apr 25 20:45:28 HomeSrv rc.nut: Network UPS Tools - Generic Q* USB/Serial driver 0.39 (2.7.4.1)
    Apr 25 20:45:28 HomeSrv rc.nut: USB communication driver 0.43
    Apr 25 20:45:28 HomeSrv rc.nut: Driver failed to start (exit status=1)
    Apr 25 20:45:28 HomeSrv rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1

     

    The FULL syslog from restart to starting NUT service is attached if it helps you see anything interesting.  Again really appreciate the help.

     

    decided to try something ...

     

    Checked Autoconfig in this 2.7.4 version and it returned a slightly different UPS.CONF (bus = "003" not REM'd out) 

     

        [ups]
        driver = "nutdrv_qx"
        port = "auto"
        vendorid = "0001"
        productid = "0000"
        product = "MEC0003"
        vendor = "MEC"
        bus = "003"

     

    Started the Service again but same error from what I can tell:

     

    Apr 25 20:57:12 HomeSrv ool www[3490]: /usr/local/emhttp/plugins/nut-dw/scripts/stop
    Apr 25 20:57:13 HomeSrv rc.nut: Writing NUT configuration...
    Apr 25 20:57:15 HomeSrv rc.nut: Updating permissions for NUT...
    Apr 25 20:57:15 HomeSrv rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
    Apr 25 20:57:15 HomeSrv rc.nut: Disabling the NUT Runtime Statistics Module...
    Apr 25 20:57:16 HomeSrv rc.nut: Stopping the NUT services... 
    Apr 25 20:57:18 HomeSrv rc.nut: Can't open /var/run/nut/nutdrv_qx-ups.pid: No such file or directory
    Apr 25 20:57:18 HomeSrv rc.nut: Can't open /var/run/nut/nutdrv_qx-auto.pid either: No such file or directory
    Apr 25 20:57:18 HomeSrv rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
    Apr 25 20:57:28 HomeSrv emhttpd: cmd: /usr/local/emhttp/plugins/nut-dw/scripts/nutscan
    Apr 25 21:00:33 HomeSrv ool www[14971]: /usr/local/emhttp/plugins/nut-dw/scripts/start
    Apr 25 21:00:34 HomeSrv rc.nut: Writing NUT configuration...
    Apr 25 21:00:36 HomeSrv rc.nut: Updating permissions for NUT...
    Apr 25 21:00:36 HomeSrv rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
    Apr 25 21:00:36 HomeSrv rc.nut: Disabling the NUT Runtime Statistics Module...
    Apr 25 21:00:51 HomeSrv rc.nut: Device not supported!
    Apr 25 21:00:51 HomeSrv rc.nut: Device not supported!
    Apr 25 21:00:51 HomeSrv rc.nut: Network UPS Tools - Generic Q* USB/Serial driver 0.39 (2.7.4.1)
    Apr 25 21:00:51 HomeSrv rc.nut: USB communication driver 0.43
    Apr 25 21:00:51 HomeSrv rc.nut: Driver failed to start (exit status=1)
    Apr 25 21:00:51 HomeSrv rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1

    homesrv-syslog-20240425-1848.zip 26.38 kB · 0 downloads

     

    Thanks, any luck with the blazer_usb driver on the 2.7.4. backend?

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted

    Just now, schalmers said:

    Thank you for replying I modified the UPS.CONF to be:

     

    [ups]
        driver = "nutdrv_qx"    # alternately: blazer_usb nutdrv_atcl_usb
        port = "auto"
        vendorid = "0001"
        productid = "0000"
        product = "MEC0003"
        vendor = "MEC"
        # bus = "003"
        # device = "002"
        # busport = "001"
        subdriver = "hunnox"

     

    And restarted the NUT Service but unfortunately I am still getting the same type of error in Syslog:

     

    Apr 25 20:21:14 HomeSrv ool www[5285]: /usr/local/emhttp/plugins/nut-dw/scripts/stop
    Apr 25 20:21:15 HomeSrv rc.nut: Writing NUT configuration...
    Apr 25 20:21:16 HomeSrv rc.nut: Updating permissions for NUT...
    Apr 25 20:21:16 HomeSrv rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
    Apr 25 20:21:16 HomeSrv rc.nut: Disabling the NUT Runtime Statistics Module...
    Apr 25 20:21:17 HomeSrv rc.nut: Stopping the NUT services... 
    Apr 25 20:21:19 HomeSrv rc.nut: Can't open /var/run/nut/nutdrv_qx-ups.pid: No such file or directory
    Apr 25 20:21:19 HomeSrv rc.nut: Can't open /var/run/nut/nutdrv_qx-auto.pid either: No such file or directory
    Apr 25 20:21:19 HomeSrv rc.nut: Network UPS Tools - UPS driver controller 2.8.2
    Apr 25 20:21:29 HomeSrv ool www[5286]: /usr/local/emhttp/plugins/nut-dw/scripts/start
    Apr 25 20:21:30 HomeSrv rc.nut: Writing NUT configuration...
    Apr 25 20:21:31 HomeSrv rc.nut: Updating permissions for NUT...
    Apr 25 20:21:31 HomeSrv rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
    Apr 25 20:21:31 HomeSrv rc.nut: Disabling the NUT Runtime Statistics Module...
    Apr 25 20:22:03 HomeSrv rc.nut: Device not supported!
    Apr 25 20:22:03 HomeSrv rc.nut: Device not supported!
    Apr 25 20:22:03 HomeSrv rc.nut: Network UPS Tools - Generic Q* USB/Serial driver 0.36 (2.8.2)
    Apr 25 20:22:03 HomeSrv rc.nut: USB communication driver (libusb 1.0) 0.47
    Apr 25 20:22:03 HomeSrv rc.nut: Driver failed to start (exit status=1)
    Apr 25 20:22:03 HomeSrv rc.nut: Network UPS Tools - UPS driver controller 2.8.2

     

    Ok let's try something else, remove the subdriver line again. Then set NUT Backend Switch to "legacy (2.7.4 stable)". Uninstall and reinstall NUT (or reboot server) and make sure the backend actually changed to 2.7.4. Then start NUT again with the same settings (without subdriver). Also try another USB port it that doesn't work.

×
×
  • Create New...