Something with the SSH is wrong

  • Hello guys,

    I installed omv on my pi 3b, and I have some errors:

    1. when I try to apply changes, a error occurs.

    2. when i try to reboot, a error occors in the web interface, but the pi reboots.

    3. After the first reboot, my pi is unavailable via web interface (the ip wasn't found) and hostname -I has no more output.

    4. almost every time I press a button I get this error:

    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run systemd-networkd 2>&1' with exit code '1': raspberrypi: ---------- ID: configure_etc_network_interfaces Function: file.managed Name: /etc/network/interfaces Result: True Comment: File /etc/network/interfaces is in the correct state Started: 10:21:33.392907 Duration: 132.274 ms Changes: ---------- ID: remove_systemd_networkd_config_files Function: module.run Result: True Comment: file.find: [] Started: 10:21:33.528152 Duration: 5.027 ms Changes: ---------- file.find: ---------- ID: remove_empty_systemd_networkd_config_files Function: module.run Result: True Comment: file.find: [] Started: 10:21:33.533837 Duration: 3.987 ms Changes: ---------- file.find: ---------- ID: remove_netplan_config_files Function: module.run Result: True Comment: file.find: ['/etc/netplan/10-openmediavault-default.yaml', '/etc/netplan/20-openmediavault-eth0.yaml'] Started: 10:21:33.538415 Duration: 5.52 ms Changes: ---------- file.find: - /etc/netplan/10-openmediavault-default.yaml - /etc/netplan/20-openmediavault-eth0.yaml ---------- ID: configure_netplan_default Function: file.managed Name: /etc/netplan/10-openmediavault-default.yaml Result: True Comment: File /etc/netplan/10-openmediavault-default.yaml updated Started: 10:21:33.544664 Duration: 42.489 ms Changes: ---------- diff: New file mode: 0644 ---------- ID: configure_netplan_ethernet_eth0 Function: file.managed Name: /etc/netplan/20-openmediavault-eth0.yaml Result: True Comment: File /etc/netplan/20-openmediavault-eth0.yaml updated Started: 10:21:33.587770 Duration: 149.52 ms Changes: ---------- diff: New file mode: 0644 ---------- ID: configure_netplan_vlan_eth0.1 Function: file.managed Name: /etc/netplan/50-openmediavault-eth0.1.yaml Result: True Comment: File /etc/netplan/50-openmediavault-eth0.1.yaml updated Started: 10:21:33.738006 Duration: 131.884 ms Changes: ---------- diff: New file mode: 0644 ---------- ID: apply_netplan_config Function: cmd.run Name: netplan apply Result: False Comment: Command "netplan apply" run Started: 10:21:33.873052 Duration: 545.269 ms Changes: ---------- pid: 4984 retcode: 78 stderr: /etc/netplan/20-openmediavault-eth0.yaml:5:20: Error in network definition: Invalid MAC address '', must be XX:XX:XX:XX:XX:XX macaddress: ^ stdout: Summary for raspberrypi ------------ Succeeded: 7 (changed=7) Failed: 1 ------------ Total states run: 8 Total run time: 1.016 s

    What could I do?


    Thanks in advance!

  • I have the same problem.

    apparently on the MAC, from the /etc/netplan/20-openmediavault-eth0.yaml file, which is blank:


    network:

    ethernets:

    eth0:

    match:

    macaddress:

    addresses:

    - 192.168.1.13/24

    gateway4: 192.168.1.1

    accept-ra: true

    dhcp4: false

    dhcp6: true

    nameservers:

    addresses:

    - 192.168.1.1

    search: [doamin.local]


    If I access via putty (SSH) and put the MAC manually, I execute the command netplan apply, everything works. However, in the web interface, when I make any changes and try to save (apply), the error returns, the MAC is empty again.



    Logs:

    Error #0:

    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; omv-salt deploy run systemd-networkd 2>&1' with exit code '1': raspberrypi:

    ----------

    ID: configure_etc_network_interfaces

    Function: file.managed

    Name: /etc/network/interfaces

    Result: True

    Comment: File /etc/network/interfaces is in the correct state

    Started: 21:38:29.683382

    Duration: 126.885 ms

    Changes:

    ----------

    ID: remove_systemd_networkd_config_files

    Function: module.run

    Result: True

    Comment: file.find: []

    Started: 21:38:29.813039

    Duration: 4.94 ms

    Changes:

    ----------

    file.find:

    ----------

    ID: remove_empty_systemd_networkd_config_files

    Function: module.run

    Result: True

    Comment: file.find: []

    Started: 21:38:29.818722

    Duration: 3.828 ms

    Changes:

    ----------

    file.find:

    ----------

    ID: remove_netplan_config_files

    Function: module.run

    Result: True

    Comment: file.find: ['/etc/netplan/10-openmediavault-default.yaml', '/etc/netplan/20-openmediavault-eth0.yaml', '/etc/netplan/30-openmediavault-wlan0.yaml']

    Started: 21:38:29.823190

    Duration: 5.93 ms

    Changes:

    ----------

    file.find:

    - /etc/netplan/10-openmediavault-default.yaml

    - /etc/netplan/20-openmediavault-eth0.yaml

    - /etc/netplan/30-openmediavault-wlan0.yaml

    ----------

    ID: configure_netplan_default

    Function: file.managed

    Name: /etc/netplan/10-openmediavault-default.yaml

    Result: True

    Comment: File /etc/netplan/10-openmediavault-default.yaml updated

    Started: 21:38:29.829751

    Duration: 38.368 ms

    Changes:

    ----------

    diff:

    New file

    mode:

    0644

    ----------

    ID: configure_netplan_ethernet_eth0

    Function: file.managed

    Name: /etc/netplan/20-openmediavault-eth0.yaml

    Result: True

    Comment: File /etc/netplan/20-openmediavault-eth0.yaml updated

    Started: 21:38:29.868763

    Duration: 144.063 ms

    Changes:

    ----------

    diff:

    New file

    mode:

    0644

    ----------

    ID: configure_netplan_wifi_wlan0

    Function: file.managed

    Name: /etc/netplan/30-openmediavault-wlan0.yaml

    Result: True

    Comment: File /etc/netplan/30-openmediavault-wlan0.yaml updated

    Started: 21:38:30.013445

    Duration: 135.257 ms

    Changes:

    ----------

    diff:

    New file

    mode:

    0644

    ----------

    ID: apply_netplan_config

    Function: cmd.run

    Name: netplan apply

    Result: False

    Comment: Command "netplan apply" run

    Started: 21:38:30.151871

    Duration: 467.125 ms

    Changes:

    ----------

    pid:

    26022

    retcode:

    78

    stderr:

    /etc/netplan/20-openmediavault-eth0.yaml:5:20: Error in network definition: Invalid MAC address '', must be XX:XX:XX:XX:XX:XX

    macaddress:

    ^

    stdout:


    Summary for raspberrypi

    ------------

    Succeeded: 7 (changed=7)

    Failed: 1

    ------------

    Total states run: 8

    Total run time: 926.396 ms in /usr/share/php/openmediavault/system/process.inc:182

    Stack trace:

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

    #1 /usr/share/openmediavault/engined/rpc/config.inc(167): 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(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusr8...', '/tmp/bgoutputpQ...')

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

    #7 /usr/share/openmediavault/engined/rpc/config.inc(189): 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}



    Command return sudo salt-call grains.items :


    local:

    ----------

    SSDs:

    - ram11

    - ram2

    - ram0

    - ram9

    - ram7

    - ram14

    - ram5

    - ram12

    - ram3

    - ram10

    - ram1

    - ram8

    - ram15

    - ram6

    - mmcblk0

    - ram13

    - ram4

    cpu_flags:

    - half

    - thumb

    - fastmult

    - vfp

    - edsp

    - neon

    - vfpv3

    - tls

    - vfpv4

    - idiva

    - idivt

    - vfpd32

    - lpae

    - evtstrm

    - crc32

    cpu_model:

    ARMv7 Processor rev 4 (v7l)

    cpuarch:

    armv7l

    cwd:

    /home/pi

    disks:

    - loop1

    - loop6

    - loop4

    - loop2

    - loop0

    - loop7

    - loop5

    - loop3

    dns:

    ----------

    domain:

    ip4_nameservers:

    - 192.168.1.1

    ip6_nameservers:

    nameservers:

    - 192.168.1.1

    options:

    search:

    - local.domain

    sortlist:

    domain:

    local.domain

    fqdn:

    server.local.domain

    fqdn_ip4:

    - 192.168.1.13

    - 192.168.1.14

    fqdn_ip6:

    - "ip6 address, all right"

    fqdns:

    gid:

    0

    gpus:

    groupname:

    root

    host:

    server

    hwaddr_interfaces:

    ----------

    enx:

    "address mac exact, all right"

    lo:

    00:00:00:00:00:00

    wlan0:

    "address mac exact, all right"

    id:

    raspberrypi

    init:

    systemd

    ip4_gw:

    192.168.1.1

    ip4_interfaces:

    ----------

    enx:

    - 192.168.1.13

    lo:

    - 127.0.0.1

    wlan0:

    ip6_gw:

    False

    ip6_interfaces:

    ----------

    enx:

    - "ip6 address, all right"

    lo:

    - ::1

    wlan0:

    ip_gw:

    True

    ip_interfaces:

    ----------

    enx:

    - 192.168.1.13

    - "ip6 address, all right"

    lo:

    - 127.0.0.1

    - ::1

    wlan0:

    ipv4:

    - 127.0.0.1

    - 192.168.1.13

    ipv6:

    - ::1

    - "ipv6 address, all right"

    kernel:

    Linux

    kernelrelease:

    4.19.97-v7+

    kernelversion:

    #1294 SMP Thu Jan 30 13:15:58 GMT 2020

    locale_info:

    ----------

    defaultencoding:

    UTF-8

    defaultlanguage:

    en_US

    detectedencoding:

    UTF-8

    timezone:

    BST

    localhost:

    server.local.domain

    lsb_distrib_codename:

    buster

    lsb_distrib_description:

    Raspbian GNU/Linux 10 (buster)

    lsb_distrib_id:

    Raspbian

    lsb_distrib_release:

    10

    machine_id:

    "id machine, all right"

    master:

    salt

    mem_total:

    926

    nodename:

    server.local.domain

    num_cpus:

    4

    num_gpus:

    0

    os:

    Raspbian

    os_family:

    Debian

    osarch:

    armhf

    oscodename:

    buster

    osfinger:

    Raspbian-10

    osfullname:

    Raspbian

    osmajorrelease:

    10

    osrelease:

    10

    osrelease_info:

    - 10

    path:

    /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

    pid:

    30474

    ps:

    ps -efHww

    pythonexecutable:

    /usr/bin/python3

    pythonpath:

    - /usr/bin

    - /usr/lib/python37.zip

    - /usr/lib/python3.7

    - /usr/lib/python3.7/lib-dynload

    - /usr/local/lib/python3.7/dist-packages

    - /usr/lib/python3/dist-packages

    pythonversion:

    - 3

    - 7

    - 3

    - final

    - 0

    saltpath:

    /usr/lib/python3/dist-packages/salt

    saltversion:

    3000.2

    saltversioninfo:

    - 3000

    - 2

    server_id:

    1900437280

    shell:

    /bin/bash

    swap_total:

    99

    systemd:

    ----------

    features:

    +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid

    version:

    241

    uid:

    0

    username:

    root

    virtual:

    physical

    zfs_feature_flags:

    False

    zfs_support:

    False

    zmqversion:

    4.3.1



    thks

  • The Output from salt-call grains.items is:

  • The output of salt-call network.hwaddr eth0 is:

    Code
    local:
        Interface "eth0" not in available interfaces: "lo", "enxb827ebfe1c8f", "wlan0"


    And if you can use the information, the content of /etc/netplan/20-openmediavault-eth0.yaml is:

    • Offizieller Beitrag

    IMO it seems to be inevitable to use predictable network device names on RPi.

    I stopped disabling predictive naming in the install script about a week ago - https://github.com/OpenMediaVa…c3e3c9d7ef68b89523eff1987


    Looking at the mac address stuff now though. I *really* don't want to have to switch to predictive naming though. I don't mind using whatever comes configured but switching would realistically require a reboot.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


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


    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

    I stopped disabling predictive naming in the install script about a week ago - https://github.com/OpenMediaVa…c3e3c9d7ef68b89523eff1987


    Looking at the mac address stuff now though. I *really* don't want to have to switch to predictive naming though. I don't mind using whatever comes configured but switching would realistically require a reboot.

    Hmmm, but working around something that is a default nowadays produces problems like this. To me it looks like there is only a UDEV rule that is related for enabling predictable device names. If this is the case, UDEV rules can be reloaded at runtime without rebooting. Or is this also a kernel boot configuration issue?

    • Offizieller Beitrag

    Maybe. I haven't tried but I also haven't had this issue on my many RPi tests.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


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


    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

    If it's not a common problem on RPi then i'm fine with current implementation. But why isn't it possible to get the MAC address for the iface in this case?

    I tried on an existing RPi2 install and had no problems. I tried on a new RPi4 install and had no problems. I tried wifi and vlan (OP had a VLAN) on the RPi4 but still had no problems. I can't figure out why the salt code can't get the mac address but it has happened on a few systems. I just can't replicate it.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

  • i had this issue, and since i didn't have a keyboard i had to resolve it the way i could, so i mounted the second partition on the sd-card om my computer, and updated the NamePolicy in /lib/systemd/network/99-default.link to be:


    NamePolicy=mac database keep kernel onboard slot path


    on my Raspberry Pi 3, i'm not sure if that's a good solution, but it works at the moment at least :)

  • Could you please provide a bit more info? I am a Beginner and having the same error


    Function: cmd.run Name: netplan apply Result: False Comment: Command "netplan apply" run Started: 17:32:28.829327 Duration: 583.915 ms Changes: ---------- pid: 16967 retcode: 78 stderr: /etc/netplan/20-openmediavault-eth0.yaml:5:20: Error in network definition: Invalid MAC address '', must be XX:XX:XX:XX:XX:XX macaddress: ^ stdout:



    so I am not exactly sure the procedure you followed. Create a new partition on the SD-Card? then go into the original partition and change the NamePolicy in /lib/systemd/network/99-default.link?


    my 99-default.link looks like this:

    [Link]

    NamePolicy=keep kernel database onboard slot path

    MACAddressPolicy=persistent


    What is the purpose of the new partition?

Jetzt mitmachen!

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