Hi Carey,
You are right.
The USER: xxx indicates the "performing user".
The FLUSH/EXPIRE is not performed by the user being released. It is some
other users that is doing something, and during/after the Demo-users
transaction, the server checks for pending FLUSH/EXPIRE-operations.
So the performing user is Demo, but the affected users is the one further
to the right in the log row.
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at http://rrr.se.
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at http://rrr.se.
> Matt,
>
> The way I read the file...What I see are the following:
>
> READ FLUSH yyyyyy
> FLOAT EXPIRED WRITE xxxxxxx (28 used of 40 write)
> FLOAT EXPIRED WRITE zzzzzz (27 used of 40 write)
> FIXED FLUSH zyzyzyzyz
> FLOAT EXPIRED WRITE aSDseasdfwesd (26 used of 40 write)
>
> I think the User log line includes a "User" part ( in your example
> Example: "<USER: Demo > ") that should be the
> user of the transaction. But on my v6.3 Server for any line that is an
> EXPIRED line the User at the end of the line does not match the
> "<USER:" part of the line header. In fact in my log file the "USER"
> part is not all "special"(Admin) users. However I do see some "Remedy
> Application Service" and other "system" type accounts.)
>
> My guess it that the value of $USER$ is set to the last account that
> used that thread and is used when the server does the FLUSH/EXPIRE
> process as if that account was the one who did the action. However I
> am guessing that the server itself is the "account" that is actually
> triggering the FLUSH/EXPIRE.
>
> In very short... think the system is poorly identifying the account in
> the header of the log file line and that it is something that can be
> safely ignored.
>
> If however your are seeing the Demo account's license being released
> like a line like this....
> "
> <USER> <TID: 2868759472> <RPC ID: 0000611296> <Queue: Fast >
> <Client-RPC: 390620 > <USER: [anything here] > /* Wed
> Oct 24 2007 15:03:47.0000 */ FIXED FLUSH Demo
> "
> Then I would be tracking down who is using that account. :)
>
> HTH.
>
> --
> Carey Matthew Black
> Remedy Skilled Professional (RSP)
> ARS = Action Request System(Remedy)
>
> Love, then teach
> Solution = People + Process + Tools
> Fast, Accurate, Cheap.... Pick two.
>
>
> On Dec 8, 2007 3:37 PM, Matthew Wollman <[EMAIL PROTECTED]> wrote:
>> **
>> Hello listers,
>>
>> I have a user log file log file that has Demo listed as logging in,
>> when it
>> shoudn't be. however, it shows another user name at the end of the
>> entry.
>> the optimizing and troubleshooting guide wasn't very clear on this. here
>> is
>> a sample:
>
> <snip>
>
>> Any assistance explaining to me what Demo is doing here would be great.
>> Also is Demo in use by any OOTB processes?
>>
>> We are using, ARS 6.3 with HelpDesk 6.0 on RH AS3 and Oracle 10g.
>>
>> Thank You.
>> --
>> Matthew L. Wollman
>>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
