Re: Upgrading from midcom-db to midcom-fs

Sonic <[email protected]> wrote:

> OK, I removed everything and installed again. midgard-config and the Array now 
> both point to /usr/local (I tried with --prefix=/usr, but the website still 
> would say /usr/local). 
> midcom-admin still is at 1.4.0, on the start page it says "This site is 
> running Midgard CMS (1.7.0) with MidCOM site template (2004.03.14).", so it 
> seems to utilize an old template, but I have no idea how to change that. The 
> phpMyAdmin segfault is still there, too:
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1079516064 (LWP 15152)]
> 0x4082e3fa in _zval_ptr_dtor () from /usr/lib/apache2/modules/libphp4.so
> (gdb) backtrace
> #0  0x4082e3fa in _zval_ptr_dtor () from /usr/lib/apache2/modules/libphp4.so
> #1  0x4083b628 in zend_hash_destroy () 
> from /usr/lib/apache2/modules/libphp4.so
> #2  0x40f8de47 in _unregister_midgard_php_class_members (key=0x8506760,
>     value=0x833b8e0, user_data=0x0)
>     at /root/Midgard_AllinOne-1.7rc1/midgard-php4-1.7rc1/midgard.c:1194
> #3  0x40c54ef6 in g_hash_table_foreach () from /usr/lib/libglib-2.0.so.0
> #4  0x40f8e270 in zm_deactivate_midgard (type=1, module_number=35)

How phpMyAdmin is configured?
I just installed it from debian packages and everything is working fine.

I wonder cause you have segfault from function which is called when midgard 
request is closed, so I hardly find any solution why Zend calls midgard request 
shutdown function for non midgard request.

Piotras