4/15/2024 0 Comments Downloading macos catalina stuckI even went back to trying to delete both the cache and the before a restart. But what kills me is that even with deleting the crl cache, I could not get Software Update to work again despite multiple tries and restarts - perhaps invalidating what I wrote was a temporary solution. And crlcache2.db is going to be created automatically regardless. After I read what I wrote above, I realized I might rename crlcache2.db to crlcache.db and run "crlrefresh rpv" again and again nothing was displayed and nothing worked. This has gotten ridiculous and I don't know if I should delete everything I've written already or not. There shouldn't be any infinite looping when there is an obvious problem that can be detected in Apple software and reported in some manner to the victimized user. There's a serious bug in the way all this is being handled. Obviously, the CRL cache creates more potential problems than just with Software Update checking. However, when trying to install the updates, the installer goes into an infinite loop just like Software Update does. Oh by the way, a month ago I found the link to manually download the Catalina security updates I was missing and I did so. I know how to get Software Update to run once when I really need to now, I can't afford to spend a lot of time on this. I hoping that someone comes along here and knows enough to explain the CRL and what might be going on and how to fix the certificate problem if that's what it is. I'll guess it's because the cache created is always crlcache2.db and not crlcache.db, so it does nothing. There is a terminal command, "crlrefresh rpv", that does nothing for me, and even with v (verbose), it runs silently. I'll guess I did something to make this happen. It appears I have an SSL certificate to straighten out but I have no idea what it could be. Unfortunately, I do not know enough to give a proper explanation, and exactly how this impacts Software Update with no message given to this sorry user. More importantly, CRL stands for certificate revocation list and concerns SSL certificates. I did recover, from Time Machine backups, older copies of my crlrcache2.db file, (and same for which I now suspect is uninvolved) should I ever come across a way of inspecting these. I'm only able to do a little bit of research now. I don't know what to make of that since running Software Update twice in a row (after deleting the crl cache and restarting) doesn't succeed on the second running of Software Update. However, when I initially deleted crlcache2.db yesterday, and restarted, I successfully ran both Software Update and the SilentKnight.app which checks for Apple security updates - and both ran and completed when they otherwise haven't been. The newly created crl cache file apparently will have the same issue impacting subsequent Software Update attempts. After running Software Update, the crl cache file (and the ist file if it's also missing) are recreated. When I booted my iMac today, it went back to endless spinning on Software Update. The problem file (for at least some of us) must be the crl cache file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |