Problems with Core-update samba

After the last core update today with samba I can no longer access my shares, all permissions are gone.
I urgently need help.

I have also noticed the following.

Apparently not all permissions are gone, the folders are completely missing permissions, the files have partial permissions. As a domain admin and owner, I cannot change any permissions for either folders or files, which is all very strange.
I don’t know how I can fix this.

Did you already try to (re)set permissions as explained in the docs: File server — NS8 documentation

Set permissions: remove any existing ACLs and recursively grant new initial ACLs

Which OS are you using? I can’t reproduce on Debian 12…

Is it possible to share logs from the core upgrade?

Did you already try to restart the service/server?

Is it the same using IP address or name when you browse a share?

The restore of an NS8 backup should set the right permissions again.

@mrmarkuz Thank you for your help

Did you already try to (re)set permissions as explained in the docs: File server — NS8 documentation

Yes, I tried that. I restarted the server and tried again, now it has partially worked.

Which OS are you using? I can’t reproduce on Debian 12…

Rocky Linux 9.3

Is it possible to share logs from the core upgrade?

Unfortunately, I do not know how to retrieve the correct log files.

Did you already try to restart the service/server?

yes

Is it the same using IP address or name when you browse a share?

yes

The restore of an NS8 backup should set the right permissions again.

I will now try a restore from last night’s backup, which will take a while.

I hope that everything will work correctly again after the restore.

From the system logs page, just share the timeframe when the core upgrade happened.

Good luck!

@mrmarkuz I have restored the backup and everything is working perfectly again.
However, I’m not sure it was due to this morning’s update, as Samba was included, it was my guess.
I don’t access all available folders and files every day and maybe it was a coincidence that I encountered this problem shortly afterwards. It’s working again and all is well.
Thank you very much for your support.

1 Like