Zimbra

dsodermanns · #1 (**permalink**) 12-28-2011, 11:20 AM

Environment:
ZCS 7.1.3
SLES 11 SP1 x64, 2 GB ram, 50GB disk
(virtual machine on ESXi)

Problem:
During the installation the setup of the MySQL databases fails.
Error messages are logged in "/opt/zimbra/log/zmmyinit.log" and give an "errno: 13" on a file with the extension "frm" that should be created in "/opt/zimbra".

Cause:
The installation process of the MySQL databases tries to write to "/opt/zimbra" but is has no rights there (the directory is owned by root).

Workaround:
During install, after the installation of the RPMs (when the install script asks you if you want to change the domain) do the following:
- open a second console and login as root
- run "chown zimbra:zimbra"
- return to the first console and continue your installation

Additional info:
So far I did not find any reason to change the ownership of "/opt/zimbra" back to root

Caution:
In another thread here in the forum the was the info to run "chown -R zimbra:zimbra /opt/zimbra" I tried that one after the installation and it did not work for me.

Regards

Dieter

PS: will file a bug as soon as my bugzilla account is ready for use.

vavai · #2 (**permalink**) 12-28-2011, 03:40 PM

Quote:

Originally Posted by dsodermanns

Environment:
ZCS 7.1.3
SLES 11 SP1 x64, 2 GB ram, 50GB disk
(virtual machine on ESXi)

Problem:
During the installation the setup of the MySQL databases fails.
Error messages are logged in "/opt/zimbra/log/zmmyinit.log" and give an "errno: 13" on a file with the extension "frm" that should be created in "/opt/zimbra".

Cause:
The installation process of the MySQL databases tries to write to "/opt/zimbra" but is has no rights there (the directory is owned by root).

I have never found such problem while installing Zimbra on top of SLES 11 SP1, both on Virtualization (VMWare ESXi, Xen, KVM) and Physical installation.

Below are my folder permission at the running system :

Code:

# ls -l /opt/
drwxr-xr-x 51 root root     4096 2011-07-05 15:57 zimbra

As you see, my /opt/zimbra owned by root and it's not problem both for installation and on running system (Folder inside /opt/zimbra may have different permission & ownership).

Are you sure you've execute the command : ./install.sh with root permission and not only by using sudo ./install.sh?

AFAIK, Default sudo on SUSE has different authority than root permission. If I login as normal user, better using :

Code:

su -

then entering password and execute ./install.sh rather than

Code:

sudo ./install.sh

dsodermanns · #3 (**permalink**) 12-29-2011, 01:16 AM

Hi Masim,

I logged in as root (no sudo), I tried it from the server console and via ssh / putty.

The permissions on my system are the same as you listed them.

SLES11 SP1 was fully patched up to 26.12.2011.

By the way: I had the same issue when I used your Suse Studio image.

Maybe there is a bug in the installation routine for the MySQL databases. Why do they try to write to /opt/zimbra and not to a temp dir or the database directory?

Let's see what the developers they when I open the bug.

Regards from Germany

Dieter

phoenix · #4 (**permalink**) 12-29-2011, 02:47 AM

Quote:

Originally Posted by dsodermanns

Maybe there is a bug in the installation routine for the MySQL databases.

I doubt that very much (but it is always possible), I think if that were the case it would have cropped up before now. Do you, by any chance, have AppArmor enabled on this server? If you do, it needs to be disabled.

dsodermanns · #5 (**permalink**) 12-29-2011, 03:52 AM

Hi Bill,

you are right, AppAmor is running on my server.
After knowing it can cause trouble I searched the documentation and checked google.

If this causes so much trouble I think it might be a good idea to put a hint into the docs. I checked:
zcs-os-admin-guide-7.1.2.pdf and zcs-os-single-server-install-7.1.2.pdf

I am not sure how this is handled at zimbra, shall I write a bug against the documentation?

Let me know what you think.

Dieter

phoenix · #6 (**permalink**) 12-29-2011, 04:30 AM

Quote:

Originally Posted by dsodermanns

If this causes so much trouble I think it might be a good idea to put a hint into the docs.

It is mentioned in the documentation, sort of. I believe that it's only mentioned in the documentation that SElinux is disabled for RHEL builds and not AppArmor - so you could infer from that comment in the docs that AppArmor should also be disabled. I would agree that there should be a specific note about this in the documentation as there is for the RHEL installs and SElinux.

Quote:

Originally Posted by dsodermanns

I am not sure how this is handled at zimbra, shall I write a bug against the documentation?

This would normally be filed in bugzilla, you'll find a 'Tech Docs' entry in the component selection and that should be what this is filed under. If you do file the report, don't forget to vote on it and post the bug number here for others to vote if they want.