#Latest update causing reboot loop

1 messages · Page 1 of 1 (latest)

pure vigil
#

Hi all- thanks in advance for the help. I am running under Docker windows (sorry lol). I've been running immich for the last couple months without problems. However, after the latest update, the immich_server component is stuck in a reboot loop. It repeatedly exits, gets restarted, and then exits again.

Logs, .env, and YML attached. Appreciate the help

torn stormBOT
#

:wave: Hey @pure vigil,

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

References

Checklist

  1. :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: I have read applicable release notes.
  3. :ballot_box_with_check: I have reviewed the FAQs for known issues.
  4. :ballot_box_with_check: I have reviewed Github for known issues.
  5. :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files, making sure to use code formatting.
  7. :ballot_box_with_check: I have 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)

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

torn stormBOT
mighty needle
#

Alright first things first, update your redis container, it's still d6c2911ac51b289db208767581a5d154544f2b2fe4914ea5056443f62dc6e900 but newest is 2d1463258f2764328496376f5d965f20c6a67f66ea2b06dc42af351f75248792

#

It's a little annoying, but check the compose file in each release for an update 🙂

pure vigil
mighty needle
#

The compose file contains a line with the redis container:
image: docker.io/redis:6.2-alpine@sha256:d6c2911ac51b289db208767581a5d154544f2b2fe4914ea5056443f62dc6e900
You need to replace that with
image: docker.io/redis:6.2-alpine@sha256:2d1463258f2764328496376f5d965f20c6a67f66ea2b06dc42af351f75248792

#

After that, just do docker compose up -d again

#

And no, the redis container isn't tagged with release or such I'm afraid, it's from another project

pure vigil
#

ok - that is done, but still same problem.

#

it did pull a new redis, but immich_server still exits

mighty needle
#

Try a simple docker restart immich_server

#

If that doesn't work let's increase verbosity by putting IMMICH_LOG_LEVEL=verbose in your .env file, and then compose down/compose up

pure vigil
#

OK - I got the actal error, but it makes no sense because nothing has changed on my system or in my config from before the update.

#

immich_server | [Nest] 19 - 09/19/2024, 11:56:32 AM ERROR [Api:StorageService] Failed to write upload/encoded-video/.immich: Error: EACCES: permission denied, open 'upload/encoded-video/.immich'
immich_server | [Nest] 19 - 09/19/2024, 11:56:32 AM ERROR [Api:StorageService] The "encoded-video" folder cannot be written to, please make sure the volume is mounted with the correct permissions
immich_server | api worker exited with code 1

rocky viper
#

We just added a check for this in the latest release

#

Like the error says, it indicates a permission issue with your UPLOAD_LOCATION

mighty needle
#

The latest release wants to make an .immich file at the top level

#

Likely your permissions for that very directory aren't fully compliant with that

pure vigil
#

ok let me just 777 it and see what happens. hold on a sec.

mighty needle
#

lol, the old "777 should fix it"

pure vigil
#

sooo... these are the permissions on that directory, already 😕

drwxrwxrwx+

#

and oddly there is already a .immich file there

#

-rwxrwxrwx+ 1 home wheel 13B Sep 17 11:03 .immich

mighty needle
#

Is this maybe somehow a CIFS UID GID thing

pure vigil
#

given it's 777 though, immich should be able to write to it. And, apparently, it already did the first time I pulled the update, right? because the timestamp on that file is Sept-17

#

should i remove .immich and see if it recreates it?

mighty needle
#

What if you delete the file, does it get recreated? :

#

Lmao

pure vigil
#

^ lol lemme see

mighty needle
#

There's one in every folder just fyi

pure vigil
#

ok - same exact error. claims it can't be written to. but it DID recreate the file.
13B Sep 19 12:10 .immich

mighty needle
#

Well I'm out of ideas for now

#

Still going for CIFS shenanigans

pure vigil
#

if CIFS is broken I basically can't use immich which is a bummer. Everything is saved on an SMB share with a password and this was the only way I was able to get the share mounted (granted I'm using docker windows but my file server is FreeBSD/FreeNAS).

