One of the problems reported by O!MPD’s users is the interruption of update process. This can have several reasons. Some of them are described below.
Update process can be interrupted by PHP service. When you use OPcache and you find in php log file info like this:
WARNING: [pool www] child 3624 exited on signal 9 (SIGKILL) after 188.998235 seconds from start
then you probably need to increase
opcache.force_restart_timeout. Go to your php.ini file, uncomment line with
opcache.force_restart_timeout and set its value to some large number, like
180000. Restart PHP service and start update process. If that was the reason then update should now be successful.
Error during getting info from files
However the most common problem is error in reading tags from music file. In this case you need to identify file causing error. First turn on debug mode: in
true. Make sure that your web server has write access to /ompd/tmp/ directory. Next start new update. When process stops, open /ompd/tmp/update_log.txt and go to the end of this file. There you’ll find name of last processed file – the one that probably broke the update process. Try to investigate if it really did: simply remove this file (or whole directory this file is in) and restart update process. You can also open this file in a tag editor (like mp3tag) and review tags: pay attention to any unusual characters in text fields and numbers in numeric fields (like YEAR or DATE). Try to correct them and restart update once again.
Sometimes it turns out that file is broken (it is not possible to read tags from it at all) – than try to fix it in a tag editor.
Cancel broken update
If you want to cancel previously broken update, go to setting page, scroll to Update, click last dot in Update in progress… and click red x. This actually doesn’t stop update process but clears update flag in database and lets you to start new update process.
If you still have problems with update don’t hesitate to write to me or report issue on GitHub.