[Cosmo-dev] Hub 500 errors
Morgen Sagen
morgen at osafoundation.org
Wed Sep 19 14:28:10 PDT 2007
While we're on the subject of server logs, I've been using the traffic
capture logs that Jared produces for debugging, and they've been
incredibly useful but they're difficult to navigate sometimes. For
instance, UUIDs can get split across two lines (with timesamps
inserted in between) making grep impossible. I'm wondering if Cosmo
could generate something a bit friendlier, with requests/responses
grouped together, and a more compact representation than XML. For
example, chandler.log has a shorthand for EIM activity:
<< ++ ItemRecord(<uuid>, 'foo', 'bar', ...) means inbound
change/addition of record
<< -- ModifiedByRecord(<uuid> ...) means inbound deletion of record
>> ++ EventRecord(<uuid>, ...) means outbound change/addition of record
>> !! <uuid> means outbound recordset deletion
~morgen
On 9/19/07, Brian Moseley <bcm at osafoundation.org> wrote:
> On 9/19/07, Jared Rhine <jared at wordzoo.com> wrote:
>
> > For next steps on the whole issue, I'm thinking that figuring out what,
> > if anything, we do to /pim and /mc to enable similar broad 5xx reporting
> > would be a good outcome.
>
> definitely.
>
> > A specific example:
> >
> > 82.135.15.150 - - [18/Sep/2007:13:16:32 -0700] "PROPFIND / HTTP/1.1" 501
> > 1238 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6)
> > Gecko/20070728 Thunderbird/2.0.0.6"
>
> oh, 501 is natural. that's what tomcat's default servlet sends when it
> gets a method it doesn't like. really ought to be 405, but whatever.
> i'm only concerned about 501s coming from our stuff and about 500s.
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>
More information about the cosmo-dev
mailing list