failed protocol test, server returned status 502 after recent update

1st Official Post

    Hello,


    installed the one available OMV update today. After the update was complete I could see the yellow bar popping up, which asked for applying changes. However, I couldn't klick on them because I was asked to reload the page first. After reload I cannot access the webgui anymore and it only gives "502 Bad Gateway".


    An email notification told: "failed protocol test [HTTP] at [127.0.0.1]:<port> [TCP/IP TLS] -- HTTP error: Server returned status 502"


    I tried to restart nginx, which was successful but did but still gave error 502.


    Any ideas how to get the webface back running?


    cheers

    Thermo

  • thermo

    Changed the title of the thread from “failed protocoll test, server returned status 502 after recent update” to “failed protocol test, server returned status 502 after recent update”.

    Status of php7.0-fpm showed that it could not load dynamic librar /usr/lib/php/20151012/pam.so - no such file or directory. Restarting of php7.0-fpm didn't change anything. Than i ran omv-salt deploy run phpfpm. Than I could type in my login credentials but it gave me the following error:


    Code
    Fehler #0:
OMV\Rpc\Exception: Failed to connect to socket: No such file or directory in /usr/share/php/openmediavault/rpc/rpc.inc:141
Stack trace:
#0 /var/www/openmediavault/rpc/session.inc(56): OMV\Rpc\Rpc::call('UserMgmt', 'authUser', Array, Array, 2, true)
#1 [internal function]: OMVRpcServiceSession->login(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('login', Array, Array)
#4 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('Session', 'login', Array, Array, 3)
#5 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()
#6 {main}


    Shall I remove php completely and reinstall it?

    Thank you!


    Tried omv-salt deploy run nginx but didn't help. After restart I could neither use ssh anymore nor login via the webgui (not responsive). Luckily I have a snapshot after the update (...) but before the reboot. So I went back and tried omv-salt stage run deploy which took about a minute but didn't help. After reboot no webgui no ssh. None of both failed as in Mobilis case.


    Output of:

    Bash
    # omv-confdbadm read --prettify conf.system.notification.notification


    Output of:


    Bash
    # omv-confdbadm read --prettify --filter '{"operator": "stringEquals", "arg0": "id", "arg1": "cronapt"}' conf.system.notification.notification
    Code
    [
    {
        "enable": false,
        "id": "cronapt",
        "uuid": "394cd565-e463-4094-a6ab-12e80270e9b4"
    }
]


    Output of:


    Bash
    omv-confdbadm migrate conf 0.5.8

    Same trouble. After reboot not webgui, no ssh. Went back to previously mentioned snapshot to have the system back running (SMB) but without being able to login via the webgui.


    cheers

    Thermo

    On another OMV system, where I now didn't install the upgrades so far it also shows me the update "openmediavault 5.3.8-1". This was the update mentioned in the first post, after which I am not able to login though the webgui anymore.


    Edit: As this other omv nas is not really import to me I did the update, didn't reload the page (as asked after update) but closed the promt with the cross at the top right and applied the new setting (yellow bar). An error occurred. Now also "502 Bad Gateway".


    Edit2: This other system was also initially an OMV 4 but was recently upgraded to OMV 5. I tried omv-salt stage run deploy which gave 1 succeeded and 1 failed.

    Following Mobilis I did omv-confdbadm migrate conf 0.5.8 followed by another omv-salt stage run deploy which didn't help, also after reboot - still 502 Bad Gateway. However, I am able to conned via SMB or SSH.


    Edit3: Any other advices. I may use the second OMV as a test system now. :)

    Lets continue with the second OMV: omv-salt deploy run phpfpm and login prompt is back again. Login works. Asked for applying changes (yellow bar). Took ages (>10 min). Reboot to see if everything survives. It did.


    Back to the first OMV: omv-engied -f. Login works. Reboot. Nothing. Ping 172.18.100.2. No Network. omv-firstaid. Reconfigured network interface. Back online. Login works. Reboot. Login works. SMB works. SFTP works. All fine.


    Anyhow, strange behaviour...

    Second OMV: While applying changes after update to openmediavault 5.3.8-1, omv-salt deploy run phpfpm to enable login through webgui and than applying changes, as prompted by the yellow bar, took about 10 minutes, all other changes only took some seconds. However, a day later the webgui became incredibly slow. Decided to reinstall OMV - done in no time.


    First OMV: Everything seemed to be ok. Than complains from operators of machines using SMB2 that they can't connect. Checked smb.config and restarted smbd but still no connection. Machines with SMB3 can connect. SFTP works.


    Any ideas?


    OMV4 was initially installed on both systems and up to date before upgrade to OMV5. For both system trouble started with update openmediavault 5.3.8-1.


    Edit: Thinking about also reinstalling omv on the other system. Is there an possibility to export the user list?

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login