Is there any way to circumvent the check, since obviously it can write there (and has been)

mighty needle
#

I'm not saying it's broken I'm saying you might need more options

pure vigil
#

open to suggestions if you (or anyone else) has them 🤞

mighty needle
#

I see people adding crazy things like ,vers=3.0,file_mode=0777,dir_mode=0777

pure vigil
#

will try rn

#

no luck

mighty needle
#

I'm out of ideas for you and I don't want to fudge it all up

pure vigil
ebon fulcrum
#

Did you set UPLOAD_LOCATION itself to 777, or just its child folders?

pure vigil
#

it's also 777

#

drwxrwxrwx+ 7 user wheel 7B Jul 5 20:55 upload

ebon fulcrum
#

Are you still getting the same error?

#

Or is it a different error?

pure vigil
#

same error

#

people on that thread are saying to touch/create the .immich file, but my issue is a little worse, bc immich actually can create the file but acts like it can't.

Guy who created profile/.immich says after he did that though problem just moved to another directory. <shrug>

ebon fulcrum
#

Can you touch that file manually and see if that changes anything?

pure vigil
#

sure lemme try

#

0B Sep 19 12:34 immich

#

lemme restart.

#

same error. lol. it overwrote it and added data

#

13B Sep 19 12:35 .immich

#

and then said it couldn't write

ebon fulcrum
#

……what is happening

pure vigil
#

tldr CIFS is evil. but this sucks honestly 😕

wise spear
#

I had issues with it as well. I had to manually go in and create each .immich file (SMB Share), then worked fine after without changing anything else

pure vigil
wise spear
#

The only difference I think I was I did it from the machine connecting to the share

ebon fulcrum
#

We tried to reproduce this and couldn’t and figured it was a case of the UPLOAD_LOCATION folder not having the right permissions. But this is clearly different

pure vigil
ebon fulcrum
#

Is the cifs share on windows?

pure vigil
#

the share is running on a FreeNAS machine (freebsd). Windows (running docker) connects with SMB

ebon fulcrum
#

Try ssh’ing into the freenas machine and touching the file from there

pure vigil
#

yah that's what i've been doing

#

just was humoring @wise spear by trying notepad

ebon fulcrum
#

Ah, gotcha

#

My only lead is that smb has some special handling with dot files to treat them as hidden, and on windows opening a hidden file with w mode is an error. I don’t know if this is the issue here but I can’t think of anything else

#

I’ve personally made a test instance in wsl2 connecting to a mounted truenas scale smb share and it had no issues. I wonder if it’s a difference in the protocol version or maybe a different share configuration

#

There’s also the share ACL besides the unix file permissions. Maybe it’s something to do with that?

pure vigil
#

yah idk. haven't issues like this before in other contexts. usually if you can create a file you're good

ebon fulcrum
#

Besides the share ACL, I’ve got nothing

#

What a weird issue

pure vigil
ebon fulcrum
#

Can you run docker compose down to stop the containers, docker compose run --entrypoint=bash immich-server to get a shell with the server container and check upload/encoded-video/.immich?

cloud lantern
#

So to be clear, you're running FreeNAS (TrueNAS Core?) as the OS your share exists in. Would you be able share the config for that share, and the mount config that you have?

#

I want to try and get a reproduction of this, but any attempts at that so far have led nowhere

pure vigil
cloud lantern
#

TIL (or remembered) you can do CIFS directly in compose

#

Thanks for that, I will test your setup next if I can't get a reproduction working on my own setup 😛

cloud lantern
#

Recreated locally with your exact mount settings (using unraid for the NAS) and everything works fine here

#

Could you please provide an ls -la output from the NAS itself?

pure vigil
#

And this is the output inside encoded-video — in fact this is the .immich file that .immich created and says it can’t write 😵‍💫

-rwxrwxrwx+ 1 user wheel 13B Sep 19 14:41 .immich

I’m just really at a loss

#

Maybe this is helpful info, too;

