I've noticed that when an error occurs in my code, hunchentoot displays an 'internal server error' page. Obviously this is good for a production environment, but during development, how can I see any debug output produced from the lisp system, perhaps in slime? That would be easier than checking log files.
Jonathon McKitrick -- My other computer is your Windows box.
On Wed, 20 Dec 2006 20:41:02 +0000, Jonathon McKitrick jcm@FreeBSD-uk.eu.org wrote:
I've noticed that when an error occurs in my code, hunchentoot displays an 'internal server error' page. Obviously this is good for a production environment, but during development, how can I see any debug output produced from the lisp system, perhaps in slime? That would be easier than checking log files.
http://weitz.de/hunchentoot/#log
Read the whole section. At least...
I'm using Hunchentoot with ACL 8.0 Express. When a browser is open and displaying one of my app's URLs, the following error pops up every few minutes. Any ideas why would this be happening?
Dan
"Connection reset by peer" (errno 10054) occured while reading buffer for #<MULTIVALENT #1=stream socket #1#connected from #2=localhost/4242 to #2#/2227 @ #x20fe4d1a>. [Condition of type EXCL:SOCKET-ERROR]
Restarts: 0: [USE-VALUE] Specify a character to be used instead. 1: [ABORT] Abort entirely from this (lisp) process.
Backtrace: 0: (SWANK::DEBUG-IN-EMACS #<EXCL:SOCKET-ERROR @ #x21019ada>) 1: ((:INTERNAL SWANK:SWANK-DEBUGGER-HOOK 0)) 2: ((METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (T T)) #<Function SWANK-DEBUGGER-HOOK> #<Closure (:INTERNAL SWANK:SWANK-DEBUGGER-HOOK 0) @ #x21019b72>) 3: ((:INTERNAL SWANK::CALL-WITH-CONNECTION 0)) 4: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION @ #x2045cb1a> #<Closure (:INTERNAL SWANK::CALL-WITH-CONNECTION 0) @ #x21019ba2>) 5: (SWANK::MAYBE-CALL-WITH-IO-REDIRECTION #<SWANK::CONNECTION @ #x2045cb1a> #<Closure (:INTERNAL SWANK::CALL-WITH-CONNECTION 0) @ #x21019ba2>) 6: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION @ #x2045cb1a> #<Closure (:INTERNAL SWANK:SWANK-DEBUGGER-HOOK 0) @ #x21019b72>) 7: (SWANK:SWANK-DEBUGGER-HOOK #<EXCL:SOCKET-ERROR @ #x21019ada> #<Function SWANK-DEBUGGER-HOOK>) 8: (INVOKE-DEBUGGER #<EXCL:SOCKET-ERROR @ #x21019ada>) 9: (SIGNAL #<EXCL:SOCKET-ERROR @ #x21019ada>) 10: (ERROR EXCL:SOCKET-ERROR :IDENTIFIER :CONNECTION-RESET :STREAM #<MULTIVALENT #1=stream socket #1#connected from #2=localhost/4242 to #2#/2227 @ #x20fe4d1a> :CODE 10054 :ACTION "reading buffer for") 11: ((METHOD EXCL:STREAM-READ-BYTE (CHUNGA:CHUNKED-INPUT-STREAM))) 12: (FLEXI-STREAMS::READ-BYTE* #<FLEXI-STREAMS:FLEXI-IO-STREAM @ #x20fe9292>) 13: (FLEXI-STREAMS::READ-CHAR-8-BIT #<FLEXI-STREAMS:FLEXI-IO-STREAM @ #x20fe9292> #(0 1 2 3 4 5 6 7 8 9 ...)) 14: ((FLET (METHOD EXCL:STREAM-READ-CHAR (FLEXI-STREAMS:FLEXI-INPUT-STREAM)) FLEXI-STREAMS::GET-CHAR-CODE)) 15: ((METHOD EXCL:STREAM-READ-CHAR (FLEXI-STREAMS:FLEXI-INPUT-STREAM)) #<FLEXI-STREAMS:FLEXI-IO-STREAM @ #x20fe9292>) 16: ((METHOD EXCL:STREAM-PEEK-CHAR (EXCL:FUNDAMENTAL-CHARACTER-INPUT-STREAM)) #<FLEXI-STREAMS:FLEXI-IO-STREAM @ #x20fe9292>) 17: (CHUNGA:READ-LINE* #<FLEXI-STREAMS:FLEXI-IO-STREAM @ #x20fe9292>) 18: (HUNCHENTOOT::GET-REQUEST-DATA) 19: (HUNCHENTOOT::PROCESS-CONNECTION #<HUNCHENTOOT::SERVER @ #x20de1722> #<MULTIVALENT #1=stream socket #1#connected from #2=localhost/4242 to #2#/2227 @ #x20fe4d1a>)
On Fri, 22 Dec 2006 13:58:33 -0700, Daniel Gackle gackle@shaw.ca wrote:
I'm using Hunchentoot with ACL 8.0 Express. When a browser is open and displaying one of my app's URLs, the following error pops up every few minutes. Any ideas why would this be happening?
"Connection reset by peer" (errno 10054) occured while reading buffer for #<MULTIVALENT #1=stream socket #1#connected from #2=localhost/4242 to #2#/2227 @ #x20fe4d1a>. [Condition of type EXCL:SOCKET-ERROR]
I /think/ this is related to this thread:
http://common-lisp.net/pipermail/tbnl-devel/2006-December/000871.html
You've set *CATCH-ERRORS-P* to NIL, right?
Yeah, looks like I should change this behaviour...
Cheers, Edi.