[10/8 SNAPSHOT] Updating Issue "Another instance is already running…Aborting!"
-
I'm on 2.4.0 RC October 8
Option 13 gives me "Another instance is already running… Aborting!"
When typing in pkg update -f from Shell I get:
Updating pfSense-core repository catalogue... pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSen se-core.sqlite) failed: No such file or directory
then after a couple minutes:
pkg: https://pkg.pfsense.org/pfSense-v2_4_0_amd64-core/meta.txz: No address reco rd repository pfSense-core has no meta file, using default settings pkg: https;//pkg.pfsense.org/pfSense_v2_4_0_amd64-core/packagesite.txz: No addre ss record Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sq lite) failed: No such file or directory
then after a couple minutes:
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-pfSense_v2_4_0/meta.txz: No ad dress record repository pfSense has no meta file, using default settings
then after a couple minutes:
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-pfSense_v2_4_0/packagesite.txz : No address record Unable to update repository pfSense Error updating repositories!
-
pkg fetch -y pkg
Same results as above.
-
pkg -ddd upgrade -n gives:
(screenshot only captures first screen of output)
Output ends with:
Unable to update repository PfSense Error updating repositories!
![pkg -ddd upgrade -n.PNG](/public/imported_attachments/1/pkg -ddd upgrade -n.PNG)
![pkg -ddd upgrade -n.PNG_thumb](/public/imported_attachments/1/pkg -ddd upgrade -n.PNG_thumb) -
pkg -ddd upgrade -Fn gives:
(screenshot only captures first screen of output)
Output ends with:
Unable to update repository PfSense Error updating repositories!
![pkg -ddd upgrade -Fn.PNG](/public/imported_attachments/1/pkg -ddd upgrade -Fn.PNG)
![pkg -ddd upgrade -Fn.PNG_thumb](/public/imported_attachments/1/pkg -ddd upgrade -Fn.PNG_thumb) -
Similar results with:
pkg -dddd upgrade -n
and
pkg -dddd upgrade -Fn
-
Update: I gave up trying to fix this and just chalked this up to a bad snapshot from 10/8. I did a reinstall with the 10/9 snapshot, and things are back to normal.