Project

General

Profile

Actions

Bug #4344

closed

package (re)installation loop after upgrading from 2.1.5-RELEASE to 2.2-RELEASE

Added by Vinícius Zavam almost 10 years ago. Updated about 9 years ago.

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?

packages related to this issue
  • squid
  • lightsquid
  • open-vm-tools
  • cron
  • autoconfigbackup
  • mtr-nox11
  • sudo
  • suricata
  • nmap
  • iperf
system logs? high priority?
  • as suricata is not working after the upgrade, i decided to tag it as 'high priority'.
about the images (screenshots)
  • 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.
misc
  • 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

warning_packages_being_reinstalled.png (29.2 KB) warning_packages_being_reinstalled.png Vinícius Zavam, 01/29/2015 11:54 AM
services_suricata.png (55.7 KB) services_suricata.png Vinícius Zavam, 01/29/2015 11:54 AM
Actions

Also available in: Atom PDF