Regression #13817
open
pfBlockerNG-devel cron jobs persist after the service is disabled or the package is uninstalled
0%
Description
Tested on 23.01.b.20221230.0600 with the latest pfBlockerNG-devel, Suricata, and ACME packages.
Using pfBlockerNG-devel as an example:
Uninstalling the package or disabling the service by unchecking Enable in the Firewall / pfBlockerNG / General page does not remove the cron jobs added when the service is configured/enabled. The following remain when disabled:
0 * * * * root /usr/local/bin/php /usr/local/www/pfblockerng/pfblockerng.php cron >> /var/log/pfblockerng/pfblockerng.log 2>&1 0 14 * * 5 root /usr/local/bin/php /usr/local/www/pfblockerng/pfblockerng.php dcc >> /var/log/pfblockerng/extras.log 2>&1
Updated by Marcos M over 1 year ago
- Subject changed from pfBlockerNG-devel cron jobs persist after the service is disabled. to pfBlockerNG-devel cron jobs persist after the service is disabled or the package is uninstalled.
- Description updated (diff)
Updated by Marcos M over 1 year ago
- Project changed from pfSense Packages to pfSense
- Subject changed from pfBlockerNG-devel cron jobs persist after the service is disabled or the package is uninstalled. to Cron jobs persist after its package is uninstalled.
- Description updated (diff)
- Category changed from pfBlockerNG to Package System
- Priority changed from Normal to High
- Affected Plus Version deleted (
23.01) - Release Notes set to Default
Updated by Jim Pingle over 1 year ago
- Status changed from New to Rejected
It's up to each package to manage its own cron jobs. There isn't a way for the package manager to know those belong to a package. This is not a general package manager problem.
If pfBlocker leaves them behind, that's a pfBlocker issue. Same for other packages.
Updated by Marcos M over 1 year ago
- Project changed from pfSense to pfSense Packages
- Subject changed from Cron jobs persist after its package is uninstalled. to pfBlockerNG-devel cron jobs persist after the service is disabled or the package is uninstalled.
- Category changed from Package System to pfBlockerNG
- Status changed from Rejected to New
- Priority changed from High to Normal
- Release Notes deleted (
Default)
I had originally opened this against just pfBLockerNG-devel, but changed it since I saw it was happening on all packages I had installed. I'll create a separate report for each, and re-open this one under the right info.
Updated by Marcos M over 1 year ago
- Status changed from New to Closed
- Assignee set to Jim Pingle
Updated by Jim Pingle over 1 year ago
- Status changed from Closed to Confirmed
- Assignee deleted (
Jim Pingle)
The cron job is still present after removing the package. There is likely a package-specific change that must be made to ensure it's removing the correct job.
Updated by Jim Pingle over 1 year ago
- Subject changed from pfBlockerNG-devel cron jobs persist after the service is disabled or the package is uninstalled. to pfBlockerNG-devel cron jobs persist after the service is disabled or the package is uninstalled
Updated by Jordan G 8 months ago
on 23.05.1 and pfB 3.2.0_6 after working through getting the package to uninstall successfully (see https://redmine.pfsense.org/issues/14287) I still have a cron entry remaining for pfBlockerNG
/usr/local/bin/php /usr/local/www/pfblockerng/pfblockerng.php cron >> /var/log/pfblockerng/pfblockerng.log 2>&1