# Abort trap (core dumped) on OpenBSD 6.0
**URL:** https://community.letsencrypt.org/t/abort-trap-core-dumped-on-openbsd-6-0/22371
**Category:** Server
**Created:** [November 8, 2016, 11:43pm UTC](https://community.letsencrypt.org/t/abort-trap-core-dumped-on-openbsd-6-0/22371 "2016-11-08T23:43:02Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@bonne](https://community.letsencrypt.org/u/bonne)
#### Post date: [November 8, 2016, 11:43pm UTC](https://community.letsencrypt.org/t/abort-trap-core-dumped-on-openbsd-6-0/22371/1 "2016-11-08T23:43:02Z")
About to sign a new certificate with letsencrypt/certbot on OpenBSD 6.0
I am doing a certbot -certonly -d [xxx.xxx.xxx](http://xxx.xxx.xxx)
and OpenBSD returns:
Abort trap (core dumped)
my /var/log/messages logs says:
python2.7(22408): mmap W^X violation
Googling this directs me to:
[http://undeadly.org/cgi?action=article&sid=20160527203200](http://undeadly.org/cgi?action=article&sid=20160527203200)
But I am not sure that I understand it.
How to move on on this error (especially when I am about to renew my certs)
Thanks, Lars.
---
### Author:  [@motoko](https://community.letsencrypt.org/u/motoko)
#### Post date: [November 9, 2016, 2:44am UTC](https://community.letsencrypt.org/t/abort-trap-core-dumped-on-openbsd-6-0/22371/2 "2016-11-09T02:44:34Z")
This looks to be an issue with Python itself, or perhaps one of the Python modules certbot uses. I’m not really sure how to go about finding the exact cause, unfortunately.
---
### Author:  [@bonne](https://community.letsencrypt.org/u/bonne)
#### Post date: [November 9, 2016, 9:40am UTC](https://community.letsencrypt.org/t/abort-trap-core-dumped-on-openbsd-6-0/22371/3 "2016-11-09T09:40:24Z")
What I do understand from the link above is that the BSD-guy does not like the “W^X” thing:
“W^X violations are no longer permitted by default”
… which as I see makes Letsencrypt unusable on OpenBSD. Especially when letsenc. needs to be renewed so often, it is a pain in the a…
)-:
Any workaround to this?
Regards, Lars.
---
### Author:  [@serverco](https://community.letsencrypt.org/u/serverco)
#### Post date: [November 9, 2016, 9:45am UTC](https://community.letsencrypt.org/t/abort-trap-core-dumped-on-openbsd-6-0/22371/4 "2016-11-09T09:45:07Z")
As far as I’m aware certbot is usually stable on BSD.
You could try one of the [alternative clients](https://letsencrypt.org/docs/client-options/), if you prefer, rather than debugging further with python.
---
### Author:  [@bonne](https://community.letsencrypt.org/u/bonne)
#### Post date: [November 9, 2016, 1:07pm UTC](https://community.letsencrypt.org/t/abort-trap-core-dumped-on-openbsd-6-0/22371/5 "2016-11-09T13:07:39Z")
The workaround is to add wxallowed to fstab like:
xxx.h /usr/local ffs rw,nodev,wxallowed 1 2
(-;
Regards, Lars.
---
### Author:  [@system](https://community.letsencrypt.org/u/system)
#### Post date: [December 9, 2016, 1:08pm UTC](https://community.letsencrypt.org/t/abort-trap-core-dumped-on-openbsd-6-0/22371/6 "2016-12-09T13:08:09Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.