molesza Posted July 30, 2013 Share Posted July 30, 2013 I am running a few plugins and restarted my machine successfully a couple of times. However the last restart has caused the GUI to stop working. I am getting a error that keeps repeating saying Tower emhttp: emhttp_read_line: emhttp_read_line: input line too long I have looked on the forum and the only solution I could find was to run chkdsk on the flash drive. I have done this and found no errors. All my plugins are starting without issue. I just cant get onto the GUI. I have run a network discovery tool from another PC and see that port 80 is open. I have attached my Syslog. Hope someone can help! syslog.zip Quote Link to comment
molesza Posted July 31, 2013 Author Share Posted July 31, 2013 Been running for 24 hours now and still no access to GUI. I really hope to find a solution because I spent ages installing all the plugins and rebooting to test if it works, which it did! Quote Link to comment
Joe L. Posted July 31, 2013 Share Posted July 31, 2013 Been running for 24 hours now and still no access to GUI. I really hope to find a solution because I spent ages installing all the plugins and rebooting to test if it works, which it did! did you send an e-mail to [email protected] pointing them to this thread? Quote Link to comment
dgaschk Posted July 31, 2013 Share Posted July 31, 2013 If you disable all of the add-ons can the GUI be accessed? Quote Link to comment
guitarlp Posted July 31, 2013 Share Posted July 31, 2013 I'd backup the flash drive, re-format, and flash the latest rc16c back onto the drive. If that doesn't work, then it doesn't sound like an unRAID issue (it would be a hardware issue). If it does work, you can try copying back all your settings to the flash drive and see if it works at that point. Quote Link to comment
molesza Posted August 1, 2013 Author Share Posted August 1, 2013 Well before you all replied I tried to shutdown cleanly by installing unmenu. This worked. I then restarted the unraid box and the web gui was accessible and all was good. Then later on in the day it became unresponsive again. So it seems like something is eventually holding it up. Is there any way to discover what that might be? Or should I just reinstall again. Quote Link to comment
molesza Posted August 1, 2013 Author Share Posted August 1, 2013 Small update. I have shutdown all my donwloading plugins, sabnzbd, sickbeard, couchpotato and headphones by going to each of their GUIs. The unraid GUI came back after doing that. So I am going to enable everything again and when the problem occurs I will disable one at a time to find out which is causing the issue. Will update once I have worked it out. After that I will post my findings in the influencer plugins thread. Quote Link to comment
drawz Posted August 2, 2013 Share Posted August 2, 2013 Running out of RAM perhaps? Quote Link to comment
molesza Posted August 25, 2013 Author Share Posted August 25, 2013 So out of the blue the problem has come back. I have restarted the array and started it in safe mode. Could not access the GUI for an hour. Finally got in and Unraid is running a parity check. I am really unsure of what to do now as the system is running in safe mode and I haven't changed anything. I have attached my syslog. Hopefully someone can shed some light. syslog.zip Quote Link to comment
victoRaid Posted October 27, 2013 Share Posted October 27, 2013 I'm having this same problem with a new install and plugins (SAB, SB, CP, HP, Boxcar). However, I've figured out that clearing the browser's cache and clearing all cookies related to the webgui brings it back. Very strange. Quote Link to comment
dalben Posted July 17, 2014 Share Posted July 17, 2014 Headphones does this to me. I swap between using the ip Address of the server and the DNS name. That sometimes helps Quote Link to comment
archedraft Posted July 17, 2014 Share Posted July 17, 2014 I recently installed Deulge via Docker and once is it installed unRAID gives the following errors: Jul 16 14:03:48 Tower emhttp: read_line: read_line: input line too long Jul 16 14:04:23 Tower last message repeated 15 times Jul 16 14:04:27 Tower last message repeated 7 times Once this happens I lose the option to connect to the unRAID Gui via http://Tower. I have to enter the IP address (192.168.1.20) to pull up the unRAID web Gui. This also happens if I install the Deluge_64.plg so it would appear that this is not a docker problem but I was hoping that some else here was running into similar issues? Quote Link to comment
Freddie Posted July 18, 2014 Share Posted July 18, 2014 I recently installed Deulge via Docker and once is it installed unRAID gives the following errors: Jul 16 14:03:48 Tower emhttp: read_line: read_line: input line too long Jul 16 14:04:23 Tower last message repeated 15 times Jul 16 14:04:27 Tower last message repeated 7 times Once this happens I lose the option to connect to the unRAID Gui via http://Tower. I have to enter the IP address (192.168.1.20) to pull up the unRAID web Gui. This also happens if I install the Deluge_64.plg so it would appear that this is not a docker problem but I was hoping that some else here was running into similar issues? I can reproduce this error with headphones running in a docker container. The Home page of the headphones webgui writes a cookie with content that is almost 900 characters long and the Logs page writes a cookie that's over 600 characters long. These two cookies together prevent the unRAID webgui from loading. Delete either cookie and the unRAID webgui loads fine again. Quote Link to comment
dmacias Posted July 19, 2014 Share Posted July 19, 2014 I have had this happen to but not sure which docker caused it since I have both deluge and headphones. I get the same error in system log. I switched browsers and it worked so I cleared history and cookies in Firefox like Freddie said and all is well. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.