#1286397327875244043 message

cloud lantern
#

I guess it's time for me to spin up truenas core...

clear wadi
pure vigil
#

This (below) is the output from a bash console inside immich-server

#1286397327875244043 message

clear wadi
clear wadi
pure vigil
#

And I’ve been running it for months and it’s been creating files and folders like there’s no tomorrow

clear wadi
cloud lantern
clear wadi
#

I'm guessing this is related to some stupid quirk with hidden files.

cloud lantern
#

Trying to replicate your setup as close as possible

pure vigil
pure vigil
cloud lantern
#

Right, that's fine, what about the user settings specifically for the user you're connecting from?

#

This screen

pure vigil
#

same thing bigger.

cloud lantern
#

Where do the ACL configs live lmao

#

Ah, found it immediately after sending that...

#

Ah, no this is just the share ACL which looks different to the view you had

pure vigil
#

storage pool ACL

#

sharing>smb>three dots>file system acl

cloud lantern
#

Nice,t y

pure vigil
ebon fulcrum
#

So you can make the file, but can't write into it?

clear wadi
#

It must be that stupid Windows thing with opening a hidden file with w flag

#

Can you open and write to immich (no leading period)?

cloud lantern
#

So with your exact setup on truenas core, everything works as expected 😅

pure vigil
cloud lantern
#

Not using wsl though, but mert did test that earlier

pure vigil
#

what was causing the issue for the other people? I saw they solved it by creating the file manually? is this related possibly?

#

idk why you can't recreate

#

maybe wsl?

cloud lantern
#

Realistically when you're connecting from WSL -> TrueNAS core, the fact it's WSL and running on windows shouldn't even be a consideration

pure vigil
#

this might be the thing that causes me to wipe the entire computer and install a linux image but ffs...

wise spear
#

Mine was it saying it couldn't create the file. So I created manually and then it started fine. Didn't touch any permission stuff, still could upload photos with no problems. I'm using truenas scale as the smb host and running docker on Linux

cloud lantern
#

As the docker engine itself is running within WSL

pure vigil
#

right

clear wadi
#

But smb can have windows compat settings for hidden files is what I meant

#

Not that Windows is actually in play.

pure vigil
#

yah is this a wsl incompatibility because it's called (dot)immich

#

instead of like writetest.txt

#

i hate hate hate docker windows

cloud lantern
#

To confirm everything created successfully

clear wadi
pure vigil
clear wadi
#

Can you write a new dot file as well? Like .immich2?

clear wadi
pure vigil
cloud lantern
#

You're root

clear wadi
#

So reading and writing everything inside the container all works

cloud lantern
#

su node

pure vigil
clear wadi
#

We run as root by default, is OP running as 1000?

pure vigil
cloud lantern
clear wadi
#

I don't think so

cloud lantern
#

Hmmm, yea it is running as root by default

pure vigil
#

so the server has been writing for months to this folder. maybe the write test is different

#

i can't write as node. anything

clear wadi
#

That's expected. You aren't running this with a specific id are you? It will default to root

#

If it was as node it would never be able to create anything like all uploads would fail

cloud lantern
#

Alright lets try something

#

Go back to root, run the following

#

node

pure vigil
cloud lantern
#

const { default: fs } = await import("node:fs/promises")

#

await fs.writeFile('/usr/src/app/upload/encoded-video/.immich1', 'test')

clear wadi
#

Is it failing on the encoded video check still when it tries to boot?

pure vigil
#

const results in undefined

cloud lantern
pure vigil
#

await also, undefined

clear wadi
#

Type node first lol

cloud lantern
#

There's nothing returned from those 😛

pure vigil
cloud lantern
#

Check the encoded-video folder pls

#

Does a .immich1 file exist with contents 'test'?

pure vigil
#

content didn't change

#

nvm

#

my bad

#

YES

cloud lantern
#

So it wrote that?

pure vigil
#

yes

cloud lantern
#

Well that's just extra confusing lmao

#

Wtaf

clear wadi
#

Can you try to start it again?

pure vigil
#

