Changelog
Latest
MetaTana v2.3.2
Fixes for MetaTana not starting after an update, a killed container or a power cut. Update as usual. The library database does not change, so 2.3.1 can still open it.
Starting after an update or an unclean stop
- Docker: a container that replaces one that was killed starts within about a minute. This happens when an update or the NAS stops the old container before it has shut down. In 2.3.1 and earlier the new container restarted over and over for about five minutes, with Runtime lease denied in its log, and a dashboard showed MetaTana as offline.
- After a power cut or a crash at the wrong moment, MetaTana starts again, in Docker and on the desktop. Before, it could refuse to start every time until you ran metatana backup unlock --confirm-stopped.
- A library upgrade that was interrupted is finished by the next start. An upgrade that 2.3.1 left half-way is taken over 30 minutes after it stopped. To open the library sooner, stop MetaTana and run metatana backup unlock --confirm-stopped, which now clears that lock too.
- A second MetaTana started on a library that is already open is still refused, as before.
- On a slow disk, such as a NAS hard drive, MetaTana waits for a library upgrade, a backup restore or a library reset to finish, up to an hour, instead of giving up at its normal startup limit. It also waits when the system's temporary folder cannot be written to.
- Split Docker: the background container waits for the web container's library upgrade, and a media folder on a network share that does not answer no longer holds up its start.
- When MetaTana cannot reach your account to check your sign-in, it opens your library with the access it last knew instead of waiting.
QNAP and ASUSTOR packages
- An update keeps the running version until the new one has been downloaded and created. If the download fails, the version you have keeps running, and you can try the update again.
- If the new version could not be started, the package brings the previous one back.
Scanning
- On a folder's first scan, MetaTana waits until it has decided whether the folder is an existing library it can trust before filling in titles from metadata providers. Before, titles filled in while that first scan was still running kept their NFO's values even when the folder turned out not to be one, and two scans of the same folder could end up with different results.
- When metadata providers fill in a title, each field records where its value came from (local artwork, TMDb and so on). Before, a field a provider had just filled in could still say it came from the NFO, or say nothing.