Microservices Error

Please help in resolving this error thrown from the microservices container /usr/src/app/node_modules/local-reverse-geocoder/index.js:746 throw err; ^ CsvError: Invalid Record Length: expect 19, got 4 on line 4538 at Object.__onRecord (/usr/src/app/node_modules/csv-parse/dist/cjs/index.cjs:940:11) at Object.parse (/usr/src/app/node_modules/csv-parse/dist/cjs/index.cjs:903:36) at Parser._flush (/usr/src/app/node_modules/csv-parse/dist/cjs/index.cjs:1336:26) at Parser.final [as _final] (node:internal/streams/transform:112:25) at callFinal (node:internal/streams/writable:694:27) at prefinish (node:internal/streams/writable:723:7) at finishMaybe (node:internal/streams/writable:733:5) at afterWrite (node:internal/streams/writable:504:3) at onwrite (node:internal/streams/writable:477:7) at Parser.Transform._read (node:internal/streams/transform:245:5) { code: 'CSV_RECORD_INCONSISTENT_FIELDS_LENGTH', bytes: 786432, comment_lines: 0, empty_lines: 0, invalid_field_length: 0, lines: 4538, records: 4537, columns: false, error: undefined, header: false, index: 4, raw: undefined, 
4 Replies
jrasm91
jrasm913y ago
Reverse geocoding downloads some files each day to work, and it looks like something went wrong with the download (connection was interrupted/failed part way through). I believe removing and re-adding the container will fix it. Alternatively, deleting the bad files in the container would fix it. Basically the Geo coding folder. https://immich.app/docs/FAQ#how-can-i-run-immich-as-a-non-root-user
FAQ | Immich
What is the difference between the cloud icon on the mobile app?
jrasm91
jrasm913y ago
(step number 3 had the details on the location of the folder) You have a bad CSV file in that folder so delete it either by recreating the container, manually removing the file in the container, creating a mount and deleting it through that, etc.
rardxyz
rardxyzOP3y ago
Ok, I just recreated the containers and its working again. Thanks!
jrasm91
jrasm913y ago
We use a third party library for the reverse geocoding and this issue happens fairly regularly so we may need to fix it upstream at some point.

Did you find this page helpful?