# Errors in workers using Spicy 1.2.0 **URL:** \ **Category:** Zeek\ **Tags:** spicy\ **Created:** [August 3, 2021, 11:23am UTC](https://community.zeek.org/t/errors-in-workers-using-spicy-1-2-0/6387 "2021-08-03T11:23:37Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![clopmz](https://avatars.discourse-cdn.com/v4/letter/c/ebca7d/32.png) [@clopmz](https://community.zeek.org/u/clopmz)\ **Post date:** [August 3, 2021, 11:23am UTC](https://community.zeek.org/t/errors-in-workers-using-spicy-1-2-0/6387/1 "2021-08-03T11:23:37Z")
Hi all, After some problems to install spicy 1.1.0 in my Zeek cluster under FreeBSD 13-p3, this morning I have tried to install spicy 1.2.0 an all works as expected. Good work!! … But after installing spicy-plugin and spicy-analysers and executing “zeekctl deploy” (only in manager side) the following error appears in all workers: root@stirling:/nsm/zeek/spool/idps-prod # more stderr.log error in /opt/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /opt/zeek/lib/zeek/plugins/packages/spicy-plugin//lib/\_Zeek-Spicy.freebsd-amd64.so: Shared object "libhilti.so" not found, required by "\_Zeek-Spicy.freebsd-amd64.so" fatal error in /opt/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors Do I need to install spicy in all Zeek cluster components: workers, managers, loggers, etc? Best regards, C. L. Martinez ---
**Author:** ![Benjamin\_Bannier](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/benjamin_bannier/32/595_2.png) [@Benjamin\_Bannier](https://community.zeek.org/u/Benjamin_Bannier)\ **Post date:** [August 3, 2021, 1:54pm UTC](https://community.zeek.org/t/errors-in-workers-using-spicy-1-2-0/6387/2 "2021-08-03T13:54:35Z")
Hi Carlos, Moving this to the Spicy mailing list. > After some problems to install spicy 1.1.0 in my Zeek cluster under FreeBSD 13-p3, this morning I have tried to install spicy 1.2.0 an all works as expected. Good work!! … That’s great to hear. > But after installing spicy-plugin and spicy-analysers and executing “zeekctl deploy” (only in manager side) the following error appears in all workers: > > root@stirling:/nsm/zeek/spool/idps-prod # more stderr.log > error in /opt/zeek/share/zeek/base/init-bare.zeek, line 1: cannot load plugin library /opt/zeek/lib/zeek/plugins/packages/spicy-plugin//lib/\_Zeek-Spicy.freebsd-amd64.so: Shared object "libhilti.so" not found, required by "\_Zeek-Spicy.freebsd-amd64.so" > fatal error in /opt/zeek/share/zeek/base/init-bare.zeek, line 1: aborting after plugin errors > > Do I need to install spicy in all Zeek cluster components: workers, managers, loggers, etc? Yes, you need to install the same Spicy on all nodes where you expect to deploy spicy-plugin. When you install spicy-plugin it will detect Spicy and its configuration during its build phase; the results of these checks get baked into the plugin, so the setup on the node you build it on (manager) should mirror the target nodes. Cheers, Benjamin ---
**Author:** ![clopmz](https://avatars.discourse-cdn.com/v4/letter/c/ebca7d/32.png) [@clopmz](https://community.zeek.org/u/clopmz)\ **Post date:** [August 3, 2021, 2:01pm UTC](https://community.zeek.org/t/errors-in-workers-using-spicy-1-2-0/6387/3 "2021-08-03T14:01:48Z")
Ok, installed on all Zeek components: workers and manager …. But now Zeek processes don’t start: Stderr is: /opt/zeek/share/zeekctl/scripts/run-zeek: line 110: 1330 Abort trap nohup "$myzeek" "$@“ Best regards, C. L. Martinez ---
**Author:** ![clopmz](https://avatars.discourse-cdn.com/v4/letter/c/ebca7d/32.png) [@clopmz](https://community.zeek.org/u/clopmz)\ **Post date:** [August 3, 2021, 2:09pm UTC](https://community.zeek.org/t/errors-in-workers-using-spicy-1-2-0/6387/4 "2021-08-03T14:09:03Z")
Subcribed to spicy mailing list .. Best regards, C. L. Martinez ---
**Author:** ![Benjamin\_Bannier](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/benjamin_bannier/32/595_2.png) [@Benjamin\_Bannier](https://community.zeek.org/u/Benjamin_Bannier)\ **Post date:** [August 3, 2021, 4:05pm UTC](https://community.zeek.org/t/errors-in-workers-using-spicy-1-2-0/6387/5 "2021-08-03T16:05:22Z")
Hi Carlos, > Ok, installed on all Zeek components: workers and manager …. But now Zeek processes don’t start: > > Stderr is: > > /opt/zeek/share/zeekctl/scripts/run-zeek: line 110: 1330 Abort trap nohup "myzeek" "@“ Could you provide any logs, e.g., on the affected nodes (which ones)? The stderr you shared doesn’t really help understand what is going on here. Cheers, Benjamin ---
**Author:** ![clopmz](https://avatars.discourse-cdn.com/v4/letter/c/ebca7d/32.png) [@clopmz](https://community.zeek.org/u/clopmz)\ **Post date:** [August 4, 2021, 8:11am UTC](https://community.zeek.org/t/errors-in-workers-using-spicy-1-2-0/6387/6 "2021-08-04T08:11:16Z")
Good morning Benjamin, That is the only log that appears in the stderr.log of the workers ... And it happens in all workers .... Maybe I need to enable a flag to return a more accurate log? ---
**Author:** ![Benjamin\_Bannier](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/benjamin_bannier/32/595_2.png) [@Benjamin\_Bannier](https://community.zeek.org/u/Benjamin_Bannier)\ **Post date:** [August 4, 2021, 9:03am UTC](https://community.zeek.org/t/errors-in-workers-using-spicy-1-2-0/6387/7 "2021-08-04T09:03:37Z")
Hi Carlos, > That is the only log that appears in the stderr.log of the workers ... And it happens in all workers .... > > Maybe I need to enable a flag to return a more accurate log? I am not familiar with zeekctl. Could you maybe as a first step check whether you can start Zeek on the workers outside of zeekctl after installing the plugins (i.e., log into a worker node, run Zeek)? Cheers, Benjamin ---
**Author:** ![clopmz](https://avatars.discourse-cdn.com/v4/letter/c/ebca7d/32.png) [@clopmz](https://community.zeek.org/u/clopmz)\ **Post date:** [August 5, 2021, 5:22am UTC](https://community.zeek.org/t/errors-in-workers-using-spicy-1-2-0/6387/8 "2021-08-05T05:22:54Z")
Hi Benjamin, Sorry for this later response. If I try to run manually Zeek in a worker, outside of zeekctl/cluster, always returns the same message: “Abort”. For example, trying to display all plugins installed: root@stirling:~ # zeek -NN Abort root@stirling:~ # Best regards, C. L. Martinez ---
**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/errors-in-workers-using-spicy-1-2-0/6387/9 "2022-05-06T15:47:44Z")