Re: Upgrading from midcom-db to midcom-fs

Sonic <[email protected]> wrote:

> Am Donnerstag, 30. Juni 2005 00:13 schrieb Piotras:
> > > Ok, I updated to 1.7rc1 and Midgard works just fine, but midcom-admin
> > > still shows the version number 1.4.0.
> >
> > Anything in php log?
> > Looks like you do not use midcom-template as root page.
> >
> 
> phperr.log showed up nothing. How can I tell if I use midcom-template as my 
> root page? (I think I am, in Aegir I can see elements like edit-this-page or 
> midcom-settings)

Root page or main page should be set to "template_midcom".
 
> After restarting Apache, I could open phpMyAdmin again, so I disabled gdb 
> again. Of course, it segfaulted right after that (I had tried to rename 
> midcom snippetdir to midcom_old), so I restartetd gdb and performed the 
> operation again, this time it didn't crash right away, but when I renamed 
> midcom_old to midcom again, I got the following message:
> 
> ** (process:13883): DEBUG: Midgard: switching to midgardlive
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1079516064 (LWP 13883)]
> 0x4082e3fa in _zval_ptr_dtor () from /usr/lib/apache2/modules/libphp4.so

type backtrace if you can reproduce it again 

Piotras