Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #180631 > unrolled thread

systemd: How to get suricata started at boot?

Started byHans <hans.ullrich@loop.de>
First post2017-05-03 11:40 +0200
Last post2017-05-03 16:00 +0200
Articles 7 — 4 participants

Back to article view | Back to linux.debian.user

Contents

  systemd: How to get suricata started at boot? Hans <hans.ullrich@loop.de> - 2017-05-03 11:40 +0200
    Re: systemd: How to get suricata started at boot? Michael Biebl <biebl@debian.org> - 2017-05-03 13:00 +0200
      Bug#861732: systemd: How to get suricata started at boot? Arturo Borrero Gonzalez <arturo@debian.org> - 2017-05-03 17:50 +0200
        Re: Bug#861732: systemd: How to get suricata started at boot? Hans <hans.ullrich@loop.de> - 2017-05-03 18:30 +0200
    Re: systemd: How to get suricata started at boot? Dejan Jocic <jodejka@gmail.com> - 2017-05-03 13:00 +0200
      Re: systemd: How to get suricata started at boot? Hans <hans.ullrich@loop.de> - 2017-05-03 13:40 +0200
        Re: systemd: How to get suricata started at boot? Michael Biebl <biebl@debian.org> - 2017-05-03 16:00 +0200

#180631 — systemd: How to get suricata started at boot?

FromHans <hans.ullrich@loop.de>
Date2017-05-03 11:40 +0200
Subjectsystemd: How to get suricata started at boot?
Message-ID<tCYVk-3kJ-17@gated-at.bofh.it>
Hello all,

I have installed suricata on my system, but it will not start at boot.

When I manually start it, it is working well.

As the document advises, I copied  /lib/systemd/system/suricata.service to 
/etc/systemd/system/suricata.service and tested with

systemctl start suricata.service

"ps -aux | grep suricata" showed me the running process. But after reboot, the 
process is not started automatically. As init is no more supported by 
suricata, but systemd, how can I add this service into systemd, so that it is 
started automatically at boot? I am still not quite experienced with systemd.

Thanks for any hints.

Best

Hans

[toc] | [next] | [standalone]

#180634

FromMichael Biebl <biebl@debian.org>
Date2017-05-03 13:00 +0200
Message-ID<tCZRo-41a-3@gated-at.bofh.it>
In reply to#180631

[Multipart message — attachments visible in raw view] — view raw

Am 03.05.2017 um 11:11 schrieb Hans:
> Hello all,
> 
> I have installed suricata on my system, but it will not start at boot.
> 
> When I manually start it, it is working well.
> 
> As the document advises, I copied  /lib/systemd/system/suricata.service to 
> /etc/systemd/system/suricata.service and tested with

You only need to copy suricata.service to /etc if you want to change its
contents. Even then, often drop-in snippets are preferrable, which only
override/extend the parts you need

> systemctl start suricata.service
> 
> "ps -aux | grep suricata" showed me the running process. But after reboot, the 
> process is not started automatically. As init is no more supported by 
> suricata, but systemd,

The suricata package still ships a SysV init script, but if a systemd
service file exists, it takes precedence.

 how can I add this service into systemd, so that it is
> started automatically at boot? I am still not quite experienced with systemd.

systemctl enable suricata.service

will do the trick. That should be done by the package though.
I see you already filed a bug report [1] for that. The package should be
using init-system-helper/dh_systemd to help automate that.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861732

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[toc] | [prev] | [next] | [standalone]

#180648 — Bug#861732: systemd: How to get suricata started at boot?

FromArturo Borrero Gonzalez <arturo@debian.org>
Date2017-05-03 17:50 +0200
SubjectBug#861732: systemd: How to get suricata started at boot?
Message-ID<tD4Ho-7iw-19@gated-at.bofh.it>
In reply to#180634
On 3 May 2017 at 12:36, Michael Biebl <biebl@debian.org> wrote:
> Am 03.05.2017 um 11:11 schrieb Hans:
>> Hello all,
>>
>> I have installed suricata on my system, but it will not start at boot.
>>
>> When I manually start it, it is working well.
>>
>> As the document advises, I copied  /lib/systemd/system/suricata.service to
>> /etc/systemd/system/suricata.service and tested with
>
> You only need to copy suricata.service to /etc if you want to change its
> contents. Even then, often drop-in snippets are preferrable, which only
> override/extend the parts you need
>
>> systemctl start suricata.service
>>
>> "ps -aux | grep suricata" showed me the running process. But after reboot, the
>> process is not started automatically. As init is no more supported by
>> suricata, but systemd,
>
> The suricata package still ships a SysV init script, but if a systemd
> service file exists, it takes precedence.
>
>  how can I add this service into systemd, so that it is
>> started automatically at boot? I am still not quite experienced with systemd.
>
> systemctl enable suricata.service
>
> will do the trick. That should be done by the package though.

