Ralf and Kevin,
In all versions of the server, the "p4 info" command does not log a starting
entry but does log a "completed" entry.
In all versions of the server on platforms that fork a p4d child process to
execute the command, if a p4d child process is killed from the OS (which in
general is not a good thing), there may not be a "completed" entry for the
command, depending upon how the process was killed and perhaps the
platform on which the server is running.
A bug in the server logging was corrected by change 68580 in 2003.2. From
the release notes:
Bugs fixed since 2003.2/51929 (first release).
#68580 **
On some platforms (windows, HP) during high concurrency the
server errorlog could contain truncated or incomplete output.
This has been fixed (Bug #15356).
I believe that we have seen this on other platforms as well; the 68580
change should correct this issue on all platforms.
Regards,
Michael
--
Michael Shields
Perforce Software Technical Support
support@xxxxxxxxxxxx
510-864-7400
> Hi Kevin,
>
> I also found some entries in the log file that are inconsistent at
> my development phase of p4gla.
> The older versions of the server had some "bugs" in the logfile.
> They improved it from rev to rev. So I guess you should contact
> support for your logfile.
> Michael advised me to throw these inconsistences away (he did the same
> in p4loga). For more details you should look at his source.
>
> The latest revision of the server should not have the completes without
> starts...
> but we'll see ;-)
>
> Please let me know what the support tells you.
>
> Regards,
> Ralf
>
> > -----Urspr�ngliche Nachricht-----
> > Von: Kevin Wang [mailto:rightsock@xxxxxxxxx]
> > Gesendet: Mittwoch, 5. Januar 2005 21:48
> > An: Martin, Ralf
> > Cc: Jean-Sebastien Pelletier; perforce-user@xxxxxxxxxxxx
> > Betreff: Re: AW: [p4] p4d log parser
> >
> >
> > > > On Mon, 3 Jan 2005 16:14:34 +0100, Martin, Ralf
> > > > <RMartin@xxxxxxxxxxxxxxxx> wrote:
> > > > > I am the guy who wrote p4gla.
> >
> > ok, one last question, and I should be done. I'm already
> > getting interesting statistics out of the log file. thanks
> > again for everyone's help!
> >
> > I'm seeing a rather high number of "compute end" and
> > "completed" but I never see a 'start' line. Is this normal?
> >
> > In my test sample of 20,000 lines of log:
> > -> 9988 lines of "Perforce server info"
> > -> 10012 lines after removing the "Perforce server info" lines
> > --> 24 lines of 5 errors: "Perforce server error:...TCP receive
> > failed|Partner exited unexpectedly" ( no big deal )
> > --> 381 lines of unmatched "compute end|completed"
> > --> 4140 matched start lines -> 4140 transactions (where transaction =
> > a matched set of start, compute end (0 or more), completed)
> > --> 1320 matched 'compute end' lines -> 4140 transactions... 4140
> > --> matched 'completed' lines -> 4140 transactions... 7
> > unmatched starts
> >
> > of the 7 unmatched starts, they all had matching ends further
> > down in the log file.
> >
> > Is it possible that these "missing" starts come from triggers
> > or something? Is there anything I can do except ignore them?
> > Approximately 4% of the events in the log file are unmatched.
> >
> > Here's a snippet of my log file. clearly it says pid 27150
> > completed in 0 clock seconds, yet nothing in the prior 2
> > seconds shows a start with that pid. and the pid is
> > consistent with being recently started, too.
> >
> > - Kevin
> >
> > 2004/12/21 00:03:18 pid 27140 juser@juser 10.2.2.231
> > 'user-describe -s 852411'
> > 2004/12/21 00:03:19 pid 27140 completed 0s 0+0us
> > 0+0io 0+0net 0k 35pf
> > 2004/12/21 00:03:19 pid 27141
> > unittest@unittest_zzd10-3 172.25.1.10 'user-filelog -i
> > //depot/src3/updater/policy_unittest.cc#1'
> > 2004/12/21 00:03:19 pid 27141 completed 0s 10+0us
> > 0+0io 0+0net 0k 27pf
> > 2004/12/21 00:03:19 pid 27142 juser@juser 10.2.2.231
> > 'user-counter p4stats 852411'
> > 2004/12/21 00:03:19 pid 27142 completed 0s 0+0us
> > 0+0io 0+0net 0k 10pf
> > 2004/12/21 00:03:20 pid 27145 juser@juser 10.2.2.231
> > 'user-describe -s 852412'
> > 2004/12/21 00:03:20 pid 27145 completed 0s 10+0us
> > 0+0io 0+0net 0k 35pf
> > 2004/12/21 00:03:20 pid 27082 completed 10s 3910+380us 0+0io
> > 0+0net 0k 8984pf
> > 2004/12/21 00:03:20 pid 27146
> > unittest@unittest_zzd40-3 172.25.1.40 'user-files
> > //depot/src3/.../BUILD@849980'
> > 2004/12/21 00:03:20 pid 27149
> > unittest@unittest_src3_asfe 10.32.4.226 'user-changes -m 1 -s
> > submitted ...'
> > 2004/12/21 00:03:21 pid 27149 completed 0s 60+0us
> > 0+0io 0+0net 0k 25pf mapstate(0)
> > 2004/12/21 00:03:21 pid 27150 completed 0s 0+0us
> > 0+0io 0+0net 0k 33pf
> > 2004/12/21 00:03:21 pid 27151 juser@juser 10.2.2.231
> > 'user-counter p4stats 852412'
> > 2004/12/21 00:03:21 pid 27151 completed 0s 10+0us
> > 0+0io 0+0net 0k 10pf
> > 2004/12/21 00:03:21 pid 27152
> > unittest@unittest_zzd23-0 172.25.1.23 'user-client -o'
> > 2004/12/21 00:03:21 pid 27152 completed 0s 0+0us
> > 0+0io 0+0net 0k 14pf
> > 2004/12/21 00:03:21 pid 27153 juser@juser 10.2.2.231
> > 'user-describe -s 852413'
> > 2004/12/21 00:03:21 pid 27154
> > unittest@unittest_zzd7-1 172.25.1.7 'user-client -o'
> > 2004/12/21 00:03:21 pid 27154 completed 0s 0+10us
> > 0+0io 0+0net 0k 14pf
> > 2004/12/21 00:03:21 pid 27157
> > unittest@unittest_zzd7-1 172.25.1.7 'user-files //depot/src3/*'
> > 2004/12/21 00:03:21 pid 27153 completed 0s 10+0us
> > 0+0io 0+0net 0k 35pf
> > 2004/12/21 00:03:21 pid 27157 completed 0s 0+20us
> > 0+0io 0+0net 0k 20pf
> >
>
>
> *******************************************
> Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und
loeschen Sie diese Mail. Das unerla
ubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please notify
the sender immediately and delete this e-mail. Any unauthorized copying,
disclosure or dis
tribution of the contents in this e-mail is strictly forbidden.
> *******************************************
>
>
> _______________________________________________
> perforce-user mailing list - perforce-user@xxxxxxxxxxxx
> http://maillist.perforce.com/mailman/listinfo/perforce-user
_______________________________________________
perforce-user mailing list - perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user
|
