Search
15:42:01
ebrasca
froggey: Do you have some trick for debuging problems when they don't give any error?
15:43:42
froggey
depends on what kind of problem it is. using trace or adding calls to format in suspect functions is usually a good place to start
15:44:23
ebrasca
I like to make hunchentoot run on mezzano
15:44:35
ebrasca
It load and starts with no error.
15:44:58
ebrasca
But when I try to load page it never load it and don't give me any error.
15:47:59
ebrasca
Yea after 1 hour mezzano panic because of hunchentoot.
15:48:18
froggey
starting from where it accepts connections and following that through until you find things go wrong might be a decent place to begin
15:48:22
froggey
oh? have you got a log?
15:49:20
ebrasca
I have it , do you know how much I waited for this error?
15:50:30
ebrasca
Today 1 hour , but others days it don't give any error.
15:51:06
ebrasca
Here panic error http://ix.io/27y8
15:55:29
froggey
that looks like a hunchentoot problem, not something I can directly help with
15:56:07
froggey
it's panicing because the error is occuring in a background thread and the debugger is trying to read from the cold stream
15:56:12
froggey
https://github.com/froggey/Mezzano/blob/master/ipl.lisp#L191
15:56:54
froggey
uncomment that line and the debugger should open up a gui window
16:19:18
ebrasca
Enabled it , and againg I get noting.
16:23:22
froggey
you should add logging to hunchentoot to see exactly where/why it's closing the connection
16:23:45
froggey
it doesn't really look like this error has much to do with it not working, it might be another problem entirely
16:35:23
ebrasca
Paniv error http://ix.io/27yg
16:36:18
ebrasca
ACTION is searching what Spinlock is.
16:42:12
froggey
thanks, I think I have an idea what happened there
17:42:12
ebrasca
Yea , I get my first useful error "The operation SET-TIMEOUTS is not implementet for the implementation Mezzano."
17:50:01
ebrasca
froggey: Thx , hunchentoot is responding. "Internal Server Error"