mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #705] Help with sync and duplication error. #498
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#498
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 @pitylee on GitHub (Jan 3, 2018).
Original GitHub issue: https://github.com/koel/koel/issues/705
On the Koel v3.7.0 commit
64be4f5I am experiencing a strange issue.Happening on Ubuntu running on Arm with full setup (npm, gulp, php, lamp, errthing) even xsendfile set up.
After a successfull init, and my post about how to init and install the webpack mix node module, and how to generate the webpack mix json and the assets found installing comment here and generating comment here what I did was:
Downloaded the SQL and rewrote all the charsets in the database's dump, but also did change'em in pma, related to the issue found here about initial duplicate error everything was fine, could log in, but can not scan the media path saying on the command:
php artisan koel:sync --forceAnyone has an idea why is this happening? I know, it's:
` // If this is a compilation album, its artist must be "Various Artists"
if ($isCompilation) {
$artist = Artist::getVariousArtist();
}
`
Any help would be greately appreciated, as I want to have a player for my open NAS and haven't yet set up with @thebigmunch/gmusicapi-scripts.
Thanks in advance.
Cheers, guys!
@pitylee commented on GitHub (Jan 3, 2018):
As this is an issue I've met already the second time, I am devoted to contribute by documenting my way to resolving it.
As my attempt above failed while messing with the migrated database, I strongly believe it was a huge mistake.
I have dropped all the tables in the DB and ran
php artisan koel:initagain, and it populated the database successfully again with the user I've set in .env (just realized I've lost everything I've set in .env - shame, I had all the API-s set up)I re-run the
php artisan koel:synccommand and now it seems to be able to sync, as 63% of my music library was successfully synced as I'm writing, 1734/2652 is imported.Will get back with results and a quick review on going to prod from demo.
@pitylee commented on GitHub (Jan 4, 2018):
After the initial sync, that succeeded only ~70%, the second sync showed this error:
SO yeah, some kind of modifications are needed in the database. :(
@BrookeDot commented on GitHub (Apr 22, 2020):
Hi @pitylee
I'm closing this as stale but please to re-open if you are still having trouble with the latest version of Koel.