mirror of
https://github.com/koel/koel.git
synced 2026-04-26 17:25:59 +03:00
[GH-ISSUE #1788] Inconsistent Issue with Media scanning #989
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#989
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DarkXero-dev on GitHub (Jul 14, 2024).
Original GitHub issue: https://github.com/koel/koel/issues/1788
Describe the bug
I use Koel as a Docker container, self-hosted with mysql/Mariadb. This one is new to me. I was using Koel just fine until today. I just added a few discographies, went to scan everytime I do it's a different number of Invalid Files...
To reproduce
php artisan koel:scanExpected behavior
No error
Screenshots

Environment
Additional context
It's really inconsistent. Just by adding music causes it to go crazy...
@phanan commented on GitHub (Jul 14, 2024):
Thanks for reporting the issue. What shows if you run
php artisan koel:scan -v?@DarkXero-dev commented on GitHub (Jul 14, 2024):
Well Invalid file...

Laravel.log file is 38mb for whatever reason so I had to upload to wormhole (Expires in 24h)
https://wormhole.app/AJWE0#x7OkYcr6k0Kwz0SuTuw5NQ
@phanan commented on GitHub (Jul 14, 2024):
All relevant errors in the log go something like this:
Please make sure the path is writable. In the past, there was no error because the image writing operation was wrapped in a try/catch. While I can restore it, this is an indication of something wrong in your system.
@DarkXero-dev commented on GitHub (Jul 14, 2024):
Well all I did was move folder that contains the compose.yml file to a new SSD which is EXT4 and all folders within it are writable owned by my user I do not see how that could have messed things up. How can I fix this issue, don't really want to start from scratch too much work lol.
Also music is on a totally different drive..
@phanan commented on GitHub (Jul 14, 2024):
I'm not familiar with such a setup, but generally, you want the directory to be owned by
www-data.@DarkXero-dev commented on GitHub (Jul 14, 2024):
I mean this entire directory is owned by me

No weird setup here. The folders are the volumes I point to within compose file. I think what you mean is within the container right ? Is there a way to fix that with them php artisan command thingies ?
@phanan commented on GitHub (Jul 14, 2024):
Yes, the directory should be owned by
www-data. You can fix this for example by using Docker Desktop andExeca command likechown -R www-data:www-data /var/www/html. Again, I'm not familiar with your custom setup and won't be able to provide support in details.@DarkXero-dev commented on GitHub (Jul 14, 2024):
I fixed it with
Scanning seems to be working now 👯
@phanan commented on GitHub (Jul 14, 2024):
Great! I'm glad you got it sorted!
@DarkXero-dev commented on GitHub (Jul 14, 2024):
You were awesome.. Thanks.. Time to do cleanup.. I still have 1000 Discographies to fix with Musicbrainz + Picard.. Will take a few decades lol....