Activity report on *[JIRA] Bug SKER4916 - Same request, diffent request id*
Scarab Link: http://sesat.no/scarab/issues/id/SKER4916 Module: Sesat> Kernel Activity generated by Mick Semb Wever ([EMAIL PROTECTED]) at 06/30/2008 17:39 *Reasons for the changes* *Attribute changes* - "Status" changed from "Open" to "In Progress" ------------------------------------------------------------------------------- *Comments* - By Mick Semb Wever - 06/30/2008 17:39 --- "> Take a look at these log lines. Should they not have the same request/session id? No. The only lines of interest (any relation to other information found here) here are those belong to request GF3Q4AoLQWcAACbExdEAAAHn. >-bash-3.2$ grep pulpit sesam.access This identicates the problem. And highlights two separate requests I2RvRgoLQWcAACk2GlsAAAA7 & I3gYEQoLQWcAACk2GmQAAAA9 being the same except the first is restricted to norwegian news (newscountry=Norge). > Grepping for the request id in sesam.access returns Is definitely the wrong request id." - By Mick Semb Wever - 06/30/2008 17:40 --- "> Take a look at these log lines. Should they not have the same request/session id? No. The only lines of interest (any relation to other information found here) here are those belong to request GF3Q4AoLQWcAACbExdEAAAHn. >-bash-3.2$ grep pulpit sesam.access This identicates the problem. And highlights two separate requests I2RvRgoLQWcAACk2GlsAAAA7 & I3gYEQoLQWcAACk2GmQAAAA9 being the same except the first is restricted to norwegian news (newscountry=Norge). > Grepping for the request id in sesam.access returns Is definitely the wrong request id."
_______________________________________________ Kernel-issues mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-issues
