# Centos 8.4 core dump

**URL:** <https://community.zeek.org/t/centos-8-4-core-dump/6369>\
**Category:** Zeek\
**Created:** [June 26, 2021, 5:26pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369 "2021-06-26T17:26:02Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Monah\_Baki](https://avatars.discourse-cdn.com/v4/letter/m/d6d6ee/32.png) [@Monah\_Baki](https://community.zeek.org/u/Monah_Baki)\
**Post date:** [June 26, 2021, 5:26pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/1 "2021-06-26T17:26:02Z")

</div>

Hi all,

I tried installing Zeek 4.0.1 and 4.0.2

[root@marvin zeek-4.0.2]# zeekctl deploy  
Segmentation fault (core dumped)  
[root@marvin zeek-4.0.2]# cat /etc/centos-release  
CentOS Linux release 8.4.2105

Doesn’t give me any other info. I was running 4.0.1 before I updated to 4.0.2, now both version I get a Seg fault.

Thanks  
Monah

---

<div class="post-metadata">

**Author:** ![Richard\_Bejtlich](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/richard_bejtlich/32/597_2.png) [@Richard\_Bejtlich](https://community.zeek.org/u/Richard_Bejtlich)\
**Post date:** [June 26, 2021, 5:51pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/2 "2021-06-26T17:51:33Z")

</div>

Hello,

Can you explain how you tried to install Zeek? Sometimes a segmentation fault is the result of trying to run a binary compiled for another system.

Sincerely,

Richard

---

<div class="post-metadata">

**Author:** ![Monah\_Baki](https://avatars.discourse-cdn.com/v4/letter/m/d6d6ee/32.png) [@Monah\_Baki](https://community.zeek.org/u/Monah_Baki)\
**Post date:** [June 26, 2021, 5:54pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/3 "2021-06-26T17:54:58Z")

</div>

Hi Richard,

I downloaded from [https://download.zeek.org/zeek-4.0.2.tar.gz](https://download.zeek.org/zeek-4.0.2.tar.gz)

and ran ./configure && make && make install

Just found out in /var/log/messages the following:

Jun 26 13:00:05 marvin systemd-coredump[17450]: Process 17423 (zeekctl) of user 0 dumped core.#012#012Stack trace of thread 17423:#012#0 0x0000000000000000 n/a (n/a)#012#1 0x00007f379f46fdf7 \_\_new\_exitfn (libc.so.6)#012#2 0x00007f379f46fe9c \_\_internal\_atexit (libc.so.6)#012#3 0x00007f37a0bdd8ba call\_init.part.0 (ld-linux-x86-64.so.2)#012#4 0x00007f37a0bdd9ba \_dl\_init (ld-linux-x86-64.so.2)#012#5 0x00007f379f56e27c \_dl\_catch\_exception (libc.so.6)#012#6 0x00007f37a0be1e8e dl\_open\_worker (ld-linux-x86-64.so.2)#012#7 0x00007f379f56e224 \_dl\_catch\_exception (libc.so.6)#012#8 0x00007f37a0be16b1 \_dl\_open (ld-linux-x86-64.so.2)#012#9 0x00007f379fd821ea dlopen\_doit (libdl.so.2)#012#10 0x00007f379f56e224 \_dl\_catch\_exception (libc.so.6)#012#11 0x00007f379f56e2e3 \_dl\_catch\_error (libc.so.6)#012#12 0x00007f379fd82969 \_dlerror\_run (libdl.so.2)#012#13 0x00007f379fd8228a dlopen@@GLIBC\_2.2.5 (libdl.so.2)#012#14 0x00007f37a0394aca \_PyImport\_FindSharedFuncptr (libpython3.6m.so.1.0)#012#15 0x00007f37a03a49ca \_PyImport\_LoadDynamicModuleWithSpec (libpython3.6m.so.1.0)#012#16 0x00007f37a03a4c11 \_imp\_create\_dynamic (libpython3.6m.so.1.0)#012#17 0x00007f37a033b202 PyCFunction\_Call (libpython3.6m.so.1.0)#012#18 0x00007f37a0348e2d \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#19 0x00007f37a029eb54 \_PyEval\_EvalCodeWithName (libpython3.6m.so.1.0)#012#20 0x00007f37a031f540 fast\_function (libpython3.6m.so.1.0)#012#21 0x00007f37a0342527 call\_function (libpython3.6m.so.1.0)#012#22 0x00007f37a0343168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#23 0x00007f37a031f358 fast\_function (libpython3.6m.so.1.0)#012#24 0x00007f37a0342527 call\_function (libpython3.6m.so.1.0)#012#25 0x00007f37a0343168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#26 0x00007f37a031f358 fast\_function (libpython3.6m.so.1.0)#012#27 0x00007f37a0342527 call\_function (libpython3.6m.so.1.0)#012#28 0x00007f37a0343168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#29 0x00007f37a031f358 fast\_function (libpython3.6m.so.1.0)#012#30 0x00007f37a0342527 call\_function (libpython3.6m.so.1.0)#012#31 0x00007f37a0343168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#32 0x00007f37a031f358 fast\_function (libpython3.6m.so.1.0)#012#33 0x00007f37a0342527 call\_function (libpython3.6m.so.1.0)#012#34 0x00007f37a0343168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#35 0x00007f37a02a0062 \_PyFunction\_FastCallDict (libpython3.6m.so.1.0)#012#36 0x00007f37a02a0e3e \_PyObject\_FastCallDict (libpython3.6m.so.1.0)#012#37 0x00007f37a038580e \_PyObject\_CallMethodIdObjArgs (libpython3.6m.so.1.0)#012#38 0x00007f37a02a14e4 PyImport\_ImportModuleLevelObject (libpython3.6m.so.1.0)#012#39 0x00007f37a033b336 PyCFunction\_Call (libpython3.6m.so.1.0)#012#40 0x00007f37a0348e2d \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#41 0x00007f37a029eb54 \_PyEval\_EvalCodeWithName (libpython3.6m.so.1.0)#012#42 0x00007f37a031f540 fast\_function (libpython3.6m.so.1.0)#012#43 0x00007f37a0342527 call\_function (libpython3.6m.so.1.0)#012#44 0x00007f37a0343168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#45 0x00007f37a029f4c6 \_PyEval\_EvalCodeWithName (libpython3.6m.so.1.0)#012#46 0x00007f37a02a025a \_PyFunction\_FastCallDict (libpython3.6m.so.1.0)#012#47 0x00007f37a02a0e3e \_PyObject\_FastCallDict (libpython3.6m.so.1.0)#012#48 0x00007f37a038580e \_PyObject\_CallMethodIdObjArgs (libpython3.6m.so.1.0)#012#49 0x00007f37a02a1443 PyImport\_ImportModuleLevelObject (libpython3.6m.so.1.0)#012#50 0x00007f37a03463d9 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#51 0x00007f37a029eb54 \_PyEval\_EvalCodeWithName (libpython3.6m.so.1.0)#012#52 0x00007f37a029fef3 PyEval\_EvalCode (libpython3.6m.so.1.0)#012#53 0x00007f37a03b0cb0 builtin\_exec (libpython3.6m.so.1.0)#012#54 0x00007f37a033b202 PyCFunction\_Call (libpython3.6m.so.1.0)#012#55 0x00007f37a0348e2d \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#56 0x00007f37a029eb54 \_PyEval\_EvalCodeWithName (libpython3.6m.so.1.0)#012#57 0x00007f37a031f540 fast\_function (libpython3.6m.so.1.0)#012#58 0x00007f37a0342527 call\_function (libpython3.6m.so.1.0)#012#59 0x00007f37a0343168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#60 0x00007f37a031f358 fast\_function (libpython3.6m.so.1.0)#012#61 0x00007f37a0342527 call\_function (libpython3.6m.so.1.0)#012#62 0x00007f37a0343168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#63 0x00007f37a031f358 fast\_function (libpython3.6m.so.1.0)  
Jun 26 13:00:05 marvin systemd[1]: systemd-coredump@2-17449-0.service: Succeeded.  
Jun 26 13:22:15 marvin su[18896]: (to root) mbaki on pts/0  
Jun 26 13:23:38 marvin kernel: zeekctl[21476]: segfault at 0 ip 0000000000000000 sp 00007ffe533aa588 error 14 in platform-python3.6[55659bf11000+2000]  
Jun 26 13:23:38 marvin kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.  
Jun 26 13:23:38 marvin systemd[1]: Started Process Core Dump (PID 21485/UID 0).  
Jun 26 13:23:39 marvin systemd-coredump[21486]: Process 21476 (zeekctl) of user 0 dumped core.#012#012Stack trace of thread 21476:#012#0 0x0000000000000000 n/a (n/a)#012#1 0x00007f7560b27df7 \_\_new\_exitfn (libc.so.6)#012#2 0x00007f7560b27e9c \_\_internal\_atexit (libc.so.6)#012#3 0x00007f75622958ba call\_init.part.0 (ld-linux-x86-64.so.2)#012#4 0x00007f75622959ba \_dl\_init (ld-linux-x86-64.so.2)#012#5 0x00007f7560c2627c \_dl\_catch\_exception (libc.so.6)#012#6 0x00007f7562299e8e dl\_open\_worker (ld-linux-x86-64.so.2)#012#7 0x00007f7560c26224 \_dl\_catch\_exception (libc.so.6)#012#8 0x00007f75622996b1 \_dl\_open (ld-linux-x86-64.so.2)#012#9 0x00007f756143a1ea dlopen\_doit (libdl.so.2)#012#10 0x00007f7560c26224 \_dl\_catch\_exception (libc.so.6)#012#11 0x00007f7560c262e3 \_dl\_catch\_error (libc.so.6)#012#12 0x00007f756143a969 \_dlerror\_run (libdl.so.2)#012#13 0x00007f756143a28a dlopen@@GLIBC\_2.2.5 (libdl.so.2)#012#14 0x00007f7561a4caca \_PyImport\_FindSharedFuncptr (libpython3.6m.so.1.0)#012#15 0x00007f7561a5c9ca \_PyImport\_LoadDynamicModuleWithSpec (libpython3.6m.so.1.0)#012#16 0x00007f7561a5cc11 \_imp\_create\_dynamic (libpython3.6m.so.1.0)#012#17 0x00007f75619f3202 PyCFunction\_Call (libpython3.6m.so.1.0)#012#18 0x00007f7561a00e2d \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#19 0x00007f7561956b54 \_PyEval\_EvalCodeWithName (libpython3.6m.so.1.0)#012#20 0x00007f75619d7540 fast\_function (libpython3.6m.so.1.0)#012#21 0x00007f75619fa527 call\_function (libpython3.6m.so.1.0)#012#22 0x00007f75619fb168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#23 0x00007f75619d7358 fast\_function (libpython3.6m.so.1.0)#012#24 0x00007f75619fa527 call\_function (libpython3.6m.so.1.0)#012#25 0x00007f75619fb168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#26 0x00007f75619d7358 fast\_function (libpython3.6m.so.1.0)#012#27 0x00007f75619fa527 call\_function (libpython3.6m.so.1.0)#012#28 0x00007f75619fb168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#29 0x00007f75619d7358 fast\_function (libpython3.6m.so.1.0)#012#30 0x00007f75619fa527 call\_function (libpython3.6m.so.1.0)#012#31 0x00007f75619fb168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#32 0x00007f75619d7358 fast\_function (libpython3.6m.so.1.0)#012#33 0x00007f75619fa527 call\_function (libpython3.6m.so.1.0)#012#34 0x00007f75619fb168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#35 0x00007f7561958062 \_PyFunction\_FastCallDict (libpython3.6m.so.1.0)#012#36 0x00007f7561958e3e \_PyObject\_FastCallDict (libpython3.6m.so.1.0)#012#37 0x00007f7561a3d80e \_PyObject\_CallMethodIdObjArgs (libpython3.6m.so.1.0)#012#38 0x00007f75619594e4 PyImport\_ImportModuleLevelObject (libpython3.6m.so.1.0)#012#39 0x00007f75619f3336 PyCFunction\_Call (libpython3.6m.so.1.0)#012#40 0x00007f7561a00e2d \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#41 0x00007f7561956b54 \_PyEval\_EvalCodeWithName (libpython3.6m.so.1.0)#012#42 0x00007f75619d7540 fast\_function (libpython3.6m.so.1.0)#012#43 0x00007f75619fa527 call\_function (libpython3.6m.so.1.0)#012#44 0x00007f75619fb168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#45 0x00007f75619574c6 \_PyEval\_EvalCodeWithName (libpython3.6m.so.1.0)#012#46 0x00007f756195825a \_PyFunction\_FastCallDict (libpython3.6m.so.1.0)#012#47 0x00007f7561958e3e \_PyObject\_FastCallDict (libpython3.6m.so.1.0)#012#48 0x00007f7561a3d80e \_PyObject\_CallMethodIdObjArgs (libpython3.6m.so.1.0)#012#49 0x00007f7561959443 PyImport\_ImportModuleLevelObject (libpython3.6m.so.1.0)#012#50 0x00007f75619fe3d9 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#51 0x00007f7561956b54 \_PyEval\_EvalCodeWithName (libpython3.6m.so.1.0)#012#52 0x00007f7561957ef3 PyEval\_EvalCode (libpython3.6m.so.1.0)#012#53 0x00007f7561a68cb0 builtin\_exec (libpython3.6m.so.1.0)#012#54 0x00007f75619f3202 PyCFunction\_Call (libpython3.6m.so.1.0)#012#55 0x00007f7561a00e2d \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#56 0x00007f7561956b54 \_PyEval\_EvalCodeWithName (libpython3.6m.so.1.0)#012#57 0x00007f75619d7540 fast\_function (libpython3.6m.so.1.0)#012#58 0x00007f75619fa527 call\_function (libpython3.6m.so.1.0)#012#59 0x00007f75619fb168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#60 0x00007f75619d7358 fast\_function (libpython3.6m.so.1.0)#012#61 0x00007f75619fa527 call\_function (libpython3.6m.so.1.0)#012#62 0x00007f75619fb168 \_PyEval\_EvalFrameDefault (libpython3.6m.so.1.0)#012#63 0x00007f75619d7358 fast\_function (libpython3.6m.so.1.0)

Thanks  
Monah

---

<div class="post-metadata">

**Author:** ![Monah\_Baki](https://avatars.discourse-cdn.com/v4/letter/m/d6d6ee/32.png) [@Monah\_Baki](https://community.zeek.org/u/Monah_Baki)\
**Post date:** [June 26, 2021, 7:38pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/4 "2021-06-26T19:38:09Z")

</div>

I went and removed and reinstalled python36,

Still getting a seg fault, but /var/log/messages just shows:

Jun 26 15:33:01 marvin kernel: zeekctl[27265]: segfault at 0 ip 0000000000000000 sp 00007fff102fc8e8 error 14 in platform-python3.6[559d9b3bd000+2000]  
Jun 26 15:33:01 marvin kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.

---

<div class="post-metadata">

**Author:** ![Monah\_Baki](https://avatars.discourse-cdn.com/v4/letter/m/d6d6ee/32.png) [@Monah\_Baki](https://community.zeek.org/u/Monah_Baki)\
**Post date:** [June 26, 2021, 10:16pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/5 "2021-06-26T22:16:52Z")

</div>

I installed it as the following:

cd /etc/yum.repos.d/  
wget [https://download.opensuse.org/repositories/security:zeek/CentOS\_8\_Stream/security:zeek.repo](https://download.opensuse.org/repositories/security:zeek/CentOS_8_Stream/security:zeek.repo)  
yum install zeek

It worked like a charm.

Monah

---

<div class="post-metadata">

**Author:** ![ericooi](https://avatars.discourse-cdn.com/v4/letter/e/ecae2f/32.png) [@ericooi](https://community.zeek.org/u/ericooi)\
**Post date:** [June 28, 2021, 9:07pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/6 "2021-06-28T21:07:21Z")

</div>

Just ran into this myself. Someone also messaged me on Twitter experiencing the same issue. For reference, I just upgraded to CentOS 8.4 as well on one of my sensors. Notably, I was able to update to 4.0.2 just fine on my CentOS 7 sensor and then realized I’ve been using gcc 9.x instead of the default one that it came with.

So I installed gcc 9.x on my CentOS 8.4 sensor, recompiled, and it worked.

[https://stackoverflow.com/questions/61590926/how-to-install-gcc-g-9-on-centos-8-docker-centoslatest](https://stackoverflow.com/questions/61590926/how-to-install-gcc-g-9-on-centos-8-docker-centoslatest)

Hope that helps,  
Eric

---

<div class="post-metadata">

**Author:** ![Tim\_Wojtulewicz](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/tim_wojtulewicz/32/594_2.png) [@Tim\_Wojtulewicz](https://community.zeek.org/u/Tim_Wojtulewicz)\
**Post date:** [June 28, 2021, 9:18pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/7 "2021-06-28T21:18:08Z")

</div>

This backtrace looks like the bug reported in [https://github.com/zeek/broker/issues/187](https://github.com/zeek/broker/issues/187). Dominik has a fix ready for it but it’ll require a new version of CAF so we’re holding waiting for that to happen. In the meantime, can you see if passing —disable-python to your configure fixes it? It’s odd that no one has run into this before, and you’re at least the second and third people who have reported it recently. I don’t think there were significant changes to broker and the related code in 4.0.2 so I’m not entirely sure why it’s popping up now.

As for compiler versions, our CI builds use GCC 8.3.1 for our CentOS 8 builds.

Tim

---

<div class="post-metadata">

**Author:** ![ericooi](https://avatars.discourse-cdn.com/v4/letter/e/ecae2f/32.png) [@ericooi](https://community.zeek.org/u/ericooi)\
**Post date:** [June 28, 2021, 9:21pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/8 "2021-06-28T21:21:25Z")

</div>

Yeah i thought it was weird too. I had 4.0.1 running fine on CentOS 8.3. CentOS 8.4 was just released and perhaps something changed with that upgrade that caused this. Are you building on CentOS 8.4 with gcc 8.3.1?

---

<div class="post-metadata">

**Author:** ![Tim\_Wojtulewicz](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/tim_wojtulewicz/32/594_2.png) [@Tim\_Wojtulewicz](https://community.zeek.org/u/Tim_Wojtulewicz)\
**Post date:** [June 28, 2021, 10:01pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/9 "2021-06-28T22:01:50Z")

</div>

It looks like Cirrus is using 8.3.2011, which is likely the version of the docker instance from centos:8 that they have cached. I’ll ask if they can upgrade it, and I’ll run a build locally to see if we can get this sorted out.

Tim

---

<div class="post-metadata">

**Author:** ![Tim\_Wojtulewicz](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/tim_wojtulewicz/32/594_2.png) [@Tim\_Wojtulewicz](https://community.zeek.org/u/Tim_Wojtulewicz)\
**Post date:** [June 28, 2021, 10:03pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/10 "2021-06-28T22:03:07Z")

</div>

Actually I went to look at what DockerHub has for CentOS, and they’re still on 8.3.2011 as well for both centos:8 and centos:latest.

Tim

---

<div class="post-metadata">

**Author:** ![ericooi](https://avatars.discourse-cdn.com/v4/letter/e/ecae2f/32.png) [@ericooi](https://community.zeek.org/u/ericooi)\
**Post date:** [June 28, 2021, 10:04pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/11 "2021-06-28T22:04:20Z")

</div>

Ah, that makes sense.

---

<div class="post-metadata">

**Author:** ![Tim\_Wojtulewicz](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/tim_wojtulewicz/32/594_2.png) [@Tim\_Wojtulewicz](https://community.zeek.org/u/Tim_Wojtulewicz)\
**Post date:** [June 28, 2021, 11:49pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/12 "2021-06-28T23:49:29Z")

</div>

I can confirm that this is happening on CentOS 8.4 using the built-in compiler. I need to recheck 8.3. I generally don’t use zeekctl since I’m not running a cluster for most of my work. I’ll see if I can get this bumped up in priority since it’s clearly happening on the release branch too.

---

<div class="post-metadata">

**Author:** ![ericooi](https://avatars.discourse-cdn.com/v4/letter/e/ecae2f/32.png) [@ericooi](https://community.zeek.org/u/ericooi)\
**Post date:** [June 28, 2021, 11:50pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/13 "2021-06-28T23:50:07Z")

</div>

Cool, thanks Tim.

---

<div class="post-metadata">

**Author:** ![Monah\_Baki](https://avatars.discourse-cdn.com/v4/letter/m/d6d6ee/32.png) [@Monah\_Baki](https://community.zeek.org/u/Monah_Baki)\
**Post date:** [June 29, 2021, 12:46am UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/14 "2021-06-29T00:46:28Z")

</div>

Hi Tim,

I reinstalled it with the ./configure --disable-python && make && make install, and it worked.

Thanks  
Monah

---

<div class="post-metadata">

**Author:** ![Tim\_Wojtulewicz](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/tim_wojtulewicz/32/594_2.png) [@Tim\_Wojtulewicz](https://community.zeek.org/u/Tim_Wojtulewicz)\
**Post date:** [July 6, 2021, 9:04pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/15 "2021-07-06T21:04:26Z")

</div>

This should now be fixed in the v4.0.3 release that came out today.

Tim

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\
**Post date:** [May 6, 2022, 3:47pm UTC](https://community.zeek.org/t/centos-8-4-core-dump/6369/16 "2022-05-06T15:47:42Z")

</div>