yes

#

it wrote 1726789955046 to .immich

clear wadi
#

So it successfully writes and then throws an error?

pure vigil
#

yup

cloud lantern
#

This is honestly baffling

#

Because it isn't even failing at the read, it's failing on the write, while succeeding to write the file...

pure vigil
#

idk how you guys coded the error. it says filed write, but then says error: eacces: permission denied, open

#

maybe it is wsl with hidden file? idk though

cloud lantern
#

The last part is just raw what node returns to us

pure vigil
#

ah

ebon fulcrum
#

Maybe the first write works, but the second write fails?

cloud lantern
#

There is only one write

#

Oh, you mean on retry

#

Sure, we can test that

#

Can you open up
node

#

const { default: fs } = await import("node:fs/promises")

#

await fs.writeFile('/usr/src/app/upload/encoded-video/.immich1', 'test1234')

ebon fulcrum
#

It calls verifyWriteAccess twice the first time it’s writing the file

pure vigil
cloud lantern
#

Had you deleted it since last time?

pure vigil
#

yup

cloud lantern
#

Just because the .immich file is gone now

pure vigil
#

i emptied everything to test

cloud lantern
#

Oh, we need to test overwriting it

#

So run the commands again, change the value to 12345

pure vigil
#

ok

#

yup

cloud lantern
#

Excellent, we have a reproduction!

pure vigil
#

oh wait

#

hoooooold on

#

i have notepad open

#

fml

cloud lantern
#

Hmmm, that's interesting actually

ebon fulcrum
#

But that might be relevant though. Maybe there’s some kind of file lock from the earlier fs calls

cloud lantern
#

Could we be writing to quickly in succession?

#

Yea.....

#

SMB loves to lock files lol

pure vigil
#

ok still happening. wasn't my fault

cloud lantern
#

Ok, could you try writing to immich1 instead twice in a row?

#

No dot

pure vigil
#

yah

#

give me a sec

cloud lantern
#

undefined is a success fyi

pure vigil
#

first attempt worked:

cloud lantern
#

And second?

pure vigil
#

yep, worked.

cloud lantern
#

Yea, so it's absolutely a dotfile thing

#

Great

#

@clear wadi do we just say fuck this and change it to not a dotfile

#

I can't reproduce this problem, I have no idea why, but it's obviously dotfile related

clear wadi
#

Why do we think it is a dot?

cloud lantern
#

He just reproduced the error in the node console

#

Writing the second time fails with a dotfile

#

It doesn't with a normal file

#

Same folder

clear wadi
#

When it was open in notepad right?

cloud lantern
#

No

#

He closed that and tried another 5 times

#

zot do a fresh test with .immich2 twice in a row just to confirm?

pure vigil
#

yah i just tried again. repro'd again

cloud lantern
#

Cool ty

#

Ahead of me 😉

clear wadi
#

Can we try pasting 3 lines? Write, read, write

pure vigil
clear wadi
#

And then do it with a dot and a non dot file and post the screenshot?

cloud lantern
#

I mean, this seems pretty clear there's a problem with the dotfiles specifically

#

But we can test a read too

pure vigil
#

non dot:

clear wadi
#

Can you reproduce Zack?

pure vigil
#

i don't know node. how should i read it out

cloud lantern
#

(await fs.readFile('/usr/src/app/upload/encoded-video/.immich1')).toString()

cloud lantern
pure vigil
cloud lantern
#

So we can write, and we can read, but we can't overwrite

clear wadi
#

The start up code does write, read, write the first time

clear wadi
pure vigil
cloud lantern
#

Yep

#

Every overwrite

clear wadi
#

So basically open with w fails

cloud lantern
#

Yea, like the docs mert posted said

clear wadi
#

And this works fine without a dot file

cloud lantern
#

Yep

clear wadi
#

Yeah I think that sounds like the problem.

#

Let's transition to not a dot file

cloud lantern
#

New cursed docs entry 🙂

#

dotfiles are cursed (on smb)

pure vigil
#

