Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Solved] unRAID 6.0 RC3-4 Dynamix WebGUI OFTEN hangs (solved in RC5?)

Featured Replies

  • Author

...

If I have well understood this could be 'compatible' with what I reported: it hangs between the 'first & second' part of page creation (tables+labels & values+icons). First ones are static, about ever the same, seconds need real time data to be filled in...

 

Am I wrong?

 

See here: http://lime-technology.com/forum/index.php?topic=40368.msg380848#msg380848

 

It seems I was quite close to it...  :P

  • Replies 79
  • Views 14.9k
  • Created
  • Last Reply
  • Author

No more gui hangs since RC5 update today!  ;)

 

Sometimes it's a bit slow on responding (even with very low load and a quite fast dual core cpu  ???) but at last the webpages are ever showed.

 

I'll test it for some mor days and then, eventually, I'll close this thread as solved.  :D

I'm late to the party but I've also had the WebGUI hang if I leave it open too long.  Usually I go in for a bit then close the window but sometimes I forget.  I don't know how long it takes but eventually the WebGUI is unresponsive and the process is pegged at 100% CPU.  Once, the entire system became unresponsive to the point where even the console was frozen.  If I keep my WebGUI usage brief I never have a problem.

I'm late to the party but I've also had the WebGUI hang if I leave it open too long.  Usually I go in for a bit then close the window but sometimes I forget.  I don't know how long it takes but eventually the WebGUI is unresponsive and the process is pegged at 100% CPU.  Once, the entire system became unresponsive to the point where even the console was frozen.  If I keep my WebGUI usage brief I never have a problem.

 

And what has your experience been with rc5?

  • Author

No more GUI lock on RC5+... it can be closed in my opinion.  ;)

I must report the issue as the webgui still hangs (running untouched for 3-4 days) in rc5 - did not update yet to rc6a.

 

I must report the issue as the webgui still hangs (running untouched for 3-4 days) in rc5 - did not update yet to rc6a.

 

Well, I'd recommend updating to RC6a because if the problem disappears then this becomes a moot point.

  • Author

I must report the issue as the webgui still hangs (running untouched for 3-4 days) in rc5 - did not update yet to rc6a.

This has happened to me too... only one time for now, BUT I think for different reasons respect what already reported & solved here.

 

Next time I'll post a syslog and some more data too...  ;)

  • 1 month later...

I believe this is happening to me too.

I'm running v6 stable since launch and had go reset the server multiple times.

 

I now found this thread describing the same issue.

Emhttp process is at 100% CPU. Shares and dockers are all accessible.

Also dockers and vm's keep working.

I stopped libvirt and docker from commandant line. But it won't return.

  • 3 weeks later...

Hello,

 

I am running 6.0.1 and am running into this issue as well with the webgui becoming unresponsive.  Everything else still works fine on the server, I am able to access my docker applications and my VM's without issue.  So far the record has been close to 2 whole days of running before the webgui goes down.  When it goes down it always happens while I am going back and forth between pages on it, looking for information.  For a product that is now out of beta testing, and this was an issue that was reported during the beta testing period, I have to admit i'm disappointed in the quality considering that I had to buy this product versus every other Linux Server distribution I have used in the past.  IN the last several days of researching your forums, I have been able to find many people describing this issue, but I have yet to be able to find a solution.  It would seem to me that the logical thing to do would be to restart the emhttp service, however everything I have read says not to do this.

 

Since it has been asked for before, here are the results of my ps-ef command

 

UID        PID  PPID  C STIME TTY          TIME CMD

root        1    0  0 Aug16 ?        00:00:07 init

root        2    0  0 Aug16 ?        00:00:00 [kthreadd]

root        3    2  0 Aug16 ?        00:00:00 [ksoftirqd/0]

root        5    2  0 Aug16 ?        00:00:00 [kworker/0:0H]

root        7    2  0 Aug16 ?        00:00:07 [rcu_preempt]

root        8    2  0 Aug16 ?        00:00:00 [rcu_sched]

