Logstash services failes on FreeBSD (11.x) [2018-11-06T12:24:56,663][INFO ][logstash.modules.scaffold] Initializing module {:module_name=>"fb_apache", :directory=>"/usr/share/logstash/modules/fb_apache/configuration"} [2018-11-06T12:24:56,664][INFO ][logstash.modules.scaffold] Initializing module {:module_name=>"netflow", :directory=>"/usr/share/logstash/modules/netflow/configuration"} Did you add procfs/fdesc in /etc/fstab? vim /etc/fstab fdesc /dev/fd fdescfs rw 0 0 proc /proc procfs rw 0 0 mount -a
If your Salt Minion fails to start with [salt.utils.process:754 ][ERROR ][5542] An un-handled exception from the multiprocessing process > ‘SignalHandlingMultiprocessingProcess-1:59’ was caught: Traceback (most recent call last): File “/usr/local/lib/python3.5/dist-packages/salt/utils/process.py”, line 747, in _run return self._original_run() […] File “/usr/lib/python3.5/asyncio/base_events.py”, line 411, in run_forever ‘Cannot run the event loop while another loop is running’) RuntimeError: Cannot run the event loop while another loop is running
You might be running Tornado version 5+
If you try to run Elasticsearch in a Jail without an external IP address you might get an error like:
No up-and-running loopback addresses found, got [name:lo1 (lo1)] How to solve it? You need to bind your Elasticsearch to your primary IP address:
vim /usr/local/etc/elasticsearch/elasticsearch.yml: network.host: 10.10.10.2
If you see the following error after pkg upgrade or pkg install Shared object “libdl.so.1” not found
Your FreeBSD version might be outdated. This currently happens on FreeBSD 11.1 if you use the latest/qarterly pkg mirror.
How to fix it? freebsd-update -upgrade -r 11.2-RELEASE reboot freebsd-update install pkg update && pkg upgrade
pw: user 'username' disappeared during update How to fix it?
/usr/sbin/pwd_mkdb -p /etc/master.passwd
About me?
#ILoveFreeBSD #FOSS For censored or paranoid users: Yes, this page is accessable via TOR as well.
http://hackacadwkfa3o6lsmaopdzy7fw5shtoika3v53lep3nmgk6py4omcad.onion/
AS211684
open peering policy