systemd service does not get stopped after uninstallation

[aminvakil]

Bug Report

Describe the bug I removed (even purged) fluent-bit package using apt purge fluent-bit, but oddly systemd service did not get stopped.

To Reproduce Install and remove fluent-bit package from fluent-bit official packages.

• Steps to reproduce the problem: Add fluent-bit key Add fluent-bit to sources.list Install fluent-bit (it will start service automatically at this step) Remove fluent-bit (apt remove fluent-bit or apt purge fluent-bit) systemctl status fluent-bit shows the service is running (although systemd service file is missing)

Expected behavior Stop the service and daemon-reload after package removal.

Your Environment

• Version used: Fluent Bit v1.9.7
• Configuration: irrelevant
• Environment name and version (e.g. Kubernetes? What version?): debian apt package
• Server type and version: irrelevant
• Operating System and version: Debian 10 Buster
• Filters and plugins: irrelevant

Additional context

I'm not sure if this is something all debian packages do like enabling/starting services after package installation or is this something which has not been implemented in fluent-bit package.

[aminvakil]

So it's considered a bug, as mentioned in https://www.debian.org/doc/manuals/debian-faq/pkg-basics.en.html#maintscripts in prerm section:

This script typically stops any daemons which are associated with a package. It is executed before the removal of files associated with the package.

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.

[aminvakil]

This is a bug, I don't have time myself to put into this, but could you please mark it as backlog or something like that, so the bot does not close it?