Actions
Bug #4344
closedpackage (re)installation loop after upgrading from 2.1.5-RELEASE to 2.2-RELEASE
Status:
Closed
Priority:
High
Assignee:
-
Category:
Upgrade
Target version:
-
Start date:
01/29/2015
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
amd64
Description
this issue was originally reported by "WolfSec-Support" <support at wolfsec.ch> on the pfSense's mailing list.
how to reproduce?
- upgrade pfSense from 2.1.5-RELEASE to 2.2-RELEASE;
- recomendations? https://doc.pfsense.org/index.php/Upgrade_Guide
- wait for the system to reboot;
- open the pfSense web interface and do your login.
- squid
- lightsquid
- open-vm-tools
- cron
- autoconfigbackup
- mtr-nox11
- sudo
- suricata
- nmap
- iperf
- as suricata is not working after the upgrade, i decided to tag it as 'high priority'.
- warning_packages_being_reinstalled: the warning you will see after the first login after the upgrade, right on your dashboard.
- services_suricata: shows a page where the suricata package/service should live. suricata can't be enabled/started.
- WolfSec tells that you may see some "crashes" and some upgrades weren't able to bring the system back and running again. some of the WolfSec's systems were running on a VMware ESXi 5.1 and just one, running on ALIX, did the upgrade with success. there's another reported system with the same issue running on baremetal (physical machine).
Files
Actions