OMV 6 error in GUI after save settings

  • Hello,


    I have installed a OMV6 over the Zyxel NAS542 but every time receive error messages after I try to save something


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color chrony 2>&1' with exit code '1': Traceback (most recent call last):

    File "/usr/sbin/omv-salt", line 152, in <module>

    sys.exit(main())

    File "/usr/sbin/omv-salt", line 147, in main

    cli()

    File "/usr/lib/python3/dist-packages/click/core.py", line 829, in __call__

    return self.main(*args, **kwargs)

    File "/usr/lib/python3/dist-packages/click/core.py", line 782, in main

    rv = self.invoke(ctx)

    File "/usr/lib/python3/dist-packages/click/core.py", line 1259, in invoke

    return _process_result(sub_ctx.command.invoke(sub_ctx))

    File "/usr/lib/python3/dist-packages/click/core.py", line 1259, in invoke

    return _process_result(sub_ctx.command.invoke(sub_ctx))

    File "/usr/lib/python3/dist-packages/click/core.py", line 1066, in invoke

    return ctx.invoke(self.callback, **ctx.params)

    File "/usr/lib/python3/dist-packages/click/core.py", line 610, in invoke

    return callback(*args, **kwargs)

    File "/usr/sbin/omv-salt", line 133, in deploy_run

    caller = salt.client.Caller(mopts=mopts)

    File "/usr/lib/python3/dist-packages/salt/client/__init__.py", line 2104, in __init__

    self.sminion = salt.minion.SMinion(self.opts)

    File "/usr/lib/python3/dist-packages/salt/minion.py", line 917, in __init__

    opts["grains"] = salt.loader.grains(opts)

    File "/usr/lib/python3/dist-packages/salt/loader.py", line 882, in grains

    ret = funcs[key]()

    File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__

    return self.loader.run(run_func, *args, **kwargs)

    File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run

    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)

    File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as

    return _func_or_method(*args, **kwargs)

    File "/usr/lib/python3/dist-packages/salt/grains/core.py", line 1852, in os_data

    grains["systemd"]["version"] = systemd_info[0].split()[1]

    IndexError: list index out of range


    OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color chrony 2>&1' with exit code '1': Traceback (most recent call last):

    File "/usr/sbin/omv-salt", line 152, in <module>

    sys.exit(main())

    File "/usr/sbin/omv-salt", line 147, in main

    cli()

    File "/usr/lib/python3/dist-packages/click/core.py", line 829, in __call__

    return self.main(*args, **kwargs)

    File "/usr/lib/python3/dist-packages/click/core.py", line 782, in main

    rv = self.invoke(ctx)

    File "/usr/lib/python3/dist-packages/click/core.py", line 1259, in invoke

    return _process_result(sub_ctx.command.invoke(sub_ctx))

    File "/usr/lib/python3/dist-packages/click/core.py", line 1259, in invoke

    return _process_result(sub_ctx.command.invoke(sub_ctx))

    File "/usr/lib/python3/dist-packages/click/core.py", line 1066, in invoke

    return ctx.invoke(self.callback, **ctx.params)

    File "/usr/lib/python3/dist-packages/click/core.py", line 610, in invoke

    return callback(*args, **kwargs)

    File "/usr/sbin/omv-salt", line 133, in deploy_run

    caller = salt.client.Caller(mopts=mopts)

    File "/usr/lib/python3/dist-packages/salt/client/__init__.py", line 2104, in __init__

    self.sminion = salt.minion.SMinion(self.opts)

    File "/usr/lib/python3/dist-packages/salt/minion.py", line 917, in __init__

    opts["grains"] = salt.loader.grains(opts)

    File "/usr/lib/python3/dist-packages/salt/loader.py", line 882, in grains

    ret = funcs[key]()

    File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__

    return self.loader.run(run_func, *args, **kwargs)

    File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run

    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)

    File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as

    return _func_or_method(*args, **kwargs)

    File "/usr/lib/python3/dist-packages/salt/grains/core.py", line 1852, in os_data

    grains["systemd"]["version"] = systemd_info[0].split()[1]

    IndexError: list index out of range in /usr/share/php/openmediavault/system/process.inc:217

    Stack trace:

    #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()

    #1 /usr/share/openmediavault/engined/rpc/config.inc(170): OMV\Engine\Module\ServiceAbstract->deploy()

    #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)

    #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)

    #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusN0...', '/tmp/bgoutputWC...')

    #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))

    #7 /usr/share/openmediavault/engined/rpc/config.inc(192): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)

    #8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)

    #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)

    #11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)

    #12 {main}



    Any ideas what can it be the problem?


    kernel version is:


    root@debian-nas:/etc# uname -r

    3.2.54


    root@debian-nas:/etc# lsb_release -a

    No LSB modules are available.

    Distributor ID: Debian

    Description: Debian GNU/Linux 11 (bullseye)

    Release: 11

    Codename: bullseye


    root@debian-nas:/etc# dpkg -l | grep openmediavault

    iF openmediavault 6.1.0-1 all openmediavault - The open network attached storage solution

    ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive

    ic openmediavault-lvm2 6.0.1-1 all openmediavault Logical Volume Manager (LVM2) plugin

    ic openmediavault-omvextrasorg 6.1.1 all OMV-Extras.org Package Repositories for OpenMediaVault



    Thank you and regards!

  • votdev

    Hat das Label gelöst hinzugefügt.
  • Can you please post the output of systemctl --version. To me it looks like a bug in SaltStack.



    Noting go out after this command :( Is it the Debian installation the problem? I use a image for bullseye which is created for Zyxel NAS542 and not sure if it has everything you need in it something seems to have been cut... Now I install it on SD card 32 GB so there is no problems with space.

    • Offizieller Beitrag

    Noting go out after this command :( Is it the Debian installation the problem? I use a image for bullseye which is created for Zyxel NAS542 and not sure if it has everything you need in it something seems to have been cut... Now I install it on SD card 32 GB so there is no problems with space.

    The command should output several information, so SaltStack breaks because it is not able to parse the expected output. Maybe the creator of the image you're using did some modifications that are different to the normal behaviour. The OMV and SaltStack project can not do anything in this case because SaltStack is expecting a systemctl that behaves normal.

  • Ok what do you recommend? This command is from OMV or from the Debian OS? Is it possible to reinstall somehow SaltStack or it is not possible. Is there any OMV 6 image but not in ISO format but on .gz format? Or a method to compile it?

    • Offizieller Beitrag

    There's a good chance that the Zyxel NAS542 is based on an SBC, at it's core, but I couldn't find a specific model. If you know what model they're using, it might be on the -> Armbian download page.

    This -> How-To is the only thing I could find that might (I want to stress "might") get OMV working on the Zylex box.

    You'll need a translation plugin, for your browser, to read this page. It's in German.
    ___________________________________________________________________________________________


    Note that the article is old and out of date. Debian is now up to Bullseye, "Debian 11".|

    You might want to look over the -> Zylex forum for something that's a bit more up to date.

  • This one here


    This whole debacle started here:

    OMV returns error 500 after try to save settings - General - openmediavault

  • Thank you for the answer crashtest. The site you mention is well known and I already read all the info in it. The image that I use now is downloaded from there and it is the debian-nas-bullseye-21.218-armhf.img.gz



    This image is for OMV 5 but I have problems whit it. The GUI is not working so need to run it always whit omv-engined -f -d , then have every time error 500 inside when try to save settings like time region change... I struggle to make it work. I think it's a pretty truncated and mutilated installation.


    In the very beginning of boot it is written that the board is Mindspeed C2000 but not found a image for this exact board.


    Hi Soma thank you for your answer. Yes this thread is mine too... I'm struggling whit this case even though I'm not very good with Linux. :)






    • Offizieller Beitrag

    Soma Thanks for intervening. Like @kmo21 (in the other thread), I didn't read the first post closely and I was completely unaware of the other thread.
    _______________________________________________________________________________

    Infinity_bg

    Given the architecture, I believe the basis of the Zylex NAS542 is an SBC. The question is, which board?

    Again, on the Armbian download page, there are several supported SBC's with images for Debian Bullseye Minimal. (Other image types, to include images with a desktop, will not work with OMV.) If you can find an Armbian supported SBC, with a Cortex A9, the Debian Bullseye Minimal image for that SBC might work.

    The only SBC's that I could find, that use the Cortex A9, are the UDOO-NEO, the iWAVE i.MX6, the STEMlab 125-10, the Pandaboard Es Arm CORTEX-A9 OMAP4460 and the XILINX Z-turn lite ZYNQ-7010. Unfortunately, none of these boards are supported by Armbian.

    Perhaps one of the above boards is at the heart of the Zylex NAS542. I would say "check with the manufactures of the above boards" but from what I found, OS support for these boards is either propriety or they're supported only with versions of Ubuntu.
    _________________________________________________________________________________


    If you can get a working Debian Bullseye armhf install on the Zylex (from Debian's Bullseye download page), the following script "might" produce a working OMV install.


    With an internet connection, on the command line as root, copy and paste the following:

    wget -O - https://github.com/OpenMediaVa…ckages/raw/master/install | bash


    • Offizieller Beitrag

    Given the architecture, I believe the basis of the Zylex NAS542 is an SBC.

    Unfortunately, these commercial NASes use a custom board. And even though the cpu is found on other SBCs, that isn't the hard part of getting them to work. You need the custom bootloader that most have and the kernel with custom drivers that aren't open sourced. That is why the image available is using the 3.2 kernel - people use the Debian armel or armhf userland and just use the very old kernel from the original OS included with the unit. I wouldn't use one of these units with a kernel that old since it is full of security holes.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    Unfortunately, these commercial NASes use a custom board. And even though the cpu is found on other SBCs, that isn't the hard part of getting them to work. You need the custom bootloader that most have and the kernel with custom drivers that aren't open sourced. That is why the image available is using the 3.2 kernel - people use the Debian armel or armhf userland and just use the very old kernel from the original OS included with the unit. I wouldn't use one of these units with a kernel that old since it is full of security holes.

    A Frankenstein image... Thanks for explanation. I suppose that is "that". :)

    _______________________________________

    Infinity_bg

    Would you be interested in the Odriod HC4? With an HC4 and the appropriate power supply for your country, you would have everything you need except hard drives and SD-cards. Equally important, open source support for the HC4 (Armbian and OMV) should be available for years to come.

  • Some more output

    root@debian-nas:/etc# cat /proc/version

    Linux version 3.2.54 (root@twsvnnt01652-01) (gcc version 4.8.5 20150209 (prerelease) (crosstool-NG 1.21.0) ) #1 SMP Thu Aug 11 15:21:01 CST 2022


    root@debian-nas:/etc# hostnamectl | grep Kernel

    System has not been booted with systemd as init system (PID 1). Can't operate.

    Failed to connect to bus: Host is down


    I have tried to install newer kernel but is seems there is noting new then 3.2.54 for my hardware after check whit this command


    Code
    apt-cache search linux-image

    root@debian-nas:/etc# apt-cache search linux-image

    linux-headers-5.10.0-16-armmp - Header files for Linux 5.10.0-16-armmp

    linux-headers-5.10.0-16-armmp-lpae - Header files for Linux 5.10.0-16-armmp-lpae

    linux-headers-5.10.0-16-rt-armmp - Header files for Linux 5.10.0-16-rt-armmp

    linux-headers-5.10.0-18-armmp - Header files for Linux 5.10.0-18-armmp

    linux-headers-5.10.0-18-armmp-lpae - Header files for Linux 5.10.0-18-armmp-lpae

    linux-headers-5.10.0-18-rt-armmp - Header files for Linux 5.10.0-18-rt-armmp

    linux-image-5.10.0-16-armmp - Linux 5.10 for ARMv7 multiplatform compatible SoCs

    linux-image-5.10.0-16-armmp-dbg - Debug symbols for linux-image-5.10.0-16-armmp

    linux-image-5.10.0-16-armmp-lpae - Linux 5.10 for ARMv7 multiplatform compatible SoCs supporting LPAE

    linux-image-5.10.0-16-armmp-lpae-dbg - Debug symbols for linux-image-5.10.0-16-armmp-lpae

    linux-image-5.10.0-16-rt-armmp - Linux 5.10 for ARMv7 multiplatform compatible SoCs, PREEMPT_RT

    linux-image-5.10.0-16-rt-armmp-dbg - Debug symbols for linux-image-5.10.0-16-rt-armmp

    linux-image-5.10.0-18-armmp - Linux 5.10 for ARMv7 multiplatform compatible SoCs

    linux-image-5.10.0-18-armmp-dbg - Debug symbols for linux-image-5.10.0-18-armmp

    linux-image-5.10.0-18-armmp-lpae - Linux 5.10 for ARMv7 multiplatform compatible SoCs supporting LPAE

    linux-image-5.10.0-18-armmp-lpae-dbg - Debug symbols for linux-image-5.10.0-18-armmp-lpae

    linux-image-5.10.0-18-rt-armmp - Linux 5.10 for ARMv7 multiplatform compatible SoCs, PREEMPT_RT

    linux-image-5.10.0-18-rt-armmp-dbg - Debug symbols for linux-image-5.10.0-18-rt-armmp

    linux-image-armmp - Linux for ARMv7 multiplatform compatible SoCs (meta-package)

    linux-image-armmp-dbg - Debugging symbols for Linux armmp configuration (meta-package)

    linux-image-armmp-lpae - Linux for ARMv7 multiplatform compatible SoCs supporting LPAE (meta-package)

    linux-image-armmp-lpae-dbg - Debugging symbols for Linux armmp-lpae configuration (meta-package)

    linux-image-rt-armmp - Linux for ARMv7 multiplatform compatible SoCs (meta-package)

    linux-image-rt-armmp-dbg - Debugging symbols for Linux rt-armmp configuration (meta-package)

    linux-headers-6.1.0-0-armmp - Header files for Linux 6.1.0-0-armmp

    linux-headers-6.1.0-0-armmp-lpae - Header files for Linux 6.1.0-0-armmp-lpae

    linux-headers-6.1.0-0-rt-armmp - Header files for Linux 6.1.0-0-rt-armmp

    linux-image-6.1.0-0-armmp - Linux 6.1-rc7 for ARMv7 multiplatform compatible SoCs

    linux-image-6.1.0-0-armmp-dbg - Debug symbols for linux-image-6.1.0-0-armmp

    linux-image-6.1.0-0-armmp-lpae - Linux 6.1-rc7 for ARMv7 multiplatform compatible SoCs supporting LPAE

    linux-image-6.1.0-0-armmp-lpae-dbg - Debug symbols for linux-image-6.1.0-0-armmp-lpae

    linux-image-6.1.0-0-rt-armmp - Linux 6.1-rc7 for ARMv7 multiplatform compatible SoCs

    linux-image-6.1.0-0-rt-armmp-dbg - Debug symbols for linux-image-6.1.0-0-rt-armmp

    linux-headers-3.2.0-6-nas5xx - Header files for Linux 3.2.0-6-nas5xx

    linux-image-3.2.0-6-nas5xx - Linux 3.2 for Zyxel NAS5XX

    linux-image-armhf - Linux for Zyxel NAS5XX (meta-package)


    Is it possible that problems I have to come from low version of kernel?

    • Offizieller Beitrag

    Is it possible that problems I have to come from low version of kernel?

    Probably not but it definitely needs to boot with systemd and your system is not.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

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