#No backups

1 messages · Page 1 of 1 (latest)

north pier
#

I just updated from 1.136.0 to 1.137.3 and while this seems to have worked, I noticed that I my last backup is from 26.07. When I create a backup job manually, nothing is shown in the logs and no backup is created.

Im using portainer, therefor my docker-compose contains the stack.env reference.

📎 docker-compose.yml 📎 stack.env 📎 logs.txt
cedar merlinBOT
#

:wave: Hey @north pier,

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. :blue_square: 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.

north pier
#

I forgot to mention, I noticed that there is a .immich file with a timestamp matching the last restart, therefor I assume the server can access the backup voluume.

civic warren
#

Can you help explaining how do you check the mount point is mounted correctly?

north pier
#

I just connected to the container console and created a file inside /data/backups using the touch command - that worked

round cloud
#

There are no logs showing an attempted backup.

#

Please post the Postgres logs as well

#

Are you using a reverse proxy? How do you connect to immich

north pier
#

no reverse proxy, postgres-logs:

Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-08-03 17:39:01.832 GMT [1] LOG: skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"

2025-08-03 17:39:01.832 GMT [1] LOG: skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"

2025-08-03 19:39:04.009 CEST [1] LOG: starting PostgreSQL 14.18 (Debian 14.18-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit

2025-08-03 19:39:04.009 CEST [1] LOG: listening on IPv4 address "0.0.0.0", port 5432

2025-08-03 19:39:04.009 CEST [1] LOG: listening on IPv6 address "::", port 5432

2025-08-03 19:39:04.054 CEST [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2025-08-03 19:39:04.057 CEST [32] LOG: database system was shut down at 2025-08-03 19:39:00 CEST

2025-08-03 19:39:04.062 CEST [1] LOG: database system is ready to accept connections

#

what do you mean by how do I connect? I'm using Firefox, http://chunky:2283

chunky is a locally resolved through my pihole to the right ip

round cloud
#

Please try using the local IP and show how you are triggering the job in the UI

north pier
#

using IP instead of hostname and creating the job here:

image.png
#

still no backup, no logs

round cloud
#

Please show more logs. You’ve only sent two lines
Please also show the tab for the database dump settings

north pier
north pier
#

I changed IMMICH_LOG_LEVEL to debug and found the following log when creating the job:

[Nest] 18 - 08/03/2025, 7:01:08 PM DEBUG [Api:LoggingInterceptor~ju3rv8jf] POST /api/jobs 201 5.38ms ::ffff:192.168.1.56

civic warren
#

Thank you, let us take a look at this to see if we can reproduce it

north pier
#

any news? anything else I should try?

civic warren
#

@plush forge Do you mind helping out this case when you have a chance as well?

plush forge
#

Yep, currently in a bit of a tunnel though and only running on very few brain cells, so maybe in a week or so

zenith garden
#

This sounds like the job is being sent to redis, but never picked up by the server. I'd recommend stopping all the services, pulling the release images again, and then starting it up again. After that, try to submit the job manually again and see if anything different happens.