WEB UI not accessible

  • Hi,
    installed latest omv on a Raspberry Pi 3, 32 GB class 10 SD Card, 2 TB 3,5" HDD (with extra power supply). After the installation everything was fine and working, now, every time I try to access the WEB UI I get an error Communication failure or an error has occurred.


    No additional plugins enabled. It looks like a timeout to me:


    Code: error.log
    2016/12/28 22:27:38 [alert] 3237#0: *1 open socket #13 left in connection 2
    2016/12/28 22:27:38 [alert] 3237#0: *2 open socket #14 left in connection 3
    2016/12/28 22:27:38 [alert] 3237#0: aborting
    2016/12/28 22:28:19 [alert] 3259#0: *3 open socket #13 left in connection 2
    2016/12/28 22:28:19 [alert] 3259#0: *4 open socket #14 left in connection 3
    2016/12/28 22:28:19 [alert] 3259#0: *5 open socket #15 left in connection 4
    2016/12/28 22:28:19 [alert] 3259#0: aborting
    2016/12/29 07:52:56 [alert] 25374#0: *1 open socket #13 left in connection 2
    2016/12/29 07:52:56 [alert] 25374#0: *3 open socket #15 left in connection 4
    2016/12/29 07:52:56 [alert] 25374#0: aborting
    Code: openmedia_webgui_access.log
    ::ffff:127.0.0.1 - - [29/Dec/2016:08:01:15 +0400] "GET / HTTP/1.1" 499 0 "-" "Monit/5.9"
    ::ffff:127.0.0.1 - - [29/Dec/2016:08:01:51 +0400] "GET / HTTP/1.1" 499 0 "-" "Monit/5.9"
    ::ffff:127.0.0.1 - - [29/Dec/2016:08:02:26 +0400] "GET / HTTP/1.1" 499 0 "-" "Monit/5.9"
    ::ffff:127.0.0.1 - - [29/Dec/2016:08:03:02 +0400] "GET / HTTP/1.1" 499 0 "-" "Monit/5.9"
    ::ffff:127.0.0.1 - - [29/Dec/2016:08:03:37 +0400] "GET / HTTP/1.1" 499 0 "-" "Monit/5.9"
    ::ffff:127.0.0.1 - - [29/Dec/2016:08:04:13 +0400] "GET / HTTP/1.1" 499 0 "-" "Monit/5.9"
    ::ffff:127.0.0.1 - - [29/Dec/2016:08:04:49 +0400] "GET / HTTP/1.1" 499 0 "-" "Monit/5.9"
    ::ffff:127.0.0.1 - - [29/Dec/2016:08:05:24 +0400] "GET / HTTP/1.1" 499 0 "-" "Monit/5.9"
    ::ffff:127.0.0.1 - - [29/Dec/2016:08:06:00 +0400] "GET / HTTP/1.1" 499 0 "-" "Monit/5.9"
    ::ffff:127.0.0.1 - - [29/Dec/2016:08:06:35 +0400] "GET / HTTP/1.1" 499 0 "-" "Monit/5.9"

    Thanks for helping me out
    Chris

  • Hi,


    check the network settings of the accessing client. Empty browser cache. Check with another browser. Check with another client. Restart nginx. Reboot.


    The error message leads to https://httpstatuses.com/499


    HTH


    P.S. Provide all information you can get. Hardware, OS, OMV-Version etc

    --
    Get a Rose Tattoo...


    HP t5740 with Expansion and USB3, Inateck Case w/ 3TB WD-Green
    OMV 5.5.7-1 Usul i386|4.19.0-9-686-pae

  • I wrote the image with dd bs=4M on my macbook. Uptime 1 day, because I tried a reboot as well. Enough disc space anyway


    Thx chris


    Code
    Filesystem Size Used Avail Use% Mounted on
    /dev/root 3.2G 1.9G 1.2G 62% /
    devtmpfs 483M 0 483M 0% /dev
    tmpfs 487M 0 487M 0% /dev/shm
    tmpfs 487M 32M 456M 7% /run
    tmpfs 5.0M 0 5.0M 0% /run/lock
    tmpfs 487M 0 487M 0% /sys/fs/cgroup
    /dev/mmcblk0p1 56M 21M 36M 38% /boot
    /dev/mmcblk0p3 25G 2.8M 24G 1% /media/fa36508a-b3c4-4499-b30a-711dd5994225
    /dev/sda1 1.8T 8.0G 1.8T 1% /media/1fdc5829-057e-4921-94fc-dd4fe0c3352b
    Code
    14:03:38 up 1 day, 16:23, 1 user, load average: 0.00, 0.03, 0.00
  • You don't say if it is a new SD card or not? Sometimes load on RPis can cause similar issues to this. If it isn't a failing SD card, I'm not sure what is causing the issue.

    omv 5.5.13 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • I have a similar issue with a Raspberry Pi 3b, with three 2.5", 1Tb HDDs attached (all powered individually, not through the Pi USBs).


    When I try to select a Shared Folder or when I try to Format (File Systems/Create) the system gives "communication failure".


    I would have tried the remedy suggested here This can not be fixed in general, except to increase the timeout value. You can try to set a higher timeout value (in milliseconds) via 'OMV_HTTPREQUEST_TIMEOUT=xxx' in /etc/default/openmediavault. Defaults to 60000. but this file has no OMV_HTTP... line.


    I did try this You need to run omv-mkconf nginx and restart nginx. by guessing this to mean

    Code
    omv-mkconf nginx start
    service nginx restart

    And it made no difference. Rebooting fixed the issue but I lost one of my HDDs from Physical Disks.


    In the end I got around the whole thing by just having one attached HDD (then established the Share) before starting and mounting the remaining discs.


    I'm guessing that since I get no "communication failure" with only one HDD attached that this is just a timing thing, i.e. the Raspberry Pi is overwhelmed (it can take what seems a lifetime to load the OMV screen) so how can I alter the timeout value when there is no OMV_HTTPREQUEST line in /etc/default/openmediavault?


    This isn't life or death, just irritating. Interestingly I get sub-second screen changes when I ask the Pi to select a radio station, and it plays the station (typically) less than a second after the request.

  • but this file has no OMV_HTTP... line.

    You have to add it. I don't think this is your problem though since it would take 60 seconds to cause an issue. The problem is you are doing disk intensive work on the usb bus and the RPi's network adapter is on the same usb bus. Like you thought, it is just being overwhelmed. When you are doing disk intensive work, it should be quick. Not much you can do to fix this other than switch to a device that doesn't share a bus with the network adapter (odroid-c2 for example).

    omv 5.5.13 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

Participate now!

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