i love you guys if you just solved this...... where's the cookie jar $$

But seriously fuck docker windows

cloud lantern
#

I still want to reproduce this...

#

I'm guessing it must be a WSL thing

#

Which is... super weird

clear wadi
cloud lantern
#

Let me spin up a windows VM

cloud lantern
#

And yet it doesn't reproduce on linux

pure vigil
#

it's only in node that it's throwing an error; since i can do whatever i want to the file from the command line

#

as root*

cloud lantern
#

Don't have to use CIFS just because you're using WSL

#

NFS will work from docker over there too

pure vigil
cloud lantern
#

I see

pure vigil
#

should've been my first clue wsl was cursed...

cloud lantern
#

What windows version are you running?

quartz spindle
#

news flash: docker on windows sucksss

#

thanks guys

cloud lantern
#

I'm now going to spin up a windows VM lmao to replicate that part of your setup

pure vigil
#

Edition Windows 10 Pro
Version 22H2
Installed on ‎6/‎18/‎2024
OS build 19045.4529
Experience Windows Feature Experience Pack 1000.19058.1000.0

cloud lantern
#

Hmmm, can I WSL within a VM...

#

I think I have nested virtualisation enabled wherever I need to, we'll see I guess

#

Who doesn't love spinning up windows VMs at 1:15AM 🙂

#

Want to say thanks to you too @pure vigil for being so responsive to allow us to actually reproduce the problem

#

I spent a lot of my day today trying to reproduce this with no success

pure vigil
#

dude, no, thank YOU. Immich is saving my life and I am surprised by how responsive you guys are. If this isn't just me being an idiot and if you're able to fix it and I get Immich back... totally worth helping you guys repro

#

fwiw, i just tried this and repro'd again. after the second test, i renamed the file test1 to .test1 and it won't overwrite it. so yah. confirmed, at least FOR ME, that it's because it's a dot file.

Hopefully you can reproduce.

#

@cloud lantern check this out

#

if you change the properties in windows and un-check hidden, you can overwrite it. once you overwrite it, it gets hidden attribute again; can't be re-overwritten

cloud lantern
#

Yeaaaaaa

ebon fulcrum
#

yeah screw that

cloud lantern
#

I still don't really get how WSL is affected by this though

#

Thought WSL is a weird concoction 😛

#

I should have a windows VM in 5 or so minutes

pure vigil
#

this is gonna make me build a linux machine. wife gonna kill me another computer.

ebon fulcrum
#

Docker can run from powershell etc. too. Maybe as far as samba is concerned, docker is mounting the share as a windows client

cloud lantern
#

The files show up as hidden for me too fyi

#

But yea, maybe linux docker doesn't care

cloud lantern
#

Right, booting immich in WSL now

#

Only 274 seconds to pull the image

#

And it's still going, just frozen 🙂

pure vigil
#

the last 300kib..

cloud lantern
#

Lmao, and it worked just fine

pure vigil
#

lol seriously

#

what the actual f

#

you're in powershell? and cifs?

cloud lantern
#

Powershell?

#

No I ran this directly in WSL

#

You're running the compose commands from powershell?

pure vigil
#

no

#

from CMD

#

and i used docker desktop

cloud lantern
#

windows command prompt?

pure vigil
#

yup

cloud lantern
#

Can you verify some settings for me?

pure vigil
#

sure

cloud lantern
#

If you go into docker desktop

#

settings > resources > WSL integration

#

What does it show?

pure vigil
cloud lantern
#

Advanced?

pure vigil
cloud lantern
#

Can you open powershell and run
wsl --list

pure vigil
#

PS C:\Users\NUC8-i3BEH1> wsl --list
Windows Subsystem for Linux Distributions:
docker-desktop-data (Default)
docker-desktop
PS C:\Users\NUC8-i3BEH1>

cloud lantern
#

Works through CMD too lol

#

But I did install ubuntu WSL as my default

#

So I think it's running in that

#

Maybe it's different if I hadn't done that?

pure vigil
cloud lantern
#

Hmmm

#

