Stelian, please take a look at the backtrace below... does it ring any bells?
it probably happens when a connection times out, or in some unusual situation. please not the "unconnected" part in the socket's print-object output...
("nafi" "http worker 5 / LEVEL-1-ERROR-HANDLER" 2008-12-05T00:34:27.217601+01:00 HU.DWIM.WUI::WUI +ERROR+ " *** At: 2008-12-05T00:34:27.203581+01:00 *** In thread: http worker 5 / LEVEL-1-ERROR-HANDLER *** Error: Unhandled memory fault at #x0. *** Backtrace is: 000: ((LAMBDA (ERROR)) #<SB-SYS:MEMORY-FAULT-ERROR {100B380821}>) [:EXTERNAL] 001: ((LABELS HU.DWIM.WUI::LEVEL-1-ERROR-HANDLER) #<SB-SYS:MEMORY-FAULT-ERROR {100B380821}>) 002: (SIGNAL #<SB-SYS:MEMORY-FAULT-ERROR {100B380821}>) [: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: ((CLOSE :AROUND (IO.STREAMS:DUAL-CHANNEL-GRAY-STREAM)) #<active IPv6 stream socket, unconnected {100B04A221}>) [:EXTERNAL] 009: ((CLOSE :AROUND (IO.STREAMS:DUAL-CHANNEL-SINGLE-FD-MIXIN)) #<active IPv6 stream socket, unconnected {100B04A221}>) [:EXTERNAL] 010: ((CLOSE :AROUND (NET.SOCKETS:SOCKET)) #<active IPv6 stream socket, unconnected {100B04A221}>) [:EXTERNAL] 011: (HU.DWIM.WUI::CALL-WITH-SERVER-ERROR-HANDLER #<CLOSURE (LAMBDA #) {100B37FAA9}> #<active IPv6 stream socket, unconnected {100B04A221}> #<CLOSURE (LAMBDA #) {100B37FAC9}>) 012: ((FLET #:CLEANUP-FUN-[WORKER-LOOP/SERVE-ONE-REQUEST]634)) [:CLEANUP]
Stelian, please take a look at the backtrace below... does it ring any bells?
it probably happens when a connection times out, or in some unusual situation. please not the "unconnected" part in the socket's print-object output...
some more info: after this, or something that causes this, or... slime-connect hangs while half-way connected.
-- attila
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,
The assertion (NOT (IO.STREAMS::IOBUF-FULL-P IO.STREAMS::IOBUF)) failed.
003: (IO.STREAMS::IOBUF-PUSH-OCTET #S(IO.STREAMS::IOBUF :DATA #.(SB-SYS:INT-SAP #X00648A70) :SIZE 4096 :START 2432 :END 4096) 32) 004: (WRITE-BYTE 32 #<active IPv6 stream socket, unconnected {100B31DF71}>) 005: (HU.DWIM.WUI::SEND-HTTP-HEADERS #<unavailable lambda list>) [:EXTERNAL] 006: ((HU.DWIM.WUI:HANDLE-TOPLEVEL-CONDITION (T SERIOUS-CONDITION)) #<unavailable argument> #<NET.SOCKETS:SOCKET-CONNECTION-RESET-ERROR 104 :ECONNRESET " Connection reset by peer", FD: 6>) 007: ((LAMBDA (SB-PCL::.PV. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.ARG1.)) #<unavailable argument> #<unavailable argument> #<EBR42-PRESENTATION::EBR42-APPLICATION "/" {1000095139}> #<NET.SOCKETS:SOCKET-CONNECTION-RESET-ERROR 104 :ECONNRESET "Connection reset by peer", FD: 6>) 008: ((HU.DWIM.WUI:HANDLE-TOPLEVEL-CONDITION :AROUND (T T)) #<EBR42-PRESENTATION::EBR42-APPLICATION "/" {1000095139}> #<NET.SOCKETS:SOCKET-CONNECTION-RESET-ERROR 104 :ECONNRESET "Connection reset by peer", FD: 6>) 009: ((FLET HU.DWIM.WUI::HANDLE-REQUEST-ERROR) #<NET.SOCKETS:SOCKET-CONNECTION-RESET-ERROR 104 :ECONNRESET "Connection reset by peer", FD: 6>) 010: ((LABELS HU.DWIM.WUI::LEVEL-1-ERROR-HANDLER) #<NET.SOCKETS:SOCKET-CONNECTION-RESET-ERROR 104 :ECONNRESET "Connection reset by peer", FD: 6>) 011: (SIGNAL #<NET.SOCKETS:SOCKET-CONNECTION-RESET-ERROR 104 :ECONNRESET "Connection reset by peer", FD: 6>) [:EXTERNAL] 012: (ERROR NET.SOCKETS:SOCKET-CONNECTION-RESET-ERROR) [:EXTERNAL] 013: (NET.SOCKETS::%SOCKET-ERROR :ECONNRESET 104 6) 014: (NET.SOCKETS::SIGNAL-SOCKET-ERROR #<unused argument> 6) 015: (NET.SOCKETS::SIGNAL-SOCKET-ERROR #<unavailable argument> 6) [:EXTERNAL] 016: (IO.STREAMS::%FLUSH-OBUF NET.SOCKETS::SOCKET-WRITE-FN 6 #S(IO.STREAMS::IOBUF :DATA #.(SB-SYS:INT-SAP #X00648A70) :SIZE 4096 :START 2432 :END 4096) NIL) 017: (IO.STREAMS::%FLUSH-OBUF-IF-NEEDED #<active IPv6 stream socket, unconnected {100B31DF71}>) 018: ((SB-GRAY:STREAM-WRITE-BYTE (IO.STREAMS:DUAL-CHANNEL-GRAY-STREAM T)) #<active IPv6 stream socket, unconnected {100B31DF71}> #<unavailable argument>) 019: (IO.STREAMS::%WRITE-VECTOR #<active IPv6 stream socket, unconnected {100B31DF71}> #(47 42 10 9 67 111 112 121 114 105 103 104 ...) 0 8192) 020: (WRITE-SEQUENCE #(47 42 10 9 67 111 112 121 114 105 103 104 ...) #<active IPv6 stream socket, unconnected {100B31DF71}>) [:EXTERNAL] 021: (HU.DWIM.WUI::SERVE-STREAM #<SB-SYS:FD-STREAM for "file /opt/ebr42-nafi/workspace/wui/wwwroot/dojo/dojo/dojo.js" {100B339A21}>) [:EXTERNAL] 022: (HU.DWIM.WUI::SERVE-FILE #P"/opt/ebr42-nafi/workspace/wui/wwwroot/dojo/dojo/dojo.js") [:EXTERNAL] 023: ((HU.DWIM.WUI::SEND-RESPONSE :AROUND (HU.DWIM.WUI:RESPONSE)) #<HU.DWIM.WUI::FILE-SERVING-RESPONSE {100B32DDF1}>)