WebGUI Login loop - no hd full

    • OMV 3.x (stable)
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • WebGUI Login loop - no hd full

      Hello,

      I just installed an OMV server in a Rock64. which will also be used for other applications. It was working fine, but after some package installation it started to fail: after entering the correct credentials it returns to the login screen without any error message or any indication in the logs. I verified the space in the partitions and no one is full:

      Source Code

      1. root@rock64:~# df -h
      2. Filesystem Size Used Avail Use% Mounted on
      3. udev 10M 0 10M 0% /dev
      4. tmpfs 386M 16M 371M 4% /run
      5. /dev/mmcblk1p7 30G 3.8G 25G 14% /
      6. tmpfs 965M 0 965M 0% /dev/shm
      7. tmpfs 5.0M 8.0K 5.0M 1% /run/lock
      8. tmpfs 965M 0 965M 0% /sys/fs/cgroup
      9. /dev/mmcblk1p6 100M 45M 56M 45% /boot/efi
      10. folder2ram 965M 21M 944M 3% /var/log
      11. folder2ram 965M 0 965M 0% /var/tmp
      12. folder2ram 965M 0 965M 0% /var/lib/openmediavault/rrd
      13. folder2ram 965M 792K 964M 1% /var/spool
      14. folder2ram 965M 9.7M 955M 1% /var/lib/rrdcached
      15. folder2ram 965M 8.0K 965M 1% /var/lib/monit
      16. folder2ram 965M 4.0K 965M 1% /var/lib/php5
      17. folder2ram 965M 4.0K 965M 1% /var/lib/netatalk/CNID
      18. folder2ram 965M 452K 964M 1% /var/cache/samba
      19. overlay 30G 3.8G 25G 14% /var/lib/docker/overlay2/e31252c6379a237dcfb5108ef4a53c4bcec422c91d1fd087aa9851ee2b61e0d3/merged
      20. shm 64M 0 64M 0% /var/lib/docker/containers/4ab0a8a01153cc3d8150ac2bfbfcee048c6054d984de5368c3e0d5cd7c023e45/shm
      21. tmpfs 193M 0 193M 0% /run/user/0
      Display All

      Could it be any of the packages installed that causes issues with the authentication? How can I see the error logs related to this issue? In the auth.log I see the following:


      Source Code

      1. Jan 26 22:20:42 rock64 openmediavault-webgui[10342]: Authorized login from ::ffff:xx.xx.xx.xx [username=admin, user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36]
      The server has also installed docker with an Unifi container and Freepbx/asterisk. Thanks!
    • try omv-firstaid and go for "reset gui password".

      You will go back to admin/openmediavault
      ---------------------------------------------------------------------------------------------------------------------
      French, so forgive my english
      Personal Rig: valid.x86.fr/v72uek as a test bench with Oracle VM.
      And YES, my avatar is real, i am flying "parapentes" in St Hilaire du Touvet and at la coupe icare.
    • Hello, and thanks for your suggestions. The following are the results:

      stratege1401 wrote:

      try omv-firstaid and go for "reset gui password".

      You will go back to admin/openmediavault
      There is no option to reset the GUI password in the omv-firstaid, instead there is an option to "Change control panel administrator password". I used that option and the password change was successful: using the old password in the GUI I got bad login error, but using the new password I have the same login loop behavior and the same "Authorized login" message in auth.log

      tkaiser wrote:

      Have you checked for counterfeit SD cards (4 GB crap card sold as 'genuine 32 GB' something)? If not, this is the first I would do:

      Source Code

      1. apt-get install f3
      2. f3write /root/
      3. f3read /root/
      I did the test and it seems that SD is not the issue:

      Source Code

      1. Free space: 26.05 GB
      2. Creating file 1.h2w ... OK!
      3. Creating file 2.h2w ... OK!
      4. Creating file 3.h2w ... OK!
      5. Creating file 4.h2w ... OK!
      6. Creating file 5.h2w ... OK!
      7. Creating file 6.h2w ... OK!
      8. Creating file 7.h2w ... OK!
      9. Creating file 8.h2w ... OK!
      10. Creating file 9.h2w ... OK!
      11. Creating file 10.h2w ... OK!
      12. Creating file 11.h2w ... OK!
      13. Creating file 12.h2w ... OK!
      14. Creating file 13.h2w ... OK!
      15. Creating file 14.h2w ... OK!
      16. Creating file 15.h2w ... OK!
      17. Creating file 16.h2w ... OK!
      18. Creating file 17.h2w ... OK!
      19. Creating file 18.h2w ... OK!
      20. Creating file 19.h2w ... OK!
      21. Creating file 20.h2w ... OK!
      22. Creating file 21.h2w ... OK!
      23. Creating file 22.h2w ... OK!
      24. Creating file 23.h2w ... OK!
      25. Creating file 24.h2w ... OK!
      26. Creating file 25.h2w ... OK!
      27. Creating file 26.h2w ... OK!
      28. Creating file 27.h2w ... OK!
      29. Free space: 16.00 MB
      30. Average writing speed: 2.78 MB/s
      31. SECTORS ok/corrupted/changed/overwritten
      32. Validating file 1.h2w ... 2097152/ 0/ 0/ 0
      33. Validating file 2.h2w ... 2097152/ 0/ 0/ 0
      34. Validating file 3.h2w ... 2097152/ 0/ 0/ 0
      35. Validating file 4.h2w ... 2097152/ 0/ 0/ 0
      36. Validating file 5.h2w ... 2097152/ 0/ 0/ 0
      37. Validating file 6.h2w ... 2097152/ 0/ 0/ 0
      38. Validating file 7.h2w ... 2097152/ 0/ 0/ 0
      39. Validating file 8.h2w ... 2097152/ 0/ 0/ 0
      40. Validating file 9.h2w ... 2097152/ 0/ 0/ 0
      41. Validating file 10.h2w ... 2097152/ 0/ 0/ 0
      42. Validating file 11.h2w ... 2097152/ 0/ 0/ 0
      43. Validating file 12.h2w ... 2097152/ 0/ 0/ 0
      44. Validating file 13.h2w ... 2097152/ 0/ 0/ 0
      45. Validating file 14.h2w ... 2097152/ 0/ 0/ 0
      46. Validating file 15.h2w ... 2097152/ 0/ 0/ 0
      47. Validating file 16.h2w ... 2097152/ 0/ 0/ 0
      48. Validating file 17.h2w ... 2097152/ 0/ 0/ 0
      49. Validating file 18.h2w ... 2097152/ 0/ 0/ 0
      50. Validating file 19.h2w ... 2097152/ 0/ 0/ 0
      51. Validating file 20.h2w ... 2097152/ 0/ 0/ 0
      52. Validating file 21.h2w ... 2097152/ 0/ 0/ 0
      53. Validating file 22.h2w ... 2097152/ 0/ 0/ 0
      54. Validating file 23.h2w ... 2097152/ 0/ 0/ 0
      55. Validating file 24.h2w ... 2097152/ 0/ 0/ 0
      56. Validating file 25.h2w ... 2097152/ 0/ 0/ 0
      57. Validating file 26.h2w ... 2097152/ 0/ 0/ 0
      58. Validating file 27.h2w ... 50208/ 0/ 0/ 0
      59. Data OK: 26.02 GB (54576160 sectors)
      60. Data LOST: 0.00 Byte (0 sectors)
      61. Corrupted: 0.00 Byte (0 sectors)
      62. Slightly changed: 0.00 Byte (0 sectors)
      63. Overwritten: 0.00 Byte (0 sectors)
      64. Average reading speed: 19.74 MB/s
      Display All
      Is there any other config/log that I can check? Thanks!
    • Gobam wrote:

      Average writing speed: 2.78 MB/s
      While the card seems to be a genuine card having 32GB capacity I would immediately try to replace it with something better since this is just too slow (if sequential write performance is already that low then random IO performance which is the most important when used with SBC will be horribly low). Personal recommendation currently is SanDisk A1 cards (the A1 is important! See this whole thread for background information)
    • tkaiser wrote:

      While the card seems to be a genuine card having 32GB capacity I would immediately try to replace it with something better since this is just too slow (if sequential write performance is already that low then random IO performance which is the most important when used with SBC will be horribly low). Personal recommendation currently is SanDisk A1 cards (the A1 is important! See this whole thread for background information)
      Thanks for the info. Really this is a test installation, just to validate the functionality of the applications. The final installation will use an emmc module, which is being shipped.

      Do you think this SD slowness could cause problems in the login process? If not, what else I can check? Thank!
    • Gobam wrote:

      Do you think this SD slowness could cause problems in the login process?
      Over at Armbian we've dealt with numerous situations where SD cards with very poor random IO performance behaved almost like broken ones (strangely these were 'Samsung EVOs' but most probably not genuine but faked ones since Samsung EVO are one of the few SD cards that show a pretty high random IO performance).

      The problem is that 'SD card crappiness' is that often reason for symptoms feeling like 'software misbehaving on SBC' that it's simply no worth the efforts to debug stuff unless SD card related troubles are ruled out. Though you could also try to provide some logs:

      Source Code

      1. sudo apt install curl
      2. dmesg | tail -n 400 | curl -F 'f:1=<-' http://ix.io
    • Hello.

      I have now received the eMMC module and reinstalled the server in this order (using Debian Jessie arm64):

      1) Asterisk + freepbx (it uses Apache2, I changed the HTTP port to 85)
      2) Docker + Unifi controller container
      3) Openmediavault

      The installation went fine, but when I try to login to the GUI for first time I got the same problem of login loop. I changed the admin password in omv-firstaids, but no difference. It seems to be a conflict of OMV with one of the packets installed by the other apps. I appreciate your help with this, we really want to use OMV but this issue is a not-go..

      The following is the new output of "df -h" just for reference:

      Source Code

      1. root@rock64:~# df -h
      2. Filesystem Size Used Avail Use% Mounted on
      3. udev 10M 0 10M 0% /dev
      4. tmpfs 386M 5.7M 381M 2% /run
      5. /dev/mmcblk0p7 15G 2.9G 11G 22% /
      6. tmpfs 965M 0 965M 0% /dev/shm
      7. tmpfs 5.0M 4.0K 5.0M 1% /run/lock
      8. tmpfs 965M 0 965M 0% /sys/fs/cgroup
      9. tmpfs 965M 0 965M 0% /tmp
      10. /dev/mmcblk0p6 100M 45M 56M 45% /boot/efi
      11. overlay 15G 2.9G 11G 22% /var/lib/docker/overlay2/d00e28b5895a8abc5e1c3129d4cc3d93aaea913fe0b7a9137121d991df827ae1/merged
      12. shm 64M 0 64M 0% /var/lib/docker/containers/a8057767e0fdc41930f772bc082ac1696343d551fe6f627d1a75e3a8a498623d/shm
      13. tmpfs 193M 0 193M 0% /run/user/1000
      Display All
    • I found the issue! In the file /var/log/nginx/openmediavault-webgui_error.log I found the following errors:

      Source Code

      1. 2018/01/31 09:31:32 [error] 757#0: *9 FastCGI sent in stderr: "PHP message: PHP Warning: session_start(): open(/var/lib/php5/sessions/sess_7cb79jt9mv49mmgh007ovt7js3, O_RDWR) failed: Permission denied (13) in /usr/share/php/openmediavault/session.inc on line 43" while reading response header from upstream, client: ::ffff:xx.xx.xx.xx, server: openmediavault-webgui, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm-openmediavault-webgui.sock:"...
      So I searched for this error and found a similar issue in this thread: [HELP] Can't Log in on the Web-Gui with right credentials. The issue is related with the permissions on folder /var/lib/php5/sessions, the user openmediavault-webgui doesn't have permission to create the new session file. Freepbx changes the permissions and ownership of this folder, so the solution is to correct the permissions and configure Freepbx to not change the permission on that folder.

      Thank for your support on this! :)