UPS plugin not working

  • My BIOS has only two options for the serial port: enable/disable and IRQ address.


    From command line:
    # dmesg | grep tty
    [ 0.000000] console [tty0] enabled
    [ 1.011463] 00:05: ttyS2 at I/O 0x3e8 (irq = 3, base_baud = 115200) is a 16550A


    The following configuration is saved for the UPS (same as I used on 2.x and earlier):



    When I attempt to enable the UPS plugin and Apply the configuration, I get the following error dialog:


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl start 'nut-driver' 2>&1' with exit code '1': Job for nut-driver.service failed because the control process exited with error code.See "systemctl status nut-driver.service" and "journalctl -xe" for details.


    When I select 'View details' from GUI:


    systemctl status nut-driver.service:


    journalctl -xe produces a huge output. I *think* this is the relevant bits:



    What am I missing in my configuration?

    OMV 5.6.26-1 (Usul); Shuttle XPC SH67H3; Intel Core i5-2390T; 8 GB DDR3-1333 RAM; 128GB SanDisk Z400s SSD (OS); Samsung 860 EVO 1TB (primary storage); WD Red 2TB (backup and archive storage).

  • The interface seems largely unchanged since OMV 2.x.


    The configuration is from the 'Driver configuration directives' field in the interface.


    The rest of the options shouldn't have any bearing on the posted directives, which I have used for a very, very long time. The last time I redid my NUT config was in 2015, and haven't touched it since.


    OMV 5.6.26-1 (Usul); Shuttle XPC SH67H3; Intel Core i5-2390T; 8 GB DDR3-1333 RAM; 128GB SanDisk Z400s SSD (OS); Samsung 860 EVO 1TB (primary storage); WD Red 2TB (backup and archive storage).

    2 Mal editiert, zuletzt von openletter ()

  • This is a fresh install of 4.1.4.

    OMV 5.6.26-1 (Usul); Shuttle XPC SH67H3; Intel Core i5-2390T; 8 GB DDR3-1333 RAM; 128GB SanDisk Z400s SSD (OS); Samsung 860 EVO 1TB (primary storage); WD Red 2TB (backup and archive storage).

  • Yeah, but I have to say that 777 has always been my least favorite resolution. Seems like the problem should be resolved somewhere else.

    OMV 5.6.26-1 (Usul); Shuttle XPC SH67H3; Intel Core i5-2390T; 8 GB DDR3-1333 RAM; 128GB SanDisk Z400s SSD (OS); Samsung 860 EVO 1TB (primary storage); WD Red 2TB (backup and archive storage).

  • Okay, I figured out a fix.


    I noticed one of the ttyS* ports was member of group nut:


    # ls -alF /dev/ttyS*
    crw-rw---- 1 root nut 4, 64 Apr 8 15:38 ttyS0
    crw-rw---- 1 root dialout 4, 65 Apr 8 15:38 ttyS1
    crw-rw---- 1 root dialout 4, 66 Apr 8 15:38 ttyS2
    crw-rw---- 1 root dialout 4, 67 Apr 8 15:38 ttyS3


    I chowned ttyS2 to root:nut, and now everything works.


    The first time I loaded the configuration I copy pasted my old one, which was ttyS0, then later figured out it was ttyS2. I wonder if nut changed the group of ttyS0 on the first configuration load, but not later configurations?

    OMV 5.6.26-1 (Usul); Shuttle XPC SH67H3; Intel Core i5-2390T; 8 GB DDR3-1333 RAM; 128GB SanDisk Z400s SSD (OS); Samsung 860 EVO 1TB (primary storage); WD Red 2TB (backup and archive storage).

  • The cable was never moved.


    Most motherboards still have a COM header, which is what this motherboard has. And a lot of networking focused boards have an RJ45 COM port.

    OMV 5.6.26-1 (Usul); Shuttle XPC SH67H3; Intel Core i5-2390T; 8 GB DDR3-1333 RAM; 128GB SanDisk Z400s SSD (OS); Samsung 860 EVO 1TB (primary storage); WD Red 2TB (backup and archive storage).

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!