Timeline


and

07/10/18:

13:53 Ticket #283 (Monitoring SOHO data server) closed by jacob
fixed: SOHO received an update yesterday, indicating that our syncing process with the sohodata server works as intended end to end following the server rebuild. Our update scripts could use some tweaking, they have a high failure rate, but I've made some small changes to them already to no avail. I'll have to set up some intensive logging to see if I can catch exactly what fails in that script, but in the meantime my monitoring scripts are also going to be keeping a much closer eye on the soho db.

07/06/18:

15:50 Ticket #327 (Too many requests to vso3.stanford.edu from Kyung Hee University) closed by alisdair
fixed: Message from Tetsuya […]

07/05/18:

11:01 Ticket #327 (Too many requests to vso3.stanford.edu from Kyung Hee University) created by alisdair
Art reports that >100K requests were coming from 2 IP addresses at Kyung …

06/27/18:

13:16 Ticket #326 (October meeting agenda) created by niles
Need to get an agenda for this together bu the end of July at the latest. …

06/26/18:

14:30 Ticket #316 (The VSO feedback page does not work) closed by jacob
fixed
13:19 Ticket #323 (STEREO & AIA data not coming back on sunpy) closed by jacob
fixed: We discovered that perl was generally unable to load other modules while running vsoi_wsdl.cgi, and a reboot fixed the problem, revealing that this is more of a server issue than a problem within the code. While this problem persisted, we found that instances of vsoi_wsdl.cgi were running indefinitely and consuming 100% of cpu resources. I wrote a cron script that runs every 5 minutes to monitor all processes over 10 seconds and terminate any instances of vsoi_wsdl.cgi taking >95% of cpu power over those 10 seconds. In case that doesn't bring vso03 back up, the cron also logs that a process was killed and sends me an email so I can run a quick test query to verify that vso03 still works and reboot if it doesn't.

06/25/18:

08:50 Ticket #325 (Tom Bridgman reports an XML(?) error trying to retrieve data from GONG ...) created by alisdair
Tom Bridgman reports an XML(?) error trying to retrieve data from GONG …

06/21/18:

11:34 Ticket #324 (SOHO DB issues) closed by jacob
fixed
11:34 Ticket #324 (SOHO DB issues) created by jacob
Earlier today SOHO data went down on the vso. Running the update script …

06/18/18:

12:40 Ticket #323 (STEREO & AIA data not coming back on sunpy) reopened by jacob
Reopening because the same problem is back. After a little testing I have some information: The problem either exists in the core code or in the definition of the "$vso" object in the wsdl. The vso object in the wsdl cgi is defined as follows: our $vso = Physics::Solar::VSO::Core->new(tpool=>$tpool); Where $tpool is: our $tpool = Physics::Solar::VSO::Utils::ThreadPool?->new(4); The last line of code that runs in the cgi script is line 87: my @res = $vso->Query({version => $version, block => $block}); Which calls a member function of the vso object (Query), however prints from the first lines of Query in Core.pm do not show up in a live log file, meaning that the process never reaches Query in Core.pm. This leads me to believe that there is something wrong with the definition of the $vso object, but since we are seeing timeouts and not internal server errors. I also think there could be an issue with VSO::Utils::ThreadPool?.

06/15/18:

09:25 Ticket #323 (STEREO & AIA data not coming back on sunpy) closed by jacob
worksforme
09:25 Ticket #323 (STEREO & AIA data not coming back on sunpy) created by jacob
For a while any queries from SunPy to vso03 boulder were timing out. …

06/13/18:

08:36 Ticket #322 (API for keywords) created by niles
It would be nice if the keywords file was made available to the public …

06/12/18:

08:52 Ticket #315 (KSO data not searchable from IDL commandline.) closed by ed
fixed

06/11/18:

10:39 Ticket #321 (Address Dead Links on the Website) created by jacob
There are several dead links on the website, some of which point to …
Note: See TracTimeline for information about the timeline view.