Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

UPP failed

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

qisionline

New member
I have three wrfout files that I want to convert into grib2 format with UPP. The script set is shown in the attachment, but an error is reported, and the error information is also given in the attachment.I tried to run ulimit -s unlimited , but it didn't work. :( I have also tried to run in docker, and the same error message appears.Can anyone help me?
/home/qisi/downloads/uppworks/test_case/wrfprd/wrfout_d01_2018-07-10_06:00:00
netcdf
grib2
2018-07-10_06:00:00
NCAR
EOF
+ rm fort.110 fort.14
+ ln -sf /home/qisi/downloads/uppworks/test_case/parm/wrf_cntrl.parm fort.14
+ [[ ARW == ARW ]]
+ /home/qisi/downloads/UPPV4.1/exec/unipost.exe
+ 1> unipost_d01.00.out 2>& 1
+ [[ ARW == ARW ]]
+ mv WRFPRS00.tm00 WRFPRS_d01.00
mv: cannot stat 'WRFPRS00.tm00': No such file or directory
+ [[ ARW == ARW ]]
+ ls -l WRFPRS_d01.00
ls: cannot access 'WRFPRS_d01.00': No such file or directory
+ err1=2
+ test 2 -ne 0
+ echo 'UNIPOST FAILED, EXITTING'
UNIPOST FAILED, EXITTING
+ exit
WrfType in getIVariable= 106
WrfType in getIVariable= 106
MAX ISLTYP= 14
GWVX XT_NCD GET FIELD 93600 93600 0
GWVX XT_NCD GET FIELD 93600 93600 0
GWVX XT_NCD GET FIELD 93600 93600 0
read past GDLAT
GWVX XT_NCD GET FIELD 93600 93600 0
read past GDLON
laststart,latlast B calling bcast= 12213203 36472095
laststart,latlast A calling bcast= 12213203 36472095
cant open file,params_grib2_tbl_new

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0 0x7f1576f7b2ed in ???
#1 0x7f1576f7a503 in ???
#2 0x7f15765df03f in ???
#3 0x7f157736b821 in ???
#4 0x7f1577c2c37a in ???
#5 0x7f1577d3e5ec in ???
#6 0x7f1577d7d02c in ???
#7 0x7f1577c202a2 in ???
#8 0x7f15765c1bf6 in ???
#9 0x7f1577c202d9 in ???
#10 0xffffffffffffffff in ???
./run_unipost: line 410: 1090: Memory fault(coredump)
 

Attachments

  • postxconfig-NT-WRF.txt
    16.7 KB · Views: 39
  • run_unipost.txt
    17.7 KB · Views: 44
  • unipost_d01.00.out.txt
    37.3 KB · Views: 45
Segmentation faults can be tricky to identify the root of the cause.

I see you are running with a single processor. The fix could be as simple as trying to run with multiple processors. (e.g. export RUN_COMMAND="mpirun -np 4 ${POSTEXEC}/unipost.exe - changed to 4 here, but you could choose np based on what would be ideal for your run)
 
hertneky said:
Segmentation faults can be tricky to identify the root of the cause.

I see you are running with a single processor. The fix could be as simple as trying to run with multiple processors. (e.g. export RUN_COMMAND="mpirun -np 4 ${POSTEXEC}/unipost.exe - changed to 4 here, but you could choose np based on what would be ideal for your run)


Thank you very much. After some attempts, it has been able to run normally.
 
Top