I've commited to cvs a fix to NACK/04 bug in emi2.
besides, I've changed the pdf creation. Please see if
everything is ok with you (it should)
instead of xml->tex->ps->pdf, it will do xml->tex->pdf
directly
I've added extra debug to http.c to print the fd being
used, and reactivated KEEPALIVE. This way I'll try to
find the bug I've mentioned before:
one MO SMS gets stuck in smsbox until several hours
later.
A debug of the problem, still without KEEPALIVE:
This is a good MO - see the Opening connection
2002-06-08 18:52:34 [6] INFO:
Starting to service <Y2: L> from <...> to <...>
2002-06-08 18:52:34 [5] DEBUG:
HTTP: Opening connection to `127.0.0.1:80'.
2002-06-08 18:52:34 [5] DEBUG:
HTTP: Sending request:
This is the bad MO I sent before (no Opening conn),
never got to apache:
2002-06-08 18:51:56 [6] INFO:
Starting to service <Y2: L> from <...> to <...>
2002-06-08 18:51:56 [5] DEBUG: HTTP: Sending request:
Several hours later, that MO got out of smsbox
Although kannel have sent and receive many more messages,
from my number and from others, to this server and
to others, only then the message got out.
I'm sure this is the same message that
got stuck back there, because of the content:
2002-06-09 14:00:37 [4] ERROR:
Error reading from fd 20:
2002-06-09 14:00:37 [4] ERROR:
System error 104: Connection reset by peer
2002-06-09 14:00:37 [5] DEBUG:
HTTP: Opening NEW connection to `127.0.0.1:80'.
2002-06-09 14:00:37 [5] DEBUG:
HTTP: Sending request:
Any thought about this?
BTW: with keepalive=0, shouldn't we send a
Connection: close when HTTP/1.1 from smsbox->httpserver ?
