Thread: Outage today for maximum of 3 hours starting at 10am Pacific due to hardware relocation

Started: 2013-12-04 16:33:16
Last activity: 2013-12-05 22:51:50
Topics: Web Services
Hello web service users,

IRIS Data Flow Planned Outage, December 4 2013
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The IRIS DMC will be offline for a maximum of three (3) hours on December 4th, 2013, starting at 10am Pacific Time. This is a planned outage and is due to hardware relocation to a new building.

This will impact all the IRIS websites (http://www.iris.edu and http://www.iris.edu/dms/), Web Services (http://service.iris.edu), and data flow in- and out-of the DMC.

Apologies for both the late notice and any inconvenience, and please plan accordingly.

- Rob Newman, IRIS DMC
_____________________________________________

Rob Newman
Lead Technology Architect, IRIS DMC
[e] rnewman<at>iris.washington.edu






  • Hello web services users,

    All DMC systems are back online and web services are functioning normally.

    Thanks for you patience.

    IRIS DMC

    On Dec 4, 2013, at 8:33 AM, Rob Newman <rnewman<at>iris.washington.edu> wrote:

    Hello web service users,

    IRIS Data Flow Planned Outage, December 4 2013
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    The IRIS DMC will be offline for a maximum of three (3) hours on December 4th, 2013, starting at 10am Pacific Time. This is a planned outage and is due to hardware relocation to a new building.

    This will impact all the IRIS websites (http://www.iris.edu and http://www.iris.edu/dms/), Web Services (http://service.iris.edu), and data flow in- and out-of the DMC.

    Apologies for both the late notice and any inconvenience, and please plan accordingly.

    - Rob Newman, IRIS DMC
    _____________________________________________

    Rob Newman
    Lead Technology Architect, IRIS DMC
    [e] rnewman<at>iris.washington.edu




    _______________________________________________
    webservices mailing list
    webservices<at>iris.washington.edu
    http://www.iris.washington.edu/mailman/listinfo/webservices



    • In the web page:
      https://seiscode.iris.washington.edu/projects/webserviceshell/wiki/Requirements_and_Recommendations
      it provides recommendations on how to run a BETA service.
      --------------------------------------
      URL recommendations

      URLs for production FDSN services should follow this format:

      http://YourDomain/fdsnws/...

      URLs for BETA FDSN services, if available, are recommended to follow this format:

      http://YourDomain/fdsnwsbeta/...

      Where '...' denotes the individual services (should they exist) that are supported at your data center, e.g. station, event, dataselect
      --------------------------------------

      However, using the IRIS Web Server Shell (wss), it appears that the
      for 2 web service services named "foo" with version "1", eg:
      fdsnws/foo/1/
      and fdsnwsbeta/foo/1/
      the wss would use the SAME configuration files in tomcat's wss-config dir,
      since the config files names include on the service name and version,
      but NOT the domain (fdsnws vs fdsnwsbeta):
      foo-1-log4j.properties
      foo-1-param.cfg
      foo-1-service.cfg

      We tried changing the version from 1 to beta1, but wss appears to be
      unhappy with this.

      Thanks for any suggestions.

      - Doug N
      --
      ------------------------------------------------------------------------
      Doug Neuhauser University of California, Berkeley
      doug<at>seismo.berkeley.edu Berkeley Seismological Laboratory
      Office: 510-642-0931 215 McCone Hall # 4760
      Fax: 510-643-5811 Berkeley, CA 94720-4760
      Remote: 530-752-5615 (Wed,Fri)

      • Doug:

        On tomcat startup there should be a system property set like

        …. -DwssConfigDir=/mypath/confdir

        The wss will then look in there for service config files.

        So if your service was deployed to
        http://myserver:8082/xyz/foo/2

        The WSS would look for:

        /mypath/confdir/foo-2-application.wadl
        /mypath/confdir/foo-2-param.cfg
        /mypath/confdir/foo-2-log4j.properties
        /mypath/confdir/foo-2-service.cfg

        When you do ps -eaf and look at the java process you should see something like " -DwssConfigDir=/mypath/confdir “ in there.
        That’s how the wss figures out where to look.

        You can’t run both beta and production together unless you name the services like

        production /fdsn/dataselect/1
        beta /fdsn/dataselectbeta/1

        and then have config files like

        dataselect-1-application.wadl
        and
        dataselectbeta-1-application.wadl

        But I don’t think you want to do that!
        You want it to look like

        /fdsn/dataselect/1

        /fdsnbeta/dataselet/1

        So that requires at least two tomcats.

        If you need to help setting up a bunch of tomcats, feel free to ask. I’ve got a nice way of doing it.

        -B

        On Dec 5, 2013, at 2:32 PM, Doug Neuhauser <doug<at>seismo.berkeley.edu> wrote:

        In the web page:
        https://seiscode.iris.washington.edu/projects/webserviceshell/wiki/Requirements_and_Recommendations
        it provides recommendations on how to run a BETA service.
        --------------------------------------
        URL recommendations

        URLs for production FDSN services should follow this format:

        http://YourDomain/fdsnws/...

        URLs for BETA FDSN services, if available, are recommended to follow this format:

        http://YourDomain/fdsnwsbeta/...

        Where '...' denotes the individual services (should they exist) that are supported at your data center, e.g. station, event, dataselect
        --------------------------------------

        However, using the IRIS Web Server Shell (wss), it appears that the
        for 2 web service services named "foo" with version "1", eg:
        fdsnws/foo/1/
        and fdsnwsbeta/foo/1/
        the wss would use the SAME configuration files in tomcat's wss-config dir,
        since the config files names include on the service name and version,
        but NOT the domain (fdsnws vs fdsnwsbeta):
        foo-1-log4j.properties
        foo-1-param.cfg
        foo-1-service.cfg

        We tried changing the version from 1 to beta1, but wss appears to be
        unhappy with this.

        Thanks for any suggestions.

        - Doug N
        --
        ------------------------------------------------------------------------
        Doug Neuhauser University of California, Berkeley
        doug<at>seismo.berkeley.edu Berkeley Seismological Laboratory
        Office: 510-642-0931 215 McCone Hall # 4760
        Fax: 510-643-5811 Berkeley, CA 94720-4760
        Remote: 530-752-5615 (Wed,Fri)
        _______________________________________________
        webservices mailing list
        webservices<at>iris.washington.edu
        http://www.iris.washington.edu/mailman/listinfo/webservices

        --------------------------------------
        Bruce R Weertman
        Software Engineer
        IRIS DMC
        1408 NE 45h St, Suite 201
        Seattle, WA 98105

        bruce<at>iris.washington.edu
        (206) 547-0393



Page built 06:11:12 | v.88350d0a