Failed System Signal Code SN 127 Command or File Not Found

Questions and other topics related to UEMS 18.
Post Reply
ryip
Posts: 4
Joined: Thu Aug 10, 2017 9:16 pm

Failed System Signal Code SN 127 Command or File Not Found

Post by ryip » Thu Mar 29, 2018 7:32 pm

Trying to run sportlis, it fetches the files fine but when it gets to the computational domain it fails with a System Signal Code 127 Command or File Not Found. What is going on?

Code: Select all

[root@headnode splis]# ems_prep --dset sportlis


  Starting UEMS Program ems_prep (V18.3.1) on headnode at Thu Mar 29 19:24:38 2018 UTC


    I.   UEMS ems_prep Simulation Initialization Summary


           Simulation Start Time        : Thu Mar 29 19:00:00 2018 UTC
           Simulation End   Time        : Thu Mar 29 19:00:00 2018 UTC
           Boundary Condition Frequency : 360 Minutes (Forecast dataset)
           Initial Condition Dataset    : SPORTLIS
           Boundary Condition Dataset   : SPORTLIS
           Static Surface Datasets      : None
           Land Surface Datasets        : None
           Aerosol Climatology Dataset  : QNWFA_QNIFA_SIGMA_MONTHLY.dat


    II.  Collecting the initialization datasets for your simulation

           *  Searching for SPORTLIS files to use as model initial and boundary conditions

              Initiating HTTP connection to geo.msfc.nasa.gov

                -> Checking if available : /SPoRT/modeling/lis/conus3km/sportlis_conus3km_model_20180329_1900.grb2 - Not Available (Failed to connect to host)

              Initiating HTTP connection to ems3.comet.ucar.edu

                -> Checking if available : /data/grib/sportlis/201803/2018032919.sportlis_conus3km.grb2 - Available (21.14 MB)
                -> Bring'n it home to you: /data/grib/sportlis/201803/2018032919.sportlis_conus3km.grb2 - Success (3.16 MB/s)



         Excellent! - Your master plan is working!


    III. Create the WPS intermediate format files

           *  Processing sportlis files for initial and boundary conditions  - Success

         Intermediate file processing completed in 1 second


    IV.  Horizontal interpolation of intermediate files to the computational domain

           *  Interpolating fields to the computational domain (15 CPUs) - Failed (System Signal Code (SN) : 127 (Command or File Not Found))


       ☠  The interpolation of data to the computational domain failed, which bites.


    Your UEMS Prep party was busted at Thu Mar 29 19:25:04 2018 UTC - Ya know, 'cause stuff just happens

  You can sometimes hear Tibetan Monks chant: "Think Globally, Model Locally!"

JMeans
Posts: 16
Joined: Wed Jan 16, 2013 7:34 am

Re: Failed System Signal Code SN 127 Command or File Not Found

Post by JMeans » Thu Apr 26, 2018 7:49 pm

I don't have the answer but I'm getting exactly the same error message, initialized by gfsp25. I'd like to know what the answer is also.

jackq7a
Posts: 11
Joined: Tue Oct 18, 2011 2:40 pm

Re: Failed System Signal Code SN 127 Command or File Not Found

Post by jackq7a » Tue May 29, 2018 6:36 pm

I ran into this same problem and the reason why I got it was that I set up the domain wrong. I used a different projection and it worked a-ok.

Canuck64
Posts: 33
Joined: Tue Sep 04, 2012 10:41 pm
Contact:

Re: Failed System Signal Code SN 127 Command or File Not Found

Post by Canuck64 » Tue May 29, 2018 9:19 pm

This won't work because Sportlis is a land surface model and can't be used for initial or boundary conditions. You need to run with the other data sets, such as NAM, GFS, etc. The sportlis only works when you pass the command switch --lsm sportlis.

So, your command should be "ems_prep --dset nam (as an example) --date 20180528 --cycle 12 --lsm sportlis"

Post Reply

Who is online

Users browsing this forum: Baidu [Spider] and 1 guest