Menu
▾
▴
[mh] Closeout:: MH on NSLU2 - OpenWRT Kamakazie 8.09
|
From: carl m. <cmc...@co...> - 2010-02-04 02:33:14
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
The thread below summarizes attempts to get a fully functional
Misterhouse running on my NSLU2 running OpenWRT (a.k.a Kamakazie 8.0.9)<br>
<br>
Summary - I gave up and moved to Debian(Lenny) which works well for me.<br>
<br>
For those who wish to pursue the OpenWRT option, here is a quick
summary:<br>
<br>
The good:<br>
MH came up and ran my Insteon scripts previously set up on a regular"
PC under Suse 11.1.<br>
Since the NSLU2 has no console and is resource challenged, I ran with
tk=0 and gd=0.<br>
<br>
The bad:<br>
MH hung at startup unless Xap and Xpl were disabled (I disabled in
mh.private.ini)<br>
<br>
The ugly:<br>
I was unable to get the MH server to communicate with a remote browser
via port 8080.<br>
a 'netstat' on the NSLU showed an ESTABLISHED connection (remote
browser to local server on 8080) but no data/html was transferred to
the browser.<br>
The netstat also showed a number of internal connections to the
localhost:8080 address starting up and timing out.<br>
I ran with debug=http;http2;http3 but no useful information was gleaned.<br>
<br>
Now that I am up and running on Debian Lenny on the NSLU2, I see the
following traffic on the console from the mh process<br>
<br>
...........<br>
<pre wrap="">03/02/2010 08:33:00 PM: Saving object states ... done
----------
http: client_ip=127.0.0.1 a=family.
http: c=0 td=0 sop= soa=.
Closing socket port http
03/02/2010 08:34:00 PM: Saving object states ... done
----------
http: client_ip=127.0.0.1 a=family.
http: c=0 td=0 sop= soa=.
Closing socket port http</pre>
..........................<br>
<br>
So every minute right after the "Saving Object states" report there is
an internal (within mh, I presume) connection established and, when
running properly, closed each cycle.<br>
This is presumably the hung/timed out traffic I was seeing when running
under OpenWRT.<br>
As expected, when the remote web browser connects to the MH:8080 server
the console gets gobs of debug information when the connection is
running.<br>
<br>
I tried all the MH debug options and looked in all the available logs
on the NSLU2, did not see any useful indicator as to what OpenWRT
packages might be missing.<br>
<br>
Since I was planning to add a File server function on theNSLU2 anyway,
had a USB HDD attached and did not need the routing functionality in
OpenWRT, I decided that Debian Lenny was a better match and it worked
out well.<br>
<br>
Thanks to Seann Clark for introducing me to 'curl' and other useful
suggestions.<br>
<br>
<br>
<br>
Seann Clark wrote:
<blockquote cite="mid:4B6...@ts..." type="cite">carl
mcgrath wrote:
<br>
<blockquote type="cite">Interesting tool "curl".
<br>
<br>
I am not sure what you saw in the 'netstat' results that caused you to
say "It looks like it is binding to port 80".
<br>
When I ran that particular netsat, I had killed the normal httpd
process that serves up the OpenWRT GUI on port 80.
<br>
<br>
What I think I see are:
<br>
+ Two SSH connections for two consoles opened on my Linux machine for
command line interface (port 22)
<br>
+ One "Established" connection on port 8080 to my Windows machine, an
attempt to connect to the MH GUI. It is hung.
<br>
From the browser, it seems that the connection is established
but server(MH) can't find the html to send back.
<br>
I get the "Waiting for <a class="moz-txt-link-freetext" href="http://192.168.10.150:8080">http://192.168.10.150:8080</a>" at bottom of
browser window along with the progress bar.
<br>
I tried both IE and Firefox.
<br>
+ Several localhost to localhost connections in the :CLOSE_WAIT state.
<br>
<br>
I installed curl onto the NSLU2.
<br>
I also have the OpenWRT GUI running again.
<br>
<br>
running 'curl localhost:80' returns a short burst of html from the
LuCI package - the OpenWRT GUI.
<br>
<br>
running 'curl localhost:8080' hangs, returns nothing.
<br>
<br>
Thanks for the tool suggestion, I'll continue the debug on the NSLU2
using the native 'curl' interface.
<br>
<br>
Seann Clark wrote:
<br>
<blockquote type="cite">carl mcgrath wrote:
<br>
<blockquote type="cite">Thanks, I am fairly sure I got the
firewall out of the way.
<br>
<br>
With MH running "normally", I see the following with a netstat:
<br>
<br>
root@PVE_NSLU1:/opt/Misterhouse/cjm_local/data# netstat
<br>
Active Internet connections (w/o servers)
<br>
Proto Recv-Q Send-Q Local Address Foreign Address
State
<br>
tcp 0 0 PVE_NSLU1:22 PVE-LinuxSRV5.capenet:43503
ESTABLISHED
<br>
tcp 1 0 localhost.:8080 localhost.:37066
CLOSE_WAIT
<br>
tcp 1 0 localhost.:8080 localhost.:37067
CLOSE_WAIT
<br>
tcp 0 0 PVE_NSLU1:22 PVE-LinuxSRV5.capenet:43505
ESTABLISHED
<br>
tcp 1 0 localhost.:8080 localhost.:34839
CLOSE_WAIT
<br>
tcp 551 0 PVE_NSLU1:8080 Dads_beast.capenet:1600
ESTABLISHED
<br>
udp 0 0 PVE_NSLU1:123 white.web-ster.com:123
ESTABLISHED
<br>
<br>
There appears to be a number of internal (to MH) connections that wake
up, then spend a lot of time in this CLOSE_WAIT state.
<br>
The number continues to grow, old ones finally die.
<br>
<br>
Otherwise, the above shows 2 SSH connections and an attempt to load the
Web interface(Recv-Q 551).
<br>
The web page loading to Dads_beast times out.
<br>
<br>
I am guessing some internal communications within MH are not set up
correctly.
<br>
<br>
Any other ideas are welcome!
<br>
<br>
<br>
Seann Clark wrote:
<br>
<blockquote type="cite">cjm5035 wrote:
<br>
<blockquote type="cite">I am trying to bring up my MH on an
NSLU2 running the current OpenWRT 8.09.
<br>
<br>
I had to disable XAP, am now running but unable to connect to the web
<br>
interface on Port 8080.
<br>
<br>
Any experiences out there?
<br>
</blockquote>
Make sure the firewall on the router is allowing port 8080 would be my
first guess. I haven't done MH on a WRT flavor, but I know it tends to
lock down access to ports depending on the build.
<br>
------------------------------------------------------------------------
<br>
<br>
</blockquote>
</blockquote>
It looks like it is binding to port 80. What do you get when you do a
curl <a class="moz-txt-link-freetext" href="http://localhost:8080/">http://localhost:8080/</a> ?
<br>
------------------------------------------------------------------------
<br>
<br>
</blockquote>
</blockquote>
<br>
I had meant to say looks like it is binding to port 8080 on localhost,
sorry for the confusion.
<br>
<br>
<pre wrap="">
<hr size="4" width="90%">
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/theplanet-com">http://p.sf.net/sfu/theplanet-com</a></pre>
<pre wrap="">
<hr size="4" width="90%">
________________________________________________________
To unsubscribe from this list, go to: <a class="moz-txt-link-freetext" href="http://sourceforge.net/mail/?group_id=1365">http://sourceforge.net/mail/?group_id=1365</a>
</pre>
</blockquote>
</body>
</html>
|