1 person found this helpful
To unlock the zimbra user try this as root user:
pam_tally --reset --user zimbra
chage -m -1 -M -1 zimbra
Thank to the unlock commands agawarikar
I managed to make it work now.
Still, when I run the mount-nfs-store.pl it seems that the command:
system("chown -R zimbra:zimbra $folder_store");
doesn't work and continue to through my a:
"Error occurred: directory does not exist or is not writable: /opt/zimbra/store78"
so at this point, I perform the necessary steps by myself:
chown -R zimbra:zimbra /opt/zimbra/store78
su - zimbra -c 'zmvolume -a -n store78 -t primaryMessage -p /opt/zimbra/store78 --compress false'
su - zimbra -c 'zmvolume -l | tail -7 | head -1 | cut -f2 -d:' < to retreive the Volume ID
su - zimbra -c 'zmvolume -sc -id 3'
and when you list the volumes:
Volume id: 1
Volume id: 2
Volume id: 3
I provisioned a new user and his account was directly using the NFS storage:
ll -h /opt/zimbra/store78/
drwxr-x--- 3 zimbra zimbra 80 Mar 21 10:00 0
drwxr-x--- 2 zimbra zimbra 80 Mar 21 10:00 incoming
now, I must check in the Horizon Workspace Data Command Line Interface how moving user storage from the local one to the NFS. I have a couple of users that were provisioned before I was able to add the NFS.
Thank you all for your help
i am getting the errors about not being able to create blob store directory /opt/zimbra/store3/incoming . i have tried the changing the permissions on the store directory, but get "permission denied". i have tried all of the above - not working
Any help much appreciated
thanks for the reply.
There was no problems mounting the export, the data appliance has root and r/w access
can you do me a favor? After mounting, please check if "su - zimbra; cd /opt/zimbra/store*"; touch blah", this will ensure that there is r/w perms for zimbra user on the mount point.
thanks for the reply
what should i see as confirmation that the command has worked?
A new file should be created named "blah" by the user "zimbra"
no - no file called "blah" has been created
Then this is a NFS server issue, and you need to enable correct perms.
The "Error occurred: directory does not exist or is not writable: /opt/zimbra/store10" is misleading, I opened an internal bug and we are in the process of updating the docs/rel notes. It's always a NFS server side perms issue indeed.
cheers for all the help
worked it out - using netapp nfs mount, security style on the qtree was "NTFS", set to "UNIX" - all good