EVENT LOG FOR SITE PRA Most recent activity to be listed first. First line of each entry lists date, time and who is reporting. Subsequent lines of each entry aligned under Time column. Do not use tabs, only spaces. Date Time Who What ---------- ----- -------- ----------------------------------------------- 12/02/2003 15:29 Brett At 3:30 pm PST 12/02/03 I put coils 01, 02, 03, 04 into standby because the fish ladders are down. I'm not sure exactly when the ladders went down. Anthony from Biomark will post the exact time ladders went down in the near future 11/17/2003 11:43 acarson@ 01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise,07:ExcessiveNoise,08 :ExcessiveNoise: Excessive noise levels will be looked at during next site visit on Nov 20th. Per Dave Marvin request, PC1's file transfer settings was changed from automated to manual. The change is to help PSMFC determine recent uploading issues and to determine the numerous problems with PC1 "locking up". The following are error messages that are present when I PCA into PC1 after Minimon has stopped interrogating: Minimon Exe has encountered a problem and needs to close. We are sorry for the inconvenience. After this window is closed it is followed by: Run time error '25061': Error initializing file upload: 25061-Error Transmitting PTTP package: 25061-Error Connecting to FTP session: [10060] Connection timed out. Data files will be uploaded daily until automated uploaded is resumed. 11/17/2003 10:39 Dave I spoke with Anthony Carson, BioMark, this morning regarding data collection at PRD, RIS, and WEL and our PSMFC firewall issues. We decided that, to ensure the integrity and security of the data files at those sites, Anthony will disable automated file uploads in Minimon (by switching to the 'archive only' mode) until the firewall issue has been resolved. Data files will be sent manually. At Anthony's request, I've disabled file-checking for PRA, RIA, and WEA in etc/sites until further notice. 10/23/2003 07:58 acarson@ PRA PC1 & PC2 are collecting data but are unable to connect to PSMFC. GCPUD personnel are working on getting the problem resolved. 10/20/2003 10:32 Anthony_ I have contacted GCPUD about getting personnel on site to assist in getting PC1 back "on-line". More later...... 10/17/2003 12:43 Brett David Duval from Grant PUD called me from the PRA computer room. He confirmed that PC 1 was locked up. I had him re-boot PC1 and synchronize the files with PC 2. the files were set at PRA03290.G. According the David, PC2 was running fine. We will have to get the files from PC2 to send to ptagis to make up for the lost files from yesterday and today on PC1. 10/17/2003 12:01 Brett I received an email this morning (10/17) that PRA had stopped sending data to ptagis. I was briefly able to log onto PC 1 via pcanywhere and saw that there was a firewall message and a Minimon error message up on the screen. The computer appeared to be locked up because I was unable to do anything on it including re-boot. I was then dis-connected and haven't been able to get on it since. I called Chris Carlson of Grant PUD and he sent David Duval to the computer room. He will call me when he gets there and we will try to get the computers up and running. I will update the event log as soon as I have something else to report. 09/23/2003 16:20 acarson@ 01:ExcessiveNoise,02:ExcessiveNoise,06:ExcessiveNoise: I have not determined the cause of the excessive noise levels. A lot of activity is near Coils 1&2 including a drill winch for open/closing of diverting gates for the adult trap. I will try to determine the time frame and frequency of when the adult trap is in use. 09/23/2003 15:57 acarson@ 08:TestTagFailure: PC1 has not sent data since 9/21/03. I will have someone from GCPUD check out PC1 the morning of 09/24/03. I PCA'd to PC2 and its working and collecting data. I can't PCA into PC1. 09/02/2003 10:03 acarson@ 08:TestTagFailure: This is a on going issue. Transceiver's FDXB level peaks at 100% when test tag is fired but intermittantly sends failure alarm. ~08-10 08/28/03 07:39:55 ALARM MESSAGE: Single-shot test with Test Tag. ~08-10 08/28/03 07:39:55 ALARM PROBLEM: Test Tag Failed ~08-10 08/28/03 07:39:56 ALARM Noise report for Reader ID#08 ~08-10 08/28/03 07:39:56 ALARM Average: 1 % ~08-10 08/28/03 07:39:56 ALARM Peak: 11 % ~08-10 08/28/03 07:39:56 ALARM FDXB Peak: 100 % I will continue to monitor this issue. 08/22/2003 11:44 acarson@ 08:TestTagFailure: Test Tag failure is an on going issue that I am still monitoring. In addition, all pc's on site have been updated with latest windows updates along with anti-virus and firewall software. The "worm" virus was detected and removed from both PC1 & PC2. All transceiver buffer data were downloaded onto a laptop. All buffer files along with data files created during the fix will be filtered and sent to Dave Marvin next week for review. Thanks to all involved for their help! 08/18/2003 14:01 Darren_C The loading problem for WEA has been passed to Anthony Carson of Biomark and he will take care of the situation. I was able to PCA into PC2 and it is up and running minimon and collecting data, I was not able to PCA into PC1 however. The situation with PRA is that they computers have been removed from the PUD's network until the computers can be cleaned of a virus. Anthony is in the process of correcting the problem. 08/13/2003 12:00 scott_li The PRA PC's have been diagnose as being infected with the W32.Blaster.worm. Alan brought this to my attention and sure enough , blaster.exe resided in the WINNT/system32 directory.. Informed Biomark they will need to install the latest patch to clean this virus... This is great! long live the !@#$%@#$^#$&% people who write these viruses. 08/13/2003 10:48 scott_li Dave alerted us to the a problem with the PRA data pc creating an excessive amount of files per day for some unknown reason. I suspected that it could have been intermittent power outages which didn't make alot of sense due to the pc's are on UPS's. I was lucky enough to be logged in to the PC and low and behold, a box had popped up and read the following. The system is shutting down, this shutdown was ititiated by NT AUTHORTY\SYSTEM. Windows must now restart because the remote procedure call service (RPC) terminated unexpectedly. So the pc IS rebooting itself due to the above error. Looked through Microsofts knowledge for some answers and fixes but is going to take some time to sort this one out. In the mean time, I suggest that we load all the current XP updates on both computers and do a hard reset rather than a soft boot. Will talk with biomark to see when the next scheduled site visit will be. With the current situation , we may want to disengage the uploader on PC1 and engage the uploader on PC2. 08/12/2003 09:43 acarson@ 08:TestTagFailure: I will check the level of the test tag during next site visit. There is no difference in noise levels from when the tag is read and when it fails. FDXB levels reach 100% and return to normal after the timer tag is fired. This is the only coil at PRA with this problem and no fish where detected while the test tag was fired. BEFORE: ~08-10 08/07/03 22:05:58 ALARM Noise report for Reader ID#08 ~08-10 08/07/03 22:05:58 ALARM Average: 2 % ~08-10 08/07/03 22:05:58 ALARM Peak: 17 % ~08-10 08/07/03 22:05:58 ALARM FDXB Peak: 19 % AFTER: ~08-10 08/07/03 22:06:58 ALARM MESSAGE: Single-shot test with Test Tag. ~08-10 08/07/03 22:06:58 ALARM PROBLEM: Test Tag Failed ~08-10 08/07/03 22:06:59 ALARM Noise report for Reader ID#08 ~08-10 08/07/03 22:06:59 ALARM Average: 2 % ~08-10 08/07/03 22:06:59 ALARM Peak: 12 % ~08-10 08/07/03 22:06:59 ALARM FDXB Peak: 100 % 07/09/2003 08:14 scottl@r 08:TestTagFailure: TT failure not of concern 06/30/2003 17:02 acarson@ 08:TestTagFailure: No reason for test tag not firing. After test tag fired a noise report showed FDXB Peak = 100%. Manually fired test tag from PCA and showed no problems. No problems since. 04/25/2003 08:59 acarson@ 03:ExcessiveNoise: Excessive Noise levels occurred during 21:04:07 - 23:00:50 on 04/24/03. I will contact GCPUD control room and check the event log. 04/13/2003 09:37 acarson@ 05:BadExcFreq,05:BadOscFreq,05:LowExcCurrent,05:TestTagFailure,06:LowExcCu rrent,06:Overrun,06:TestTagFailure,08:TestTagFailure: Alarms caused during biomark site visit. 04/13/2003 09:37 acarson@ 05:BadExcFreq,05:BadOscFreq,05:LowExcCurrent,05:TestTagFailure,06:LowExcCu rrent,06:Overrun,06:TestTagFailure,08:TestTagFailure: Alarms caused during biomark site visit. 04/11/2003 11:25 Scott_Li Correction to the previous entry, the system was brought online 4/10/03 not 3/10. 04/11/2003 09:19 Scott_Li The site platform was brought online with PTAGIS on 3/10/03 @ 1321 pst. Interrogation files that had accumulated since day 89.G was batched in groups of 8 and sent to PTAGIS. One note, This site was a victim of the DST gotchya. Minimon/PTTP and system clocks are now synchronized. 03/24/2003 15:42 Carter_S cea config for pra was setup. 03/21/2003 13:41 Dave I enabled site polling. 01/01/2003 12:19 Dave Initialized new event log for 2003. This is a new site definition. ####End of Event Log for PRA###