[GH-ISSUE #425] Koel:sync --force always Killed at 50% #302

Closed
opened 2026-02-26 02:32:45 +03:00 by kerem · 17 comments
Owner

Originally created by @Porco-Rosso on GitHub (Aug 25, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/425

Hey, thanks for contributing to Koel! To save time for both of us, please make sure these checkboxes are checked before submitting the issue:

  • You have read and followed closely the Wiki, Upgrade Guide, as well as Troubleshooting
  • The issue has not been reported before
  • This is not a "how to install on Windows" or "why is my npm messed up" question
  • You're a cool pig

All checked? Now also make sure your issue

  • Is associated with a version. Or better yet, a commit.
  • Is as detailed as possible (ahem... OS, browser, steps to reproduce, maybe?)
  • Includes the error output if it's a bug/error report ("Whoops!" is not very helpful, you know)
  • Is in English, 因为我不说中文。

Hi! Once again great project.
I recently logged in to my koel install after updating to the newest version and noticed the album art was missing.
I found that running php artisan koel:sync --force repopulated the saved images, and I no longer got 404 errors in the browser.
However, when executing the sync with the --force trigger the scan gets killed at exactly 50%

screen shot 2016-08-25 at 10 03 09 pm

Running a normal scan completes without errors, but does not restore the images.
Running another forced resync always gets killed at the same point and so I can't progress.

Any idea what might be causing this?

I am running Debian 8, with the latest version of Koel.

Originally created by @Porco-Rosso on GitHub (Aug 25, 2016). Original GitHub issue: https://github.com/koel/koel/issues/425 Hey, thanks for contributing to Koel! To save time for both of us, please make sure these checkboxes are checked before submitting the issue: - [x] You have read and followed closely the [Wiki](https://github.com/phanan/koel/wiki), [Upgrade Guide](https://github.com/phanan/koel/releases), as well as [Troubleshooting](https://github.com/phanan/koel/wiki/Troubleshooting) - [x] The issue has not been reported before - [x] This is not a "how to install on Windows" or "why is my npm messed up" question - [x] You're a cool _pig_ All checked? Now also make sure your issue - [ ] Is associated with a version. Or better yet, a commit. - [x] Is as detailed as possible (ahem... OS, browser, steps to reproduce, maybe?) - [x] Includes the error output if it's a bug/error report ("Whoops!" is not very helpful, you know) - [x] Is in English, 因为我不说中文。 # Hi! Once again great project. I recently logged in to my koel install after updating to the newest version and noticed the album art was missing. I found that running `php artisan koel:sync --force` repopulated the saved images, and I no longer got 404 errors in the browser. However, when executing the sync with the --force trigger the scan gets killed at exactly 50% <img width="603" alt="screen shot 2016-08-25 at 10 03 09 pm" src="https://cloud.githubusercontent.com/assets/7024527/17982475/9811e9d6-6b10-11e6-9bab-521771b7134d.png"> Running a normal scan completes without errors, but does not restore the images. Running another forced resync always gets killed at the same point and so I can't progress. Any idea what might be causing this? I am running Debian 8, with the latest version of Koel.
kerem closed this issue 2026-02-26 02:32:45 +03:00
Author
Owner

@BernardGoldberger commented on GitHub (Aug 25, 2016):

To start with check the storage/logs/laravel.log, you can also run php artisan koel:sync -v --force so that it logs to the console.

<!-- gh-comment-id:242511358 --> @BernardGoldberger commented on GitHub (Aug 25, 2016): To start with check the `storage/logs/laravel.log`, you can also run `php artisan koel:sync -v --force` so that it logs to the console.
Author
Owner

@Porco-Rosso commented on GitHub (Aug 25, 2016):

Adding the -v switch gives no additional information, only that the scan died 12 minutes in.

here is the laravel.log, but from what I can see it has no relation.

[2016-08-25 17:36:46] local.ERROR: exception 'Tymon\JWTAuth\Exceptions\TokenExpiredException' with message 'Token has expired' in /home/koel/koel/vendor/tymon/jwt-auth/src/Validators/PayloadValidator.php:83
Stack trace:
#0 /home/koel/koel/vendor/tymon/jwt-auth/src/Validators/PayloadValidator.php(41): Tymon\JWTAuth\Validators\PayloadValidator->validateTimestamps(Array)
#1 /home/koel/koel/vendor/tymon/jwt-auth/src/Payload.php(38): Tymon\JWTAuth\Validators\PayloadValidator->check(Array)
#2 /home/koel/koel/vendor/tymon/jwt-auth/src/PayloadFactory.php(77): Tymon\JWTAuth\Payload->__construct(Array, Object(Tymon\JWTAuth\Validators\PayloadValidator), false)
#3 /home/koel/koel/vendor/tymon/jwt-auth/src/JWTManager.php(81): Tymon\JWTAuth\PayloadFactory->make(Array)
#4 /home/koel/koel/vendor/tymon/jwt-auth/src/JWTManager.php(126): Tymon\JWTAuth\JWTManager->decode(Object(Tymon\JWTAuth\Token))
#5 /home/koel/koel/vendor/tymon/jwt-auth/src/JWTAuth.php(158): Tymon\JWTAuth\JWTManager->invalidate(Object(Tymon\JWTAuth\Token))
#6 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(218): Tymon\JWTAuth\JWTAuth->invalidate(Object(Tymon\JWTAuth\Token))
#7 /home/koel/koel/app/Http/Controllers/API/AuthController.php(45): Illuminate\Support\Facades\Facade::__callStatic('invalidate', Array)
#8 /home/koel/koel/app/Http/Controllers/API/AuthController.php(45): Tymon\JWTAuth\Facades\JWTAuth::invalidate(Object(Tymon\JWTAuth\Token))
#9 [internal function]: App\Http\Controllers\API\AuthController->logout()
#10 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(78): call_user_func_array(Array, Array)
#11 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(146): Illuminate\Routing\Controller->callAction('logout', Array)
#12 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(94): Illuminate\Routing\ControllerDispatcher->call(Object(App\Http\Controllers\API\AuthController), Object(Illuminate\Routing\Route), 'logout')
#13 [internal function]: Illuminate\Routing\ControllerDispatcher->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#14 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(52): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#15 [internal function]: Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#16 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#17 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(96): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#18 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(54): Illuminate\Routing\ControllerDispatcher->callWithinStack(Object(App\Http\Controllers\API\AuthController), Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request), 'logout')
#19 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Route.php(174): Illuminate\Routing\ControllerDispatcher->dispatch(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request), 'App\\Http\\Contro...', 'logout')
#20 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Route.php(140): Illuminate\Routing\Route->runController(Object(Illuminate\Http\Request))
#21 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Router.php(724): Illuminate\Routing\Route->run(Object(Illuminate\Http\Request))
#22 [internal function]: Illuminate\Routing\Router->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#23 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(52): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#24 [internal function]: Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#25 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#26 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Router.php(726): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#27 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Router.php(699): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request))
#28 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Router.php(675): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#29 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(246): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#30 [internal function]: Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request))
#31 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(52): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#32 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(44): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#33 [internal function]: Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(Object(Illuminate\Http\Request), Object(Closure))
#34 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(124): call_user_func_array(Array, Array)
#35 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#36 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#37 [internal function]: Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#38 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#39 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(132): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#40 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(99): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#41 /home/koel/koel/index.php(53): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#42 /home/koel/koel/server.php(19): require_once('/home/koel/koel...')
#43 {main}  
<!-- gh-comment-id:242533162 --> @Porco-Rosso commented on GitHub (Aug 25, 2016): Adding the -v switch gives no additional information, only that the scan died 12 minutes in. here is the laravel.log, but from what I can see it has no relation. ``` [2016-08-25 17:36:46] local.ERROR: exception 'Tymon\JWTAuth\Exceptions\TokenExpiredException' with message 'Token has expired' in /home/koel/koel/vendor/tymon/jwt-auth/src/Validators/PayloadValidator.php:83 Stack trace: #0 /home/koel/koel/vendor/tymon/jwt-auth/src/Validators/PayloadValidator.php(41): Tymon\JWTAuth\Validators\PayloadValidator->validateTimestamps(Array) #1 /home/koel/koel/vendor/tymon/jwt-auth/src/Payload.php(38): Tymon\JWTAuth\Validators\PayloadValidator->check(Array) #2 /home/koel/koel/vendor/tymon/jwt-auth/src/PayloadFactory.php(77): Tymon\JWTAuth\Payload->__construct(Array, Object(Tymon\JWTAuth\Validators\PayloadValidator), false) #3 /home/koel/koel/vendor/tymon/jwt-auth/src/JWTManager.php(81): Tymon\JWTAuth\PayloadFactory->make(Array) #4 /home/koel/koel/vendor/tymon/jwt-auth/src/JWTManager.php(126): Tymon\JWTAuth\JWTManager->decode(Object(Tymon\JWTAuth\Token)) #5 /home/koel/koel/vendor/tymon/jwt-auth/src/JWTAuth.php(158): Tymon\JWTAuth\JWTManager->invalidate(Object(Tymon\JWTAuth\Token)) #6 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(218): Tymon\JWTAuth\JWTAuth->invalidate(Object(Tymon\JWTAuth\Token)) #7 /home/koel/koel/app/Http/Controllers/API/AuthController.php(45): Illuminate\Support\Facades\Facade::__callStatic('invalidate', Array) #8 /home/koel/koel/app/Http/Controllers/API/AuthController.php(45): Tymon\JWTAuth\Facades\JWTAuth::invalidate(Object(Tymon\JWTAuth\Token)) #9 [internal function]: App\Http\Controllers\API\AuthController->logout() #10 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(78): call_user_func_array(Array, Array) #11 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(146): Illuminate\Routing\Controller->callAction('logout', Array) #12 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(94): Illuminate\Routing\ControllerDispatcher->call(Object(App\Http\Controllers\API\AuthController), Object(Illuminate\Routing\Route), 'logout') #13 [internal function]: Illuminate\Routing\ControllerDispatcher->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request)) #14 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(52): call_user_func(Object(Closure), Object(Illuminate\Http\Request)) #15 [internal function]: Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request)) #16 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): call_user_func(Object(Closure), Object(Illuminate\Http\Request)) #17 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(96): Illuminate\Pipeline\Pipeline->then(Object(Closure)) #18 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(54): Illuminate\Routing\ControllerDispatcher->callWithinStack(Object(App\Http\Controllers\API\AuthController), Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request), 'logout') #19 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Route.php(174): Illuminate\Routing\ControllerDispatcher->dispatch(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request), 'App\\Http\\Contro...', 'logout') #20 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Route.php(140): Illuminate\Routing\Route->runController(Object(Illuminate\Http\Request)) #21 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Router.php(724): Illuminate\Routing\Route->run(Object(Illuminate\Http\Request)) #22 [internal function]: Illuminate\Routing\Router->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request)) #23 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(52): call_user_func(Object(Closure), Object(Illuminate\Http\Request)) #24 [internal function]: Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request)) #25 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): call_user_func(Object(Closure), Object(Illuminate\Http\Request)) #26 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Router.php(726): Illuminate\Pipeline\Pipeline->then(Object(Closure)) #27 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Router.php(699): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request)) #28 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Router.php(675): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request)) #29 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(246): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request)) #30 [internal function]: Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request)) #31 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(52): call_user_func(Object(Closure), Object(Illuminate\Http\Request)) #32 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(44): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request)) #33 [internal function]: Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(Object(Illuminate\Http\Request), Object(Closure)) #34 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(124): call_user_func_array(Array, Array) #35 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #36 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request)) #37 [internal function]: Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request)) #38 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): call_user_func(Object(Closure), Object(Illuminate\Http\Request)) #39 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(132): Illuminate\Pipeline\Pipeline->then(Object(Closure)) #40 /home/koel/koel/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(99): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request)) #41 /home/koel/koel/index.php(53): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request)) #42 /home/koel/koel/server.php(19): require_once('/home/koel/koel...') #43 {main} ```
Author
Owner

@BernardGoldberger commented on GitHub (Aug 25, 2016):

One of the differences when running with --force is that it uses more memory, try to increase the memory_limit and see if it changes anything.

<!-- gh-comment-id:242540799 --> @BernardGoldberger commented on GitHub (Aug 25, 2016): One of the differences when running with `--force` is that it uses more memory, try to increase the `memory_limit` and see if it changes anything.
Author
Owner

@BernardGoldberger commented on GitHub (Aug 25, 2016):

Have a look here

<!-- gh-comment-id:242541239 --> @BernardGoldberger commented on GitHub (Aug 25, 2016): Have a look [here](http://stackoverflow.com/questions/20667761/composer-killed-while-updating)
Author
Owner

@Porco-Rosso commented on GitHub (Aug 25, 2016):

yup, that turned out to be the problem!
Upped the RAM and Swap temporarily on the VM and gave it another shot.
Didn't post as I was waiting to see if the scan would complete, and it did.
Thanks for the help @bdgold !

<!-- gh-comment-id:242542297 --> @Porco-Rosso commented on GitHub (Aug 25, 2016): yup, that turned out to be the problem! Upped the RAM and Swap temporarily on the VM and gave it another shot. Didn't post as I was waiting to see if the scan would complete, and it did. Thanks for the help @bdgold !
Author
Owner

@Porco-Rosso commented on GitHub (Aug 25, 2016):

Actually although the scan worked. I still get missing errors for some of the artwork (404).
Is there a way to regenerate the thumbnails? (newly added tracks display proper artwork)

<!-- gh-comment-id:242543810 --> @Porco-Rosso commented on GitHub (Aug 25, 2016): Actually although the scan worked. I still get missing errors for some of the artwork (404). Is there a way to regenerate the thumbnails? (newly added tracks display proper artwork)
Author
Owner

@BernardGoldberger commented on GitHub (Aug 25, 2016):

php artisan koel:sync --force --tags=cover

<!-- gh-comment-id:242548106 --> @BernardGoldberger commented on GitHub (Aug 25, 2016): `php artisan koel:sync --force --tags=cover`
Author
Owner

@Porco-Rosso commented on GitHub (Aug 26, 2016):

Sorry to comment, but --force --tags=cover still didn't do it. I still have many missing images

<!-- gh-comment-id:242678408 --> @Porco-Rosso commented on GitHub (Aug 26, 2016): Sorry to comment, but `--force --tags=cover` still didn't do it. I still have many missing images
Author
Owner

@phanan commented on GitHub (Aug 26, 2016):

Hmm. Actually php artisan koel:sync --force --tags=cover shouldn't fix your problem. I'm not sure what went wrong honestly. Is it an option to empty the database and start from scratch, given that you've just installed Koel?

<!-- gh-comment-id:242679865 --> @phanan commented on GitHub (Aug 26, 2016): Hmm. Actually `php artisan koel:sync --force --tags=cover` shouldn't fix your problem. I'm not sure what went wrong honestly. Is it an option to empty the database and start from scratch, given that you've just installed Koel?
Author
Owner

@Porco-Rosso commented on GitHub (Aug 26, 2016):

I've had it installed for some time. But yes, I can empty the database.

Is there a way to just clear the songs from the database? I rather not have to re-setup the user accounts.

<!-- gh-comment-id:242694586 --> @Porco-Rosso commented on GitHub (Aug 26, 2016): I've had it installed for some time. But yes, I can empty the database. Is there a way to just clear the songs from the database? I rather not have to re-setup the user accounts.
Author
Owner

@phanan commented on GitHub (Aug 26, 2016):

In such a case then no, don't empty the database, but maybe try another installation elsewhere and see if the covers are there. Again, I don't know the cause of your problem (yet), so am just suggesting here.

<!-- gh-comment-id:242697640 --> @phanan commented on GitHub (Aug 26, 2016): In such a case then no, don't empty the database, but maybe try another installation elsewhere and see if the covers are there. Again, I don't know the cause of your problem (yet), so am just suggesting here.
Author
Owner

@BernardGoldberger commented on GitHub (Aug 26, 2016):

I was able to reproduce it by simply deleting one of the cover files from /public/img/covers/, now no matter what I have done it wont regenerate.

<!-- gh-comment-id:242710061 --> @BernardGoldberger commented on GitHub (Aug 26, 2016): I was able to reproduce it by simply deleting one of the cover files from `/public/img/covers/`, now no matter what I have done it wont regenerate.
Author
Owner

@phanan commented on GitHub (Aug 26, 2016):

It might be a bug, but why would Koel (assuming it's Koel) delete a cover from the first place?

<!-- gh-comment-id:242752976 --> @phanan commented on GitHub (Aug 26, 2016): It might be a bug, but why would Koel (assuming it's Koel) delete a cover from the first place?
Author
Owner

@BernardGoldberger commented on GitHub (Aug 26, 2016):

It happened to me a while ago when I reinstalled Koel and exported the DB but not the public/img folder, I ended up restoring from a backup.

@Porto-Rosso can you check the image file name in the DB for and album that gives a 404, then go to public/img/covers and check if the file exists or not.

<!-- gh-comment-id:242772433 --> @BernardGoldberger commented on GitHub (Aug 26, 2016): It happened to me a while ago when I reinstalled Koel and exported the DB but not the public/img folder, I ended up restoring from a backup. @Porto-Rosso can you check the image file name in the DB for and album that gives a 404, then go to public/img/covers and check if the file exists or not.
Author
Owner

@Porco-Rosso commented on GitHub (Aug 27, 2016):

@bdgold So I checked which albums are giving 404 errors.

Most (but not all) missing images begin with 56XXXXX.XXXXXX.png, however in my public/img/covers all the filenames begin with 57XXXXX.XXXXXX.png

<!-- gh-comment-id:242920695 --> @Porco-Rosso commented on GitHub (Aug 27, 2016): @bdgold So I checked which albums are giving 404 errors. Most (but not all) missing images begin with `56XXXXX.XXXXXX.png`, however in my `public/img/covers` all the filenames begin with `57XXXXX.XXXXXX.png`
Author
Owner

@BernardGoldberger commented on GitHub (Aug 28, 2016):

@Porco-Rosso that confirms that the images are indeed gone, the question now as @phanan pointed out is, why?

Do you remember doing what I did https://github.com/phanan/koel/issues/425#issuecomment-242772433? Maybe there is something else you did that can try to replicate?

<!-- gh-comment-id:242978836 --> @BernardGoldberger commented on GitHub (Aug 28, 2016): @Porco-Rosso that confirms that the images are indeed gone, the question now as @phanan pointed out is, why? Do you remember doing what I did https://github.com/phanan/koel/issues/425#issuecomment-242772433? Maybe there is something else you did that can try to replicate?
Author
Owner

@Porco-Rosso commented on GitHub (Aug 29, 2016):

Besides running the scan multiple times, and the process getting killed due to limited RAM no.

My suspicions are that whatever happened occurred during the updating process of Koel.

Seeing as I am having other minor issues with Koel (not being able to get a login cookie when using a reverse proxy) I think at this point I might just save myself some time by reinstalling everything from scratch.

<!-- gh-comment-id:243009174 --> @Porco-Rosso commented on GitHub (Aug 29, 2016): Besides running the scan multiple times, and the process getting killed due to limited RAM no. My suspicions are that whatever happened occurred during the updating process of Koel. Seeing as I am having other minor issues with Koel (not being able to get a login cookie when using a reverse proxy) I think at this point I might just save myself some time by reinstalling everything from scratch.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#302
No description provided.