invalid key/value pair in file /etc/udev/rules.d/99-openmediavault-nut-serialups.rules

  • Not sure if this is related to my other ticket regarding the journal starting. I have enclosed that part of the log below.


    Not sure when this started, but the UPS correctly identified via USB cable to APC 1000.
    There is no statistics gui screen for the UPS. I have uninstalled and re-installed the plugin but didn't help


    2017-11-10T11:23:08+0100 eapenas kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    2017-11-10T11:23:08+0100 eapenas kernel: usb 5-1: Product: Smart-UPS C 1000 FW:UPS 10.0 / ID=1005
    2017-11-10T11:23:08+0100 eapenas kernel: usb 5-1: Manufacturer: American Power Conversion


    2017-11-10T11:23:08+0100 eapenas systemd-udevd[209]: invalid key/value pair in file /etc/udev/rules.d/99-openmediavault-nut-serialups.rules on line 3,starting at character 1 ('E')
    2017-11-10T11:23:08+0100 eapenas systemd-udevd[209]: invalid key/value pair in file /etc/udev/rules.d/99-openmediavault-nut-serialups.rules on line 4,starting at character 1 ('u')
    --------------------
    # /etc/udev/rules.d/99_nut-serialups.rules - give nut access to serial port
    KERNEL=="ttyS0", GROUP="nut"
    -----------------
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Started Load Kernel Modules.
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Found ordering cycle on systemd-journald.service/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Found dependency on systemd-journald-dev-log.socket/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Found dependency on folder2ram_temporary.service/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Found dependency on basic.target/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Found dependency on sysinit.target/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Found dependency on systemd-journald.service/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Breaking ordering cycle by deleting job systemd-journald-dev-log.socket/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Job systemd-journald-dev-log.socket/start deleted to break ordering cycle starting with systemd-journald.service/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Found ordering cycle on systemd-journald.service/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Found dependency on systemd-journald-dev-log.socket/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Found dependency on folder2ram_temporary.service/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Found dependency on basic.target/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Found dependency on sysinit.target/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Found dependency on systemd-journald.service/start
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Unable to break cycle
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Requested transaction contains an unfixable cyclic ordering dependency: Transaction order is cyclic. See system logs for details.
    2017-11-10T11:23:08+0100 eapenas systemd[1]: systemd-journald.socket failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction order is cyclic. See system logs for details.
    2017-11-10T11:23:08+0100 eapenas systemd[1]: Unit systemd-journald.socket entered failed state.

  • So, it would seem this has something to do with it.
    I note that i had a firewall rule to allowe 3493 from the ip network but not the localhost of 127.0.0.1 specifically.


    Nov 10 11:23:08 eapenas collectd[1787]: Initialization complete, entering read-loop.
    Nov 10 11:23:08 eapenas collectd[1787]: nut plugin: Connection to (localhost, 3493) established.
    Nov 10 11:38:47 eapenas collectd[1787]: nut plugin: nut_read_one: upscli_list_start (eapeups) failed: Write error: Broken pipe
    Nov 10 11:38:47 eapenas collectd[1787]: read-function of plugin `nut' failed. Will suspend it for 20.000 seconds.
    Nov 10 11:39:07 eapenas collectd[1787]: nut plugin: nut_read_one: upscli_connect (localhost, 3493) failed: Connection failure: Connection refused
    Nov 10 11:39:07 eapenas collectd[1787]: read-function of plugin `nut' failed. Will suspend it for 40.000 seconds.
    Nov 10 11:39:47 eapenas collectd[1787]: nut plugin: nut_read_one: upscli_connect (localhost, 3493) failed: Connection failure: Connection refused
    Nov 10 11:39:47 eapenas collectd[1787]: read-function of plugin `nut' failed. Will suspend it for 80.000 seconds.

  • Nov 10 11:39:07 eapenas collectd[1787]: nut plugin: nut_read_one: upscli_connect (localhost, 3493) failed: Connection failure: Connection refused
    Nov 10 11:39:07 eapenas collectd[1787]: read-function of plugin `nut' failed. Will suspend it for 40.000 seconds.
    Nov 10 11:39:47 eapenas collectd[1787]: nut plugin: nut_read_one: upscli_connect (localhost, 3493) failed: Connection failure: Connection refused
    Nov 10 11:39:47 eapenas collectd[1787]: read-function of plugin `nut' failed. Will suspend it for 80.000 seconds.


    I fixed the above by adding a new firewall rule for localhost. previously i only had the network address.


    but i am still getting the below errors on startup.


    2017-11-10T14:37:06+0100 eapenas systemd-udevd[204]: invalid key/value pair in file /etc/udev/rules.d/99-openmediavault-nut-serialups.rules on line 3,starting at character 1 ('E')
    2017-11-10T14:37:06+0100 eapenas systemd-udevd[204]: invalid key/value pair in file /etc/udev/rules.d/99-openmediavault-nut-serialups.rules on line 4,starting at character 1 ('u')
    2017-11-10T14:37:06+0100 eapenas systemd-udevd[204]: invalid key/value pair in file /etc/udev/rules.d/99_nut-serialups.rules on line 2,starting at character 29 ('r')

  • Nov 10 11:39:07 eapenas collectd[1787]: nut plugin: nut_read_one: upscli_connect (localhost, 3493) failed: Connection failure: Connection refused
    Nov 10 11:39:07 eapenas collectd[1787]: read-function of plugin `nut' failed. Will suspend it for 40.000 seconds.
    Nov 10 11:39:47 eapenas collectd[1787]: nut plugin: nut_read_one: upscli_connect (localhost, 3493) failed: Connection failure: Connection refused
    Nov 10 11:39:47 eapenas collectd[1787]: read-function of plugin `nut' failed. Will suspend it for 80.000 seconds.


    I fixed the above by adding a new firewall rule for localhost. previously i only had the network address.


    but i am still getting the below errors on startup.


    2017-11-10T14:37:06+0100 eapenas systemd-udevd[204]: invalid key/value pair in file /etc/udev/rules.d/99-openmediavault-nut-serialups.rules on line 3,starting at character 1 ('E')
    2017-11-10T14:37:06+0100 eapenas systemd-udevd[204]: invalid key/value pair in file /etc/udev/rules.d/99-openmediavault-nut-serialups.rules on line 4,starting at character 1 ('u')
    2017-11-10T14:37:06+0100 eapenas systemd-udevd[204]: invalid key/value pair in file /etc/udev/rules.d/99_nut-serialups.rules on line 2,starting at character 29 ('r')


    --------------------------
    # /etc/udev/rules.d/99_nut-serialups.rules - give nut access to serial port
    KERNEL=="ttyS0", GROUP="nut"


    ---------------------------- ** this seems to be the problem with 99-openmediavault-nut-serialups.rules
    # This configuration file is auto-generated.
    # WARNING: Do not edit this file, your changes will be lost.
    KERNEL=="ttyUSB0
    auto", GROUP="nut"

  • I managed to resolve the issue with nut rules.


    a) my "driver configuration directive" in the gui had white spaces. I removed the white spaces. disabled - saved and enabled - saved to clear this.
    [ups]
    # SmartUPS C1000i
    driver = usbhid-ups
    port = auto
    vendorid = 051d
    desc = "apc smc1000i"


    the re-write deleted the 99-openmediavault-nut-serialups.rules completely


    b) for the nut-serialus.rules i couldn't remember if this was from 2.x, or i manually created following nut setup instructions, or something else.
    I deleted 99_nut-serialups.rules, disabled - saved and enabled - saved and no specific nut rules were created.



    Log is clear, and all is accessible via the gui.

Jetzt mitmachen!

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