webgui/emhttp not responsive


Recommended Posts

I'm running v. 4.7 and cannot connect to emhttp :80 on my instance. I've tried restarting and rebooting. sabnzbd, unmenu etc are all working fine as is the array itself. I would like to add a new drive that I've pre-cleared, but can't access the GUI to do so and haven't found documentation to do it via CLI.

The system itself is fine. I get 70mb through sabnzbd and am using almost no resources.

 

 

root@Tower:~# uptime

21:53:35 up 15 min,  2 users,  load average: 0.08, 0.16, 0.16

root@Tower:~# free -m

            total      used      free    shared    buffers    cached

Mem:          4051      2266      1785          0        60      2042

-/+ buffers/cache:        163      3888

Swap:            0          0          0

 

 

root@Tower:~# vmstat 5 5

procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----

r  b  swpd  free  buff  cache  si  so    bi    bo  in  cs us sy id wa

0  0      0 1695236  61988 2223124    0    0    84  523 1412 2784  2 10 78 11

1  0      0 1679580  61988 2238528    0    0    0  1490 3769 5985  0 13 83  4

0  0      0 1664932  61992 2253056    0    0    1  1477 3598 5700  0 13 82  5

0  0      0 1647828  61992 2270012    0    0    0  1694 4169 6644  0 15 80  4

0  0      0 1626476  61992 2291172    0    0    0  2104 5058 8096  0 17 77  5

 

Even a telnet to the webserver and a simple get / hangs.

 

I'd love to have a way to debug the emhttp, and/or a solution/workaround.

Thanks,

Ruckus

syslog-2012-09-13.txt

Link to comment

telnet for access is:

telnet tower

 

telnet to test the http response is:

telnet tower 80

get /

<hang>

 

Ruckus

 

After

get /

press return TWICE  (servers do not respond until they get an empty line, the second carriage return is the empty line)

 

You'll then see:

HTTP/1.1 501 Not Implemented

 

 

If you then try instead using an UPPER CASE "GET" (again pressing return twice after GET) you'll see:

# telnet tower 80

Trying 192.168.2.100...

Connected to tower.

Escape character is '^]'.

GET /

 

HTTP/1.1 200 OK

Server: emhttp

Cache-Control: no-cache

Content-Type: text/html; charset=utf-8

 

<html>

<head>

<link rel="stylesheet" type="text/css" href="style.css" />

<title>Wait</title>

<script language="javascript">

function addLog(logID, logValue) {

  if (logObj = document.getElementById(logID)) {

    logObj.innerHTML = logObj.innerHTML + logValue;

    logObj.scrollTop=100000;

  }

}

</script>

</head>

 

<body onload="window.location='main.htm';">

 

<div id="logMain" style="border: 1px solid #C0C0C0; height: 100%; overflow: auto; padding: 5px; width: 100%;">

<p>Wait...</p>

</div>

 

You'll see a tiny bit of javascript is sent to the browser to have it show "Wait" and requesting it subsequently load the main page of unRAID

 

Have fun... you were just using an invalid "request type"

 

RFC 2616                        HTTP/1.1                      June 1999

 

 

5.1.1 Method

 

  The Method  token indicates the method to be performed on the

  resource identified by the Request-URI. The method is case-sensitive.

 

      Method        = "OPTIONS"                ; Section 9.2

                      | "GET"                    ; Section 9.3

                      | "HEAD"                  ; Section 9.4

                      | "POST"                  ; Section 9.5

                      | "PUT"                    ; Section 9.6

                      | "DELETE"                ; Section 9.7

                      | "TRACE"                  ; Section 9.8

                      | "CONNECT"                ; Section 9.9

                      | extension-method

      extension-method = token

 

  The list of methods allowed by a resource can be specified in an

  Allow header field (section 14.7). The return code of the response

  always notifies the client whether a method is currently allowed on a

  resource, since the set of allowed methods can change dynamically. An

  origin server SHOULD return the status code 405 (Method Not Allowed)

  if the method is known by the origin server but not allowed for the

  requested resource, and 501 (Not Implemented) if the method is

  unrecognized or not implemented by the origin server. The methods GET

  and HEAD MUST be supported by all general-purpose servers. All other

  methods are OPTIONAL; however, if the above methods are implemented,

  they MUST be implemented with the same semantics as those specified

  in section 9.

 

Joe L.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.