- tbnl-devel@common-lisp.net - mailman3.common-lisp.net

[hunchentoot-devel] invalid initarg error
by Patrick May 22 Sep '09

22 Sep '09

I'm running the latest version of Hunchentoot available from bknr.net in Clozure CL on a 64-bit Linux box. I see this error in the logs occasionally: [2009-09-15 19:44:49 [ERROR]] Error while processing connection: :REAL- ERROR is an invalid initarg to INITIALIZE-INSTANCE for #<STANDARD- CLASS USOCKET:TIMEOUT-ERROR>. Valid initargs: (:SOCKET). From poking around in the source it appears that this is only called in the usocket package. The site doesn't appear affected. Is this a known issue? Thanks, Patrick

3 8

[hunchentoot-devel] Hunchentoot on PORT 80
by Phil Marneweck 18 Sep '09

18 Sep '09

Hi Yesterday I tried to run hunchentoot on port 80 for the first time, but a get a "Permission Denied" error when hunchentoot tries to bind to port 80. Between the #ubuntu and #lisp guys we established that nothing else was running on port 80 and that I was indeed running as root. Everybody agreed that it must be that permissions gets dropped some where along the line. Searching the web regarding dropped permissions got me no where. So I was wondering if anybody else got this configuration to work on port 80 and could share their experience with me please. I have a clean ubuntu server, no apache or anything installed. I have an in init.d script that starts up a screen session which runs swank and start up stuff to load hunchentoot etc ie swank-daemon from clwiki. Regards Phil

6 7

Re: [hunchentoot-devel] [Openmcl-devel] Exception in foreign context
by Patrick May 13 Sep '09

13 Sep '09

