I was performing an upgrade and all seemed to go well until I saw this:
Code:
Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...Restoring backup schedule...done
chown: cannot access `/opt/zimbra/conf/smtpd.key': No such file or directory
chown: cannot access `/opt/zimbra/conf/smtpd.crt': No such file or directory
Can't load '/opt/zimbra/zimbramon/lib/i386-linux-thread-multi/auto/DBI/DBI.so' for module DBI: /lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by /opt/zimbra/zimbramon/lib/i386-linux-thread-multi/auto/DBI/DBI.so) at /usr/lib/perl5/5.8.5/i386-linux-thread-multi/DynaLoader.pm line 230, line 228.
at /opt/zimbra/zimbramon/lib/i386-linux-thread-multi/DBI.pm line 266
BEGIN failed--compilation aborted at /opt/zimbra/zimbramon/lib/i386-linux-thread-multi/DBI.pm line 266, line 228.
Compilation failed in require at /opt/zimbra/libexec/scripts/Migrate.pm line 18, line 228.
BEGIN failed--compilation aborted at /opt/zimbra/libexec/scripts/Migrate.pm line 18, line 228.
Compilation failed in require at /opt/zimbra/libexec/zmupgrade.pm line 21, line 228.
BEGIN failed--compilation aborted at /opt/zimbra/libexec/zmupgrade.pm line 21, line 228.
Compilation failed in require at /opt/zimbra/libexec/zmsetup.pl line 59, line 228.
BEGIN failed--compilation aborted at /opt/zimbra/libexec/zmsetup.pl line 59, line 228.
It looks like there is a new DBI.so being installed that expects glibc 2.4. Am I right on this? Is there another work around? I would have to do a major upgrade to get glibc 2.4 ( I don't feel lik egoing through the pain of installing it in addition to what is there ... that always turns into a nightmare) Could I get a DBI.so linked against glibc 2.3?
I forgot to add that we are using the NETWORK edition. If I need to put this in through support please let me know.
Thanks