You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to import my 10 year history of Spotify, it managed 160416 out of 222467 songs.
When I retry I get the following:
your-spotify-server-1 | POST /import/retry 200 2420.327 ms - 25 your-spotify-server-1 | GET /imports 200 6.054 ms - 915 your-spotify-server-1 | [error] Retrying crashed promise, 1/10, retrying in 30 seconds... mongo | {"t":{"$date":"2024-11-13T08:40:39.078+00:00"},"s":"I", "c":"WTCHKPT", "id":22430, "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":{"ts_sec":1731487239,"ts_usec":78878,"thread":"1:0x77faab600640","session_name":"WT_SESSION.checkpoint","category":"WT_VERB_CHECKPOINT_PROGRESS","category_id":6,"verbose_level":"DEBUG","verbose_level_id":1,"msg":"saving checkpoint snapshot min: 277722, snapshot max: 277722 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0) base write gen: 7538"}}} your-spotify-server-1 | [error] Retrying crashed promise, 2/10, retrying in 30 seconds...
Expected behavior
Continue import
Additional context
services: server: image: yooooomi/your_spotify_server restart: always ports: - 8080:8080 links: - mongo depends_on: - mongo environment: API_ENDPOINT: http://192.168.1.103:8080 # This MUST be included as a valid URL in the spotify dashboard (see below) CLIENT_ENDPOINT: http://192.168.1.103:3001 SPOTIFY_PUBLIC: XXX SPOTIFY_SECRET: XXX mongo: container_name: mongo image: mongo:6 volumes: - ./your_spotify_db:/data/db web: image: yooooomi/your_spotify_client restart: always ports: - 3001:3000 environment: API_ENDPOINT: http://192.168.1.103:8080 networks: {}
Screenshots
If applicable, add screenshots to help explain your problem.
Shared link
If you don't mind, you can add a Shared link to this issue by clicking Share this page on your YourSpotify application so that I can identify the issue quicker.
The text was updated successfully, but these errors were encountered:
This same thing happened to me, except with zero of the songs (of a 13 year history) imported. I was using a vpn. I turned off the vpn, and then got a successful import.
Describe the bug
Trying to import my 10 year history of Spotify, it managed 160416 out of 222467 songs.
When I retry I get the following:
your-spotify-server-1 | POST /import/retry 200 2420.327 ms - 25 your-spotify-server-1 | GET /imports 200 6.054 ms - 915 your-spotify-server-1 | [error] Retrying crashed promise, 1/10, retrying in 30 seconds... mongo | {"t":{"$date":"2024-11-13T08:40:39.078+00:00"},"s":"I", "c":"WTCHKPT", "id":22430, "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":{"ts_sec":1731487239,"ts_usec":78878,"thread":"1:0x77faab600640","session_name":"WT_SESSION.checkpoint","category":"WT_VERB_CHECKPOINT_PROGRESS","category_id":6,"verbose_level":"DEBUG","verbose_level_id":1,"msg":"saving checkpoint snapshot min: 277722, snapshot max: 277722 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0) base write gen: 7538"}}} your-spotify-server-1 | [error] Retrying crashed promise, 2/10, retrying in 30 seconds...
Expected behavior
Continue import
Additional context
services: server: image: yooooomi/your_spotify_server restart: always ports: - 8080:8080 links: - mongo depends_on: - mongo environment: API_ENDPOINT: http://192.168.1.103:8080 # This MUST be included as a valid URL in the spotify dashboard (see below) CLIENT_ENDPOINT: http://192.168.1.103:3001 SPOTIFY_PUBLIC: XXX SPOTIFY_SECRET: XXX mongo: container_name: mongo image: mongo:6 volumes: - ./your_spotify_db:/data/db web: image: yooooomi/your_spotify_client restart: always ports: - 3001:3000 environment: API_ENDPOINT: http://192.168.1.103:8080 networks: {}
Screenshots
If applicable, add screenshots to help explain your problem.
Shared link
If you don't mind, you can add a Shared link to this issue by clicking Share this page on your YourSpotify application so that I can identify the issue quicker.
The text was updated successfully, but these errors were encountered: