Re: Midcom-2.2 to 2.4 upgrade

Thanks Torben. I'm guessing this is becoming a FAQ now. My problem was 
that midcom-template was not updating correctly. I also noticed that 
autoconf.php is not packaged with Midcom-2.4.x. I pulled it from CVS 
and created /etc/midgard/midcom.conf.

I ran into another issue though: After successfully upgrading to Midcom 
2.4 (tried 2.4.0 and 2.4.1) apache locks up midcom-enabled hosts: cpu 
utilization runs to 100%. The only messages I get when the php hits 
memory_limit(128M) or max_execution_time(10m).

This happens at random and once it begins I have to stop apache, remove 
all cache files and start it again. I enabled midcom debugging and this 
is what I see:

Jun 28 15:07:35 [debug] midcom_helper__basicnav::_is_object_visible: The 
object ae1203dad4d2cab289db6062ee3970eb (node) is hidden by a viewer 
group setting.
Jun 28 15:07:35 [info] _basicnav::constructor: The current node is 
hidden behind a undecendable one.
Jun 28 15:07:35 [debug] _basicnav::constructor: Activating last good 
node (-1) as current node
Jun 28 15:07:35 [error] _basicnav::_loadNode: Node -1 is not in the 
MidCOM content tree 8. Aborting
Jun 28 15:07:35 [debug] midcom_application::_process: _process finished 
sucessfully
Jun 28 15:07:35 [info] midcom_application::codeinit: code-init finished
Jun 28 15:07:35 [error] _basicnav::_loadNode: Node -1 is not in the 
MidCOM content tree 8. Aborting
Jun 28 15:07:35 [error] _basicnav::_loadNode: Node -1 is not in the 
MidCOM content tree 8. Aborting
Jun 28 15:07:35 [error] _basicnav::_loadNode: Node -1 is not in the 
MidCOM content tree 8. Aborting
Jun 28 15:07:35 [debug] midcom_services_cache::initialize: We got this 
Node Path:
Variable Type: array
Array
(
)
Jun 28 15:07:35 [error] _basicnav::_loadNode: Node -1 is not in the 
MidCOM content tree 8. Aborting
Jun 28 15:07:35 [error] _basicnav::get_node_uplink: Parameter passed is 
no integer: []
Jun 28 15:07:35 [error] _basicnav::get_node: Parameter passed is no 
integer: []
Jun 28 15:07:35 [error] _basicnav::get_node_uplink: Parameter passed is 
no integer: []
Jun 28 15:07:35 [error] _basicnav::get_node: Parameter passed is no 
integer: []

with the last two lines repeating ad nauseum. Any ideas what could be 
wrong? I've gone back to midcom-2.2.2 for now.


Again, thanks a lot for all your help.


Nico

On Monday 27 June 2005 02:26 am, Torben Nehmer wrote:

> > 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-9c2915217bcb879068fe
>cf41e5b58e43 [2]:
> http://www.nathan-syntronics.de/midcom-permalink-42b74a40f635c7cb1123
>5feea0f21051 [3]:
> http://www.nathan-syntronics.de/midcom-permalink-99ad0ca71f7619c714c6
>8e973910ba6e [4]:
> http://www.nathan-syntronics.de/midcom-permalink-68666d1ae755a05479a5
>0b83ae89aef4 [5]:
> http://bergie.iki.fi/midcom-permalink-656cda78fb6086ecad96e6d2f86bcb4
>9 [6]:
> http://www.nathan-syntronics.de/midcom-permalink-31bcbf5547213478d17c
>0b1c28e5aa6f
>
>
> Live long and Prosper!
> Torben Nehmer

-- 
Marcelo N. Halpern,  your favorite daemon.
UNIX Systems Administrator - Ramapo College
TEL: +1.201.684.6821  FAX: +1.201.684.7961