another backtrace, now with a little more detail.
seems like the remote side times out, or some firewall gets bored due
to a slow traffic and closes the connection. the problem only comes
after the print-object method of the socket starts saying
"unconnected" and we try to call close on the socket then.
then the attached backtrace comes and the lisp vm is dead after that.
it's also strange that write-sequence happily returns with success to
the unconnected socket.
hth,
--
attila
("nafi" "http worker 6 / serving request 81 / SERVE-FILE / SERVE-STREAM"
2008-12-05T14:46:06.157057+01:00 HU.DWIM.WUI::WUI +DRIBBLE+ "SERVE-STREAM will
write 6693 bytes to the network stream #<active IPv6 stream socket, unconnected
{100A735931}>")
("nafi" "http worker 6 / serving request 81 / SERVE-FILE / SERVE-STREAM"
2008-12-05T14:46:06.158481+01:00 HU.DWIM.WUI::WUI +DEBUG+ "SERVE-STREAM
finished copying input stream #<FD-STREAM for \"file
/opt/ebr42-nafi/workspace/wui/wwwroot/dojo/dojo/dojo.js\" {100A817A21}> to the
network stream #<active IPv6 stream socket, unconnected {100A735931}>")
("nafi" "http worker 6 / serving request 81" 2008-12-05T14:46:06.158740+01:00
HU.DWIM.WUI::WUI +DEBUG+ "Sending response #<DO-NOTHING-RESPONSE {100BA78601}>")
("nafi" "http worker 6 / serving request 81" 2008-12-05T14:46:06.159091+01:00
HU.DWIM.WUI::WUI +INFO+ "Handled request in 369.270 secs, 1523.961 MB allocated
(request came from @::ffff:79.120.193.114 for \"/static/dojo/dojo/dojo.js\")")
("nafi" "http worker 6 / serving request 81" 2008-12-05T14:46:06.159322+01:00
HU.DWIM.WUI::WUI +DRIBBLE+ "Worker #<WORKER {100A8B2671}> finished processing a
request")
("nafi" "http worker 6 / LEVEL-1-ERROR-HANDLER"
2008-12-05T14:46:06.167606+01:00 HU.DWIM.WUI::WUI +DEBUG+ "Calling custom error
handler from CALL-WITH-SERVER-ERROR-HANDLER for error: Unhandled memory fault
at #x0.")
("nafi" "http worker 6 / LEVEL-1-ERROR-HANDLER"
2008-12-05T14:46:06.168015+01:00 HU.DWIM.WUI::WUI +ERROR+ "Failed to close the
socket stream in SERVE-ONE-REQUEST while normally exiting. Backtrace
follows...")
("nafi" "http worker 6 / LEVEL-1-ERROR-HANDLER"
2008-12-05T14:46:06.200881+01:00 HU.DWIM.WUI::WUI +ERROR+ "
*** At: 2008-12-05T14:46:06.168122+01:00
*** In thread: http worker 6 / LEVEL-1-ERROR-HANDLER
*** Error:
Unhandled memory fault at #x0.
*** Backtrace is:
000: ((LAMBDA (ERROR)) #<SB-SYS:MEMORY-FAULT-ERROR {100BA9D6A1}>) [:EXTERNAL]
001: ((LABELS HU.DWIM.WUI::LEVEL-1-ERROR-HANDLER) #<SB-SYS:MEMORY-FAULT-ERROR
{100BA9D6A1}>)
002: (SIGNAL #<SB-SYS:MEMORY-FAULT-ERROR {100BA9D6A1}>) [:EXTERNAL]
003: (ERROR SB-SYS:MEMORY-FAULT-ERROR) [:EXTERNAL]
004: (SB-SYS:MEMORY-FAULT-ERROR)
005: (SB-SYS:MEMORY-FAULT-ERROR) [:EXTERNAL]
006: (\"foreign function: #x41E9B2\")
007: (\"foreign function: #x41EA70\")
008: (\"foreign function: #x7F5DCE817020\")
009: (\"foreign function: #x40F716\")
010: (\"foreign function: #x41179C\")
011: (\"foreign function: #x20100017\")
012: (\"foreign function: #x1009F65000\")
013: (SB-SYS:SAP-FOREIGN-SYMBOL 17505095719486)
")
("nafi" "http worker 0 / serving request 93 / LEVEL-1-ERROR-HANDLER /
LEVEL-2-ERROR-HANDLER / LEVEL-3-ERROR-HANDLER" 2008-12-05T14:46:16.818264+01:00
HU.DWIM.WUI::WUI +ERROR+ "Failed to log nested error message, probably due to
nested print errors. Condition type of the nested error is
SB-SYS:MEMORY-FAULT-ERROR.")
("nafi" "http worker 0 / serving request 93 / LEVEL-1-ERROR-HANDLER /
LEVEL-2-ERROR-HANDLER / LEVEL-3-ERROR-HANDLER" 2008-12-05T14:46:16.818499+01:00
HU.DWIM.WUI::WUI +INFO+ "Gracefully aborting request because: Unhandled memory
fault at #x0..")
("nafi" "http worker 0 / serving request 93" 2008-12-05T14:46:16.819327+01:00
HU.DWIM.WUI::WUI +DRIBBLE+ "ABORT-SERVER-REQUEST restart is being invoked")
("nafi" "http worker 0 / serving request 93" 2008-12-05T14:46:16.819566+01:00
HU.DWIM.WUI::WUI +DRIBBLE+ "Worker #<WORKER {100B62CDD1}> finished processing a
request")
("nafi" "http worker 0 / LEVEL-1-ERROR-HANDLER"
2008-12-05T14:46:16.827151+01:00 HU.DWIM.WUI::WUI +DEBUG+ "Calling custom error
handler from CALL-WITH-SERVER-ERROR-HANDLER for error: Unhandled memory fault
at #x0.")
_______________________________________________
iolib-devel mailing list
[email protected]
http://common-lisp.net/cgi-bin/mailman/listinfo/iolib-devel
