September 2009 - tbnl-devel@common-lisp.net

[hunchentoot-devel] maybe bug + patch
by Richard KLINDA 06 Jun '10

06 Jun '10

Hello, I may have found a bug. After stopping an acceptor with STOP, one can't start it again with START, because the START method doesn't reset the value of acceptor-shutdown-p to NIL, so the listener returns/quits instantly. See the attached trivial patch, that fixes the issue for me, but maybe I'm just missing something here. -- Richard

3 2

[hunchentoot-devel] Backtrace display
by Jonathon McKitrick 27 Dec '09

27 Dec '09

I recall some time ago, the break and backtrace capability of Hunchentoot was removed, perhaps to make it less platform dependent. But I still find myself often trying to find the origin of cryptic error messages, and adding FORMAT and BREAK statements to narrow down the problem area. What is a good way to drop in support for, say, SBCL, so that an error will break into the debugger with a backtrace, or even dump the backtrace to the log file? -- Jonathon McKitrick

7 9

[hunchentoot-devel] Small patch for LispWorks 6 beta
by Nico de Jager 14 Oct '09

14 Oct '09

$ diff -u lispworks.lisp_orig lispworks.lisp_patched --- lispworks.lisp_orig 2009-09-30 11:42:22.000000000 +0200 +++ lispworks.lisp_patched 2009-09-30 19:06:22.118317238 +0200 @@ -90,14 +90,14 @@ (defun make-socket-stream (socket acceptor) "Returns a stream for the socket SOCKET. The ACCEPTOR argument is used to set the timeouts." - #-:lispworks5 + #+:lispworks4 (when (acceptor-write-timeout acceptor) (parameter-error "You need LispWorks 5 or higher for write timeouts.")) (make-instance 'comm:socket-stream :socket socket :direction :io :read-timeout (acceptor-read-timeout acceptor) - #+:lispworks5 #+:lispworks5 + #-:lispworks4 :write-timeout (acceptor-write-timeout acceptor) :element-type 'octet))

3 6

[hunchentoot-devel] Constructing development and production environments
by Sebastian Tennant 24 Sep '09

24 Sep '09

Hi all, I'd like to instantiate two acceptors that use the standard log functions (LOG-MESSAGE-TO-FILE & LOG-ACCESS-TO-FILE) but with different values of *access-log-pathname* and *message-log-pathname* for each acceptor. One way is to define two (cloned) log functions with hardcoded pathnames and pass these log functions to MAKE-INSTANCE when instantiating each acceptor, but I'm wondering if there isn't a better (more Lispy) way to do it? I'd also welcome any advice/tips/pointers/suggestions people may have regarding how best to construct development and production environments within a single Hunchentoot process. Unfortunately my server is very low-powered and I don't have the resources to run two Hunchentoot processes. Regards, Sebastian -- Emacs' AlsaPlayer - Music Without Jolts Lightweight, full-featured and mindful of your idyllic happiness. http://home.gna.org/eap

1 0

[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