root        9    2  0 Aug16 ?        00:00:00 [rcu_bh]

root        10    2  0 Aug16 ?        00:00:00 [migration/0]

root        11    2  0 Aug16 ?        00:00:00 [migration/1]

root        12    2  0 Aug16 ?        00:00:00 [ksoftirqd/1]

root        14    2  0 Aug16 ?        00:00:00 [kworker/1:0H]

root        15    2  0 Aug16 ?        00:00:00 [migration/2]

root        16    2  0 Aug16 ?        00:00:00 [ksoftirqd/2]

root        18    2  0 Aug16 ?        00:00:00 [kworker/2:0H]

root        19    2  0 Aug16 ?        00:00:00 [migration/3]

root        20    2  0 Aug16 ?        00:00:00 [ksoftirqd/3]

root        23    2  0 Aug16 ?        00:00:00 [migration/4]

root        24    2  0 Aug16 ?        00:00:00 [ksoftirqd/4]

root        26    2  0 Aug16 ?        00:00:00 [kworker/4:0H]

root        27    2  0 Aug16 ?        00:00:00 [migration/5]

root        28    2  0 Aug16 ?        00:00:00 [ksoftirqd/5]

root        30    2  0 Aug16 ?        00:00:00 [kworker/5:0H]

root        31    2  0 Aug16 ?        00:00:00 [migration/6]

root        32    2  0 Aug16 ?        00:00:00 [ksoftirqd/6]

root        34    2  0 Aug16 ?        00:00:00 [kworker/6:0H]

root        35    2  0 Aug16 ?        00:00:00 [migration/7]

root        36    2  0 Aug16 ?        00:00:00 [ksoftirqd/7]

root        37    2  0 Aug16 ?        00:00:00 [kworker/7:0]

root        39    2  0 Aug16 ?        00:00:00 [khelper]

root        40    2  0 Aug16 ?        00:00:00 [kdevtmpfs]

root        41    2  0 Aug16 ?        00:00:00 [netns]

root        44    2  0 Aug16 ?        00:00:00 [perf]

root      278    2  0 Aug16 ?        00:00:00 [writeback]

root      280    2  0 Aug16 ?        00:00:00 [ksmd]

root      281    2  0 Aug16 ?        00:00:00 [khugepaged]

root      282    2  0 Aug16 ?        00:00:00 [crypto]

root      283    2  0 Aug16 ?        00:00:00 [kintegrityd]

root      284    2  0 Aug16 ?        00:00:00 [bioset]

root      286    2  0 Aug16 ?        00:00:00 [kblockd]

root      477    2  0 Aug16 ?        00:00:00 [ata_sff]

root      495    2  0 Aug16 ?        00:00:00 [devfreq_wq]

root      596    2  0 Aug16 ?        00:00:00 [rpciod]

root      640    2  0 Aug16 ?        00:00:02 [kswapd0]

root      710    2  0 Aug16 ?        00:00:00 [fsnotify_mark]

root      730    2  0 Aug16 ?        00:00:00 [nfsiod]

root      734    2  0 Aug16 ?        00:00:00 [cifsiod]

root      746    2  0 Aug16 ?        00:00:00 [xfsalloc]

root      747    2  0 Aug16 ?        00:00:00 [xfs_mru_cache]

root      794    2  0 Aug16 ?        00:00:00 [acpi_thermal_pm]

root      845    2  0 Aug16 ?        00:00:00 [kloopd]

root      886  1552  0 21:38 ?        00:00:00 sshd: root@pts/2

root      894  886  0 21:39 pts/2    00:00:00 -bash

root      904    2  0 Aug16 ?        00:00:00 [vfio-irqfd-clea]

root      909  1603  0 21:39 ?        00:00:00 sleep 1

root      910  894  0 21:39 pts/2    00:00:00 ps -ef

root      1003    2  0 Aug16 ?        00:00:00 [bioset]

root      1010    2  0 Aug16 ?        00:00:00 [deferwq]

