Hello again Rich,
I guess you have already followed the newly made source installation instructions, but in case you haven't http://www.midgard-project.org/documentation/installation/source/ will be your friend.
rich wrote:
>>|
>>| I have installed midgard 1.6.1 on a RHEL3 box (apache info:
>>Apache/1.3.33 (Unix) Midgard/1.6.1/Repository/MultiLang
>>| mod_auth_passthrough/1.8 mod_log_bytes/1.2
>>mod_bwlimited/1.4 PHP/4.3.9
>>FrontPage/5.0.2.2635 mod_ssl/2.8.22 OpenSSL/0.9.7a).
>>|
>>| I compiled midgard from source and it seemed to compile and install
>>ok, but I am getting errors.
>>|
>>| When I add the midgard.so extension to the php.ini file and
>>then call
>>php from the command line I get the following error:
>>
>>AFAIR, Midgard cannot be used from the command line.
>
>
> That's ok but I would have thought I should still be able to use PHP from the command line for non-midgard stuff?
> The latest docs for the midgard-php install (http://www.midgard-project.org/documentation/installation/source/midgard-php.html) say
> that I should add the following line to php.ini:
AFAIR you don't actually have to have the extension call in the php.ini - this should be done by the midgard-root.php. This may have changed in 1.6.1 though...
> extension=midgard.so
>
> I also edited the extension_dir line in PHP.ini so that PHP would find the midgard.so module.
>
> extension_dir = "/usr/local/lib/php/extensions/no-debug-non-zts-20020429" ; directory in which the loadable extensions
> (modules) reside
>
> But this breaks PHP - it complains that in midgard.so ap_find_linked_module is an undefined symbol - which it is when I check with
> nm:
>
> [EMAIL PROTECTED] [~]# nm /usr/local/lib/php/extensions/no-debug-non-zts-20020429/midgard.so | grep -i ap_find_linked_module
> U ap_find_linked_module
>
> So I have removed the "extension=midgard.so" line, but will Midgard work without this?
I think so, yes.
> If it helps - PHP is version 4.3.9 compiled with support for the following:
>
> './configure' '--with-apxs=/usr/local/apache/bin/apxs' '--with-xml' '--enable-bcmath' '--enable-calendar' '--with-curl'
> '--enable-exif' '--enable-ftp' '--with-gd' '--with-jpeg-dir=/usr/local' '--with-png-dir=/usr' '--with-xpm-dir=/usr/X11R6'
> '--with-gettext' '--with-imap' '--with-imap-ssl' '--with-kerberos' '--enable-mbstring' '--enable-mbstr-enc-trans' '--enable-mbregex'
> '--with-mcrypt' '--with-mhash' '--with-mysql' '--with-openssl' '--enable-discard-path' '--with-pear' '--enable-sockets'
> '--enable-track-vars' '--with-ttf' '--with-freetype-dir=/usr' '--enable-gd-native-ttf' '--enable-versioning' '--enable-wddx'
> '--with-zip' '--with-zlib'
Hmmm... the installation requirements mention also iconv and dba. (Under "Required packages for running Midgard" --> Midgard-data.)
>>| When I visit the virtual server in web browser on port 8001 I get a
>>403 Forbidden error. The root of the midgard virtual server is
>>| empty.
>
>
> Should there be any files or symlinks inside the midgard root of the virtual server which I created with datagard?
No, Midgard stores absolutely everything to the MySQL db. See http://www.midgard-project.org/documentation/concepts/host_and_page/ for reference.
>>| As I said the install from source seemed to go ok and I executed
>>datagard and created a database and a virtual server with no
>>| trouble.
>>
>>Did you install any packages after db creation?
>
>
> No none at all. Should I install aegir and hope for the best?
>
>
>>Take a look at the hosts table in your db. You should have
>>matches in name (as in hostname) and port (as in server port).
>>I.e. if you have VirtualHost for localhost:80, you should
>>have the exact same match in the hosts table (with
>>name=localhost and port=80).
>
>
> Yes this all seems to match. I have a VirtualHost for www.midgard.[my domain] on port 8001.
>
> The host table also contains 7 other enties such as devel.aegir-cms.org. Not sure what the other fields (ie root, style and info
> fields etc.) represent.
This means that you have Aegir already installed. You can change the name field to match with your hostname. Don't worry about the style/page or such fields for now, what you need to match is the name, port and prefix.
For example, Aegir commonly resides in http://www.yourhost.com:8001/aegir/
Obviously, these three keys should always represent unique combination - there should never be two hosts with the same name, port and prefix.
>
>>You may also want to try and run midgard-pageresolve (use -h
>>for help). If you're able to connect to a Web page with
>>midgard-pageresolve, your Midgard installation is ok - the
>>problem is most likely in the Apache configuration.
>
>
> Didn't work:
>
> [EMAIL PROTECTED] [~]# midgard-pageresolve -h www.midgard.[my domain] -u /midgard/ -d dump.html -c ls -P telecaster
> Connecting to mysql://midgard:<hidden>@localhost/midgard
> Resolving host: http://www.midgard.[my domain]:80/midgard/
> RESULT: No host record match
>
OK, this looks actually pretty good - Midgard is able to connect to the db and Midgard libs can be found.
Now take a look at the "-u /midgard/" part again. Do you have a host record with a prefix "/midgard"? If not, that's the key... In case you do have such a host... we're in trouble.
> > I really appreciate your help with this. Have you any more ideas?
No problems, hope we get this solved.
> Cheers > > Rich >
Cheers!
//Henri
-- Henri Kaukola [EMAIL PROTECTED] Consultant Tel: +358-20-198 6037 Nemein Oy http://www.nemein.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