On Sep 3, 2009, at 5:47 PM, Patrick May wrote: > On Sep 3, 2009, at 4:30 PM, R. Matthew Emerson wrote: >> On Sep 3, 2009, at 3:13 PM, Patrick May wrote: >>> I'm getting this error every couple of days when running >>> Hunchentoot >>> in CCL (1.3-r11936, 64 bit, Linux). Any idea what's causing it? >>> >>> ? exception in foreign context >>> Exception occurred while executing foreign code >>> at create_exception_callback_frame + 80 >>> ? for help >>> >>> [26583] Clozure CL kernel debugger: b >>> [26583] Clozure CL kernel debugger: current thread: tcr = >>> 0x7fe8ab2267b0, native thread ID = 0x11ec, interrupts disabled >>> >>> >>> (#x00007FE8ADBEDF48) #x0000300040018F7C : #<Function RECORD-SYSTEM- >>> LOCK #x0000300040018F2F> + 77 >>> Bogus frame 7fe8adbedf60 >>> [26583] Clozure CL kernel debugger: >> >> Those symptoms don't remind me of any bug I know about right off >> hand. >> >> You might try updating your CCL, though. You appear to be using the >> original 1.3 release binary, and I know that there have been >> important bug fixes to the 1.3 branch since release. > > Thanks for the quick response. I've updated from Subversion and > rebuilt CCL to 1.3-r12755M. Hopefully that will fix the problem. I just got the following problem. I don't know if it's related to Clozure or to Hunchentoot (64-bit Linux): Welcome to Clozure Common Lisp Version 1.3-r12755M (LinuxX8664)! ? STRING-OUTPUT-STREAM #x300041AC43AD> is not of the expected tyexception in foreign context Exception occurred while executing foreign code at create_exception_callback_frame + 80 ? for help [5067] Clozure CL kernel debugger: ? (G) Set specified GPR to new value (R) Show raw GPR/SPR register values (L) Show Lisp values of tagged registers (F) Show FPU registers (S) Find and describe symbol matching specified name (B) Show backtrace (T) Show info about current thread (X) Exit from this debugger, asserting that any exception was handled (K) Kill Clozure CL process (?) Show this help [5067] Clozure CL kernel debugger: b current thread: tcr = 0x7fd6b38177b0, native thread ID = 0x1e96, interrupts disabled [5067] Clozure CL kernel debugger: t Current Thread Context Record (tcr) = 0x7fd6b38177b0 Control (C) stack area: low = 0x7fd6b35c4000, high = 0x7fd6b3818000 Value (lisp) stack area: low = 0x7fd6b33a2000, high = 0x7fd6b35b3000 Exception stack pointer = 0x7fd6b35c3788 [5067] Clozure CL kernel debugger: k Any idea what could be causing this? Is anyone here running a website with Clozure and Hunchentoot? Thanks, Patrick

1 1

[hunchentoot-devel] question about the url of the request
by Mackram Raydan 07 Sep '09

07 Sep '09

Hey everyone, so i was working on my website and i noticed something peculiar in the documentation of hunchentoot that i thought i should probably ask about. As i understand hunchentoot has a function called get-uri* which returns the full uri including the query (the thing after the ?) and also has a function called get-query which returns the string that is after the ?. So my question is, is there a function that returns the url without the query string so that i can use my own dispatchers or should i use string manipulation? Also a side question not related to hunchentoot but that which i would greatly appreciate an anser too, does anyone know of some library that offer mail server ability in lisp or maybe just can recieve emails and offer them for processing (i currently use a modified version of cl-smtp by bknr to send emails.) Thanks in advance. Mackram Raydan Company: www.imagimate.com Website: www.trailoflight.net "An invasion of armies can be resisted, but not an idea whose time has come." Victor Hugo

3 2

[hunchentoot-devel] Issue with setting a dispatcher
by Mackram Raydan 06 Sep '09

06 Sep '09

Hey everyone, I have been trying to get a dispatcher to work with hunchentoot but I have been unable to do it at all. Specifically running the following line on the REPL *(hunchentoot:start (make-instance 'hunchentoot:acceptor :port 4555 :request-dispatcher (apply 'hunchentoot:create-prefix-dispatcher '("/" make-home-page))))* would result in an error appearing when i try to access the localhost:4555. The error I get is *[2009-08-31 21:04:16 [ERROR]] Error while processing connection: The value MAKE-HOME-PAGE is not of type SEQUENCE.* Note also that I tried to pass a list as an argument to :request-dispatcher but I got a very weird error as well *[2009-08-31 20:17:37 [ERROR]] The value (#<CLOSURE (LAMBDA #) {B229325}>) is not of type (OR FUNCTION SYMBOL). *I though that i should pass a list as a variable. Can you please tell me what I am doing wrong? Thanks in advance. Mackram Raydan Website: www.trailoflight.net "An invasion of armies can be resisted, but not an idea whose time has come." Victor Hugo

2 3

[hunchentoot-devel] question about the dispatcher
by Mackram Raydan 29 Aug '09

29 Aug '09

Hey everyone, so i was going through the hunchentoot documenation and I noticed that Edi said "Unless you are in a Lisp without MP capabilities, you can have several active instances of ACCEPTOR <http://weitz.de/hunchentoot/#acceptor>(listening on different ports) at the same time." Now this is great but I can not seem to understand how do you link a dispatcher to an acceptor (any kind of dispatcher) should the uri we put include a port or something. Can anyone point out this? Thanks in advance. Regards, Mackram Raydan Website: www.trailoflight.net "An invasion of armies can be resisted, but not an idea whose time has come." Victor Hugo

3 3

[hunchentoot-devel] form validation
by Eric Abrahamsen 28 Aug '09

28 Aug '09

define-easy-handler has some pretty extensive features for accepting GET/POST parameters, but when it comes to validating those parameters, and possibly returning errors to the client, it seems like the only viable thing to do is write a standard handler function and work with get-parameters* and post-parameters* directly. Does anyone have any experience to share in this direction? How is everyone handling more complex form validation and error reporting? Has there ever been any talk of a small external library for doing validation? Eric

3 3

[hunchentoot-devel] Problem with late calls to POST-PARAMETERS
by Peter Seibel 21 Aug '09

21 Aug '09

I ran into a problem converting some of my code to run with Hunchentoot 1.0. This patch fixes it and -- as far as I can tell after a bit of poking around -- is possibly righteous. What do you think? The basic problem that I ran into is explained in the comment in the patch. -Peter diff -r 635083ac9419 hunchentoot/request.lisp --- a/hunchentoot/request.lisp Sun May 31 11:31:25 2009 -0700 +++ b/hunchentoot/request.lisp Mon Jun 01 14:19:19 2009 -0700 @@ -346,7 +346,12 @@ (get-parameters request)) (defmethod post-parameters :before ((request request)) - (maybe-read-post-parameters :request request)) + ;; Force here because if someone calls POST-PARAMETERS they actually + ;; want them, regardless of why the RAW-POST-DATA has been filled + ;; in. (For instance, if SEND-HEADERS has been called, filling in + ;; RAW-POST-DATA, and then subsequent code calls POST-PARAMETERS, + ;; without the :FORCE flag POST-PARAMETERS would return NIL.) + (maybe-read-post-parameters :request request :force t)) (defun post-parameters* (&optional (request *request*)) "Returns an alist of the POST parameters associated with the REQUEST -- Peter Seibel http://www.codersatwork.com/ http://www.gigamonkeys.com/blog/

6 15

[hunchentoot-devel] Error in long running Hunchentoot process
by Patrick May 16 Aug '09

16 Aug '09

I have a site that uses Clozure and Hunchentoot. At the moment it's primarily serving static content. After being up for a few days, I got the following error message in the log file for the ccl process: Welcome to Clozure Common Lisp Version 1.3-r11936 (LinuxX8664)! ? > Error: #<STRING-OUTPUT-STREAM :CLOSED #x300041C1B52D> is closed > While executing: CCL::STREAM-IS-CLOSED, in process Hunchentoot listener (*:808 0)(3). ;;; ;;; #<PROCESS Hunchentoot listener (*:8080)(3) [Reset] #x300041B94CFD> requires access to Shared Terminal Input ;;; Type (:y 3) to yield control to this thread. ;;; ;Compiler warnings : ; In SAVE-PRESENTED-OBJECT: Undeclared free variable OBJECT (3 references) ; In SAVE-PRESENTED-OBJECT: Unused lexical variable #|symbol not found in home package!!|#SWANK::OBJECT The Hunchentoot message log file contains a number of lines like this: [2009-08-10 16:54:46 [ERROR]] Error while processing connection: Input timeout o n #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/9) #x300041BF867D> [2009-08-10 16:54:46 [ERROR]] Error while processing connection: Input timeout o n #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/8) #x300041BF730D> [2009-08-10 16:56:09 [ERROR]] Error while processing connection: Input timeout o n #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/11) #x300041BF5BBD> [2009-08-10 21:18:46 [ERROR]] Error while processing connection: Input timeout o n #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/8) #x300041BBE12D> [2009-08-10 22:38:23 [INFO]] Default handler called for script / robots.txt [2009-08-11 00:39:55 [INFO]] Default handler called for script / w00tw00t.at.ISC. SANS.DFind:) [2009-08-11 00:39:55 [ERROR]] Error while processing connection: on #<BASIC-TCP- STREAM ISO-8859-1 (SOCKET/8) #x300041C1D33D> : Connection reset by peer (error #104) during read [2009-08-11 02:08:49 [INFO]] Default handler called for script / favicon.ico [2009-08-11 02:09:09 [ERROR]] Error while processing connection: Input timeout o n #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/9) #x300041C1993D> [2009-08-11 02:09:09 [ERROR]] Error while processing connection: Input timeout o n #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/11) #x300041C181CD> [2009-08-11 02:09:09 [ERROR]] Error while processing connection: Input timeout o n #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/8) #x300041C1AC9D> [2009-08-11 02:17:19 [INFO]] Default handler called for script /fastenv [2009-08-11 02:17:20 [ERROR]] Error while processing connection: on #<BASIC-TCP- STREAM ISO-8859-1 (SOCKET/12) #x300041C16A7D> : Connection reset by peer (error #104) during read [2009-08-11 02:18:25 [ERROR]] Error while processing connection: Input timeout o n #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/8) #x300041C143ED> [2009-08-11 02:23:19 [ERROR]] Error while processing connection: Input timeout o n #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/9) #x300041C130AD> [2009-08-11 02:55:18 [ERROR]] Error while processing connection: Input timeout o n #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/8) #x300041C11D6D> [2009-08-11 03:24:51 [ERROR]] Error while processing connection: Input timeout o n #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/8) #x300041C0F6ED> [2009-08-11 03:35:35 [INFO]] Default handler called for script /fastenv [2009-08-11 03:35:36 [ERROR]] Error while processing connection: on #<BASIC-TCP- STREAM ISO-8859-1 (SOCKET/9) #x300041BC41CD> : Connection reset by peer (error #104) during read [2009-08-11 03:42:48 [ERROR]] Error while processing connection: Input timeout o n #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/8) #x300041C1E39D> [2009-08-11 03:42:48 [ERROR]] Error while processing connection: Input timeout o n #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/9) #x300041C1D03D> Do I have something misconfigured? Thanks, Patrick

2 1

[hunchentoot-devel] CLOS versus closures
by Jonathon McKitrick 12 Aug '09

12 Aug '09

quick question... Hunchentoot recently (?) moved to a more OO model, correct? I'm just curious... since lambda expressions, closures, macros, and other lisp constructs are often considered 'better' than CLOS (less verbose, less overhead), what made Edi decide to move to the more OO design? Surely it wasn't just popular demand. ;-) -- Jonathon McKitrick http://moltencopper.com

3 3