Claudio Corvino
2020-Jul-13 13:45 UTC
Dovecot permission denied errors on NFS after upgrade to 2.2.17
Hi Jochen, the ID has not changed, in addition the "permission denied" error is random, most of the time Dovecot works well. How can I check the mappings NFS uses? After the Debian upgrade I was using these NFS mount options: rw,user,rsize=8192,wsize=8192,timeo=30,intr Now trying to fix the problem I set "defaults" mount option, but nothing has changed. Thanks On 13/07/20 13:08, Jochen Bern wrote:> On 07/13/2020 12:57 PM, Claudio Corvino wrote: >> we just upgraded our mail server from Debian 8 to Debian 9, so our >> dovecot packages just got upgraded from version 2.2.13 to 2.2.17. > [...] >> Every directory and sub-dir under >> /mnt/mail-storage >> is assigned to vmail:vmail with >> drwx------ >> permission set. > Just a quick shot into the dark, you verified the ownerships on the NFS > *client*, not the NFS *server*, yes? Because NFS speaks UIDs and GIDs, > not their names, so if your Debian 9 installation assigned different IDs > to "vmail" ... > > (You might also want to check what mappings the NFS mount uses, > including possible *default* behaviour.) > > Good luck,-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3812 bytes Desc: S/MIME Cryptographic Signature URL: <https://dovecot.org/pipermail/dovecot/attachments/20200713/4e320e22/attachment.p7s>
Maybe Matching Threads
- Dovecot permission denied errors on NFS after upgrade to 2.2.17
- Dovecot permission denied errors on NFS after upgrade to 2.2.17
- Dovecot permission denied errors on NFS after upgrade to 2.2.17
- Dovecot permission denied errors on NFS after upgrade to 2.2.17
- Dovecot permission denied errors on NFS after upgrade to 2.2.17