> --> ERROR #1
>   * Forcing reload of web server  (Apache2)...
> (98)Address already in use: make_sock: could not bind to address [::]:80
> no listening sockets available, shutting down
> Unable to open logs
>     ...fail!
>
> HOW TO FIX
>
> edit  /etc/midgard/apache/httpd.conf
>
> change the contents so that the Listen directive is commented out
>
> LoadModule midgard_module /usr/lib/apache2/modules/midgard-apache2.so
> #Listen 80
> NameVirtualHost *:80
> Include /etc/midgard/apache/vhosts/*

Automagic configuration is difficult. Sometimes very difficult.
1.6.3 midgard-data shouldn't allow to add Listen directive when port is already
defined. This is a bug. Absolutely.

> --> ERROR #2
>
> visit - http://admin.greatvideo.com/
>
> Warning: dl(): Unable to load dynamic library
> '/usr/lib/php4/20020429/midgard.so' -
> /usr/lib/php4/20020429/midgard.so: cannot open shared object file: No
> such file or directory in /var/cache/midgard/4-49-8-0.php on line 7
>
> Fatal error: Call to undefined function: mgd_get_midgard() in
> /var/cache/midgard/4-49-8-0.php on line 9
>
> HOW TO FIX
>
> cp /usr/lib/php4/20020429-zts/midgard.so /usr/lib/php4/20020429/.
>
> i'm not sure this is the - proper fix - but, it does allow the site to load.

Debian sarge and sid had different extension defined cause of zts enabled in
PHP. Last week this feature was disabled, but I had not time to rebuild 
packages.
Your fix is absolutely correct , however midgard extension may not work as it 
should.

>
> download the latest version of MidCom 2.x at the following location..
> http://www.midgard-project.org/projects/midcom/download/
>
> bunzip2 MidCOM-2.2.1.tar.bz2
> tar xvf MidCOM-2.2.1.tar
>
> mkdir /usr/share/pear/midcom
>
> cp -R MidCOM-2.2.1/* /usr/share/pear/midcom/
>
> - make symbolic links for the midcom-static pages
>
> ln -s /usr/share/pear/midcom/static/ /var/www/midcom-static
>
> - make another link for the domain just created
>
> ln -s /usr/share/pear/midcom/static
> /var/lib/midgard/vhosts/admin.greatvideo.com/80/midcom-static

I must say it is stable feature of 1.7 midgard-data.

>
> - next you need to install the midcom-template.xml package using datagard
>
> - copy the .xml file to datagard
>
> cp MidCOM-2.2.1/midcom-template/midcom-template.xml /usr/share/midgard/data

> * Get updated midgard-welcome
>
> curl -O
> http://www.midgard-project.org/midcom-serveattachmentguid-ddc9bb88bc88ec3a7cd493c1b0cd85be/midgard-welcome-2005.03.28.tar.bz2
>
> bunzip midgard-welcome-2005.03.28.tar.bz2
> tar xvf midgard-welcome-2005.03.28.tar.bz2
>
> cp midgard-welcome-2005.03.28/midgard-welcome.xml /usr/share/midgard/data
>
>
> Now import the template using datagard

These should be too. New midgard-data has "update" defined as
"update from previous installation" which means:

- check database
- import all required packages
- set midcom
- make symlinks

> --> ERROR
>
> upon accessing the site -  http://admin.greatvideo.com/

> Warning: main(/usr/share/midgard/midcom/lib//midcom.php): failed to
> open stream: No such file or directory in
> /var/cache/midgard/4-49-8-0.php on line 326
>
> Fatal error: main(): Failed opening required
> '/usr/share/midgard/midcom/lib//midcom.php'
> (include_path='.:/usr/share/php:/usr/share/pear') in
> /var/cache/midgard/4-49-8-0.php on line 326

Forget about pear directory. It is *impossible* to check what pear directory is.
We do copy midcom to  /usr/share/midgard/ dir.
However midcom-template tries to init midcom from hardcoded /usr/share/pear 
directory
and if it is not found , tries to init midcom from midgard "share" path.
This looks like a bug ( remember , alpha is not released yet ), one slash is
needless and breaks things.

Piotras






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to