Failed to index key 'hostname' of 'hostname.0' because it has no children.

  • Ich benutze OMV 3.x schon eine ganze Zeit und bislang war die network Seite immer leer. Seit dem letzten Update (omv 3.0.64) erscheint beim Aufrufen der Seite die folgende Fehlermeldung / call Stack:

    Code
    #0 /usr/share/php/openmediavault/config/configobject.inc(193): OMV\Dictionary->set('hostname.0', 'marvin') 
    #1 /usr/share/php/openmediavault/config/configobject.inc(271): OMV\Config\ConfigObject->set('hostname.0', 'marvin', false) 
    #2 /usr/share/php/openmediavault/config/configobject.inc(233): OMV\Config\ConfigObject->setFlatAssoc(Array, false, false) 
    #3 /usr/share/php/openmediavault/config/database.inc(90): OMV\Config\ConfigObject->setAssoc(Array, false) 
    #4 /usr/share/openmediavault/engined/rpc/network.inc(169): OMV\Config\Database->get('conf.system.net...') 
    #5 [internal function]: OMVRpcServiceNetwork->getGeneralSettings(NULL, Array) 
    #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array) 
    #7 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getGeneralSetti...', NULL, Array) #8 /usr/sbin/omv-engined(522): OMV\Rpc\Rpc::call('Network', 'getGeneralSetti...', NULL, Array, 1) 
    #9 {main}
  • Ich benutze OMV 3.x schon eine ganze Zeit und bislang war die network Seite immer leer. Seit dem letzten Update (omv 3.0.64) erscheint beim Aufrufen der Seite die folgende Fehlermeldung / call Stack:

    Code
    #0 /usr/share/php/openmediavault/config/configobject.inc(193): OMV\Dictionary->set('hostname.0', 'marvin') 
    #1 /usr/share/php/openmediavault/config/configobject.inc(271): OMV\Config\ConfigObject->set('hostname.0', 'marvin', false) 
    #2 /usr/share/php/openmediavault/config/configobject.inc(233): OMV\Config\ConfigObject->setFlatAssoc(Array, false, false) 
    #3 /usr/share/php/openmediavault/config/database.inc(90): OMV\Config\ConfigObject->setAssoc(Array, false) 
    #4 /usr/share/openmediavault/engined/rpc/network.inc(169): OMV\Config\Database->get('conf.system.net...') 
    #5 [internal function]: OMVRpcServiceNetwork->getGeneralSettings(NULL, Array) 
    #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array) 
    #7 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getGeneralSetti...', NULL, Array) #8 /usr/sbin/omv-engined(522): OMV\Rpc\Rpc::call('Network', 'getGeneralSetti...', NULL, Array, 1) 
    #9 {main}

    I'm sure I broke some rule by doing this... I have the same problem after upgrading to 3.0.64


    Failed to index key 'hostname' of 'hostname.0' because it has no children.
    Obviously the hostname differs, but the stacktrace is the same...
    Thanks,
    Dan

    • Offizieller Beitrag

    Assuming you have omv-extras installed, post the output of: omv-showkey network

    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

    As root:
    cp /etc/openmediavault/config.xml /root/
    nano /etc/openmediavault/config.xml


    Find the sections and change to the following (just involves removing lines):


    ctrl-o to save ctrl-x to exit

    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!

  • Thanks! It no longer displays the error and it look like everything works fine.
    Much appreciated. Sorry to be a pain, can you elaborate a bit on the changes and why were they necessary?
    Cheers,
    Dan

    • Offizieller Beitrag

    can you elaborate a bit on the changes and why were they necessary?

    Something in an update/upgrade went wrong and probably happened multiple times. I haven't run into this myself so not sure what is causing it. They were necessary because the duplicate XML elements were causing a problem for OMV.

    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!

Jetzt mitmachen!

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