root      1013    2  0 Aug16 ?        00:00:00 [scsi_eh_0]

root      1014    2  0 Aug16 ?        00:00:00 [scsi_tmf_0]

root      1015    2  0 Aug16 ?        00:00:01 [usb-storage]

root      1027    2  0 Aug16 ?        00:00:00 [kworker/7:1]

root      1028    2  0 Aug16 ?        00:00:00 [kworker/5:1]

root      1029    2  0 Aug16 ?        00:00:49 [kworker/6:1]

root      1084    1  0 Aug16 ?        00:00:00 /sbin/udevd --daemon

root      1120    2  0 Aug16 ?        00:00:00 [scsi_eh_1]

root      1121    2  0 Aug16 ?        00:00:00 [scsi_tmf_1]

root      1122    2  0 Aug16 ?        00:00:00 [fw_event0]

root      1123    2  0 Aug16 ?        00:00:00 [kipmi0]

root      1124    2  0 Aug16 ?        00:00:00 [scsi_eh_2]

root      1125    2  0 Aug16 ?        00:00:00 [scsi_tmf_2]

root      1126    2  0 Aug16 ?        00:00:00 [scsi_eh_3]

root      1127    2  0 Aug16 ?        00:00:00 [scsi_tmf_3]

root      1128    2  0 Aug16 ?        00:00:00 [scsi_eh_4]

root      1129    2  0 Aug16 ?        00:00:00 [scsi_tmf_4]

root      1130    2  0 Aug16 ?        00:00:00 [scsi_eh_5]

root      1131    2  0 Aug16 ?        00:00:00 [scsi_tmf_5]

root      1132    2  0 Aug16 ?        00:00:00 [scsi_eh_6]

root      1133    2  0 Aug16 ?        00:00:00 [scsi_tmf_6]

root      1134    2  0 Aug16 ?        00:00:00 [scsi_eh_7]

root      1135    2  0 Aug16 ?        00:00:00 [scsi_tmf_7]

root      1168    2  0 Aug16 ?        00:00:00 [poll_0_status]

root      1267    1  0 Aug16 ?        00:00:00 /usr/sbin/rsyslogd -i /var/run/r

root      1496    2  0 Aug16 ?        00:00:00 [kworker/6:2]

root      1518    1  0 Aug16 ?        00:00:00 /sbin/dhcpcd -w -t 10 -h Tower -

bin      1528    1  0 Aug16 ?        00:00:00 /sbin/rpc.portmap

rpc      1532    1  0 Aug16 ?        00:00:00 /sbin/rpc.statd

root      1542    1  0 Aug16 ?        00:00:00 /usr/sbin/inetd

root      1552    1  0 Aug16 ?        00:00:00 /usr/sbin/sshd

root      1564    1  0 Aug16 ?        00:00:01 /usr/sbin/ntpd -g -p /var/run/nt

root      1573    1  0 Aug16 ?        00:00:00 /usr/sbin/acpid

81        1585    1  0 Aug16 ?        00:00:00 /usr/bin/dbus-daemon --system

root      1587    1  0 Aug16 ?        00:00:00 /usr/sbin/crond -l notice

daemon    1589    1  0 Aug16 ?        00:00:00 /usr/sbin/atd -b 15 -l 1

root      1594    1  0 Aug16 ?        00:00:00 /usr/sbin/nmbd -D

root      1596    1  0 Aug16 ?        00:00:00 /usr/sbin/smbd -D

root      1603    1  0 Aug16 ?        00:00:50 /bin/bash /usr/local/sbin/cpuloa

root      1832    1 91 Aug16 ?        1-01:00:04 /usr/local/sbin/emhttp

root      1833    1  0 Aug16 tty1    00:00:00 /sbin/agetty --noclear 38400 tty

root      1834    1  0 Aug16 tty2    00:00:00 /sbin/agetty 38400 tty2 linux

root      1835    1  0 Aug16 tty3    00:00:00 /sbin/agetty 38400 tty3 linux

