omv gui unresponsive - Gateway Timeout & An error has occured

    • Resolved
    • OMV 4.x

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

    • omv gui unresponsive - Gateway Timeout & An error has occured

      Dear All,

      I upgraded recently, and got a lot of help from @ryecoaaron on this thread : forum.openmediavault.org/index…?postID=210918#post210918

      Figured i would start a new thread, as i have other issues now.

      since the other thread, i added 5 ssd disks to my nas, it took about 48 hours for them to sync a new raid 5 array.

      I was getting the same messaged as i do now during the raid setup, but i figured the nas was very busy with building the array, so i left it alone.

      now the raid setup seems to have finished (checked with nmon, the disk activity, and all disks are now idling)

      But still now i get "an error has occured" when i try to view disks/raid or file systems in the omv gui, i also sometimes get "Gateway timeout" and "communication failure"

      appreciate any input on this.

      EDIT , its also not working to mount nfs exports on clients :

      Source Code

      1. sudo showmount -e omv
      2. Export list for omv:
      3. /export 192.168.0.0/24
      4. /export/pgnas2 192.168.0.0/24



      Source Code

      1. sudo mount -av
      2. / : ignored
      3. /boot : already mounted
      4. /boot/efi : already mounted
      5. /var : already mounted
      6. swap : ignored
      7. /home//mrpg/ntfs : already mounted
      8. mount.nfs: timeout set for Fri Aug 16 10:25:29 2019
      9. mount.nfs: trying text-based options 'hard,vers=4.2,addr=192.168.0.112,clientaddr=192.168.0.133'
      (it just hangs))

      Best Regards
      Patric

      The post was edited 1 time, last by mrpg ().

    • mrpg wrote:

      /home//mrpg/ntfs
      Yuck...

      mrpg wrote:

      mount.nfs: trying text-based options 'hard,vers=4.2,addr=192.168.0.112,clientaddr=192.168.0.133'
      This looks like you are using the remotemount plugin and it can't contact the remote server?
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Hi

      no plugins on omv except zfs.

      and the client is a fedora 29 laptop, the ntfs mount is for my windows partition on my laptop,(dual boot) needed for work :( (i know, but it works)

      :)

      my /etc/fstab on my laptop :


      Source Code

      1. cat /etc/fstab
      2. #
      3. # /etc/fstab
      4. # Created by anaconda on Thu Aug 2 14:17:56 2018
      5. #
      6. # Accessible filesystems, by reference, are maintained under '/dev/disk'
      7. # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
      8. #
      9. /dev/mapper/pg-root / xfs defaults 0 0
      10. UUID=3f905e88-75fe-4df5-9f42-e046ff81edf3 /boot ext4 defaults 1 2
      11. UUID=9994-0B76 /boot/efi vfat umask=0077,shortname=winnt 0 2
      12. /dev/mapper/pg-var /var xfs defaults 0 0
      13. /dev/mapper/pg-swap swap swap defaults 0 0
      14. #NTFS MOUNT
      15. /dev/nvme0n1p3 /home//mrpg/ntfs ntfs-3g defaults,rw 0 0
      16. # NFS MOUNTS
      17. 192.168.0.112:/pgnas2 /data/nas2 nfs rw,hard,async,_netdev
      18. 192.168.0.112:/ssd /data/ssd nfs rw,hard,async,_netdev
      Display All
      But its the same issue on all my nfs clients..
      Br
      Patric
    • mrpg wrote:

      the client is a fedora 29 laptop
      I guess I don't understand the problem. Your laptop is having problems mounting the OMV nfs share?

      As for the error in the web interface, that usually happens when a slow system (not sure what your system is) is doing a lot of work. What is the output of: cat /proc/mdstat
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I have around 5 client computers, none of them can mount anything on my omv nas.

      Brainfuck Source Code

      1. root@pgnas2:~# cat /proc/mdstat
      2. Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
      3. md127 : active raid5 sdc[1] sda[0] sde[3] sdd[2]
      4. 8790405120 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
      5. [>....................] resync = 2.5% (73408188/2930135040) finish=469606.6min speed=101K/sec
      6. bitmap: 22/22 pages [88KB], 65536KB chunk
      7. md0 : active (auto-read-only) raid5 sdf[0] sdg[1] sdh[2] sdj[4] sdi[3]
      8. 7500972032 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]
      9. bitmap: 0/14 pages [0KB], 65536KB chunk
      10. unused devices: <none>
      Display All



      i have not yet setup a filesystem on /dev/md0 , as i cannot access this section in the omv gui.

      my system is quite old and slow, but its not under load at all :


      Source Code

      1. Tasks: 263 total, 1 running, 199 sleeping, 0 stopped, 2 zombie
      2. %Cpu(s): 0.3 us, 0.6 sy, 0.0 ni, 17.3 id, 81.8 wa, 0.0 hi, 0.0 si, 0.0 st
      3. KiB Mem : 4041248 total, 3116528 free, 665000 used, 259720 buff/cache
      4. KiB Swap: 4190204 total, 4190204 free, 0 used. 3131248 avail Mem
      5. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
      6. 10213 root 20 0 42956 3696 2988 R 11.8 0.1 0:00.03 top
      7. 1 root 20 0 139716 7440 5160 S 0.0 0.2 0:03.67 systemd
      8. 2 root 20 0 0 0 0 S 0.0 0.0 0:00.01 kthreadd
      9. 3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
      10. 4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp
      11. 6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0H-kb
      12. 8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq
      13. 9 root 20 0 0 0 0 S 0.0 0.0 0:00.06 ksoftirqd/0
      14. 10 root 20 0 0 0 0 I 0.0 0.0 0:01.41 rcu_sched
      15. 11 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_bh
      16. 12 root rt 0 0 0 0 S 0.0 0.0 0:00.04 migration/0
      17. 14 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/0
      18. 15 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/1
      19. 16 root rt 0 0 0 0 S 0.0 0.0 0:00.04 migration/1
      20. 17 root 20 0 0 0 0 S 0.0 0.0 0:00.03 ksoftirqd/1
      21. 19 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/1:0H-kb
      22. 20 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/2
      23. 21 root rt 0 0 0 0 S 0.0 0.0 0:00.03 migration/2
      24. 22 root 20 0 0 0 0 S 0.0 0.0 0:00.03 ksoftirqd/2
      25. 24 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/2:0H-kb
      26. 25 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/3
      27. 26 root rt 0 0 0 0 S 0.0 0.0 0:00.03 migration/3
      28. 27 root 20 0 0 0 0 S 0.0 0.0 0:00.04 ksoftirqd/3
      29. 29 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/3:0H-kb
      30. 30 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs
      31. 31 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 netns
      32. 32 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kauditd
      33. 34 root 20 0 0 0 0 S 0.0 0.0 0:00.01 khungtaskd
      34. 35 root 20 0 0 0 0 S 0.0 0.0 0:00.00 oom_reaper
      35. 36 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 writeback
      36. 37 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kcompactd0
      37. 38 root 25 5 0 0 0 S 0.0 0.0 0:00.00 ksmd
      38. 39 root 39 19 0 0 0 S 0.0 0.0 0:00.25 khugepaged
      Display All
      i can see now that it says re-sync 2.5%

      but it does not seem to be doing anything?


      Source Code

      1. Segmentation faultfor help]───Hostname=pgnas2───────Refresh= 2secs ───14:01.57───────────────────────────────┐
      2. root@pgnas2:~# roc/diskstats────mostly in KB/s─────Warning:contains duplicates───────────────────────────────│
      3. │DiskName Busy Read WriteKB|0 |25 |50 |75 100| │
      4. │sdb 0% 0.0 0.0|> | │
      5. │sdb1 0% 0.0 0.0|> | │
      6. │sdb9 0% 0.0 0.0|> | │
      7. │sda 0% 0.0 0.0|> | │
      8. │sde 0% 0.0 0.0|> | │
      9. │sdf 0% 0.0 0.0|> | │
      10. │sdg 0% 0.0 0.0|> | │
      11. │sdi 0% 0.0 0.0|> | │
      12. │sdc 0% 0.0 0.0|> | │
      13. │sdd 0% 0.0 0.0|> | │
      14. │sdh 0% 0.0 0.0|> | │
      15. │sdk 0% 0.0 0.0|> | │
      16. │sdk1 0% 0.0 0.0|> | │
      17. │sdk2 0% 0.0 0.0|>disk busy not available | │
      18. │sdk5 0% 0.0 0.0|> | │
      19. │sdj 0% 0.0 0.0|> | │
      20. │md0 0% 0.0 0.0|>disk busy not available | │
      21. │md127 0% 0.0 0.0|>disk busy not available | │
      22. │Totals Read-MB/s=0.0 Writes-MB/s=0.0 Transfers/sec=0.0 │
      23. │────────────────────────────────────────────────────────────────────────────────────────────────────────────│
      24. │ │
      25. │ │
      26. │ │
      27. │ │
      28. │ │
      29. │ │
      30. │ │
      31. │ │
      32. │ │
      33. │ │
      34. │ │
      35. │ │
      36. │ │
      37. │ │
      38. │ │
      39. │ │
      40. └────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
      Display All

      The post was edited 1 time, last by mrpg ().

    • mrpg wrote:

      md0 : active (auto-read-only)
      This is bad.

      mrpg wrote:

      i can see now that it says re-sync 2.5%
      resync allows the files to still be accessible but it will be very slow which causes the web interface to give you the errors you are getting.

      mrpg wrote:

      but it does not seem to be doing anything?
      re-syncing won't show up as I/O.

      Why again are you using raid?? This system seems to be very unhappy with all things raid.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      mrpg wrote:

      md0 : active (auto-read-only)
      Is this not because i have not yet created a filesystem on it? i managed to setup an array on these five disks, but it took around 40 hours

      mrpg wrote:

      i can see now that it says re-sync 2.5%
      >resync allows the files to still be accessible but it will be very slow which causes the web interface to give you the errors you are getting.



      mrpg wrote:

      but it does not seem to be doing anything?
      >re-syncing won't show up as I/O.

      It does, at least in nmon i can see 100% read activity when its syncing the array ( i watched it on and off for 2 days)


      Why again are you using raid?? This system seems to be very unhappy with all things raid.


      My system was running omv without issues since 2017 :)
      its only since i upgraded to version 4 that all hell broke loose.


      i use raid because :
      1 it gives me some redundancy
      2 it creates a big logical disk out of smaller disks.


      i have managed to get the array to start syncing again, with

      Source Code

      1. echo check > /sys/block/md127/md/sync_action


      and now in nmon we see this :


      Source Code

      1. ┌nmon─16f──────[H for help]───Hostname=pgnas2───────Refresh= 2secs ───14:37.39───────────────────────────────┐
      2. │ Disk I/O ──/proc/diskstats────mostly in KB/s─────Warning:contains duplicates───────────────────────────────│
      3. │DiskName Busy Read WriteMB|0 |25 |50 |75 100| │
      4. │sdc 100% 53.1 0.0|RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR> │
      5. │sda 100% 54.1 0.0|RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR> │
      6. │sdf 0% 0.0 0.0|> | │
      7. │sdd 100% 53.1 0.0|RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR> │
      8. │sde 100% 54.1 0.0|RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR> │
      9. │sdk 0% 0.0 0.0|> | │
      10. │sdk1 0% 0.0 0.0|> | │
      11. │sdk2 0% 0.0 0.0|>disk busy not available | │
      12. │sdk5 0% 0.0 0.0|> | │
      13. │sdh 0% 0.0 0.0|> | │
      14. │sdj 0% 0.0 0.0|> | │
      15. │sdi 0% 0.0 0.0|> | │
      16. │sdg 0% 0.0 0.0|> | │
      17. │sdb 0% 0.0 0.0|> | │
      18. │sdb1 0% 0.0 0.0|> | │
      19. │sdb9 0% 0.0 0.0|>disk busy not available | │
      20. │md0 0% 0.0 0.0|>disk busy not available | │
      21. │md127 0% 0.0 0.0|>disk busy not available | │
      22. │Totals Read-MB/s=214.5 Writes-MB/s=0.0 Transfers/sec=330.3 │
      23. │────────────────────────────────────────────────────────────────────────────────────────────────────────────│
      24. │ │
      25. │ │
      26. │ │
      27. │ │
      28. │ │
      29. │ │
      30. │ │
      31. │ │
      32. │ │
      33. │ │
      34. │ │
      35. │ │
      36. │ │
      37. │ │
      38. │ │
      39. │ │
      40. └────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
      Display All

      The post was edited 1 time, last by mrpg ().