[THREDDS #TWN-232939]: AWS THREDDS NEXRAD server down?
- Subject: [THREDDS #TWN-232939]: AWS THREDDS NEXRAD server down?
- Date: Tue, 18 Apr 2017 09:51:46 -0600
Actually, I was in contact from Illinois yesterday who was doing some
statistics--looked like against KBUF, getting a new volume every couple of
minutes. Nothing crazy, but sustained enough use to bring down the machine.
Anyhow, the problem was that the memory on the machine was filling up (the
micros only have 1GB). I'm hoping an extra GB of memory can solve the problem.
I'm already doing some pretty aggressive cleaning of the cache, so disk isn't
If you give me a heads up on days you're expecting heavy use, I can keep a
better watch on it. I'm pretty confident the bigger machine will help, though.
I'm also happy to bump up the instance to something even beefier for a couple
days if necessary.
> Hi Ryan,
> I wonder if that "someone" could have been me last night, as I was doing
> things like changing the site from Louisville for the single, most recent
> image, as well as changing the date and location for the animation.
> Although, it was probably only two times that I ran it before things went
> kablooey. I'm intending for our ATM350 students to use the server for their
> case study presentation that concludes the class in a couple weeks, so it
> would be good to have this quasi-stable, although of course I will have some
> backup plans.
> I found that on the THREDDS server I'm running on AWS for big weather web, I
> had to greatly reduce caching in order to keep the root file system from
> filling up, in case that was what the issue was here.
> I'll do some more testing today to see how the larger instance handles things!
> Kevin Tyle, Manager of Departmental Computing
> Dept. of Atmospheric & Environmental SciencesÂÂ
> University at Albany
> Earth Science 235, 1400 Washington
> Albany, NY 12222
> Email: address@hidden
> Phone: 518-442-4578ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
> -----Original Message-----
> From: Unidata THREDDS Support [mailto:address@hidden
> Sent: Tuesday, April 18, 2017 11:36 AM
> To: Tyle, Kevin R <address@hidden>
> Cc: address@hidden
> Subject: [THREDDS #TWN-232939]: AWS THREDDS NEXRAD server down?
> Someone else has been utilizing the server a lot, and it seems to be
> overwhelming the limited memory of the micro AWS instance we were hosting it
> on. I've bumped up the machine now to a bigger one now (all of 2GB of RAM!).
> Please feel free to beat on this machine so we can see if that solves the
> > Hi folks,
> > Last night I was using the THREDDS_Radar_Server_AWS Jupyter notebook to
> > interact with the Thredds server you are running on AWS to serve the Nexrad
> > 2 archive. While the first couple of attempts worked fine, I noticed that
> > the server stopped responding, and it looks to still be down this morning:
> > ConnectionError: HTTPConnectionPool(host='thredds-aws.unidata.ucar.edu',
> > port=80): Max retries exceeded with url:
> > /thredds/radarServer/nexrad/level2/S3/dataset.xml (Caused by
> > NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection
> > object at 0x2b70cd146750>: Failed to establish a new connection: [Errno
> > 111] Connection refused',))
> > Can you take a look and advise, please?
> Ticket Details
> Ticket ID: TWN-232939
> Department: Support THREDDS
> Priority: Normal
> Status: Closed
> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publicly available through the
> web. If you do not want to have your interactions made available in this
> way, you must let us know in each email you send to us.
Ticket ID: TWN-232939
Department: Support THREDDS
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata
inquiry tracking system and then made publicly available through the web. If
you do not want to have your interactions made available in this way, you must
let us know in each email you send to us.
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web. If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.