root      1836    1  0 Aug16 tty4    00:00:00 /sbin/agetty 38400 tty4 linux

root      1837    1  0 Aug16 tty5    00:00:00 /sbin/agetty 38400 tty5 linux

root      1838    1  0 Aug16 tty6    00:00:00 /sbin/agetty 38400 tty6 linux

root      1850    2  0 Aug16 ?        00:00:00 [md]

root      1851    2  2 Aug16 ?        00:45:26 [mdrecoveryd]

root      1855    2  0 Aug16 ?        00:00:00 [spinupd]

root      1856    2  0 Aug16 ?        00:00:00 [spinupd]

root      1857    2  0 Aug16 ?        00:00:00 [spinupd]

root      1878    1  0 Aug16 ?        00:00:01 /sbin/apcupsd

root      1898    2  4 Aug16 ?        01:14:55 [unraidd]

root      1910    2  0 Aug16 ?        00:00:00 [xfs-buf/md1]

root      1911    2  0 Aug16 ?        00:00:00 [xfs-data/md1]

root      1912    2  0 Aug16 ?        00:00:00 [xfs-conv/md1]

root      1913    2  0 Aug16 ?        00:00:00 [xfs-cil/md1]

root      1914    2  0 Aug16 ?        00:00:03 [xfsaild/md1]

root      1915    2  0 Aug16 ?        00:00:35 [kworker/2:1H]

root      1928    2  0 Aug16 ?        00:00:00 [xfs-buf/md2]

root      1929    2  0 Aug16 ?        00:00:00 [xfs-data/md2]

root      1930    2  0 Aug16 ?        00:00:00 [xfs-conv/md2]

root      1931    2  0 Aug16 ?        00:00:00 [xfs-cil/md2]

root      1932    2  0 Aug16 ?        00:00:00 [xfsaild/md2]

root      1933    2  0 Aug16 ?        00:00:00 [kworker/7:1H]

root      1943    2  0 Aug16 ?        00:00:00 [xfs-buf/sdb1]

root      1944    2  0 Aug16 ?        00:00:00 [xfs-data/sdb1]

root      1945    2  0 Aug16 ?        00:00:00 [xfs-conv/sdb1]

root      1946    2  0 Aug16 ?        00:00:00 [xfs-cil/sdb1]

root      1947    2  0 Aug16 ?        00:00:04 [xfsaild/sdb1]

root      1959    1  0 Aug16 ?        00:00:00 /usr/local/sbin/shfs /mnt/user0

root      1969    1  0 Aug16 ?        00:01:42 /usr/local/sbin/shfs /mnt/user -

root      1981    2  0 Aug16 ?        00:00:36 [kworker/1:1H]

root      1982    2  0 Aug16 ?        00:00:38 [kworker/0:1H]

