kibana, curator, elastalert fail to start after reboot

619 views
Skip to first unread message

ledin...@gmail.com

unread,
Jun 9, 2018, 7:58:31 PM6/9/18
to security-onion
I am noticing that kibana, curator, and elastalert are failing to start after rebooting my SO machine. I know it can take a while for logstash to finish starting up and I do wait for that to complete and still, these three services require a restart to come up properly.

Is this normal? Anything that can be done to resolve this aside from a manual restart?

ledin...@gmail.com

unread,
Jun 9, 2018, 7:59:38 PM6/9/18
to security-onion
FYI - I neglected to add - this is for SO_16.04...

Doug Burks

unread,
Jun 10, 2018, 4:43:33 PM6/10/18
to securit...@googlegroups.com
Hi ledingtech,

This is a known issue:

Please try setting TimeoutStartSec in /etc/systemd/system/securityonion.service as shown below and let us know whether or not it works for you.

[Unit]
Description=Security Onion Service
After=network.target

[Service]
Type=forking
ExecStart=/usr/sbin/so-boot
Restart=on-abort
TimeoutStartSec=300

[Install]
WantedBy=multi-user.target



On Sat, Jun 9, 2018 at 7:59 PM, <ledin...@gmail.com> wrote:
FYI - I neglected to add - this is for SO_16.04...

--
Follow Security Onion on Twitter!
https://twitter.com/securityonion
---
You received this message because you are subscribed to the Google Groups "security-onion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to security-onion+unsubscribe@googlegroups.com.
To post to this group, send email to security-onion@googlegroups.com.
Visit this group at https://groups.google.com/group/security-onion.
For more options, visit https://groups.google.com/d/optout.



--
Doug Burks
Reply all
Reply to author
Forward
0 new messages