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.

google chrome on android device kills emhttp

Featured Replies

morning all, i am pretty sure i have found an issue with emhttp and google chome for android, basically if you go to the main tab of unraid webui using google chrome on an android device and click on start/stop or spin up/spin down then it kills emhttp, from that point on you cannot view the webui either from a phone or pc (any browser), the only way around this is to then telnet in and force a reboot of the server.

 

whilst i realise this isnt a bug per say and more an incompatibility, it would be nice to have this issue fixed.

 

anybody else noticed this issue?.

 

edit sorry forgot to post version im running, its 5.0.2

 

binhex.

 

 

  • Author

Why don't you post a log that you capture after the emhttp failure?  That will enable more knowledgeable people to analyze what is happening.  You can find instruction on how to do this here:

 

http://lime-technology.com/forum/index.php?topic=9880.0

 

ok i will do, just wondered really if anybody was seeing this or not firstly i will post my syslog later on.

  • 1 month later...

Did hit me today. Used Google Chrome to check if my Parity Check (that needs 50 hours on my machine) is still running. I could check once - after that I can't open the WebUI any longer. SSH still works and I do see an emhttp process when callig ps.

 

My problem now is: If I use /usr/local/sbin/powerdown the system starts another parity check (another 50 hours) when it comes up from the powerdown. I want to avoid that. How can I gracefully stop the system from SSH?

 

Here's part of the log:

 

Jan 18 15:37:53 Tower kernel: mdcmd (60): spindown 11
Jan 19 01:02:34 Tower kernel: mdcmd (61): spindown 6
Jan 19 01:02:34 Tower kernel: mdcmd (62): spindown 7
Jan 19 01:02:34 Tower kernel: mdcmd (63): spindown 8
Jan 19 01:02:34 Tower kernel: mdcmd (64): spindown 9
Jan 19 08:12:01 Tower emhttp: returnFile: sendfile /usr/local/emhttp/plugins/webGui/js/jquery.js: Broken pipe
Jan 19 08:12:02 Tower emhttp: returnFile: sendfile /usr/local/emhttp/plugins/webGui/js/jquery.jgrowl.js: Broken pipe
Jan 19 08:12:02 Tower emhttp: returnFile: sendfile /usr/local/emhttp/plugins/webGui/js/jquery.ui.custom.js: Broken pipe
Jan 19 08:12:02 Tower emhttp: returnFile: sendfile /usr/local/emhttp/plugins/webGui/js/ui.dropdown.checklist.js: Broken pipe

Thanks. Did add the last line and that worked:

 

/root/samba stop
umount /dev/md1
...
umount /dev/md14
/root/mdcmd stop
/usr/local/sbin/powerdown

 

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.