Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 31
Posts: 31   Pages: 4   [ Previous Page | 1 2 3 4 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 9088 times and has 30 replies Next Thread
adriverhoef
Master Cruncher
The Netherlands
Joined: Apr 3, 2009
Post Count: 2346
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Error: SIGSEGV: segmentation violation, process exited with code 193 (0xc1, -63)

The first segmentation violation workunit reported in 2023 (at least nobody else reported one):

workunit 241822746
App: Africa Rainfall Project
Workunit: ARP1_0031151_128
Created: 2023-01-07T02:05:54
Quorum: 2
Replication: 2

ARP1_0031151_128_0 Debian GNU/L Error 2023-01-07T02:20:12 2023-01-07T08:56:05 5.50/5.59 275.9/0.0
ARP1_0031151_128_1 Arch Linux Error 2023-01-07T02:20:42 2023-01-07T11:19:56 4.06/4.16 334.0/0.0
ARP1_0031151_128_2 Linux Ubuntu Error 2023-01-07T08:56:11 2023-01-07T21:10:29 5.22/5.22 238.8/0.0
ARP1_0031151_128_3 Fedora Linux Error 2023-01-07T11:20:04 2023-01-07T15:44:16 4.35/4.37 36.3/0.0
ARP1_0031151_128_4 Linux Ubuntu Error 2023-01-07T15:45:02 2023-01-07T20:00:14 4.19/4.19 279.7/0.0
ARP1_0031151_128_5 Linux Ubuntu SAbrt 2023-01-07T20:00:31 2023-01-07T22:15:48 0.00/0.00 0.0/0.0
---------------------------------------------------------------------------------------------------------------------------------------
Details:
ARP1_0031151_128_0  Debian GNU/L  Error  2023-01-07T02:20:12  2023-01-07T08:56:05    5.50/5.59     275.9/0.0   
Devicename: debian
Logfile:
<core_client_version>7.16.16</core_client_version>
<message>
process exited with code 193 (0xc1, -63)</message>
<stderr_txt>
INFO: Initializing
INFO: No state to restore. Start from the beginning.
Starting WRFMain
[04:45:38] INFO: Checkpoint taken at 2019-03-14_06:00:00
[06:35:40] INFO: Checkpoint taken at 2019-03-14_12:00:00
[08:19:51] INFO: Checkpoint taken at 2019-03-14_18:00:00
SIGSEGV: segmentation violation
Stack trace (17 frames):
[0x2d13b72]
[0x2da0400]
[0x1ed9107]
[0x1e9c664]
[0x1e9444a]
[0x1e8997c]
[0x188518c]
[0x1b6f8e2]
[0x135f570]
[0x11f86d4]
[0x5848b7]
[0x448f61]
[0x4475c9]
[0x440967]
[0x2eb2344]
[0x2eb25c1]
[0x405466]

Exiting...

</stderr_txt>
(---snip---8<---snip---8<---snip---)

I was able to capture the last 9700 lines from stdout.txt. Its last line was:
Timing for main: time 2019-03-14_20:40:48 on domain   1:    4.26186 elapsed seconds

From namelist.input: time_step=36,
----------------------------------------
[Edit 3 times, last edit by adriverhoef at Jan 9, 2023 11:29:41 AM]
[Jan 7, 2023 4:02:30 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 31   Pages: 4   [ Previous Page | 1 2 3 4 ]
[ Jump to Last Post ]
Post new Thread