transferred from Redmine -Bug #16341 Updating repositories metadata" returned error code 1 -- &/or Bug #15097
-
@jimp I apologize Jim, - I got so caught up in the theme that I didn't take that into account.
"
Attention:
The pfSense Redmine site is not a discussion platform and is never to be used for support requests."
I don't want to retype everything here, so I refer to what has been written on behalf of my company (Grid Solution Ltd.) here.
Please read this too, so you can see the whole picture.: https://redmine.pfsense.org/issues/16341So, the conclusion is that now adding an HW element (&/or change) deletes the files(??) from the /usr/local/etc/pfSense/pkg/repos folder
After restarting again, pfSense will no longer start up.When this occurs, this error message is immediately displayed.
check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-10-30 19:19:11
brief background:
1. Restore the pfSense installation from a snapshot; this is the starting point, basic installation
In this state, there were 9 interfaces + VMware Tools installation. 4x X710 rNDC + 4x X710 rNDC + vmx0 for mgmt. (VMXNET3) + QAT 10VFs-----The "pkg" files were here in the folder----
2. since it was necessary -- add an I350 with passthrough, - afterwards - REBOOT pfSense & ESXi host
3. after restarting , the "pkg" files are missing and * Bug #16341 occurs immediately.*
So, the conclusion is that now adding an HW element (&/or change) deletes the files(??) from the /usr/local/etc/pfSense/pkg/repos folder. hmmmm....?
After restarting again, pfSense will no longer start up.
Does anyone have any ideas about this?
-
@DaddyGo You had plus, correct? If one adds a NIC it changes the calculated NDI. The pfSense plus license is tied to the NDI so it's no longer valid. (Netgate will transfer it for this but IIRC only once)
pfSense should function but you're blocked from updating, or installing packages, without a valid license.
I've not seen anyone report core dumps or problems booting, though.
Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
When upgrading, allow 10-15 minutes to reboot, or more depending on packages, CPU, and/or disk speed.
Upvote 👍 helpful posts! -
Hi, thanks for your reply.
Yes, - fresh crispy license, two days old :-)
I bought it during installation.You may have pointed out the solution.
But how crazy would it be if, due to a hardware change, the box would throw away the license?
(or the update options and the "pkg" repo)Mainly of adding or removing NICs.
There are other parameters that could be linked to this ID, such as CPUID, etc.You should be able to add HW elements at any time, even if the device ID is calculated from them.
Otherwise, the license status remains valid.
That's exactly what happens, by the way.
https://redmine.pfsense.org/issues/15097I restored pfSense from the ESXi snapshot (was on half way) and copied the directory.
(/usr/local/etc/pfSense/pkg/repos/)I don't know if this is okay, but I copied it back. :)
I followed the workaround suggested in Bug #15097, but the files disappeared again.Please watch the video about this.
https://mega.nz/file/phUWyCaI#xmz6H_4VJB3OvwP8aQqz8Gz6ioGr49qDTz7jat1cpBQ
Edit1:
Yes, I read that the license can be transferred once.
but I didn't replace the entire box, I just added a NIC :)
(I only added one NIC port, not the entire 4-port card.) -
@SteveITS said in transferred from Redmine -Bug #16341 Updating repositories metadata" returned error code 1 -- &/or Bug #15097:
The pfSense plus license is tied to the NDI so it's no longer valid. (Netgate will transfer it for this but IIRC only once)
And you were right, I never would have imagined this, now that I'm back at pfSense.
I just got a message from support, at least they were quick, hahaha....
-
We are working on improving the license stuff. FWIW I tested the issue and it did not result in an unbootable system.
-
@marcosm said in transferred from Redmine -Bug #16341 Updating repositories metadata" returned error code 1 -- &/or Bug #15097:
We are working on improving the license stuff. FWIW I tested the issue and it did not result in an unbootable system.
@marcosm ---Thanks for the Follow-Up
It would be great to be able to manage NICs flexibly on a NGFW, which is the "heart" of such a system.
I have learned a lot about the relationship between NDI and MACs over the past few days. :)Kris is a great guy at TAC.
I missed out a bit on this NDI and Plus license thing, but as I explained above, as soon as the added NIC created a new MAC, this license became invalid (so far, so good) and the firewall immediately threw up the error messages described in Bug #16341.
After rebooting, it wouldn't start up again, and I had to continue from a snapshot.
Now I understand that this is not directly related to the Bug #16341.
