# Segmentation fault during UM recon

**URL:** <https://cms-helpdesk.ncas.ac.uk/t/segmentation-fault-during-um-recon/1338>\
**Category:** Unified Model\
**Tags:** ARCHER2\
**Created:** [13 February 2024 08:50 UTC](https://cms-helpdesk.ncas.ac.uk/t/segmentation-fault-during-um-recon/1338 "2024-02-13T08:50:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jtalib](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/jtalib/32/244_2.png) [@jtalib](https://cms-helpdesk.ncas.ac.uk/u/jtalib)\
**Post date:** [13 February 2024 08:50 UTC](https://cms-helpdesk.ncas.ac.uk/t/segmentation-fault-during-um-recon/1338/1 "2024-02-13T08:50:56Z")

</div>

Morning CMS,

I’m getting the following segmentation error when running the UM reconfiguration for job u-dd522.

> [0] exceptions: An exception was raised:11 (Segmentation fault)  
> [0] exceptions: the exception reports the extra information: Address not mapped to object.  
> [0] exceptions: whilst in a serial region  
> [0] exceptions: Task had pid=154616 on host nid003557  
> [0] exceptions: Program is “/work/n02/n02/jostal/cylc-run/u-dd522/share/fcm\_make\_um/build-recon/bin/um-recon.exe”  
> [0] exceptions: calling registered handler @ 0x0040d1b0

I’ve printed off extra diagnostics and it seems to stop running when reading the qrclim.biog ancillary. It’s never stopped here before?

Any ideas what could be the issue?

Please note, for this simulation I’ve added new prognostics and added additional UM source code. Surprised that it crashes at the recon.

Kind regards,  
Josh

---

<div class="post-metadata">

**Author:** ![grenville](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/grenville/32/29_2.png) [@grenville](https://cms-helpdesk.ncas.ac.uk/u/grenville)\
**Post date:** [13 February 2024 17:02 UTC](https://cms-helpdesk.ncas.ac.uk/t/segmentation-fault-during-um-recon/1338/2 "2024-02-13T17:02:03Z")

</div>

Josh

Where is the output?

Grenville

---

<div class="post-metadata">

**Author:** ![jtalib](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/jtalib/32/244_2.png) [@jtalib](https://cms-helpdesk.ncas.ac.uk/u/jtalib)\
**Post date:** [13 February 2024 18:13 UTC](https://cms-helpdesk.ncas.ac.uk/t/segmentation-fault-during-um-recon/1338/3 "2024-02-13T18:13:16Z")

</div>

Hi Grenville,

/work/n02/n02/jostal/cylc-run/u-dd522/log/job/20210411T0000Z/EastAfrica\_38p5L80\_4p4km\_RA2T\_um\_recon/NN contains the relevant job.err and job.out script.

Kind regards,  
Josh

---

<div class="post-metadata">

**Author:** ![jtalib](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/jtalib/32/244_2.png) [@jtalib](https://cms-helpdesk.ncas.ac.uk/u/jtalib)\
**Post date:** [14 February 2024 12:39 UTC](https://cms-helpdesk.ncas.ac.uk/t/segmentation-fault-during-um-recon/1338/4 "2024-02-14T12:39:19Z")

</div>

Solved! In my STASHmaster\_A file I was defining the LEVEL\_TYPE for my new prognostics wrong.

[https://code.metoffice.gov.uk/doc/um/latest/papers/umdp\_C04.pdf](https://code.metoffice.gov.uk/doc/um/latest/papers/umdp_C04.pdf) - is a very helpful document if you have a similar issue.

Thanks  
NCAS CMS

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/cms_support/original/1X/1fd2411499ffcbc299fe756cd5cdf26e44956558.png) [@system](https://cms-helpdesk.ncas.ac.uk/u/system)\
**Post date:** [15 February 2024 12:40 UTC](https://cms-helpdesk.ncas.ac.uk/t/segmentation-fault-during-um-recon/1338/5 "2024-02-15T12:40:02Z")

</div>

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.