Iain,
The store is not used for DLR's, just for messages. Thats why you
don't see them in the store-status. I use PostgreSQL to store my
DLRs, then I can look them up easily to see what's outstanding.
Your error looks like the web-server that you are sending the DLRs to
is not responding correctly (it looks like its just closing the
connection instead of talking HTTP). Possibly a firewall issue?
Regards
Ben
On 2 Apr 2007, at 05:15, Iain Dooley wrote:
hi, i'm seeing this error quite a bit:
2007-04-02 11:58:12 [26174] [4] INFO: Starting delivery report
<USER> from <+NUMBER>
2007-04-02 11:58:12 [26174] [9] ERROR: Error reading from fd 28:
2007-04-02 11:58:12 [26174] [9] ERROR: System error 54: Connection
reset by peer
what can that mean? also if i do:
lynx -dump "http://localhost:PORT/store-status.txt?password=PASS";
i get an empty queue, but if i do:
lynx -dump "http://localhost:PORT/status.txt?password=PASS";
it says that there are 194 queued DLR's, shouldn't they be showing
up in the store-status report? i'm using internal dlr storage.
cheers
iain