Let me see if I can revert to that

#

The performance is actually terrible

#

Crazy to me that so many people run setups like this 🤣

pure vigil
#

It’s atrocious and I hate it. I have like two things that won’t natively run under BSD and this is one of them (bc of docker). The easy thing for me is if you can repro this and fix it (maybe by renaming the test file). But if you can’t repro it and I am like the edge case’s edge case, I am gonna have to figure something else out. Docker desktop in windows is hot garage. It’s so painful to use

cloud lantern
#

It probably doesn't help that I am double virtualising here

#

But I don't think that's really the problem 😛

#

I still can't reproduce it though lmao

pure vigil
#

Ok I mean you have been super generous with your time. I am bewildered bc it’s clear what’s happening on my system re refusing to overwrite hidden files. But if you can’t reproduce it 🤷‍♂️

Honestly bizarre

cloud lantern
#

I think we'll still make the change

#

I mostly wanted a reproduction case so we could understand it further potentially 😛

pure vigil
#

The zot fix… affected user(s): 1

cloud lantern
#

I assume you don't have any special config in the truenas core smb service settings?

#

Services > SMB

pure vigil
#

SMB 2/3 extensions

cloud lantern
#

Enable Apple SMB2/3 Protocol Extensions?

#

You have that turned on?

pure vigil
#

Yep

clear wadi
#

I think the windows settings are in the smb stuff.

#

Like the behavior we are seeing is via the smb server itself not the client.

cloud lantern
clear wadi
#

What about aux params?

#

Idk, there are the actual underlying settings, not just what true nas shows you

cloud lantern
#

TrueNAS applies the defaults

#

Which in this case is "hidden dot files = true"

#

But I just tried applying that manually even, and it still doesn't break for me...

clear wadi
#

With same file mask?

#

Can you get all the raw settings and compare them or something like that?

pure vigil
#

@cloud lantern you used CIFS, not NFS?

cloud lantern
#

Yea, I used CIFS

#

I am copying your exact setup

pure vigil
#

Blah

cloud lantern
pure vigil
#

If the issue is the SMB server I don’t get why I can overwrite, open, delete, those same files (like in other contexts)

#

🤷‍♂️

cloud lantern
clear wadi
#

Man this is so annoying

#

I am so unsatisfied

torn stormBOT
cloud lantern
#

I found the issues

clear wadi
#

Is it because the filesystem is still "Windows"

#

Even if you run code in wsl?

cloud lantern
#

Honestly I am at a loss

#

Why the hell can't I reproduce it man

clear wadi
#

On Windows right

cloud lantern
#

I am running in WSL, from command prompt, docker compose is the exact same

clear wadi
#

And it is marked as hidden?

cloud lantern
#

I am connecting to truenas core

pure vigil
clear wadi
#

And override works?

cloud lantern
#

File shows as hidden

#

Yep overwrite works, the server starts just fine

clear wadi
#

Can you open with the w flag explicitly?

cloud lantern
#

Well node does that

#

So yes

#

Totally fine

#

What version of docker desktop are you using @pure vigil ?

pure vigil
#

Latest 4.34.2

cloud lantern
#

Can you run wsl -l -v?

pure vigil
cloud lantern
#

The only difference I can see is you have docker-desktop-data, which is something that was removed in docker version 4.30.0

#

But if you had a previous version installed before, it won't remove it, it'll just keep using it

#

But I don't see that causing this issue

clear wadi
#

On Windows, opening an existing hidden file using the 'w' flag (either through fs.open(), fs.writeFile(), or fsPromises.open()) will fail with EPERM. Existing hidden files can be opened for writing with the 'r+' flag.

#

It is in the fs node docs actually

#

Zack needs to go to bed because I am going to bed and he is like 5 hours ahead of me lol

pure vigil
#

lol yah dude. You’ve been at this for a while. If there’s a fix or a workaround immich can implement that would be awesome. But either way, I really appreciate you guys spending so much time on this. And after reading that issue and in the node docs… super goofy. I don’t know why you can’t reproduce it though

