theypsilon
Linux Update phase stuck forever on "Reading default db"
Just ran update_all, which self-updated to the latest version, then it ran all the way through until the Linux Update phase, where it's now stuck seemingly forever on "Reading default db", whatever that means.
...and just as I submitted that new issue, it finally emitted a warning:
WARNING: cacert file at "/etc/ssl/certs/cacert.pem" seems to be wrong!
Return Code: 55
Removing /etc/ssl/certs/cacert.pem (/etc/ssl/certs/cacert.pem)
Now it seems to be stuck again on that. Never had any problems like this before pulling down the latest updater.
If it runs well until that point, it could be something flaky with your SD. Could you try another SD to see if you still face the same errors?
A rerun of update_all resolved the issue. No idea what caused it or what resolved it. I did check that the cacert.pem was never 0 bytes at any point.
Keith F. Kelly
https://www.keithfkelly.info/
From: José Manuel Barroso Galindo @.> Sent: Tuesday, January 9, 2024 1:15:59 PM To: theypsilon/Update_All_MiSTer @.> Cc: Keith F. Kelly @.>; Author @.> Subject: Re: [theypsilon/Update_All_MiSTer] Linux Update phase stuck forever on "Reading default db" (Issue #113)
If it runs well until that point, it could be something flaky with your SD. Could you try another SD to see if you still face the same errors?
— Reply to this email directly, view it on GitHubhttps://github.com/theypsilon/Update_All_MiSTer/issues/113#issuecomment-1883804097, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AF2EYJBQ7T74244XHMWUB53YNWXQ7AVCNFSM6AAAAABBSYRWOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBTHAYDIMBZG4. You are receiving this because you authored the thread.Message ID: @.***>
I spoke too soon. Tried running it again, and this time is stalling in the same way.
It didn't hang i definitely or exhibit the same cacert.pem error, but it did take an exceptionally long time (11 minutes) to finish Reading default db.
I don't know what dB it is reading, but it's worth noting I keep a 2TB SATA SSD attached to my MiSTer's USB hub board, and it is loaded up with many thousands of ROMs, CHDs, and ISOs. If the updater is now searching the entire filesystem for something, that would definitely take a long time.
@c0d3h4x0r you could enable verbose = true to see the more fine grained logs about what is actually doing in real time. That way you may identify if it's actually expending this time in checking drives.