avahi    2007    1  0 Aug16 ?        00:00:01 avahi-daemon: running [Tower.loc

avahi    2008  2007  0 Aug16 ?        00:00:00 avahi-daemon: chroot helper

root      2016    1  0 Aug16 ?        00:00:00 /usr/sbin/avahi-dnsconfd -D

root      2033    2  0 Aug16 ?        00:00:00 [btrfs-worker]

root      2034    2  0 Aug16 ?        00:00:00 [btrfs-worker-hi]

root      2035    2  0 Aug16 ?        00:00:00 [btrfs-delalloc]

root      2036    2  0 Aug16 ?        00:00:00 [btrfs-flush_del]

root      2037    2  0 Aug16 ?        00:00:00 [btrfs-cache]

root      2038    2  0 Aug16 ?        00:00:00 [btrfs-submit]

root      2039    2  0 Aug16 ?        00:00:00 [btrfs-fixup]

root      2040    2  0 Aug16 ?        00:00:00 [btrfs-endio]

root      2041    2  0 Aug16 ?        00:00:00 [btrfs-endio-met]

root      2042    2  0 Aug16 ?        00:00:00 [btrfs-endio-met]

root      2043    2  0 Aug16 ?        00:00:00 [btrfs-endio-rai]

root      2044    2  0 Aug16 ?        00:00:00 [btrfs-endio-rep]

root      2045    2  0 Aug16 ?        00:00:00 [btrfs-rmw]

root      2046    2  0 Aug16 ?        00:00:00 [btrfs-endio-wri]

root      2047    2  0 Aug16 ?        00:00:00 [btrfs-freespace]

root      2048    2  0 Aug16 ?        00:00:00 [btrfs-delayed-m]

root      2049    2  0 Aug16 ?        00:00:00 [btrfs-readahead]

root      2050    2  0 Aug16 ?        00:00:00 [btrfs-qgroup-re]

root      2051    2  0 Aug16 ?        00:00:00 [btrfs-extent-re]

root      2052    2  0 Aug16 ?        00:00:00 [btrfs-cleaner]

root      2053    2  0 Aug16 ?        00:00:00 [btrfs-transacti]

root      2055    1  0 Aug16 ?        00:00:08 /usr/bin/docker -d -p /var/run/d

root      2068    2  0 Aug16 ?        00:00:00 [kworker/6:1H]

root      2108    2  0 Aug16 ?        00:00:00 [kworker/5:1H]

root      2110    2  0 Aug16 ?        00:00:00 [kworker/4:1H]

root      2216  2055  0 Aug16 ?        00:00:00 docker-proxy -proto tcp -host-ip

root      2224  2055  0 Aug16 ?        00:00:00 /usr/bin/python3 -u /sbin/my_ini

root      2271    2  0 Aug16 ?        00:00:00 [jbd2/loop1-8]

root      2272    2  0 Aug16 ?        00:00:00 [ext4-rsv-conver]

root      2287    2  0 Aug16 ?        00:00:00 [kvm-irqfd-clean]

root      2291    1  0 Aug16 ?        00:00:00 /usr/sbin/libvirtd -d -l -f /etc

nobody    2380    1  0 Aug16 ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/v

root      2381  2380  0 Aug16 ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/v

root      2391    1  2 Aug16 ?        00:38:36 /usr/bin/qemu-system-x86_64 -nam

root      2393    2  0 Aug16 ?        00:00:02 [vhost-2391]

root      2396    2  0 Aug16 ?        00:00:00 [kvm-pit/2391]

root      2450  2224  0 Aug16 ?        00:00:00 /usr/bin/runsvdir -P /etc/servic

root      2451  2450  0 Aug16 ?        00:00:00 runsv cron

root      2452  2450  0 Aug16 ?        00:00:00 runsv syslog-forwarder

root      2453  2450  0 Aug16 ?        00:00:00 runsv syslog-ng

root      2454  2450  0 Aug16 ?        00:00:00 runsv emby

root      2457  2452  0 Aug16 ?        00:00:00 tail -f -n 0 /var/log/syslog

nobody    2458  2454  2 Aug16 ?        00:41:47 mono-sgen /opt/emby-server/Media

root      2459  2453  0 Aug16 ?        00:00:00 syslog-ng -F -p /var/run/syslog-

root      2460  2451  0 Aug16 ?        00:00:00 /usr/sbin/cron -f

root      2666  1084  0 Aug16 ?        00:00:00 /sbin/udevd --daemon

root      2667  1084  0 Aug16 ?        00:00:00 /sbin/udevd --daemon

root      2670    1  0 Aug16 ?        00:02:05 /usr/bin/qemu-system-x86_64 -nam

root      2672    2  0 Aug16 ?        00:00:01 [vhost-2670]

root      2674    2  0 Aug16 ?        00:00:00 [kvm-pit/2670]

root      5620    2  0 Aug16 ?        00:00:10 [kworker/0:3]

root      6632    2  0 00:29 ?        00:00:00 [kworker/2:2]

root      7091    2  0 00:32 ?        00:00:00 [kworker/3:1]

root      7099    2  0 00:32 ?        00:00:00 [kworker/5:3]

root    25398    2  0 05:27 ?        00:00:00 [kworker/3:2H]

root    27777    2  0 14:58 ?        00:00:00 [kworker/u17:9]

root    30817    2  0 21:25 ?        00:00:00 [kworker/u16:1]

root    30963    2  0 21:26 ?        00:00:00 [kworker/u17:4]

root    31177    2  0 21:27 ?        00:00:00 [kworker/4:1]

root    32040    2  0 18:27 ?        00:00:00 [kworker/4:0]

root    32054    2  0 18:27 ?        00:00:00 [kworker/1:3]

root    32066    2  0 18:27 ?        00:00:00 [kworker/1:9]

root    32069    2  0 18:27 ?        00:00:00 [kworker/7:0H]

root    32101    2  0 18:28 ?        00:00:00 [kworker/3:2]

root    32169    2  0 18:28 ?        00:00:00 [kworker/2:0]

root    32188    2  0 21:33 ?        00:00:00 [kworker/u16:2]

root    32201    2  0 18:28 ?        00:00:01 [kworker/0:4]

root    32213    2  0 18:28 ?        00:00:00 [kworker/3:1H]

 

and my lsof -Pni command

 

COMMAND    PID  USER  FD  TYPE DEVICE SIZE/OFF NODE NAME

sshd      886  root    3u  IPv4 384936      0t0  TCP 192.168.10.20:22->192.168.10.39:50608 (ESTABLISHED)

dhcpcd    1518  root    7u  IPv4  13550      0t0  UDP *:68

rpc.portm 1528    bin    4u  IPv4  13555      0t0  UDP *:111

rpc.portm 1528    bin    5u  IPv4  13556      0t0  TCP *:111 (LISTEN)

rpc.statd 1532    rpc    5u  IPv4  13580      0t0  UDP *:47073

rpc.statd 1532    rpc    7u  IPv4  13583      0t0  TCP *:56517 (LISTEN)

rpc.statd 1532    rpc    8u  IPv4  13572      0t0  UDP 127.0.0.1:862

inetd    1542  root    4u  IPv4  13589      0t0  TCP *:37 (LISTEN)

inetd    1542  root    5u  IPv4  13590      0t0  UDP *:37

inetd    1542  root    6u  IPv4  13591      0t0  TCP *:21 (LISTEN)

inetd    1542  root    7u  IPv4  13592      0t0  TCP *:23 (LISTEN)

sshd      1552  root    3u  IPv4  12939      0t0  TCP *:22 (LISTEN)

ntpd      1564  root  16u  IPv4  12947      0t0  UDP *:123

ntpd      1564  root  17u  IPv4  12952      0t0  UDP 127.0.0.1:123

ntpd      1564  root  18u  IPv4  12954      0t0  UDP 192.168.10.20:123

ntpd      1564  root  22u  IPv4  13133      0t0  UDP 172.17.42.1:123

ntpd      1564  root  23u  IPv4  13276      0t0  UDP 192.168.122.1:123

nmbd      1594  root  11u  IPv4  1573      0t0  UDP *:137

nmbd      1594  root  12u  IPv4  1574      0t0  UDP *:138

nmbd      1594  root  13u  IPv4  1576      0t0  UDP 192.168.10.20:137

nmbd      1594  root  14u  IPv4  1577      0t0  UDP 192.168.10.255:137

nmbd      1594  root  15u  IPv4  1578      0t0  UDP 192.168.10.20:138

nmbd      1594  root  16u  IPv4  1579      0t0  UDP 192.168.10.255:138

nmbd      1594  root  18u  IPv4  23842      0t0  UDP 172.17.42.1:137

nmbd      1594  root  19u  IPv4  23843      0t0  UDP 172.17.255.255:137

nmbd      1594  root  20u  IPv4  23844      0t0  UDP 172.17.42.1:138

nmbd      1594  root  21u  IPv4  23845      0t0  UDP 172.17.255.255:138

nmbd      1594  root  22u  IPv4  23846      0t0  UDP 192.168.122.1:137

nmbd      1594  root  23u  IPv4  23847      0t0  UDP 192.168.122.255:137

nmbd      1594  root  24u  IPv4  23848      0t0  UDP 192.168.122.1:138

nmbd      1594  root  25u  IPv4  23849      0t0  UDP 192.168.122.255:138

smbd      1596  root  26u  IPv4  13644      0t0  TCP *:445 (LISTEN)

smbd      1596  root  27u  IPv4  13645      0t0  TCP *:139 (LISTEN)

emhttp    1832  root    3u  IPv4  15606      0t0  TCP *:80 (LISTEN)

apcupsd  1878  root    4u  IPv4    329      0t0  TCP *:3551 (LISTEN)

avahi-dae 2007  avahi  13u  IPv4  13099      0t0  UDP *:5353

avahi-dae 2007  avahi  14u  IPv4  13100      0t0  UDP *:35482

docker    2216  root    4u  IPv4    490      0t0  TCP *:8096 (LISTEN)

libvirtd  2291  root  13u  IPv4  16436      0t0  TCP *:16509 (LISTEN)

dnsmasq  2380 nobody    4u  IPv4  16766      0t0  UDP *:67

dnsmasq  2380 nobody    5u  IPv4  16771      0t0  UDP 192.168.122.1:53

dnsmasq  2380 nobody    6u  IPv4  16772      0t0  TCP 192.168.122.1:53 (LISTEN)

qemu-syst 2391  root  16u  IPv4  13263      0t0  TCP *:5900 (LISTEN)

qemu-syst 2391  root  17u  IPv4  13266      0t0  TCP *:5700 (LISTEN)

qemu-syst 2670  root  16u  IPv4  13941      0t0  TCP *:5901 (LISTEN)

qemu-syst 2670  root  17u  IPv4  13944      0t0  TCP *:5701 (LISTEN)

 

Hardware is a tyan motherboard with intel NIC'S

Intel Xeon Proc

8GB ECC memory

3 x 3TB drives (1 for parity)

1 x 128GB SSD

 

This is the same hardware that I have been running Windows Server 2012R2 and ClearOS 6 on previously with no hardware issues occuring in either of those operating systems.

 

Any suggestions on how to remedy this problem will be much appreciated.

Hello,

 

I am running 6.0.1 and am running into this issue as well with the webgui becoming unresponsive.  Everything else still works fine on the server, I am able to access my docker applications and my VM's without issue.  So far the record has been close to 2 whole days of running before the webgui goes down.  When it goes down it always happens while I am going back and forth between pages on it, looking for information. 

 

Since your server remains accessible once it enters this state, it would be extremely helpful if you can post your system log.  You can do this by logging in to the console or use telnet/ssh window and copy the system log to your usb flash device:

 

cp /var/log/syslog /boot/syslog.txt

 

Then you should be able to fetch the syslog.txt file off your flash share.

 

Also what pages are you mainly bouncing between when this issue happens?

Which browser are you using and have you tried to use another browser when the issue appears ?

 

Which browser are you using and have you tried to use another browser when the issue appears ?

 

 

I have been using Internet explorer 11 and Microsoft Edge

Hello,

 

I am running 6.0.1 and am running into this issue as well with the webgui becoming unresponsive.  Everything else still works fine on the server, I am able to access my docker applications and my VM's without issue.  So far the record has been close to 2 whole days of running before the webgui goes down.  When it goes down it always happens while I am going back and forth between pages on it, looking for information. 

 

Since your server remains accessible once it enters this state, it would be extremely helpful if you can post your system log.  You can do this by logging in to the console or use telnet/ssh window and copy the system log to your usb flash device:

 

cp /var/log/syslog /boot/syslog.txt

 

Then you should be able to fetch the syslog.txt file off your flash share.

 

Also what pages are you mainly bouncing between when this issue happens?

 

This seems to happen when I change between any two pages. I haven't really noticed it as always happening between the same two pages.  As for my log, during the time in question, it fills up with repeated lines of Aug 26 15:07:51 Tower avahi-daemon[5100]: Invalid response packet from host 192.168.10.109.  The IP address being that of the machine I am connecting to the server with.

 

Hello,

 

I am running 6.0.1 and am running into this issue as well with the webgui becoming unresponsive.  Everything else still works fine on the server, I am able to access my docker applications and my VM's without issue.  So far the record has been close to 2 whole days of running before the webgui goes down.  When it goes down it always happens while I am going back and forth between pages on it, looking for information. 

 

Since your server remains accessible once it enters this state, it would be extremely helpful if you can post your system log.  You can do this by logging in to the console or use telnet/ssh window and copy the system log to your usb flash device:

 

cp /var/log/syslog /boot/syslog.txt

 

Then you should be able to fetch the syslog.txt file off your flash share.

 

Also what pages are you mainly bouncing between when this issue happens?

 

This is the line from my log file that was written at the time of my most recent crash

 

Sep  1 09:19:38 Tower avahi-daemon[3514]: Invalid response packet from host 192.168.10.109.

That's a meaningless line (harmless) that just indicates that you have a windows 10 box on your network.  You should post the full diagnostics

Below is the zip file of my diagnostics.  Looking at the syslog file though I don't see anything obviously wrong.

Technically, Unassigned Devices is not yet supported on 6.1.0. Probably not the cause of your issue.

I had that installed in 6.0.1 and was having this same issue.  Had this issue actually before unassigned devices was installed in 6.0.1

I'm having the same issue, the emhttp takes the 100% of cpu and webgui not responding any more.

 

Here the last lines of the log:

 

Sep  3 09:29:21 UnRaid emhttp: sendFile: sendfile /usr/local/emhttp/plugins/dynamix.apcupsd/images/dynamix.apcupsd.png: Broken pipe
Sep  3 09:29:21 UnRaid emhttp: need_authorization: getpeername: Transport endpoint is not connected
Sep  3 09:29:21 UnRaid emhttp: sendFile: sendfile /usr/local/emhttp/plugins/dynamix.vm.manager/images/dynamix.vm.manager.png: Broken pipe
Sep  3 09:29:21 UnRaid emhttp: need_authorization: getpeername: Transport endpoint is not connected
Sep  3 09:29:21 UnRaid emhttp: sendFile: sendfile /usr/local/emhttp/plugins/dynamix/icons/networkservices.png: Broken pipe
Sep  3 09:29:21 UnRaid emhttp: need_authorization: getpeername: Transport endpoint is not connected
Sep  3 09:29:21 UnRaid emhttp: sendFile: sendfile /usr/local/emhttp/plugins/dynamix/images/apple-logo.png: Broken pipe
Sep  3 09:29:21 UnRaid emhttp: need_authorization: getpeername: Transport endpoint is not connected
Sep  3 09:32:08 UnRaid emhttp: need_authorization: getpeername: Transport endpoint is not connected
Sep  3 09:32:08 UnRaid emhttp: need_authorization: getpeername: Transport endpoint is not connected
Sep  3 09:32:08 UnRaid emhttp: need_authorization: getpeername: Transport endpoint is not connected

 

Hope this can be helpful.

 

 

Hey,

 

Sorry, this might not be related as I haven't read all of the pages/posts but this used to happen to me (hanging of WebGUI in v5/v6, webgui not loading)  b/c I had multiple boxes of OpenELEC running and each of those boxes were set to run as Local Master.  I was still able to browse all shares/telnet etc, but just not access the web gui.

 

For me the solution that fixed it was to create/edit the samba.conf file on my OpenELEC boxes and add/edit the following lines:

  preferred master = no
  domain master = no
  local master = no

 

After that just ensure the Unraid is set as your local master and reboot all your boxes.

 

Again, sorry if this is not related but after doing the above fixed the issue of a non-responsive webgui for me (although I don't know what it had to do with the samba.conf).

 

Take Care

 

6.1.2 seems to have done the trick for me :)

Woo hoo!

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.