[Citadel Development] Re: Citadel commit log: revision 8597

2010-06-01 Thread IGnatius T Foobar
Ok, now we're getting somewhere. 4 alerts in the last 8 hours. It isn't locking up; it's getting the message Received unexpected answer from Citadel server; bailing out.

[Citadel Development] Re: Citadel commit log: revision 8597

2010-06-01 Thread dothebart
that seems to be if get_serv_info() fails? it does... serv_printf("IDEN %d|%d|%d|%s|%s", DEVELOPER_ID, CLIENT_ID, CLIENT_VERSION, ChrPtr(user_agent), ChrPtr(browser_host) ); StrBuf_ServGetln(Buf); serv_puts("ICAL sgi|1"); StrBuf_ServGetln(Buf); serv_puts("INFO"); StrBuf_ServGetln(Buf); if

[Citadel Development] Re: Citadel commit log: revision 8597

2010-06-01 Thread IGnatius T Foobar
maybe you'd like to add a debug statement here?? Yes, that's obviously the right thing to do; I haven't been writing webcit logs but it's probably time to start. :)

[Citadel Development] Re: Citadel commit log: revision 8597

2010-06-01 Thread IGnatius T Foobar
Ok, here's the answer: The INFO command returned a *blank line*.

[Citadel Development] Citadel commit log: revision 8599

2010-06-01 Thread dothebart
r8599 | dothebart | 2010-06-01 16:57:18 -0400 (Tue, 01 Jun 2010) | 2 lines Changed paths: M /trunk/webcit/serv_func.c * get_serv_info(): evaluate server replies

[Citadel Development] Re: Citadel commit log: revision 8599

2010-06-01 Thread IGnatius T Foobar
I'm working on this too. It isn't actually that specific server command. WebCit's ability to receive server replies appears to be broken by the time get_serv_info() starts. When I began checking the output of the IDEN command, it failed there too. I just added some code to check the

[Citadel Development] Re: Citadel commit log: revision 8597

2010-06-01 Thread dothebart
Di Jun 01 2010 11:32:17 EDT von IGnatius T Foobar @ Uncensored Betreff: Re: Citadel commit log: revision 8597 Ok, here's the answer: The INFO command returned a *blank line*. hm, theres not much way out in cmd_info; it might be cmd_iden barfed? maybe we'll find out.

[Citadel Development] Re: Citadel commit log: revision 8599

2010-06-01 Thread dothebart
ah, yea that might be a good thing to do. Maybe 200 isn't the appropriate HTTP status for that situation either?

[Citadel Development] Re: Citadel commit log: revision 8599

2010-06-01 Thread IGnatius T Foobar
Very weird. We had another unexpected response error with those checks in place. The server passed the 200 banner check, but then by the time we got into get_serv_info(), the server responses became blank. The next time it happens I will try to analyze it from the citserver side to see if

[Citadel Development] Citadel commit log: revision 8600

2010-06-01 Thread dothebart
r8600 | dothebart | 2010-06-01 18:27:02 -0400 (Tue, 01 Jun 2010) | 4 lines Changed paths: M /trunk/libcitadel/lib/libcitadel.h M /trunk/libcitadel/lib/stringbuf.c M /trunk/libcitadel/lib/tools.c A

[Citadel Development] Citadel commit log: revision 8601

2010-06-01 Thread dothebart
r8601 | dothebart | 2010-06-01 18:35:53 -0400 (Tue, 01 Jun 2010) | 2 lines Changed paths: M /trunk/webcit/messages.c * post_message(): QP encode TO/CC/BCC if necessary

[Citadel Development] Citadel commit log: revision 8600

2010-06-01 Thread dothebart
  Di Jun 01 2010 18:27:03 EDT von "dothebart" dotheb...@uncensored.citadel.org Betreff: Citadel commit log: revision 8600 r8600 | dothebart | 2010-06-01 18:27:02 -0400 (Tue, 01 Jun 2010) | 4 lines Changed paths: A