The pfSense Store

Author Topic: Cleanup package mess caused by restoring config  (Read 110 times)

0 Members and 1 Guest are viewing this topic.

Offline lpallard

  • Full Member
  • ***
  • Posts: 249
  • Karma: +0/-0
    • View Profile
Cleanup package mess caused by restoring config
« on: August 21, 2016, 10:46:44 am »
When I reinstalled pfsense (2.2) I restored my config from a backup file that had been created on a previous pfsense release.  The restore feature tried to install some packages that are no longer supported and are leaving traces everywhere.

For example

In the services menu I see an entry for "Zabbix2 Agent", this should not be there as the package is not installed.  If I click on this entry I get "No valid package defined."

In the Status > Services I see "ntop" and "zabbix_agentd " that are both "stopped" and cannot be started (of course they're not installed).

In the Status menu I see "Vnstat2", this should not be there as the package is not installed.  If I click on this entery I get "No valid package defined."

How do I cleanup the mess caused by the restore?

Offline lpallard

  • Full Member
  • ***
  • Posts: 249
  • Karma: +0/-0
    • View Profile
Re: Cleanup package mess caused by restoring config
« Reply #1 on: August 21, 2016, 10:47:12 am »
I found this Reddit thread where the OP has the same issue:

https://www.reddit.com/r/PFSENSE/comments/4hnmw5/remove_orphaned_package_listing_after_upgrade_to/

Someone recommended to play with config.xml... Is there a better/more "enterprise" way of solving this mess?