Upgrade 8.6 to 8.7 back_mdb.la file not found [SOLVED]

[L. Mark Stone]

A fix for this is mentioned here: viewtopic.php?t=60288
But when I stop the broken setup it leads me to my first problem to the missing back_mdb.la which is located in

/opt/zimbra/common/libexec/openldap/back_mdb.la

OK, let's try some housecleaning...

Please shut down Zimbra and run as root zmfixperms --verbose --extended

then start up 8.6.0 again, confirm you have installed Patch7, then try the upgrade again.

Mark

[353gregor]

EDIT: zmfixperms didn't helped

After digging into the ldap config did now the following to fix ldap:

. mkdir /opt/zimbra/openldap/sbin
. cd /opt/zimbra/openldap/sbin
. ln -s /opt/zimbra/common/libexec/openldap

[L. Mark Stone]

EDIT: zmfixperms didn't helped

After digging into the ldap config did now the following to fix ldap:

. mkdir /opt/zimbra/openldap/sbin
. cd /opt/zimbra/openldap/sbin
. ln -s /opt/zimbra/common/libexec/openldap

Glad you got it sorted, but... the symlink targets which file?

Thanks,
Mark

[353gregor]

Yes but the Upgrade still did not work. Now it stucks in "Starting mysql..." and the mysql_error.log reports "161026 02:03:29 mysqld_safe A mysqld process already exists"
The solution from the post did not solve my problem: viewtopic.php?t=60288



EDIT: The symlinks targets to /opt/zimbra/common/libexec/openldap

[L. Mark Stone]

Yes but the Upgrade still did not work. Now it stucks in "Starting mysql..." and the mysql_error.log reports "161026 02:03:29 mysqld_safe A mysqld process already exists"
The solution from the post did not solve my problem: viewtopic.php?t=60288



EDIT: The symlinks targets to /opt/zimbra/common/libexec/openldap

OK re the symlink; I had to reread the man page to understand how ln -s works when you only give it one argument (out of habit I always give source and target arguments).

So the good news is you are making progress, but you have a ways to go.

That MySQL error is clear, so what I would do is shut down zimbra before running the upgrade installer, and after you shut down Zimbra, run as root "ps -ax | grep zimbra" to make sure no zimbra processes are still running. Use "kill <process id#>" -- except for MySQL. If for some reason MySQL is still running under the zimbra user after you've done "zmcontrol stop", then I would become the zimbra user and issue "mysql.server stop".

Basically, you want to try running the upgrade installer with no Zimbra processes running; the installer will start whatever process it needs to. But, you want to make sure MySQL was shut down cleanly.

You may also want to look for any stale pid files, just in case... As root, "cd /opt/zimbra; find -name *.pid" will give you a list. Regrettably, Zimbra scatters pid files all over the place:

Code: Select all

root@zmail:/opt/zimbra# find -name *.pid
./log/amavisd.pid
./log/zmmailboxd_java.pid
./log/zmrrdfetch-server.pid
./log/swatch.pid
./log/freshclam.pid
./log/convertd.pid
./log/nginx.pid
./log/httpd.pid
./log/opendkim.pid
./log/amavis-mc.pid
./log/zmmailboxd_manager.pid
./log/zmconfigd.pid
./log/logswatch.pid
./log/memcached.pid
./log/clamd.pid
./zmstat/pid/zmstat-cpu.pid
./zmstat/pid/zmstat-allprocs.pid
./zmstat/pid/zmstat-fd.pid
./zmstat/pid/zmstat-nginx.pid
./zmstat/pid/zmstat-mysql.pid
./zmstat/pid/zmstat-df.pid
./zmstat/pid/zmstat-ldap.pid
./zmstat/pid/zmstat-proc.pid
./zmstat/pid/zmstat-convertd.pid
./zmstat/pid/zmstat-mtaqueue.pid
./zmstat/pid/zmstat-vm.pid
./zmstat/pid/zmstat-fd-real.pid
./zmstat/pid/zmstat-io-x.pid
./zmstat/pid/zmstat-io.pid
./db/mysql.pid
./data/ldap/state/run/slapd.pid
./data/postfix/spool/pid/master.pid
./data/sasl2/state/saslauthd.pid
root@zmail:/opt/zimbra# 

Hope that helps,
Mark

[353gregor]

Hi,

I finally solved the problem after hours of try and error, read throug the config and read through the output of "lsof". After started my first post here I tried it for about two full weekends.

These are my steps to upgrade from 8.6 to 8.7 under centos 6 x86_64:

