Unable to add NFS storage to the Data appliance

[ekrejci]

Hello,

I’m trying to add NFS storage to the data appliance.

I followed the documentation, and when I ran the script supposed to mount/add the NFS storage to the appliance, an error saying that the export is read only, which is actually not the case:

./mount-nfs-store.pl --nfs servername.domain.com:/hzn-data-01

NFS: servername.domain.com:/hzn-data-01

HOST: servername.domain.com

servername.domain.com is alive.

mount.nfs: timeout set for Fri Mar  8 21:33:13 2013

mount.nfs: trying text-based options 'hard,rsize=32768,wsize=32768,intr,addr=128.178.102.59'

mount.nfs: prog 100003, trying vers=3, prot=6

mount.nfs: trying XXX.XXX.XXX.XXX prog 100003 vers 3 prot TCP port 2049

mount.nfs: prog 100005, trying vers=3, prot=17

mount.nfs: trying XXX.XXX.XXX.XXX prog 100005 vers 3 prot UDP port 1234

servername.domain.com:/hzn-data-01 on /opt/zimbra/store10 type nfs (rw,sync,noatime,hard,rsize=32768,wsize=32768,intr)

Error occurred: directory does not exist or is not writable: /opt/zimbra/store10

zmvolume failed at ./mount-nfs-store.pl line 49.

Of course, I tried to go in the mount point (in this case /opt/zimbra/store10) and was totally able to write into it (touch, create file + dir, etc...).

The data appliance has root access to the NFS export. I don’t have any idea about the cause of this error.

Any clue?

Many thanks

Eric

[Zeilon]

I also have problems adding an external NFS share to horizon data.

DId you manage to get this to work?

/Zeilon

[ekrejci]

Hi,

no success at all with the NFS.

going to open a SR. no other choice.

will keep you informed

sincerely

Eric

[sravuri]

Hi Eric,

Can you please check the following? You will need to run the script as zimbra user. Did you do that already?

Also, you may need to do the following: chown -R zimbra:zimbra /opt/zimbra/store10

[ekrejci]

Hi,

thank you for the update.

I'm gonna check these tomorrow. but it is certain that the chown hasn't been applied.

I will keep you informed ASAP.

sincerely

Eric

[Zeilon]

Hi

Sorry for hijacking your thread.

I tried the script with zimbra user. No success..

Maybe i,m missing a step..  (or 2 )

I,ll attach a screen dump for you guys to check..

Thanx for helping..

Zeilon

[agawarikar]

I was able to successfully mount an NFS with the following command:

./mount-nfs-store.pl --nfs 10.112.16.222:/nfs2

(where --nfs will take the hostname:/mount_point)

The command has to be run as root, and it should also chown the new folder with the user zimbra:zimbra

===

agawarikar-vm5:/opt/vmware-hdva-installer/bin # ./mount-nfs-store.pl --nfs 10.112.16.222:/nfs2

NFS: 10.112.16.222:/nfs2
HOST: 10.112.16.222
10.112.16.222 is alive.

....

...

Volume 4 is now the current primaryMessage volume.
Successfully setup nfs store at /opt/zimbra/store53.

agawarikar-vm5:/opt/vmware-hdva-installer/bin # ls -lat /opt/zimbra/store53
total 8
drwxr-xr-x  2 zimbra zimbra 4096 Mar 15 14:56 .

[Zeilon]

Hi

Could you please explain this

"and it should also chown the new folder with the user zimbra:zimbra"

How do i "chown" the folder?

Thanx for your input.

/Zeilon

[agawarikar]

The data processes runs as "zimbra" user. The script manages to ensure that the files are readable/writable by that user.

[sravuri · Accepted solution]

I think Ashish is asking you to run the following command, so the folder is owned by "zimbra" user.

chown -R zimbra:zimbra <your folder name for nfs>

[Zeilon]

Hi

Thanx everyone for helping out..

I managed to "chown" the folder to zimbra. Also i checked mount-nfs-store.pl and could see that it tries to do just that but fails for some reason.,

However.

The script did run as expected and it changed the "current" store to a new  one.

chown -R command worked and i can see that zimbra owns the store folder..

But i still cant upload any new documents with horizon data..

Is there a log somewhere to check so i can investigate why i cant upload files anymore?

Thanx

Joakim

[agawarikar]

The log file is /opt/zimbra/log/mailbox.log

[Zeilon]

Thanx

The log only told me that it could,nt create blob store at directory /opt/zimbra/store66/incoming

Can someone explain ho to properly set up the NFS share on the Windows server?

I suspect that it might has to do with security settings on the actual share rather then the zimbra "store"

Thanx

/Zeilon

[ekrejci]

in the different try I made to mount the NFS, I'm now with the zimbra account locked 😞

I tried to unlock it with :

passwd -u zimbra

but the system says:

Cannot unlock the password for `zimbra'!

any idea on how I could unlock the zimbra user?

thank you

Eric

[agawarikar]

The log only told me that it could,nt create blob store at directory /opt/zimbra/store66/incoming

You could do this following:

1. mkdir -p /opt/zimbra/store66/incoming

2. chown zimbra:zimbra /opt/zimbra/store66/incoming

And then issue "zmcontrol restart"

[agawarikar]

To unlock the zimbra user try this as root user:

pam_tally --reset --user zimbra

chage -m -1 -M -1 zimbra

[ekrejci]

Hi,

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:

zmvolume -l
   Volume id: 1
        name: message1
        type: primaryMessage
        path: /opt/zimbra/store
  compressed: false
     current: false

   Volume id: 2
        name: index1
        type: index
        path: /opt/zimbra/index
  compressed: false
     current: true

   Volume id: 3
        name: store78
        type: primaryMessage
        path: /opt/zimbra/store78
  compressed: false
     current: true

I provisioned a new user and his account was directly using the NFS storage:

ll -h /opt/zimbra/store78/
total 0
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

Sincerely

Eric

[aarron]

Hi

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

[agawarikar]

Hi,

That could be due to permissions on the NFS server. Ensure that while mounting the NFS server, you have given full permissions for everyone.

Check it out here:

Re: Manual or documentation

[aarron]

thanks for the reply.

There was no problems mounting the export, the data appliance has root and r/w access