feat: drop init.d support and go-daemon binaries

[kruskall]

Proposed commit message

remove init.d scripts
drop go-daemon dep and daemon binaries
cleanup mage task

init.d should not be needed on distros we support
According to go-daemon readme: "Go daemon is not needed on systems with systemd."

See https://www.elastic.co/support/matrix#matrix_os

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Closes [packaging] Retire init.d support in linux packages #36799

Use cases

Screenshots

Logs

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @kruskall? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit

[mergify]

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

[elasticmachine]

Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services)

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[elasticmachine]

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

[elasticmachine]

Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform)

[elasticmachine]

Pinging @elastic/sec-windows-platform (Team:Security-Windows Platform)

[cmacknz]

Similar to Elastic Agent, the Beats DEB and RPM packages need to be able to run as services and that there is no systemd unit file to do this makes me suspect this doesn't work. There are no tests of the DEB and RPM packages in CI here AFAIK.

For Beats, we do have a reference system unit file and actually document so outside of those packages this should be fine https://github.com/elastic/elastic-agent/blob/54932dc7b46cdd0d16791e07b8fc5dd596efb129/dev-tools/packaging/templates/linux/systemd.unit.tmpl#L1

https://www.elastic.co/guide/en/beats/filebeat/current/running-with-systemd.html

We do reference init.d directly in some documentation. https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-starting.html. We should also remove those references.

[kruskall]

maybe I'm missing something but isn't the systemd service file available at

beats/dev-tools/packaging/packages.yml

Lines 58 to 60 in 583d345

	/lib/systemd/system/{{.BeatServiceName}}.service:
	template: '{{ elastic_beats_dir }}/dev-tools/packaging/templates/linux/systemd.unit.tmpl'
	mode: 0644

?

[cmacknz]

Yes it exists, we just need to double check the RPM and DEB packages include and use it properly. They have not been looked at in a long time.