| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66143
|
Sun Jan 11 22:48:38 2009 |
 | kyoo | josh@newgistics.com | Bug report | Windows | 2.7.5-2130 | Re: Google Chrome issues | > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
>
> I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> Is is possible the corporate elog server is running behind apache or in some
> other proxy config while the one you are having issues with is being connected
> to directly by chrome?
>
> -- rouilj
So, is your kubuntu elog server internal only, as well? My elog server on windows is an internal only server..
and there is no proxy or firewall between chrome and the elog server.. I didn't set it up, but I think elogd runs
it's own web service.. probably apache within the win32 port.
It's good to know someone else has the issue, at least. I'd like to find a publicly available elog server so
that the elog developers could recreate the issue and thusly fix the issue. Or at the very least send the broken
URL to Google Chrome developers to see if it's a bug in the browser or not.
I ran wireshark to capture what happens at the ethernet level, and it seems that the HTTP response doesn't come
through properly. My response packets to the TCP response packets seems to be:
"Acknowledgment number: Broken TCP. The acknowledge field is nonzero while the ACK flag is not set"
My system never receives enough TCP packets to reassemble it to a properly formatted HTTP response.
The stream goes like this:
GET /Company+IT+Change+Log/ HTTP/1.1
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/525.19 (KHTML, like Gecko)
Chrome/1.0.154.42 Safari/525.19
Referer: http://changelog.Company.com/Company+IT+Change+Log/?cmd=New
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,bzip2,sdch
Cookie: unm=Name; upwd=amhpbGoijoihbmQ=; urem=1
Accept-Language: en-US,en
Accept-Charset: ISO-8859-1,*,utf-8
Host: changelog.Company.com
Connection: Keep-Alive
HTTP/1.1 200 Document follows
Server: ELOG HTTP 2.7.5-2130
Content-Type: text/html;charset=ISO-8859-1
Set-Cookie: elmode=Summary; path=/Company+IT+Change+Log; expires=Tuesday, 09-Jun-20 12:31:45 GMT;
path=/Company+IT+Change+Log;
Connection: Keep-Alive
Keep-Alive: timeout=60, max=10
Pragma: no-cache
Expires: Fri, 01 Jan 1983 00:00:00 GMT
Content-Length: 24455
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<title>ELOG Company IT Change Log</title>
<link rel="stylesheet" type="text/css" href="default.css">
<link rel="shortcut icon" href="favicon.ico" />
<link rel="icon" href="favicon.png" type="image/png" />
<link rel="alternate" type="application/rss+xml" title="ELOG Company IT Change Log" href="elog.rdf" />
</head>
<body>
<form name="form1" method="GET" action=".">
<table class="frame" cellpadding="0" cellspacing="0"><!-- show_standard_title -->
<tr><td class="tabs">
<span class="sltab"><a href="../Company+IT+Change+Log/" title="Company
TI">Company IT Change Log</a></span>
</td></tr>
<tr><td><table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr><td class="title1"> Company TI, Page 1 of 272 </td>
<td class="title2">Logged in as "My Name"</td>
<td class="title3"><img border=0 src="elog.png" alt="ELOG logo" title="ELOG logo"></td>
</tr></table></td></tr>
<tr><td class="menuframe"><span class="menu1">
<a href="?cmd=New">New</a> |
<a href="?cmd=Find">Find</a> |
<a href="?select=1">Select</a> |
<a href="?cmd=Import">Import</a> |
<a href="?cmd=Config">Config</a> |
<a href="?cmd=Logout">Logout</a> |
<a href="?cmd=Help">Help</a>
</span></td></tr>
<tr><td class="menuframe">
<table width="100%" border=0 cellpadding="0" cellspacing="0">
<tr>
<td class="menu2a">
<a href="?mode=full">Full</a> | Summary | <a href="?
mode=threaded">Threaded</a> </td>
<td class="menu2b">
<a href="?new_entries=1"><img align="middle" border="0" src="new_entry.png" alt="Show only new entries"
title="Show only new entries"></a> <select title="Select period" name=last
onChange="document.form1.submit()">
<option value="_all_">-- All entries --
<option value=1>Last day
<option value=7>Last week
<option value=31>Last month
<option value=92>Last 3 Months
<option value=182>Last 6 Months
<option value=364>Last Year
</select>
<select title="Select Type" name="Type" onChange="document.form1.submit()">
<option value="_all_">-- Type --
<option value="^Hardware$">Hardware
<option value="^Software$">Software
<option value="^Database$">Database
<option value="^Network$">Network
<option value="^NGS Applications$">NGS Applications
<option value="^Storage$">Storage
<option value="^Monitor$">Monitor
<option value="^VMware$">VMware
</select>
<noscript>
<input type=submit value="Search">
</noscript>
<b>5429 Entries</b> </td></tr></table></td></tr>
<tr><td class="menuframe"><span class="menu3">
Goto page
1,
<a href="page2">2</a>,
<a href="page3">3</a> ... <a href="page270">270</a>,
<a href="page271">271</a>,
<a href="page272">272</a>
<a href="page2">Next</a> </span></td></tr>
<tr><td><table class="listframe" width="100%" cellspacing=0>
<tr>
<th class="listtitle"><a href="?sort=ID">ID</a></th>
<th class="listtitle"><a href="?sort=Date">Date</a></th>
<th class="listtitle"><a href="?sort=Author">Author</a></th>
<th class="listtitle"><a href="?sort=Author+Email">Author Email</a></th>
<th class="listtitle"><a href="?sort=Type">Type</a></th>
<th class="listtitle"><a href="?sort=Category">Category</a></th>
<th class="listtitle"><a href="?sort=Subject">Subject</a></th>
<th class="listtitle"><a href="?sort=Last+Revision">Last Revision</a></th>
<th class="listtitle"><a href="?sort=Reason+for+Change">Reason for Change</a></th>
<th class="listtitle">Text</th>
<th class="listtitle"><img src="attachment.png" alt="Attachments" title="Attachments"</th></tr>
<tr><td class="list2">
<a href="../Company+IT+Change+Log/5431"> 5431 </a>
</td>
<td class="list2" nowrap><a href="../Company+IT+Change+Log/5431">1/9/2009 4:40:54 PM</a></td>
<td class="list2"><a href="../Company+IT+Change+Log/5431">Gary</a></td><td class="list2"><a
href="../Company+IT+Change+Log/5431"><a href="gmercier@Company.com">gmercier@Company.com</a></a></td><td
class="list2"><a href="../Company+IT+Change+Log/5431">Applications</a></td><td class="list2"><a
href="../Company+IT+Change+Log/5431">Patch - Hotfix</a></td><td class="list2"><a
href="../Company+IT+Change+Log/5431">PRN 18718 Update</a></td><td class="list2"><a
href="../Company+IT+Change+Log/5431"></a> </td><td class="list2"><a
href="../Company+IT+Change+Log/5431"></a> </td><td class="summary">A</td>
<td class="listatt"> </td><tr><td class="list1">
<a href="../Company+IT+Change+Log/5430"> 5430 </a>
</td>
<td class="list1" nowrap><a href="../Company+IT+Change+Log/5430">1/9/2009 4:37:01 PM</a></td>
<td class="list1"><a href="../Company+IT+Change+Log/5430">Gary</a></td><td class="list1"><a
href="../Company+IT+Change+Log/5430"><a href="gary@compan
Then the stream just aborts, apparently. |
|
66145
|
Mon Jan 12 05:33:04 2009 |
| kyoo | josh@newgistics.com | Bug report | Windows | 2.7.5-2130 | Re: Google Chrome issues | > > > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> > >
> > > I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> > > Is is possible the corporate elog server is running behind apache or in some
> > > other proxy config while the one you are having issues with is being connected
> > > to directly by chrome?
> >
> > It's good to know someone else has the issue, at least. I'd like to find a publicly available elog server so
> > that the elog developers could recreate the issue and thusly fix the issue. Or at the very least send the broken
> > URL to Google Chrome developers to see if it's a bug in the browser or not.
>
> I just brought up the current head release of elog, and the problem is fixed. Looks like it
> was some sort of cookie issue IIRC the log entry.
>
> So build a new elogd and you should be all set.
>
> - rouilj
Thanks. I'll have to wait for someone else to build the win32 binary, as I'm not set up to compile it myself. |
|
66146
|
Mon Jan 12 21:00:27 2009 |
| kyoo | josh@newgistics.com | Bug report | Windows | 2.7.5-2130 | Re: Google Chrome issues | > > > > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> > > >
> > > > I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> > > > Is is possible the corporate elog server is running behind apache or in some
> > > > other proxy config while the one you are having issues with is being connected
> > > > to directly by chrome?
> > >
> > > It's good to know someone else has the issue, at least. I'd like to find a publicly available elog server so
> > > that the elog developers could recreate the issue and thusly fix the issue. Or at the very least send the broken
> > > URL to Google Chrome developers to see if it's a bug in the browser or not.
> >
> > I just brought up the current head release of elog, and the problem is fixed. Looks like it
> > was some sort of cookie issue IIRC the log entry.
> >
> > So build a new elogd and you should be all set.
> >
> > - rouilj
>
> Thanks. I'll have to wait for someone else to build the win32 binary, as I'm not set up to compile it myself.
I installed the latest Windows build (didn't realize I missed a build in November), and it now works in Chrome. Thanks! |
|
65656
|
Sat Nov 24 03:16:46 2007 |
 | lance | lance1.hayward@yahoo.com | Info | Windows | ELOG V2.7. | Message ID and trouble ticketing system | I am trying to create a trouble ticket system however when you do a reply you get a new message ID. I was hoping to use the message ID as a ticket number and just wanted to use the reply as an append to the orginal message id, however each reply creates a new message id. This would be a nightmare to track and if I closed the ticket I would have to close every log entry related to this.
Does anyone know how to either make the reply and appended reply (appended to the orignal message id) or how to create a field that automatically gives it a new trouble ticket number.
Has anyone configured a trouble ticket system that I could look at to get some ideas?
Thanks,
Lance |
|
65658
|
Mon Nov 26 16:58:26 2007 |
| lance | lance1.hayward@yahoo.com | Info | Windows | ELOG V2.7. | Re: Message ID and trouble ticketing system |
| Stefan Ritt wrote: |
|
| lance wrote: |
|
I am trying to create a trouble ticket system however when you do a reply you get a new message ID. I was hoping to use the message ID as a ticket number and just wanted to use the reply as an append to the orginal message id, however each reply creates a new message id. This would be a nightmare to track and if I closed the ticket I would have to close every log entry related to this.
Does anyone know how to either make the reply and appended reply (appended to the orignal message id) or how to create a field that automatically gives it a new trouble ticket number.
Has anyone configured a trouble ticket system that I could look at to get some ideas?
|
First of all, ELOG has been designed having shift logbooks in mind, so it probably will never be a perfect trouble ticket system. Nevertheless, there are some options which can help in that respect:
- Use attributes Ticket and Status
- Preset Ticket with a running ticket number via
Preset ticket = TCK-#####
This will increment the 5-digit ticket number whenever you create a new ticket, but will not update it when you do a reply
-
Use Status to determine the status of the whole trouble ticket chain (initial entry plus replies)
Options Status = open, closed
Preset Status = open
-
Once a ticked chain is closed, do the following:
- Go to the threaded list display
- Click on Select
- Select the trouble ticket chain
- Click on Edit
- Now change Status from "Open" to "Closed"
This will then modify the Status of the whole chain from "Open" to "Closed"
|
Stefan,
Thanks for this, I had already implemented the Preset Ticket Nr = TT-##### but I didnt use the threaded and Select to close the ticket, very nice tip thanks. I think this program can be have several uses, and working very well. The trouble ticketing will work for us.
Once again thanks for the very speedy support.
Lance |
|
66401
|
Wed Jun 17 09:05:27 2009 |
 | lance | lance1.hayward@yahoo.com | Question | Windows | 2.7.2 | synchronization | We are running elog across two sites and synchronizing every four hours on change only. There are about 100 entries per day of which most are just one line entries. However this is taking up to 9 mins and during the replication process the server gives us an "unavailable" error. We are using a T1 across the sites so bandwidth should not be an issue, I am confused as to why this takes so long.
The issue for us is not how long the sync takes, providing this was happening in the background, and doesnt lock out the server while the replication was taking place. We are operating under a 24 hour call center type environment so the server being available all the time is of paramount importance.
We use version 2.7.2 and I know there have been several changes made since this version. Would changing to the latest version have any impact on this?
Cheers,
Lance |
|
66405
|
Fri Jun 19 09:44:02 2009 |
| lance | lance1.hayward@yahoo.com | Question | Windows | 2.7.2 | Re: synchronization |
| lance wrote: |
|
We are running elog across two sites and synchronizing every four hours on change only. There are about 100 entries per day of which most are just one line entries. However this is taking up to 9 mins and during the replication process the server gives us an "unavailable" error. We are using a T1 across the sites so bandwidth should not be an issue, I am confused as to why this takes so long.
The issue for us is not how long the sync takes, providing this was happening in the background, and doesnt lock out the server while the replication was taking place. We are operating under a 24 hour call center type environment so the server being available all the time is of paramount importance.
We use version 2.7.2 and I know there have been several changes made since this version. Would changing to the latest version have any impact on this?
Cheers,
Lance
|
Stefan,
I have been running logging and I think I have found the problem however I do not know how to resolve it.
Here is where it is going wrong:
19-May-2009 04:02:48 [] {NSS} MIRROR: ID21268: Local entry submitted
19-May-2009 04:07:34 [] {AMC} MIRROR: send entry #31056
It seems that when it has finished replication on one logbook there is a significant time before the next logbook replication starts. During this time the server is not avalable. I have noticed that the time between ending one logbook and starting the next differs betwee 2 and 5 minutes. Again the server is not available when this happens.
Do you have any idea?
Cheers,
Lance |
|
66425
|
Fri Jun 26 14:27:27 2009 |
| lance | lance1.hayward@yahoo.com | Question | Windows | 2.7.2 | Re: synchronization |
| Stefan Ritt wrote: |
|
| lance wrote: |
|
| lance wrote: |
|
We are running elog across two sites and synchronizing every four hours on change only. There are about 100 entries per day of which most are just one line entries. However this is taking up to 9 mins and during the replication process the server gives us an "unavailable" error. We are using a T1 across the sites so bandwidth should not be an issue, I am confused as to why this takes so long.
The issue for us is not how long the sync takes, providing this was happening in the background, and doesnt lock out the server while the replication was taking place. We are operating under a 24 hour call center type environment so the server being available all the time is of paramount importance.
We use version 2.7.2 and I know there have been several changes made since this version. Would changing to the latest version have any impact on this?
Cheers,
Lance
|
Stefan,
I have been running logging and I think I have found the problem however I do not know how to resolve it.
Here is where it is going wrong:
19-May-2009 04:02:48 [] {NSS} MIRROR: ID21268: Local entry submitted
19-May-2009 04:07:34 [] {AMC} MIRROR: send entry #31056
It seems that when it has finished replication on one logbook there is a significant time before the next logbook replication starts. During this time the server is not avalable. I have noticed that the time between ending one logbook and starting the next differs betwee 2 and 5 minutes. Again the server is not available when this happens.
Do you have any idea?
Cheers,
Lance
|
Hi,
I need more information to narrow down the problem:
- does this only happen on automatic mirroring or also when you do a manual synchronize?
- does this happen on both sides, like when you make the "other" elog server the master?
- if the server is inresponsive, does the CPU on that machine go to 100% or to 0%?
- do you have very long attachments in your logbooks?
- do you have the same problem on a "tiny" logbook like it comes with the distribution?
- are you using any Apache proxy in between?
I'm afraid that in the end you have to debug this yourself, since it will be very hard for me to reproduce exactly your problem (unless you send me all your files).
Cheers,
Stefan
|
Stefan,
Thanks for the reply.
This happens on automatic mirroring and by manual sync. However only the site initializing the mirror is locked out the remote seems to still be able to function.
The CPU jumps from very little usage to 50%+ being used by elogd.exe as soon as you start the mirroring/sync process
I have attached a file that that is in three parts and its pretty big. When I start up the elogd -v it takes over two minutes to scroll through hundreds of files. I have attached the last of those entries in the first part of the attached PDF, the second part of the PDF shows a manual sync and the third part shows the same sync on the same logbook a few mins later. It seems to take about 3 minutes even when there has been no new log entries. In addition if you are mirroring more that one log book through the automated cron job it can take about 3-5 mins before the second logbook starts its replication. I have also added a screenshot of the completed replications on both runs.
If there is a way to redirect the output of the cmd window when running elogd -v I would capture all the data for you but the standard redirect ">> elog.txt" only creates a blank file.
We are running several logbooks and it does look like the smaller logbooks still take several minutes to start up. I have attached the PMCLogfile and if you look between the NSS and the AMC replications on any day there seems to be a 3 min gap between one book finishing and another starting.
We are not using Apache prox in between.
I am not a programmer but I can follow instruction, if you need anything else let me know.
Stefan this has been driving me nuts for a while now so any help you can give would be more than appreciated.
Cheers,
Lance
|
| Attachment 1: log_for_stefan.pdf
|
|
| Attachment 2: PMCLogfile
|
19-Jun-2009 13:33:17 [] Server listening on port 8080 ..
19-Jun-2009 13:36:34 [dino@10.32.0.71] {NSS} EDIT entry #23326
19-Jun-2009 13:36:34 [dino@10.32.0.71] {NSS} READ entry #23326
19-Jun-2009 13:47:23 [lance@172.16.18.72] {NSS} READ entry #23109
19-Jun-2009 13:58:51 [lance@172.16.18.72] {NSS} LOGOUT
19-Jun-2009 13:58:57 [172.16.18.72] {NSS} LOGIN user "pmc" (attempt)
19-Jun-2009 13:59:21 [172.16.18.72] {NSS} LOGIN user "pmc" (attempt)
19-Jun-2009 13:59:21 [172.16.18.72] {NSS} LOGIN user "pmc" (success)
19-Jun-2009 14:10:11 [pmc@172.16.18.72] {NSS} READ entry #22861
19-Jun-2009 14:13:01 [] Server listening on port 8080 ..
19-Jun-2009 14:18:30 [] Server listening on port 8080 ..
19-Jun-2009 15:41:05 [lance@127.0.0.1] {NSS} MIRROR change entry #1095 to #23357
19-Jun-2009 15:41:05 [lance@127.0.0.1] {NSS} DELETE entry #1095
19-Jun-2009 15:41:05 [lance@127.0.0.1] {NSS} MIRROR send entry #23357
19-Jun-2009 15:41:11 [lance@127.0.0.1] {NSS} MIRROR change entry #8751 to #23358
19-Jun-2009 15:41:11 [lance@127.0.0.1] {NSS} DELETE entry #8751
19-Jun-2009 15:41:11 [lance@127.0.0.1] {NSS} MIRROR send entry #23358
19-Jun-2009 15:41:11 [lance@127.0.0.1] {NSS} MIRROR change entry #8787 to #23359
19-Jun-2009 15:41:11 [lance@127.0.0.1] {NSS} DELETE entry #8787
19-Jun-2009 15:41:12 [lance@127.0.0.1] {NSS} DELETE entry #8787
19-Jun-2009 15:41:12 [lance@127.0.0.1] {NSS} MIRROR send entry #23359
19-Jun-2009 15:41:12 [lance@127.0.0.1] {NSS} MIRROR send entry #23358
19-Jun-2009 15:41:20 [lance@127.0.0.1] {NSS} MIRROR change entry #15829 to #23360
19-Jun-2009 15:41:20 [lance@127.0.0.1] {NSS} DELETE entry #15829
19-Jun-2009 15:41:20 [lance@127.0.0.1] {NSS} MIRROR send entry #23360
19-Jun-2009 15:41:22 [lance@127.0.0.1] {NSS} MIRROR change entry #16552 to #23361
19-Jun-2009 15:41:22 [lance@127.0.0.1] {NSS} DELETE entry #16552
19-Jun-2009 15:41:22 [lance@127.0.0.1] {NSS} MIRROR send entry #23361
19-Jun-2009 15:41:23 [lance@127.0.0.1] {NSS} MIRROR change entry #16568 to #23362
19-Jun-2009 15:41:23 [lance@127.0.0.1] {NSS} DELETE entry #16568
19-Jun-2009 15:41:23 [lance@127.0.0.1] {NSS} MIRROR send entry #23362
19-Jun-2009 15:41:23 [lance@127.0.0.1] {NSS} MIRROR change entry #16721 to #23363
19-Jun-2009 15:41:23 [lance@127.0.0.1] {NSS} DELETE entry #16721
19-Jun-2009 15:41:23 [lance@127.0.0.1] {NSS} MIRROR send entry #23363
19-Jun-2009 15:41:24 [lance@127.0.0.1] {NSS} MIRROR change entry #16722 to #23364
19-Jun-2009 15:41:24 [lance@127.0.0.1] {NSS} DELETE entry #16722
19-Jun-2009 15:41:24 [lance@127.0.0.1] {NSS} MIRROR send entry #23364
19-Jun-2009 15:41:24 [lance@127.0.0.1] {NSS} MIRROR change entry #16734 to #23365
19-Jun-2009 15:41:24 [lance@127.0.0.1] {NSS} DELETE entry #16734
19-Jun-2009 15:41:24 [lance@127.0.0.1] {NSS} MIRROR send entry #23365
19-Jun-2009 15:41:24 [lance@127.0.0.1] {NSS} MIRROR change entry #16910 to #23366
19-Jun-2009 15:41:24 [lance@127.0.0.1] {NSS} DELETE entry #16910
19-Jun-2009 15:41:24 [lance@127.0.0.1] {NSS} MIRROR send entry #23366
19-Jun-2009 15:41:25 [lance@127.0.0.1] {NSS} MIRROR change entry #16973 to #23367
19-Jun-2009 15:41:25 [lance@127.0.0.1] {NSS} DELETE entry #16973
19-Jun-2009 15:41:25 [lance@127.0.0.1] {NSS} MIRROR send entry #23367
19-Jun-2009 15:41:25 [lance@127.0.0.1] {NSS} MIRROR change entry #16941 to #23368
19-Jun-2009 15:41:25 [lance@127.0.0.1] {NSS} DELETE entry #16941
19-Jun-2009 15:41:25 [lance@127.0.0.1] {NSS} MIRROR send entry #23368
19-Jun-2009 15:41:25 [lance@127.0.0.1] {NSS} MIRROR change entry #16974 to #23369
19-Jun-2009 15:41:25 [lance@127.0.0.1] {NSS} DELETE entry #16974
19-Jun-2009 15:41:25 [lance@127.0.0.1] {NSS} MIRROR send entry #23369
19-Jun-2009 15:41:26 [lance@127.0.0.1] {NSS} MIRROR change entry #16975 to #23370
19-Jun-2009 15:41:26 [lance@127.0.0.1] {NSS} DELETE entry #16975
19-Jun-2009 15:41:26 [lance@127.0.0.1] {NSS} MIRROR send entry #23370
19-Jun-2009 15:41:26 [lance@127.0.0.1] {NSS} MIRROR change entry #17018 to #23371
19-Jun-2009 15:41:26 [lance@127.0.0.1] {NSS} DELETE entry #17018
19-Jun-2009 15:41:26 [lance@127.0.0.1] {NSS} MIRROR send entry #23371
19-Jun-2009 15:41:27 [lance@127.0.0.1] {NSS} MIRROR change entry #17052 to #23372
19-Jun-2009 15:41:27 [lance@127.0.0.1] {NSS} DELETE entry #17052
19-Jun-2009 15:41:27 [lance@127.0.0.1] {NSS} MIRROR send entry #23372
19-Jun-2009 15:41:27 [lance@127.0.0.1] {NSS} MIRROR change entry #17053 to #23373
19-Jun-2009 15:41:27 [lance@127.0.0.1] {NSS} DELETE entry #17053
19-Jun-2009 15:41:27 [lance@127.0.0.1] {NSS} MIRROR send entry #23373
19-Jun-2009 15:41:27 [lance@127.0.0.1] {NSS} MIRROR change entry #17119 to #23374
19-Jun-2009 15:41:27 [lance@127.0.0.1] {NSS} DELETE entry #17119
19-Jun-2009 15:41:27 [lance@127.0.0.1] {NSS} MIRROR send entry #23374
19-Jun-2009 15:41:28 [lance@127.0.0.1] {NSS} MIRROR change entry #17128 to #23375
19-Jun-2009 15:41:28 [lance@127.0.0.1] {NSS} DELETE entry #17128
19-Jun-2009 15:41:28 [lance@127.0.0.1] {NSS} MIRROR send entry #23375
19-Jun-2009 15:41:28 [lance@127.0.0.1] {NSS} MIRROR change entry #17121 to #23376
19-Jun-2009 15:41:28 [lance@127.0.0.1] {NSS} DELETE entry #17121
19-Jun-2009 15:41:28 [lance@127.0.0.1] {NSS} MIRROR send entry #23376
19-Jun-2009 15:41:28 [lance@127.0.0.1] {NSS} MIRROR change entry #17127 to #23377
19-Jun-2009 15:41:29 [lance@127.0.0.1] {NSS} DELETE entry #17127
19-Jun-2009 15:41:29 [lance@127.0.0.1] {NSS} DELETE entry #17127
19-Jun-2009 15:41:29 [lance@127.0.0.1] {NSS} MIRROR send entry #23377
19-Jun-2009 15:41:29 [lance@127.0.0.1] {NSS} MIRROR send entry #23377
19-Jun-2009 15:41:30 [lance@127.0.0.1] {NSS} MIRROR change entry #17235 to #23378
19-Jun-2009 15:41:30 [lance@127.0.0.1] {NSS} DELETE entry #17235
19-Jun-2009 15:41:30 [lance@127.0.0.1] {NSS} MIRROR send entry #23378
19-Jun-2009 15:41:30 [lance@127.0.0.1] {NSS} MIRROR change entry #17233 to #23379
19-Jun-2009 15:41:30 [lance@127.0.0.1] {NSS} DELETE entry #17233
19-Jun-2009 15:41:30 [lance@127.0.0.1] {NSS} MIRROR send entry #23379
19-Jun-2009 15:41:31 [lance@127.0.0.1] {NSS} MIRROR change entry #17317 to #23380
19-Jun-2009 15:41:31 [lance@127.0.0.1] {NSS} DELETE entry #17317
19-Jun-2009 15:41:31 [lance@127.0.0.1] {NSS} MIRROR send entry #23380
19-Jun-2009 15:41:31 [lance@127.0.0.1] {NSS} MIRROR change entry #17318 to #23381
19-Jun-2009 15:41:31 [lance@127.0.0.1] {NSS} DELETE entry #17318
19-Jun-2009 15:41:31 [lance@127.0.0.1] {NSS} MIRROR send entry #23381
19-Jun-2009 15:41:31 [lance@127.0.0.1] {NSS} MIRROR change entry #17349 to #23382
19-Jun-2009 15:41:31 [lance@127.0.0.1] {NSS} DELETE entry #17349
19-Jun-2009 15:41:31 [lance@127.0.0.1] {NSS} MIRROR send entry #23382
19-Jun-2009 15:41:32 [lance@127.0.0.1] {NSS} MIRROR change entry #17379 to #23383
19-Jun-2009 15:41:32 [lance@127.0.0.1] {NSS} DELETE entry #17379
19-Jun-2009 15:41:32 [lance@127.0.0.1] {NSS} MIRROR send entry #23383
19-Jun-2009 15:41:32 [lance@127.0.0.1] {NSS} MIRROR change entry #17380 to #23384
19-Jun-2009 15:41:32 [lance@127.0.0.1] {NSS} DELETE entry #17380
19-Jun-2009 15:41:32 [lance@127.0.0.1] {NSS} MIRROR send entry #23384
19-Jun-2009 15:41:32 [lance@127.0.0.1] {NSS} MIRROR change entry #17381 to #23385
19-Jun-2009 15:41:32 [lance@127.0.0.1] {NSS} DELETE entry #17381
19-Jun-2009 15:41:32 [lance@127.0.0.1] {NSS} MIRROR send entry #23385
19-Jun-2009 15:41:33 [lance@127.0.0.1] {NSS} MIRROR change entry #17393 to #23386
19-Jun-2009 15:41:33 [lance@127.0.0.1] {NSS} DELETE entry #17393
19-Jun-2009 15:41:33 [lance@127.0.0.1] {NSS} MIRROR send entry #23386
19-Jun-2009 15:41:33 [lance@127.0.0.1] {NSS} MIRROR change entry #17394 to #23387
19-Jun-2009 15:41:33 [lance@127.0.0.1] {NSS} DELETE entry #17394
19-Jun-2009 15:41:33 [lance@127.0.0.1] {NSS} MIRROR send entry #23387
19-Jun-2009 15:41:34 [lance@127.0.0.1] {NSS} MIRROR change entry #17497 to #23388
19-Jun-2009 15:41:34 [lance@127.0.0.1] {NSS} DELETE entry #17497
19-Jun-2009 15:41:34 [lance@127.0.0.1] {NSS} MIRROR send entry #23388
19-Jun-2009 15:41:34 [lance@127.0.0.1] {NSS} MIRROR change entry #17498 to #23389
19-Jun-2009 15:41:34 [lance@127.0.0.1] {NSS} DELETE entry #17498
19-Jun-2009 15:41:34 [lance@127.0.0.1] {NSS} MIRROR send entry #23389
19-Jun-2009 15:41:35 [lance@127.0.0.1] {NSS} MIRROR change entry #17499 to #23390
19-Jun-2009 15:41:35 [lance@127.0.0.1] {NSS} DELETE entry #17499
19-Jun-2009 15:41:35 [lance@127.0.0.1] {NSS} MIRROR send entry #23390
19-Jun-2009 15:41:35 [lance@127.0.0.1] {NSS} MIRROR change entry #17527 to #23391
19-Jun-2009 15:41:35 [lance@127.0.0.1] {NSS} DELETE entry #17527
19-Jun-2009 15:41:35 [lance@127.0.0.1] {NSS} MIRROR send entry #23391
19-Jun-2009 15:41:35 [lance@127.0.0.1] {NSS} MIRROR change entry #17668 to #23392
19-Jun-2009 15:41:35 [lance@127.0.0.1] {NSS} DELETE entry #17668
19-Jun-2009 15:41:35 [lance@127.0.0.1] {NSS} MIRROR send entry #23392
19-Jun-2009 15:41:36 [lance@127.0.0.1] {NSS} MIRROR change entry #17699 to #23393
19-Jun-2009 15:41:36 [lance@127.0.0.1] {NSS} DELETE entry #17699
19-Jun-2009 15:41:36 [lance@127.0.0.1] {NSS} MIRROR send entry #23393
19-Jun-2009 15:41:37 [lance@127.0.0.1] {NSS} MIRROR change entry #17744 to #23394
19-Jun-2009 15:41:37 [lance@127.0.0.1] {NSS} DELETE entry #17744
19-Jun-2009 15:41:37 [lance@127.0.0.1] {NSS} MIRROR send entry #23394
19-Jun-2009 15:41:37 [lance@127.0.0.1] {NSS} MIRROR change entry #17845 to #23395
19-Jun-2009 15:41:37 [lance@127.0.0.1] {NSS} DELETE entry #17845
19-Jun-2009 15:41:37 [lance@127.0.0.1] {NSS} MIRROR send entry #23395
19-Jun-2009 15:41:37 [lance@127.0.0.1] {NSS} MIRROR change entry #17882 to #23396
19-Jun-2009 15:41:37 [lance@127.0.0.1] {NSS} DELETE entry #17882
19-Jun-2009 15:41:38 [lance@127.0.0.1] {NSS} DELETE entry #17882
19-Jun-2009 15:41:38 [lance@127.0.0.1] {NSS} MIRROR send entry #23396
19-Jun-2009 15:41:38 [lance@127.0.0.1] {NSS} MIRROR change entry #17866 to #23397
19-Jun-2009 15:41:38 [lance@127.0.0.1] {NSS} DELETE entry #17866
19-Jun-2009 15:41:38 [lance@127.0.0.1] {NSS} MIRROR send entry #23397
19-Jun-2009 15:41:39 [lance@127.0.0.1] {NSS} MIRROR change entry #17924 to #23398
19-Jun-2009 15:41:39 [lance@127.0.0.1] {NSS} DELETE entry #17924
19-Jun-2009 15:41:39 [lance@127.0.0.1] {NSS} MIRROR send entry #23398
19-Jun-2009 15:41:39 [lance@127.0.0.1] {NSS} MIRROR change entry #17953 to #23399
19-Jun-2009 15:41:39 [lance@127.0.0.1] {NSS} DELETE entry #17953
19-Jun-2009 15:41:39 [lance@127.0.0.1] {NSS} MIRROR send entry #23399
19-Jun-2009 15:41:40 [lance@127.0.0.1] {NSS} MIRROR change entry #17998 to #23400
19-Jun-2009 15:41:40 [lance@127.0.0.1] {NSS} DELETE entry #17998
19-Jun-2009 15:41:40 [lance@127.0.0.1] {NSS} MIRROR send entry #23400
19-Jun-2009 15:41:40 [lance@127.0.0.1] {NSS} MIRROR change entry #18008 to #23401
19-Jun-2009 15:41:40 [lance@127.0.0.1] {NSS} DELETE entry #18008
19-Jun-2009 15:41:40 [lance@127.0.0.1] {NSS} MIRROR send entry #23401
19-Jun-2009 15:41:41 [lance@127.0.0.1] {NSS} MIRROR change entry #18009 to #23402
19-Jun-2009 15:41:41 [lance@127.0.0.1] {NSS} DELETE entry #18009
19-Jun-2009 15:41:41 [lance@127.0.0.1] {NSS} MIRROR send entry #23402
19-Jun-2009 15:41:41 [lance@127.0.0.1] {NSS} MIRROR change entry #18016 to #23403
19-Jun-2009 15:41:41 [lance@127.0.0.1] {NSS} DELETE entry #18016
19-Jun-2009 15:41:41 [lance@127.0.0.1] {NSS} MIRROR send entry #23403
19-Jun-2009 15:41:41 [lance@127.0.0.1] {NSS} MIRROR change entry #18017 to #23404
19-Jun-2009 15:41:41 [lance@127.0.0.1] {NSS} DELETE entry #18017
19-Jun-2009 15:41:41 [lance@127.0.0.1] {NSS} MIRROR send entry #23404
19-Jun-2009 15:41:42 [lance@127.0.0.1] {NSS} MIRROR change entry #18040 to #23405
19-Jun-2009 15:41:42 [lance@127.0.0.1] {NSS} DELETE entry #18040
19-Jun-2009 15:41:42 [lance@127.0.0.1] {NSS} MIRROR send entry #23405
19-Jun-2009 15:41:42 [lance@127.0.0.1] {NSS} MIRROR change entry #18057 to #23406
19-Jun-2009 15:41:42 [lance@127.0.0.1] {NSS} DELETE entry #18057
19-Jun-2009 15:41:42 [lance@127.0.0.1] {NSS} MIRROR send entry #23406
19-Jun-2009 15:41:42 [lance@127.0.0.1] {NSS} MIRROR change entry #18078 to #23407
19-Jun-2009 15:41:42 [lance@127.0.0.1] {NSS} DELETE entry #18078
19-Jun-2009 15:41:42 [lance@127.0.0.1] {NSS} MIRROR send entry #23407
19-Jun-2009 15:41:43 [lance@127.0.0.1] {NSS} MIRROR change entry #18107 to #23408
19-Jun-2009 15:41:43 [lance@127.0.0.1] {NSS} DELETE entry #18107
19-Jun-2009 15:41:43 [lance@127.0.0.1] {NSS} MIRROR send entry #23408
19-Jun-2009 15:41:43 [lance@127.0.0.1] {NSS} MIRROR change entry #18119 to #23409
19-Jun-2009 15:41:43 [lance@127.0.0.1] {NSS} DELETE entry #18119
19-Jun-2009 15:41:43 [lance@127.0.0.1] {NSS} MIRROR send entry #23409
19-Jun-2009 15:41:44 [lance@127.0.0.1] {NSS} MIRROR change entry #18336 to #23410
19-Jun-2009 15:41:44 [lance@127.0.0.1] {NSS} DELETE entry #18336
19-Jun-2009 15:41:44 [lance@127.0.0.1] {NSS} MIRROR send entry #23410
19-Jun-2009 15:41:44 [lance@127.0.0.1] {NSS} MIRROR change entry #18448 to #23411
19-Jun-2009 15:41:44 [lance@127.0.0.1] {NSS} DELETE entry #18448
19-Jun-2009 15:41:44 [lance@127.0.0.1] {NSS} MIRROR send entry #23411
19-Jun-2009 15:41:45 [lance@127.0.0.1] {NSS} MIRROR change entry #18506 to #23412
19-Jun-2009 15:41:45 [lance@127.0.0.1] {NSS} DELETE entry #18506
19-Jun-2009 15:41:45 [lance@127.0.0.1] {NSS} MIRROR send entry #23412
19-Jun-2009 15:41:45 [lance@127.0.0.1] {NSS} MIRROR change entry #18560 to #23413
19-Jun-2009 15:41:45 [lance@127.0.0.1] {NSS} DELETE entry #18560
19-Jun-2009 15:41:45 [lance@127.0.0.1] {NSS} MIRROR send entry #23413
19-Jun-2009 15:41:46 [lance@127.0.0.1] {NSS} MIRROR change entry #18561 to #23414
19-Jun-2009 15:41:46 [lance@127.0.0.1] {NSS} DELETE entry #18561
19-Jun-2009 15:41:46 [lance@127.0.0.1] {NSS} MIRROR send entry #23414
19-Jun-2009 15:41:47 [lance@127.0.0.1] {NSS} MIRROR change entry #18583 to #23415
19-Jun-2009 15:41:47 [lance@127.0.0.1] {NSS} DELETE entry #18583
19-Jun-2009 15:41:47 [lance@127.0.0.1] {NSS} MIRROR send entry #23415
19-Jun-2009 15:41:48 [lance@127.0.0.1] {NSS} MIRROR change entry #18584 to #23416
19-Jun-2009 15:41:48 [lance@127.0.0.1] {NSS} DELETE entry #18584
19-Jun-2009 15:41:48 [lance@127.0.0.1] {NSS} MIRROR send entry #23416
19-Jun-2009 15:41:48 [lance@127.0.0.1] {NSS} MIRROR change entry #18585 to #23417
19-Jun-2009 15:41:48 [lance@127.0.0.1] {NSS} DELETE entry #18585
19-Jun-2009 15:41:48 [lance@127.0.0.1] {NSS} MIRROR send entry #23417
19-Jun-2009 15:41:48 [lance@127.0.0.1] {NSS} MIRROR change entry #18648 to #23418
19-Jun-2009 15:41:48 [lance@127.0.0.1] {NSS} DELETE entry #18648
19-Jun-2009 15:41:48 [lance@127.0.0.1] {NSS} MIRROR send entry #23418
19-Jun-2009 15:41:49 [lance@127.0.0.1] {NSS} MIRROR change entry #18649 to #23419
19-Jun-2009 15:41:49 [lance@127.0.0.1] {NSS} DELETE entry #18649
19-Jun-2009 15:41:49 [lance@127.0.0.1] {NSS} MIRROR send entry #23419
19-Jun-2009 15:41:49 [lance@127.0.0.1] {NSS} MIRROR change entry #18764 to #23420
19-Jun-2009 15:41:49 [lance@127.0.0.1] {NSS} DELETE entry #18764
19-Jun-2009 15:41:49 [lance@127.0.0.1] {NSS} MIRROR send entry #23420
19-Jun-2009 15:41:49 [lance@127.0.0.1] {NSS} MIRROR change entry #18765 to #23421
19-Jun-2009 15:41:49 [lance@127.0.0.1] {NSS} DELETE entry #18765
19-Jun-2009 15:41:49 [lance@127.0.0.1] {NSS} MIRROR send entry #23421
19-Jun-2009 15:41:50 [lance@127.0.0.1] {NSS} MIRROR change entry #18766 to #23422
19-Jun-2009 15:41:50 [lance@127.0.0.1] {NSS} DELETE entry #18766
19-Jun-2009 15:41:50 [lance@127.0.0.1] {NSS} MIRROR send entry #23422
19-Jun-2009 15:41:50 [lance@127.0.0.1] {NSS} MIRROR change entry #18848 to #23423
19-Jun-2009 15:41:50 [lance@127.0.0.1] {NSS} DELETE entry #18848
19-Jun-2009 15:41:50 [lance@127.0.0.1] {NSS} MIRROR send entry #23423
19-Jun-2009 15:41:50 [lance@127.0.0.1] {NSS} MIRROR change entry #18849 to #23424
19-Jun-2009 15:41:50 [lance@127.0.0.1] {NSS} DELETE entry #18849
19-Jun-2009 15:41:50 [lance@127.0.0.1] {NSS} MIRROR send entry #23424
19-Jun-2009 15:41:51 [lance@127.0.0.1] {NSS} MIRROR change entry #18850 to #23425
19-Jun-2009 15:41:51 [lance@127.0.0.1] {NSS} DELETE entry #18850
19-Jun-2009 15:41:51 [lance@127.0.0.1] {NSS} MIRROR send entry #23425
19-Jun-2009 15:41:51 [lance@127.0.0.1] {NSS} MIRROR change entry #18904 to #23426
19-Jun-2009 15:41:51 [lance@127.0.0.1] {NSS} DELETE entry #18904
19-Jun-2009 15:41:51 [lance@127.0.0.1] {NSS} MIRROR send entry #23426
19-Jun-2009 15:41:52 [lance@127.0.0.1] {NSS} MIRROR change entry #18905 to #23427
19-Jun-2009 15:41:52 [lance@127.0.0.1] {NSS} DELETE entry #18905
19-Jun-2009 15:41:52 [lance@127.0.0.1] {NSS} MIRROR send entry #23427
19-Jun-2009 15:41:52 [lance@127.0.0.1] {NSS} MIRROR change entry #18950 to #23428
19-Jun-2009 15:41:52 [lance@127.0.0.1] {NSS} DELETE entry #18950
19-Jun-2009 15:41:52 [lance@127.0.0.1] {NSS} MIRROR send entry #23428
19-Jun-2009 15:41:52 [lance@127.0.0.1] {NSS} MIRROR change entry #18963 to #23429
19-Jun-2009 15:41:52 [lance@127.0.0.1] {NSS} DELETE entry #18963
19-Jun-2009 15:41:52 [lance@127.0.0.1] {NSS} MIRROR send entry #23429
19-Jun-2009 15:41:53 [lance@127.0.0.1] {NSS} MIRROR change entry #18971 to #23430
19-Jun-2009 15:41:53 [lance@127.0.0.1] {NSS} DELETE entry #18971
19-Jun-2009 15:41:53 [lance@127.0.0.1] {NSS} MIRROR send entry #23430
19-Jun-2009 15:41:53 [lance@127.0.0.1] {NSS} MIRROR change entry #19260 to #23431
19-Jun-2009 15:41:53 [lance@127.0.0.1] {NSS} DELETE entry #19260
19-Jun-2009 15:41:53 [lance@127.0.0.1] {NSS} MIRROR send entry #23431
19-Jun-2009 15:41:54 [lance@127.0.0.1] {NSS} MIRROR change entry #19261 to #23432
19-Jun-2009 15:41:54 [lance@127.0.0.1] {NSS} DELETE entry #19261
19-Jun-2009 15:41:54 [lance@127.0.0.1] {NSS} MIRROR send entry #23432
19-Jun-2009 15:41:54 [lance@127.0.0.1] {NSS} MIRROR change entry #19276 to #23433
19-Jun-2009 15:41:54 [lance@127.0.0.1] {NSS} DELETE entry #19276
19-Jun-2009 15:41:54 [lance@127.0.0.1] {NSS} MIRROR send entry #23433
19-Jun-2009 15:41:54 [lance@127.0.0.1] {NSS} MIRROR change entry #19324 to #23434
19-Jun-2009 15:41:54 [lance@127.0.0.1] {NSS} DELETE entry #19324
19-Jun-2009 15:41:54 [lance@127.0.0.1] {NSS} MIRROR send entry #23434
19-Jun-2009 15:41:55 [lance@127.0.0.1] {NSS} MIRROR change entry #19480 to #23435
19-Jun-2009 15:41:55 [lance@127.0.0.1] {NSS} DELETE entry #19480
19-Jun-2009 15:41:55 [lance@127.0.0.1] {NSS} MIRROR send entry #23435
19-Jun-2009 15:41:55 [lance@127.0.0.1] {NSS} MIRROR change entry #19481 to #23436
19-Jun-2009 15:41:55 [lance@127.0.0.1] {NSS} DELETE entry #19481
19-Jun-2009 15:41:55 [lance@127.0.0.1] {NSS} MIRROR send entry #23436
19-Jun-2009 15:41:56 [lance@127.0.0.1] {NSS} MIRROR change entry #19482 to #23437
19-Jun-2009 15:41:56 [lance@127.0.0.1] {NSS} DELETE entry #19482
19-Jun-2009 15:41:56 [lance@127.0.0.1] {NSS} MIRROR send entry #23437
19-Jun-2009 15:41:56 [lance@127.0.0.1] {NSS} MIRROR change entry #19630 to #23438
19-Jun-2009 15:41:56 [lance@127.0.0.1] {NSS} DELETE entry #19630
19-Jun-2009 15:41:56 [lance@127.0.0.1] {NSS} MIRROR send entry #23438
19-Jun-2009 15:41:57 [lance@127.0.0.1] {NSS} MIRROR change entry #19631 to #23439
19-Jun-2009 15:41:57 [lance@127.0.0.1] {NSS} DELETE entry #19631
19-Jun-2009 15:41:57 [lance@127.0.0.1] {NSS} MIRROR send entry #23439
19-Jun-2009 15:41:57 [lance@127.0.0.1] {NSS} MIRROR change entry #19720 to #23440
19-Jun-2009 15:41:57 [lance@127.0.0.1] {NSS} DELETE entry #19720
19-Jun-2009 15:41:57 [lance@127.0.0.1] {NSS} MIRROR send entry #23440
19-Jun-2009 15:41:57 [lance@127.0.0.1] {NSS} MIRROR change entry #19771 to #23441
19-Jun-2009 15:41:57 [lance@127.0.0.1] {NSS} DELETE entry #19771
19-Jun-2009 15:41:57 [lance@127.0.0.1] {NSS} MIRROR send entry #23441
19-Jun-2009 15:41:58 [lance@127.0.0.1] {NSS} MIRROR change entry #19783 to #23442
19-Jun-2009 15:41:58 [lance@127.0.0.1] {NSS} DELETE entry #19783
19-Jun-2009 15:41:58 [lance@127.0.0.1] {NSS} MIRROR send entry #23442
19-Jun-2009 15:41:58 [lance@127.0.0.1] {NSS} MIRROR change entry #19911 to #23443
19-Jun-2009 15:41:58 [lance@127.0.0.1] {NSS} DELETE entry #19911
19-Jun-2009 15:41:58 [lance@127.0.0.1] {NSS} MIRROR send entry #23443
19-Jun-2009 15:41:59 [lance@127.0.0.1] {NSS} MIRROR change entry #19930 to #23444
19-Jun-2009 15:41:59 [lance@127.0.0.1] {NSS} DELETE entry #19930
19-Jun-2009 15:41:59 [lance@127.0.0.1] {NSS} MIRROR send entry #23444
19-Jun-2009 15:41:59 [lance@127.0.0.1] {NSS} MIRROR change entry #19931 to #23445
19-Jun-2009 15:41:59 [lance@127.0.0.1] {NSS} DELETE entry #19931
19-Jun-2009 15:41:59 [lance@127.0.0.1] {NSS} MIRROR send entry #23445
19-Jun-2009 15:41:59 [lance@127.0.0.1] {NSS} MIRROR change entry #19962 to #23446
19-Jun-2009 15:41:59 [lance@127.0.0.1] {NSS} DELETE entry #19962
19-Jun-2009 15:41:59 [lance@127.0.0.1] {NSS} MIRROR send entry #23446
19-Jun-2009 15:42:00 [lance@127.0.0.1] {NSS} MIRROR change entry #19991 to #23447
19-Jun-2009 15:42:00 [lance@127.0.0.1] {NSS} DELETE entry #19991
19-Jun-2009 15:42:00 [lance@127.0.0.1] {NSS} MIRROR send entry #23447
19-Jun-2009 15:42:00 [lance@127.0.0.1] {NSS} MIRROR change entry #19992 to #23448
19-Jun-2009 15:42:00 [lance@127.0.0.1] {NSS} DELETE entry #19992
19-Jun-2009 15:42:00 [lance@127.0.0.1] {NSS} MIRROR send entry #23448
19-Jun-2009 15:42:00 [lance@127.0.0.1] {NSS} MIRROR change entry #19993 to #23449
19-Jun-2009 15:42:00 [lance@127.0.0.1] {NSS} DELETE entry #19993
19-Jun-2009 15:42:00 [lance@127.0.0.1] {NSS} MIRROR send entry #23449
19-Jun-2009 15:42:01 [lance@127.0.0.1] {NSS} MIRROR change entry #19994 to #23450
19-Jun-2009 15:42:01 [lance@127.0.0.1] {NSS} DELETE entry #19994
19-Jun-2009 15:42:01 [lance@127.0.0.1] {NSS} MIRROR send entry #23450
19-Jun-2009 15:42:01 [lance@127.0.0.1] {NSS} MIRROR change entry #19995 to #23451
19-Jun-2009 15:42:01 [lance@127.0.0.1] {NSS} DELETE entry #19995
... 1930 more lines ...
|
|