Thanks for the help john
Now the fstab is working and mounting correct
Fstab entry
10.7.248.45:/mnt/nfs-pool1 /mnt/nfspool1 nfs defaults 0 0
Rights on the freenas nfs share
User root
Group wheel
Now I have the problem that my postfix does not start any more due to user
rights error.
administrator@eqx-postfix01:~> sudo service postfix status
* postfix.service - Postfix Mail Transport Agent
Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor
preset: enabled)
Active: failed (Result: timeout) since Thu 2019-03-28 11:36:01 CET; 7s ago
Process: 3995 ExecStopPost=/etc/postfix/system/cond_slp deregister
(code=exited, status=0/SUCCESS)
Process: 3984 ExecStartPost=/etc/postfix/system/cond_slp register
(code=exited, status=0/SUCCESS)
Process: 3982 ExecStartPost=/etc/postfix/system/wait_qmgr 60 (code=exited,
status=0/SUCCESS)
Process: 3893 ExecStart=/usr/sbin/postfix start (code=exited,
status=0/SUCCESS)
Process: 3882 ExecStartPre=/etc/postfix/system/update_postmaps (code=exited,
status=0/SUCCESS)
Process: 3881 ExecStartPre=/etc/postfix/system/update_chroot (code=exited,
status=0/SUCCESS)
Process: 3880 ExecStartPre=/etc/postfix/system/config_postfix (code=exited,
status=0/SUCCESS)
Process: 3879 ExecStartPre=/bin/echo Starting mail service (Postfix)
(code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 19660)
CGroup: /system.slice/postfix.service
Mar 28 11:34:31 eqx-postfix01 postfix/postfix-script[3972]: warning: not owned
by group maildrop: /mnt/nfspool1/public
Mar 28 11:34:31 eqx-postfix01 postfix/postfix-script[3973]: warning: not owned
by group maildrop: /mnt/nfspool1/maildrop
Mar 28 11:34:31 eqx-postfix01 postfix/postfix-script[3977]: starting the
Postfix mail system
Mar 28 11:34:31 eqx-postfix01 postfix/master[3979]: daemon started -- version
3.3.1, configuration /etc/postfix
Mar 28 11:34:31 eqx-postfix01 systemd[1]: postfix.service: PID file
/var/spool/postfix/pid/master.pid not readable (yet?) after start-post: No such
file or directory
Mar 28 11:36:01 eqx-postfix01 systemd[1]: postfix.service: Start-post operation
timed out. Stopping.
Mar 28 11:36:01 eqx-postfix01 postfix/master[3979]: terminating on signal 15
Mar 28 11:36:01 eqx-postfix01 systemd[1]: Failed to start Postfix Mail
Transport Agent.
Mar 28 11:36:01 eqx-postfix01 systemd[1]: postfix.service: Unit entered failed
state.
Mar 28 11:36:01 eqx-postfix01 systemd[1]: postfix.service: Failed with result
'timeout'.
Can anybody help on what to do ?
What do I need to change further more sow postfix can own the files.
Met vriendelijke groeten
Kind regards
De Petter Mattheas
Technical support engineer - projects team
IT-Department Jan De Nul Dredging N.V.
T +32 (0)53 73 95 53
F +32 (0)53 21 00 31
www.jandenul.com
-----Original Message-----
From: John Stoffel <j...@stoffel.org>
Sent: 27 March 2019 15:05
To: De Petter Mattheas <mattheas.depet...@jandenul.com>
Cc: Postfix users <postfix-users@postfix.org>
Subject: RE: nfs as mailq storage?
De> Can you tell me witch param I need to change in main.cf to mount the
De> nfs to the mailq?
As others have said, you need to mount the NFS data store holding your mailq
onto the server. But then you need to make sure your NFS server is robust and
reliable as well. This starts to get into system design, and how your system
is designed with influence you Postfix (and other) design choices.
De> Or do I need to make a symbolic link to the current mailq destination?
- Boot the VM/server running postfix.
- mount the NFS volume(s) you need.
- start networking
- start postfix
All of the above is setup in the VM's linux boot order. I'm assuming you're
running postfix on Linux.
So put your NFS mounts into /etc/fstab on the postfix server, and the system
will boot up with the needed setup.
You will probably want to mount /var/spool/postfix and /var/mail from your NFS
server. If you have just one postfix server, then you don't need to be
careful, but if you have multiple postfix servers, they each need to have their
OWN dedicated /var/spool/postfix directory on the NFS storage.
Making sure your NFS server is reliable is another problem.
John
************************************************************
Any reaction to this e-mail or any other mail, including any
files transmitted therewith to sender's e-mail address(es)
shall be dealt with not as private, but as business
communication(s) and shall be registered as such.
************************************************************
