Hi Hans, It turns out my server was configured so that only ports 80 and 3336 were open. Running it on port 80 works perfectly.
Thanks for your help and being patient! Jeff
On Thu, Jun 7, 2012 at 3:37 AM, Hans Hübner hans.huebner@gmail.com wrote:
Hi Jeff,
I found this summary on how to configure EC2 security groups: http://cloud-computing.learningtree.com/2010/09/24/understanding-amazon-ec2-...
Basically, you need to make port 8080 accessible from the outside.
HTH, Hans
On Thu, Jun 7, 2012 at 4:15 AM, Jeff Byrd jeffreydbyrd@gmail.com wrote:
Hi guys, thanks for all the suggestions. I do believe threads are enabled (otherwise the start command wouldn't return right?). And I've tried running it on several arbitrary ports, but the behavior remains consistent. I'm having trouble figuring out how to see the request logs. All I know is that the connection is timing out (Chrome gives me the message "Error 118 (net::ERR_CONNECTION_TIMED_OUT): The operation timed out."). It runs great on my localhost though so you're probably right in that it's a port or a host issue. Can anyone point me to some good books or tutorials on how this works?
On Wed, Jun 6, 2012 at 9:10 PM, William Halliburton < whalliburton@gmail.com> wrote:
Note that since this is an amazon EC2 instance you will have to have allowed access to the instance on the 8080 port. Since you said that it worked earlier on the same instance I'm just throwing this out there as a low possibility.
On Wed, Jun 6, 2012 at 12:22 PM, Jeff Byrd jeffreydbyrd@gmail.comwrote:
Hi Hans thanks for your reply, I do have Hunchentoot installed using quicklisp. And sorry for the ambiguity, I meant that I enter the server's address in my browser's address bar (in this case it would be ec2-184-72-143-0.compute-1.amazonaws.com:8080), it then hangs for a while, and eventually shows an error page saying "Opps, Google Chrome could not connect..."
Some additional info: On my local host, after entering the hunchentoot:start command, the prompt hangs until I hit CNTL-C. But on the remote host, it brings me back to the REPL. I'm still able to enter commands while sbcl runs (which I've read is characteristic of threading). I think I'll do a bit more homework and try to print request logs (if any) to a file.
Thanks, Jeff
On Wed, Jun 6, 2012 at 1:56 PM, Hans Hübner hans.huebner@gmail.comwrote:
Hi Jeff,
I don't quite know what exactly the problem is. Did you install Hunchentoot with quicklisp (http://www.quicklisp.org/)? If not, please do so. Also, what do you mean when you write "going to <remotehost>:8080/ doesn't display anything"? Do you get an empty page?
-Hans
On Wed, Jun 6, 2012 at 5:48 PM, Jeff Byrd jeffreydbyrd@gmail.comwrote:
Hi everyone,
This is my first attempt at a webapp, and first time posting to the mailing list. I have a question about starting a server on a remote machine. I've been playing with Hunchentoot on my localhost, and it works great. Earlier it worked on my remote webspace also. But recently I've been playing with SBCL threading and Allegro (following thishttp://www.gigamonkeys.com/book/practical-web-programming-with-allegroserve.htmltutorial, which had me install all sorts of weird gigamonkey stuff) and now when I run the command
(hunchentoot:start http://www.weitz.de/hunchentoot/#start (make-instance 'hunchentoot:easy-acceptor http://www.weitz.de/hunchentoot/#acceptor :port 8080))
it says #<HUNCHENTOOT:EASY-ACCEPTOR (host *, port 8080)> and going to <remotehost>:8080/ doesn't display anything. I hit cntr-z to put it in the background and then
$ lsof -i :8080 and I get
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME sbcl 11350 root 5u IPv4 1816786 0t0 TCP *:http-alt (LISTEN)
I have a feeling it's something simple, like incorrect host variable or a separate thread being stopped, but I'm having a hard time finding answers on Google and related documentation. Any suggestions or information on what that above message means would be greatly appreciated.
Thanks! Jeff
tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel