Erreur #0: exception 'OMV\Config\DatabaseException' with message 'Fatal error 9: PCDATA invalid Char value 22

  • Hello,
    My OMV NAS worked well since half a year, but today after the login on the web GUI I have this eroor message :


    Fatal error 9: PCDATA invalid Char value 22 (line=159, column=23); Fatal error 9: PCDATA invalid Char value 25 (line=160, column=33); Fatal error 9: PCDATA invalid Char value 5 (line=160, column=44)
    Erreur #0:
    exception 'OMV\Config\DatabaseException' with message 'Fatal error 9: PCDATA invalid Char value 22 (line=159, column=23); Fatal error 9: PCDATA invalid Char value 25 (line=160, column=33); Fatal error 9: PCDATA invalid Char value 5 (line=160, column=44)' in /usr/share/php/openmediavault/config/databasebackend.inc:115
    Stack trace:
    #0 /usr/share/php/openmediavault/config/database.inc(34): OMV\Config\DatabaseBackend->load()
    #1 /usr/share/php/openmediavault/config/database.inc(44): OMV\Config\Database->__construct()
    #2 /usr/share/openmediavault/engined/module/proftpd.inc(71): OMV\Config\Database::getInstance()
    #3 /usr/share/openmediavault/engined/rpc/services.inc(56): OMVModuleProftpd->getStatus()
    #4 [internal function]: OMVRpcServiceServices->getStatus(Array, Array)
    #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
    #6 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getStatus', Array, Array)
    #7 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Services', 'getStatus', Array, Array, 1)
    #8 {main}


    And I don't know how to solve this issue
    Thank you in advance for your help

  • Here is the result of omv-firstaid --> Check RRD database



    Checking all RRD files. Please wait ...
    ERROR: PCDATA invalid Char value 22, line 159, column 23

  • No I didn't install the flash memory plugin :(


    here are the lines 159 and 160 of my config.xml file :


    9upY0CiJe54VvZEMozOUgA^V/TRav2xACIuRigSQkXbJXdsl39lnjQw3AZcSBWkbl
    oyMGL9h0gdKe5Tjz+GgMkE5CZUzD9LjK^YIc59H5yrAj^EF5nwywvoExIzU/1qXLFm


    I hope it will be possible to repair the file


    may be I can remove
    ^V from line 159
    ^Y from line 160
    and ^E from line 160

  • Hello
    you are right, I was not enough precise


    the 2 lines (159 and 160) are in the <sslcertificate> <privatekey> part of the file



    <privatekey>-----BEGIN PRIVATE KEY-----
    MIIJQwIBADANBgkqhkiG9w0BAQEFAASCCS0wggkpAgEAAoICAQDKRHcX5b+k8mGJ
    vgge5FElGkwDr0cMoKqn0FQb/dpdvze0KB7feartFyTnls5zOnVXYCf8fNf/qQQZ
    omeyPouWTn4M6YGyaxjrpShPorDRuI87xQpgoKgVO97OW2giOyDUMg90rRzez6GY
    DPaHEx6B5e/sGVwvfzX4rHNJMNuSgc3rJx0hXPKsvI6HZZe+lIHMH3Li1gWOCFd7
    6bMBG9MnS8NtWZHSkqrUXYBbaOeXCfnOyi4JkrdQjfNGIpzTaC7x3/bSl6jGAA/a
    6ozqTwA+jkS5NlNVcNrSzGUnnl6QBcew7XpQzDzZovLoSARxdWvjfhu7JF2nJjLj
    92PVcJCiG6B1I+/Vo1PUh59OaneWmLbn4H2P7txzZnwFqWKIaOBvDsIm6hRFJSxj
    4SC3ZSMnGVgqG0RFrQjje8Sf4SRoU38EsLoQ7r8ccD2RDOq9BAK9/BahM6HatiIN
    u0u1968hQki138LH4SGe0zMGytU57yxnLuQ-taQxAS/U/6QD0zlMzDegdGz/yI2q
    9upY0CiJe54VvZEMozOUgA^V/TRav2xACIuRigSQkXbJXdsl39lnjQw3AZcSBWkbl
    oyMGL9h0gdKe5Tjz+GgMkE5CZUzD9LjK^YIc59H5yrAj^EF5nwywvoExIzU/1qXLFm
    0S7Xbo93MqBFY/QP26mKaIXa90bDMwIDAQABAoICAHltgNGn69VqBYPzwYxKJSzR
    DLFpmI3MJqd4OgZT77Q4B4jwTRh8QlDzhAREVMx4W9mIsHizujiRjXSUmww24DXs
    CWBXDrW99cgB7qFgWiaNVe/b6s73o/CbcLcRyQJD3QGGzCCPjLV2kNxna9jLcZUq
    JU7oKp+ZDx2q6csWubrKkoSJhsNwuX9Z83b1VpPjM8kHWEE1m0AZYevR8NTJj4oX
    w


    I think this is the certificate used for https login


    the rest of the file seems to be good



    Is it possible to modify the config.xml file to allow to connect to the webui using http ?

  • I mofidied this line in the config.xml file
    <forcesslonly>1</forcesslonly>


    to
    <forcesslonly>0</forcesslonly>


    and reboot, but I'm still forced to https ....


    I think I ave to do something more ... ?

Jetzt mitmachen!

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