Cloudy in the morning but clear by mid-day. A very pleasant afternoon with highs in the upper 60's/lower 70's again.
Laura went with Chris and the Enterprise Risk Management person (Cliff??) to various sites today, and I believe they were joined by Terry and Brigitte who were up from Oxnard today. The WV at ISS2 was acting up again on Nagios, so I asked Laura to check the cables when they were there. All cables were seated just fine, so we power cycled the Trimble box and that seemed to work. I only power cycled the sensor when I was out there a couple of days ago. Will keep an eye on it and repeat the procedure if problem persists. I did spend some time today looking for the screw pins that hold the DB9 connector to the back of the Trimble, as they are missing currently and the cable is being held on by two zip ties. No luck at any hardware store or the local Best Buy. I will look into ordering some from Digikey if I can't find a substitute at the hardware store so as to eliminate a poor DB9 connection as a possible error source.
At ISS3, Laura found an error message on the ceilometer monitor and it appeared that the hard drive, or at lease part of it, had reached capacity. See comments in this thread for details: iss3 data check and ceilometer PC problems. Cleaning out the C:\temp folder on the computer, rebooting, and restarting software has resolved the issue as of drive 1930 PDT this evening. Again, will monitor and repeat procedure if problem persists.
I stopped by ISS1 late this afternoon to the check on the lidar as there were several red errors in Nagios again. The system was scanning as I approached and the tool running in Chrome on the laptop (forget its name) showed that the servers of the lidar were also running. Bill did some remote investigation and determined nothing was askew. It looks as those there is some lag in the data getting moved about, so the errors in Nagios are not critical. I will wait for guidance from Bill (or someone else) if and when these become an issue that needs attention.
3 Comments
William Brown
I noticed that radxconvert is not keeping up with the raw data. Ie: over each of the past few days there's been about 500 - 600 raw data files (which is about right), but many fewer cfradial files being produced by radxconvert. I suspect there have been delays in the raw files but they eventually come in - however the radxconvert process is not going back and filling in the gaps. I emailed Isabel about this and she can hopefully investigate.
Isabel Suhr
The radxconvert and hawkeye processes were originally set to only process data from the most recent two hours, to avoid the case of trying a few bad files over and over again. With the lidar taking so long to do the downloads, the recently downloaded files end up being more than 2 hours old by the time the lidar script calls the processes. I've upped that limit to the last 24 hours, so that should fix the lidar processed data checks in nagios.
Isabel Suhr
I backfilled the cfradial and hawkeye files on the data manager, so all the plots should be browseable on the data manager. I started a data transfer to EOL, so the plots on barolo should be updated soon too.