Re: Midcom-2.2 to 2.4 upgrade

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

- --Marcelo N. Halpern wrote on 2005-06-27 01:45:
> I recently tried to upgrade my midcom v2.2.0 site to v2.4.0. I figured I'd be 
> smart and replace the midcom directories under /usr/share/php/PEAR and see 
> what would happen. When I pointed my web browser to the site, I was greeted 
> with this message:
> 
> "Tried to load the topic for NAP cache backend creation, which failed: Object 
> does not exist"
> 
> I know there have been some major updates to the Midcom codebase and I 
> *mostly* expected the site not to come up. I tried updating the db part of 
> the Midcom template via repligard but it didn't seem to do the trick: the 
> template was still the same when I logged into Aegir and looked around.
> 
> What am I doing wrong, and how should I upgrade my site to midcom-2.4?

In general it should be enough to upgrade the midcom-template. This is required
as the configuration system in MidCOM 2.4 has change drastically. See [1], [2]
and [3] for a few more details.

For more debugging, go to the midcom-template intro page
(www.yourhost.com/midcom-admin), log in and look for the site template version.
It is a date and should be something in April 2005 (I think it is 2005.04.15, I
can't tell for sure).

I also suggest that you run the autoconf and configtest scripts supplied with
MidCOM after upgrading the template, as outlined in [1]. That page does also
tell you how to place systemwide MidCOM config options into
/etc/midgard/midcom.conf, which is strongly recommended for path settings and
the like. Note: If you use autoconf.php under Debian, remember, that Debian has
different PHP config files for CLI and Apachpe-PHP, which can lead to an
incorrect detection of the set memory limit (see [1] how to circumvent this).

Some hints:

The MidCOM cache directory, defaulting to /tmp/ and settable through the
'cache_base_directory' configuration option, has to be writeable by the Apache
user including the permission to create subdirectories. I recommend to set it to
/var/cache/midgard/midcom for better structurization. The default is only there
as an last-ditch fallback, as the tmp dir should always be writable by Apache.

If you want to use the new MidCOM indexer, see [4] and [5]. Beware that some
links in [5] are outdated. Note: The Indexer now assumes the lucene.jar file in
/usr/share/java/lucene.jar, as this is the place where most rpms/debs install it to.

If you have been using metadata like approval or scheduling, see also [6]
besides [3].

[1]:
http://www.nathan-syntronics.de/midcom-permalink-9c2915217bcb879068fecf41e5b58e43
[2]:
http://www.nathan-syntronics.de/midcom-permalink-42b74a40f635c7cb11235feea0f21051
[3]:
http://www.nathan-syntronics.de/midcom-permalink-99ad0ca71f7619c714c68e973910ba6e
[4]:
http://www.nathan-syntronics.de/midcom-permalink-68666d1ae755a05479a50b83ae89aef4
[5]: http://bergie.iki.fi/midcom-permalink-656cda78fb6086ecad96e6d2f86bcb49
[6]:
http://www.nathan-syntronics.de/midcom-permalink-31bcbf5547213478d17c0b1c28e5aa6f


Live long and Prosper!
Torben Nehmer

- --
Torben Nehmer, Guenzburg, Bavaria, Germany
http://www.nathan-syntronics.de, mailto:[email protected]
PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCv5wWJPh4Kn6d5FYRAitbAKCB+41PNRyGTcKlqHCj2tbYuniJEQCfe0pf
UQrofxsHREsWgARJvX+XuCc=
=Ud6q
-----END PGP SIGNATURE-----