#Unable to search location in web

1 messages · Page 1 of 1 (latest)

lucid zenith
#

While trying to manual add GPS info to some of my uploaded pictures, I notice the location search does not work.

This was added in https://github.com/immich-app/immich/pull/7139 and uses the geodata_places table. Executing a select-all query in my postgres database, I can see there are no rows in this table.

I there any special procedure needed to fill this table? I followed the https://immich.app/docs/install/docker-compose/ guide to set everything up.

No backup/restores have been done, and upgrades have been done directly on the stack using docker compose pull && docker compose up -d.

Docker-compose: https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml

.env

UPLOAD_LOCATION=./upload
DB_DATA_LOCATION=./postgres
IMMICH_VERSION=release
DB_USERNAME=postgres
DB_DATABASE_NAME=immich
livid pagodaBOT
#

:wave: Hey @lucid zenith,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich immich.

References

#

Checklist

I have...

  1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: read applicable release notes.
  3. :ballot_box_with_check: reviewed the FAQs for known issues.
  4. :ballot_box_with_check: reviewed Github for known issues.
  5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: uploaded the relevant information (see below).
  7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

  • Your docker-compose.yml and .env files.
  • Logs from all the containers and their status (see above).
  • All the troubleshooting steps you've tried so far.
  • Any recent changes you've made to Immich or your system.
  • Details about your system (both software/OS and hardware).
  • Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
  • The version of the Immich server, mobile app, and other relevant pieces.
  • Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

livid pagodaBOT
short laurel
#

It should get populated on startup. Are there any errors in the log when you start the container?

tired citrus
#

Did you ever do a database backup/restore?

lucid zenith
#

I have never done a backup/restore. There also seem to be no errors on startup (in none of containers searching for "err")

livid pagodaBOT
tired citrus
#

so the table does exist in the DB but is empty, correct?

lucid zenith
#

Correct

#

I tried to find references in the Github repository where table is populated, but could not find anything.

tired citrus
#

can you post the postgres logs please? when did you install this immich instance?

#

it definitely should be populated automatically

#

to the point that there is no manual method

lucid zenith
# tired citrus can you post the postgres logs please? when did you install this immich instance...
2024-12-10 14:11:27.509 UTC [1] LOG:  starting PostgreSQL 14.10 (Debian 14.10-1.pgdg120+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-12-10 14:11:27.509 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2024-12-10 14:11:27.509 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2024-12-10 14:11:27.510 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-12-10 14:11:27.516 UTC [29] LOG:  database system was shut down at 2024-12-10 14:11:26 UTC
[2024-12-10T14:11:27Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17332".
[2024-12-10T14:11:27Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17576".
[2024-12-10T14:11:27Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17576/segments/b1e636e4-b7e0-4f06-8325-8515092027b7".
2024-12-10 14:11:27.536 UTC [1] LOG:  database system is ready to accept connections
[2024-12-10T14:11:27Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17332/segments/4a90dccf-5229-4507-856f-ebe78bf6faae".
#

I created this stack not so long ago, couple of months ago

short laurel
#

Can you post the output of select * from system_metadata where key = 'reverse-geocoding-state';?

lucid zenith
short laurel
#

hmm, seems normal

lucid zenith
#

And just to be sure, I am not crazy:

immich=# select * from geodata_places;
 id | name | longitude | latitude | countryCode | admin1Code | admin2Code | modificationDate | admin1Name | admin2Name | alternateNames 
----+------+-----------+----------+-------------+------------+------------+------------------+------------+------------+----------------
(0 rows)
short laurel
#

Can you restart the container and post the full log?

lucid zenith
#

I can see the init log of "Initializing metadata repository" but not the completion of "Geodata import completed"

short laurel
#

Lol, not sure how I missed that

#

Just delete that row from the table

lucid zenith
#

Looks much better:

2024-12-10 15:50:16 [Nest] 7  - 12/10/2024, 2:50:16 PM     LOG [Microservices:MapRepository] 10000 geodata records imported
2024-12-10 15:50:16 [Nest] 17  - 12/10/2024, 2:50:16 PM     LOG [Api:EventRepository] Websocket Connect:    PxPZbVPWc-zJMQflAAAB
2024-12-10 15:50:17 [Nest] 7  - 12/10/2024, 2:50:16 PM     LOG [Microservices:MapRepository] 20000 geodata records imported
2024-12-10 15:50:17 [Nest] 7  - 12/10/2024, 2:50:16 PM     LOG [Microservices:MapRepository] 30000 geodata records imported
#

Thank you very much for the fast support!

livid pagodaBOT
#

This thread has been closed. To re-open, use the button below.