Code: Select all

# change the hostname to the same as the public certificate, not documented here
sudo -u zimbra /opt/zimbra/bin/zmcontrol start
# activate the proxy otherwise the zimbra installer wont start
sudo -u zimbra /opt/zimbra/bin/zmprov ms `/opt/zimbra/bin/zmhostname` zimbraReverseProxyMailEnabled TRUE zimbraReverseProxyHttpEnabled TRUE
sudo -u zimbra /opt/zimbra/bin/zmcontrol stop
/opt/zimbra/libexec/zmfixperms --verbose --extended
visudo add
	#includedir /etc/sudoers.d
sudo -u zimbra /opt/zimbra/bin/mysql.server stop
ps aux | grep -i zimbra
# kill all zimbra processes
find /opt/zimbra -iname "*.pid"
# delete all pid files
sudo -u zimbra ln -s /opt/zimbra/data/tmp/mysql/mysql.sock /opt/zimbra/db/mysql.sock # needed to recognize that the database is up, this line took the most of the time to figure out the main problem
sudo -u zimbra /opt/zimbra/bin/ldap start # otherwise the zimbra installer wont start
./install.sh 
# ignore conflict
sudo -u zimbra ln -s /opt/zimbra/data/tmp/mysql/mysql.sock /opt/zimbra/db/mysql.sock # needed to recognize that the database is up
sudo -u zimbra /opt/zimbra/bin/zmcontrol stop
/opt/zimbra/libexec/zmfixperms --verbose --extended
./install.sh 
sudo -u zimbra /opt/zimbra/bin/zmcontrol status
# Now the server is up

Later I saw permission problems from the postfix process, here is the solution documented: viewtopic.php?t=6737

And thats how I solve it:

Code: Select all

sudo -u zimbra /opt/zimbra/bin/zmcontrol stop
ps aux | grep -i zimbra
# kill all zimbra processes
usermod -a -G postdrop zimbra
/opt/zimbra/libexec/zmfixperms --verbose --extended
sudo -u zimbra /opt/zimbra/bin/zmcontrol start

And here we have the next problem for example the files for postfix are ignored by zmfixperms. Truly since then I can't trust this tool. Maybe it fix the permission for some files but not all under the zimbra installation folder which is in my case useless or like posted below it also set the wrong permissions.

...
/postfix-script: warning: not owned by root: /opt/zimbra/common/libexec/./openldap/valsort-2.4.so.2.10.7
/postfix-script: warning: not owned by root: /opt/zimbra/common/libexec/./openldap/translucent.so
/postfix-script: warning: not owned by root: /opt/zimbra/common/libexec/./openldap/memberof-2.4.so.2.10.7
/postfix-script: warning: not owned by root: /opt/zimbra/common/libexec/./openldap/dds.so
/postfix-script: warning: not owned by root: /opt/zimbra/common/libexec/./openldap/ppolicy.la
/postfix-script: warning: not owned by root: /opt/zimbra/common/libexec/./openldap/constraint.so
/postfix-script: warning: not owned by root: /opt/zimbra/common/libexec/./openldap/syncprov.so
/postfix-script: warning: not owned by root: /opt/zimbra/common/libexec/./openldap/seqmod.so
...

Code: Select all

chown -R root /opt/zimbra/common/libexec
chgrp postdrop /opt/zimbra/common/sbin/postqueue
chgrp postdrop /opt/zimbra/common/sbin/postdrop
chmod g+s /opt/zimbra/common/sbin/postqueue
chmod g+s /opt/zimbra/common/sbin/postdrop

When "zmfixperms --extended" is triggered all the permissions for /opt/zimbra/common/libexec are broken again !!!

I know this reads a little bit confusing but this is how I have to fix all the zimbra problems. In fact to upgrade from 8.6 to 8.7 there have to be manually fixed a punch of problems.
Hopefully this will change anytime with zimbra. I have to play this game since release 5 and it doesn't get better since then On the other hand I love the zimbra server compared to all other products I have found.

The next stunt will be to move from CentOS 6 to 7

[phoenix]

I have to play this game since release 5 and it doesn't get better since then

Did you file any bug reports for this supposed problems? I've upgraded ZCS since the first public release without any such problems, I'd go so far as to suggest there's something wrong with your server as this type of repeated upgrade problem isn't normal.

[L. Mark Stone]

Glad you got it working!

FWIW, 8.7.1 was just released: https://www.zimbra.com/downloads/zimbra ... en-source/

All the best,
Mark