cloud lantern
#

So we could manually handle this

clear wadi
#

It looks like it has to do with the actual underlying filesystem call, on the windows side

cloud lantern
#

But just seems like pain

clear wadi
cloud lantern
#

I'd rather just never touch dotfiles ever again :))

clear wadi
#

I think we know why, but best to leave dot files behind at this point

cloud lantern
#

lol

clear wadi
#

Dot files on Windows are cursed

cloud lantern
#

It just works man...

clear wadi
#

I think fs.write is a lower level api

#

You use it with fs.open and I assume specifying the wrong flags would be a problem.

#

Unless this isn't a "real" windows partition or something

#

I have a Windows machine I'll boot to and test tomorrow I think

cloud lantern
#

You can specify the flags with fs.writeFile

#

But yes, r+ only works if the file exists

#

Whereas w works even if it doesn't

clear wadi
#

I see. The problem seems to be fs open with the wrong flags causes Windows to throw an error. If it doesn't for you I don't know what to say lol

cloud lantern
#

Yea, I agree that's the problem

clear wadi
#

Maybe they fixed it in Windows 11 🤣🤣🤣

cloud lantern
#

But I am baffled that it isn't happening here 😛

cloud lantern
#

Btw, @pure vigil I think if you go into your samba share settings and add hide dot files = no into the Auxillary parameters

#

Then turn the SMB service off and on again

#

That'll fix the issue for you until we deploy a patch

pure vigil
#

Oh I will try this tonight. Thank you

cloud lantern
#

I'm done trying to reproduce this though, at least for now 🤣

#

I even downgraded my docker desktop so I had the two different WSL instances

#

I'm just deemed worthy of being allowed to write to hidden files obviously...

pure vigil
#

Yep

#

That worked

cloud lantern
#

Neat

#

At least we can get you up and running again 😛

pure vigil
#

Thank you so much

cloud lantern
#

And it's only 4AM, look at that!

#

🤣

pure vigil
#

LOL oh man

#

Go to bed. But seriously, thank you

cloud lantern
#

@clear wadi we'll see who wakes up first in the morning 😛

ebon fulcrum
#

Bun tried to warn us, but it’s too late now 😔

mighty needle
#

Well this was a wild ride to wake up to

cloud lantern
#

Hey @pure vigil, whenever you're around, if you'd be willing to revert the change to your SMB config from last night and upgrade to a test build for us, it'd be much appreciated 🙂

#

So if you could remove that SMB setting around the hidden dot files, restart SMB service, then verify your instance doesn't reboot correctly anymore.

#

Then, if you could set your immich-server to use this image ghcr.io/immich-app/immich-server:pr-12812 and docker compose down, docker compose pull then docker compose up -d and see if the server starts correctly, that'd be great! 🙂

#

You're like, the only reliably reproduction case we have for this issue 🤣

pure vigil
#

Yep. I can do this in a couple hours. (Maybe less. I have one thing for work I need to take care of first but I will do this and report back. Won’t take long to check.)

cloud lantern
#

Perfect! Thanks a bunch 🙂

pure vigil
#

reverted the SMB config. confirmed broken again. going to try the new build.

#

looks good to me

#

yeah; it's working

mighty needle
#

What changed 👀

bronze vessel
#

@cloud lantern great news!

cloud lantern
#

Excellent!

pure vigil
#

assuming fix was changing the test file name?

cloud lantern
#

It's still a hidden file actually

#

We just changed the way we write files in the server 🙂

#

Thanks so much for testing, we'll probably roll this out early next week

pure vigil
#

all good. thank you for fixing!

cloud lantern
#

You should be good to stay on this release until then, then update to that version when it's out

#

Though, this is pre-release

pure vigil
#

appreciate you guys.

cloud lantern
#

So you can also rollback to 1.115.0 if you'd prefer 😛

pure vigil
#

nah. i'll stay on it. if something breaks i'll let you know

cloud lantern
#

Everything should be compatible with doing that

#

Cool, sounds good 🙂

pure vigil
#

thanks guys