This conflicts with what was reported in #850889 [0].

I think both arguments are valid:

1) any suricata deployment is likely to require manual configuration
before proper service. Auto-start makes no sense.
2) yes, we are debian, we like things running out of the box

So, I'm unsure what path to follow.

In any case, a fix is not landing in stretch at this point. We should
wait for the stretch stable release.

Comments/discussion welcome.

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861732

[toc] | [prev] | [next] | [standalone]

#180653 — Re: Bug#861732: systemd: How to get suricata started at boot?

FromHans <hans.ullrich@loop.de>
Date2017-05-03 18:30 +0200
SubjectRe: Bug#861732: systemd: How to get suricata started at boot?
Message-ID<tD5k5-7NI-13@gated-at.bofh.it>
In reply to#180648
I suggest, if it is not wanted, to get suricata started at boot by default, 
then just leave the package as it is.

However, in that case, you should mention the opportunity by systemctl in the 
README.debian (or better let the user decide during install) if he wants it 
running at boot or not.

I personally found the solution with systemctl, so this regardless what you 
decide, IMO this bugreport can be closed. 

To discuss this is a welcome decision and real open-source-thinking!

Best 

Hans

[toc] | [prev] | [next] | [standalone]

#180636

FromDejan Jocic <jodejka@gmail.com>
Date2017-05-03 13:00 +0200
Message-ID<tD0aK-4bC-47@gated-at.bofh.it>
In reply to#180631
On 03-05-17, Hans wrote:
> Hello all,
> 
> I have installed suricata on my system, but it will not start at boot.
> 
> When I manually start it, it is working well.
> 
> As the document advises, I copied  /lib/systemd/system/suricata.service to 
> /etc/systemd/system/suricata.service and tested with
> 
> systemctl start suricata.service
> 
> "ps -aux | grep suricata" showed me the running process. But after reboot, the 
> process is not started automatically. As init is no more supported by 
> suricata, but systemd, how can I add this service into systemd, so that it is 
> started automatically at boot? I am still not quite experienced with systemd.
> 
> Thanks for any hints.
> 
> Best
> 
> Hans
> 
> 

Short answer:

#systemctl enable suricata.service

Bit longer answers and something that you should read:

https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units

http://linoxide.com/linux-command/systemd-vs-sysvinit-cheatsheet/

https://dynacont.net/documentation/linux/Useful_SystemD_commands/

[toc] | [prev] | [next] | [standalone]

#180637

FromHans <hans.ullrich@loop.de>
Date2017-05-03 13:40 +0200
Message-ID<tD0Nr-4I5-1@gated-at.bofh.it>
In reply to#180636
Am Mittwoch, 3. Mai 2017, 12:38:39 CEST schrieb Dejan Jocic:
> On 03-05-17, Hans wrote:
> > Hello all,
> > 
Hi Michael, high Dejan,

this works! But I will let the bugreport open (unless, you think it can be 
closed), because the maintainer might want to look, why the installation 
script in the package did not configure suricata correctly. 

However, if there is no bug found, so it is here on my system gone defective 
by chance, who knows.

Whatever: Thank you very much for your fast help, and Dejan, Yes, I will read 
your links carefully! 

Best regards

Hans
> 
> Short answer:
> 
> #systemctl enable suricata.service
> 
> Bit longer answers and something that you should read:
> 
> https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-man
> age-systemd-services-and-units
> 
> http://linoxide.com/linux-command/systemd-vs-sysvinit-cheatsheet/
> 
> https://dynacont.net/documentation/linux/Useful_SystemD_commands/


-- 
Ullrich-IT-Consult
Ihr Partner für die Themen 
* IT-SICHERHEIT * IT-SERVICE * 
* LINUX * EDV-SCHULUNGEN *

Hans-J. Ullrich
Münstedter Weg 10
31246 Oberg 
 
Tel.: 0152 287 30804
FAX: 05172 930 414

E-Mail: hans.ullrich@loop.de

[toc] | [prev] | [next] | [standalone]

#180643

FromMichael Biebl <biebl@debian.org>
Date2017-05-03 16:00 +0200
Message-ID<tD2YW-6a8-5@gated-at.bofh.it>
In reply to#180637

[Multipart message — attachments visible in raw view] — view raw

Am 03.05.2017 um 13:12 schrieb Hans:
> Am Mittwoch, 3. Mai 2017, 12:38:39 CEST schrieb Dejan Jocic:
>> On 03-05-17, Hans wrote:
>>> Hello all,
>>>
> Hi Michael, high Dejan,
> 
> this works! But I will let the bugreport open (unless, you think it can be 
> closed), because the maintainer might want to look, why the installation 
> script in the package did not configure suricata correctly. 
> 
> However, if there is no bug found, so it is here on my system gone defective 
> by chance, who knows.

It's a valid bug in the package and needs to be fixed there. Don't close it.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web