Project

General

Profile

Actions
Copy link

Bug #12766

closed

Packages with custom ``internal_name`` values do not reinstall properly when restoring a backup

Added by Viktor Gurov almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
Package System
Target version:
2.7.0
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
22.05
Release Notes:
Default
Affected Version:
2.6.0
Affected Architecture:

Description

After restoring pfSense 2.7 (2.7.0.a.20220207.0600) from the backup:

Feb  7 20:20:07 pf100 php[97635]: rc.package_reinstall_all: New alert found: Package radiusd does not exist in current pfSense version and it has been removed.
Feb  7 20:20:07 pf100 php[97635]: rc.package_reinstall_all: The command '/usr/local/etc/rc.d/radiusd.sh stop' returned exit code '1', the output was 'radiusd not running?' 
Feb  7 20:20:07 pf100 php[97635]: rc.package_reinstall_all: The command '/usr/local/etc/rc.d/radiusd.sh stop' returned exit code '1', the output was 'radiusd not running?' 
Feb  7 20:20:07 pf100 php[97635]: rc.package_reinstall_all: Configuration Change: (system): Intermediate config write during package removal for radiusd.
Feb  7 20:20:07 pf100 php[97635]: rc.package_reinstall_all: Configuration Change: (system): Removed radiusd package.

workaround: reinstall FreeRADIUS package

no such issue with other packages (at least with acme, frr, haproxy, lightsquid, openvpn-client-export, pimd, squid, stunnel, suricata, syslog-ng, telegraf and wireguard)

Actions
Copy link
 #1

Updated by Jim Pingle almost 3 years ago

I think this may be because internal_name in the package tags is set to radiusd though I can't recall why that is the case, but at some point it may have been because the service name was keyed off that before it was moved to its own service tag. It likely should not be set that way anymore.

Actions
Copy link
 #2

Updated by Viktor Gurov almost 3 years ago

+ same issue with BIND package:

Package named does not exist in current pfSense version and it has been removed. @ 2022-02-07 21:10:08

Actions
Copy link
 #3

Updated by Viktor Gurov almost 3 years ago

  • Project changed from pfSense Packages to pfSense
  • Category changed from FreeRADIUS to Package System
  • Assignee set to Viktor Gurov
  • Affected Version changed from 2.7.0 to 2.6.0
  • Release Notes set to Default
Actions
Copy link
 #4

Updated by Jim Pingle almost 3 years ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.7.0
  • Plus Target Version set to 22.05
Actions
Copy link
 #5

Updated by Viktor Gurov almost 3 years ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #6

Updated by Danilo Zrenjanin over 2 years ago

  • Status changed from Feedback to Resolved

Tested against:

2.7.0-DEVELOPMENT (amd64)
built on Mon Mar 28 06:17:26 UTC 2022
FreeBSD 12.3-STABLE

Both packages got installed successfully with the configuration restore process.

I am marking this ticket resolved.

Actions
Copy link
 #7

Updated by Jim Pingle over 2 years ago

  • Subject changed from ```Package radiusd does not exist in current pfSense version and it has been removed``` message on pfSense 2.7 restore to Packages with custom ``internal_name`` values do not reinstall properly when restoring a backup

Updating subject for release notes.

Actions
Copy link

Also available in: Atom PDF