Can't install or remove packages
-
@teamits Thanks for pointing that one out
-
@Qinn said in Can't install or remove packages:
pkg-static: Cannot get an advisory lock on a database, it is locked by another process
Maybe related...
https://forum.netgate.com/topic/141155/package-are-being-reinstalled-in-the-background
-
@kiokoman said in Can't install or remove packages:
try with Prefer IPv4 over IPv6 under system / advanced / networking
Why would that make a difference? I've been running pfSense with IPv6 for over 4 years without issue.
-
I'm having the exact same issue
I followed what @serbus suggested with this link... https://docs.netgate.com/pfsense/en/latest/packages/fixing-a-broken-pkg-database.html
I started a thread here....
https://forum.netgate.com/topic/154389/2-4-5r1-update-no-package-re-install/14My installer seems to be getting stuck on "Writing configuration... done." and then does nothing, it just sits there.
-
@JKnott
i though that maybe other isp have the same problem, and for me ipv4 is generally faster
https://forum.netgate.com/topic/153464/pfsense-updates-an-package-installation-very-slow-when-using-deutsche-telekom -
He said he couldn't install or remove packages. That doesn't sound like an ISP problem to me.
-
Well, the "installable package list" and the "installed package list" both query the remote pfsense package server before they show up.
The last one checks at that moment if installed packages have the same version number as the version available in the 'store'.This includes some traffic.
-
Well, that's certainly easy enough to verify. There are IPv6 test sites, including a couple that run IPv6. Also, this web site runs IPv6. A bit of testing can often reveal a lot. If it were an IPv6 issue, then it would affect a lot more than updates. For example Google & Youtube are both available on IPv6. A slow or broken connection would show with either of them.
-
you didn't read the thread I linked
Telekom said they do not accept your subnet because there is no route object for 2607:ee80:10::/48.
See https://bgp.he.net/net/2607:ee80:10::/48#_irrsome isp didn't have a valid route only to Netgate, no one will be able to troubleshoot this with some random ipv6 test
in any case, this was not the issue, it was just a suggestion because it comes to my mind something similar. and there wasn't enough information on the first post to think about something until he posted the log at least
-
@kiokoman said in Can't install or remove packages:
some isp didn't have a valid route only to Netgate
Again, this would be shown by observing what happens when you connect to this site. About 1.5 years ago, I had a problem with my ISP. This was indicated by any site that had an IPv6 address would be slow to load, because it would try IPv6 first, time out and then try IPv4. Regardless, it still went through. You simply cannot make such blanket assumptions without doing some testing. I often use Packet Capture or Wireshark, to see what's actually happening, instead of jumping to conclusions.
One thing I've noticed is some people are all too quick to blame IPv6, when they've done nothing to determine what the problem is. BTW, this sort of thing is not unique to IPv6, but I suspect some blame it first, simply because it's new and they don't understand it.
-
bla bla bla
are you really trying to bully me?
eh sadly I don't have time for this shit, I'd rather help than stay here to argue
