Project

General

Profile

Bug #11391

Zeek crashes on 2.5.0

Added by Zachary McGibbon 2 months ago. Updated 2 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Zeek
Target version:
-
Start date:
02/09/2021
Due date:
% Done:

0%

Estimated time:
Affected Version:
Affected Architecture:
amd64

Description

Trying to use zeek on 2.5.0 RC and I get a crash email and the service will not start. Also, chose 'sudo' category as there is no 'zeek' category yet.

User-Agent: ZeekControl 2.0.0

This crash report does not include a backtrace.  In order for crash reports to be useful when Zeek crashes, a backtrace is needed.

No core file found and gdb is not installed.  It is recommended to install gdb so that ZeekControl can output a backtrace if Zeek crashes.

Zeek 3.0.12
FreeBSD 12.2-STABLE

Zeek plugins:
Bro::Netmap - Packet acquisition via Netmap (dynamic, version 1.0.0)

==== No reporter.log

==== stderr.log
fatal error in /usr/local/share/zeek/zeekctl/standalone.zeek, line 3: can't find standalone-layout

==== stdout.log
max memory size             (kbytes, -m) unlimited
data seg size               (kbytes, -d) 33554432
virtual memory              (kbytes, -v) unlimited
core file size              (blocks, -c) unlimited

==== .cmdline
-i em1 -U .status -p zeekctl -p zeekctl-live -p standalone -p local -p zeek local.zeek zeekctl zeekctl/standalone zeekctl/auto

==== .env_vars
PATH=/usr/local/bin:/usr/local/share/zeekctl/scripts:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
ZEEKPATH=/usr/local/spool/installed-scripts-do-not-touch/site::/usr/local/spool/installed-scripts-do-not-touch/auto:/usr/local/share/zeek:/usr/local/share/zeek/policy:/usr/local/share/zeek/site
CLUSTER_NODE=

==== .status
TERMINATED [atexit]

==== No prof.log

==== No packet_filter.log

==== No loaded_scripts.log

--
[Automatically generated.]

History

#1 Updated by Jim Pingle 2 months ago

  • Category changed from sudo to Zeek

#2 Updated by Viktor Gurov 2 months ago

  • Status changed from New to Confirmed

running `zeekctl deploy` fixes this issue

Also available in: Atom PDF