In an attempt to get php and postgres working together I have attempted installing apache 1.3.35 and php 5.1.4 on my Slackware 10.2 linux server.
Neither build from source gave any errors but I cannot get httpd to start with apachectl start. The error I see in /var/log/apache/error_log is:-
*** glibc detected *** double free or corruption (!prev): 0x08170ce8 ***

and when browsing to the site the browser gets:-

Server Error
The following error occurred:

[code=CANT_CONNECT] Could not connect because of networking problems. Contact your system administrator.

Please tell me what I have done wrong.

Why not use the Slackware packages?

Anyway check your httpd.conf file for a conflicting LoadModule entry which PHP may have added.

I cannot see any conflicts and in fact would be quite happy to back off to the standard Slackware packages but do not know how.
Suggestions please on how to get back.

Now you're asking.

I'm not sure of the most efficient method for uninstalling Apache when it's been compiled. Some programs have an uninstall option or you can make with an uninstaller, this may be your best bet. If not someone else may be able to assist. This may also apply to PHP.

This is also why using Slackware packages is so convenient, you can uninstall the entire application with one command:

Once you have stopped httpd and managed to uninstall it you can set about installing the Slackware packages.

To install the apache and PHP packages, please visit Slackware.com on the "Get Slackware" link and find a nearby FTP mirror. I assume you are using stable rather than current.

You need to download the following packages which will be in Patches, as these are security updates since the release of 10.2.

apache-1.3.35-i486-2_slack10.2.tgz
php-4.4.2-i486-3.tgz
mod_ssl-2.8.26_1.3.35-i486-1_slack10.2.tgz

You'll note that this is PHP4 which may not be what you are after. Download to one folder and try this command:

Once they have been installed restart apache with either:

or

if you use mod_ssl:

Let us know how you get on.

Regards

dkpw

Thank you for your suggestions however no success as yet.
I have done all that you said, the only change being I am using current rather than stable.
The error I see in /var/log/apache/error_log is:-
*** glibc detected *** double free or corruption (!prev): 0x08170cc8 ***
almost the same as I had before.
I have also done a reinstall of glibc all without avail.
apachectl configtest tells me
Syntax OK
so I do not suspect the httpd.conf.

Hi Stockton,

Sorry to hear that you are still experiencing problems. I must confess that I am at the end of my suggestions and so hopefully someone else on the forum may be able to assist.

My only remaining comment would be to suggest a reinstall of Slackware, which depending on the amount of other configuration you have performed, may be the quickest route to a working system.

Good luck

dkpw

I am going to avoid a reinstall as long as possible but thank you for your help and suggestions.

One problem you'll be facing is that the PHP that Pat delivers
knows nothing about postgres.

I'd suggest to do a standard install of slack (minus PHP) and
grab the source-package and install-script for PHP of Pat,
edit the build-script to accommodate postgres and all should
be well with the world.

As far as your own builds go: in which directories did you
install the stuff, did you remove the originals?


Cheers,
Tink

Reinstalling from scratch sounded too much like a Windows solution to me so being somewhat hard headed I did not do that.
My solution so far, with some guidance from Patrick J. Volkerding, is as follows:-
I altered my swaret.conf settings to 10.2, and "upgraded" Apache and glibc and removed all references to php from httpd.conf and restarted Apache and as I can now browse to the site(www.stockton.co.za) I am happy that the Apache part of the problem is resolved.
Next trick is to get php to work again and here I am going to try your suggestion.

Good luck, and I don't use swaret or tools the like for reasons
just like that - if anyone is to break my system it's me ;}

The php-approach should work - no troubles. I've done that before
in exactly that way (well, I also removed the references to MySQL
since I have no desire to use that heap of bovine excrement).


Cheers,
Tink

In an email I received from Patrick Volkerding, he said and I quote
I'm on record as being no huge fan of Swaret though... it's messed up more machines than I can count.
end quote
So yes I will go along with your suggestion and not allow someone else to break my system. I will do it myself.......:-)
BTW Your comment re MySQL interests me. Why would you postgresSQL rather than MySQL?

Excellent choice ;}

Let's just say the licensing aspect and standard compliance.
MySQL has done a dis-service to StandardSQL like MS has to
HTML to begin with ...

And many other things :}
Read here:
http://groups.google.com/group/pgsql...0b2027f04dff0e
and
http://groups.google.com/group/pgsql...11b0e5b8791a65

And of course:
http://sql-info.de/mysql/gotchas.html

I'm not saying that PostgreSQL is flawless, it had (and
has) a few issues; but over all it's way more mature
that MySQL is;
http://sql-info.de/postgresql/postgres-gotchas.html




Cheers,
Tink

Hi people

I have Apache 2.2.2 and PHP 5.1.4 built from source and running. No problems so far. I just made the packages using the great SlackBuilds (just as Pat does). (modifying them to suit my needs of course). I think the better way to use the Source is to use it the same way the Master does

May the Source be with you!

What an excellent suggestion, this must be why I made it
three days ago ;}


Cheers,
Tink

Can you give me a bit more info please.
I have the Slackware 10.2 CDs here in South Africa and my server is in Texas USofA.
On the Extra CD from the Slackware 10.2 in the n directory I find a php directory containing:-
-rw-r--r-- 1 root root 152 2002-03-03 08:06 doinst.sh.gz
-rw-r--r-- 1 root root 343 2003-11-13 23:43 mod_php.conf.example
drwxr-xr-x 2 root root 2048 2005-08-30 19:11 pear
-rw-r--r-- 1 root root 4086074 2005-07-11 12:07 php-4.4.0.tar.bz2
-rw-r--r-- 1 root root 619 2003-11-16 23:26 php.ini.diff.gz
-rwxr-xr-x 1 root root 4717 2005-09-05 04:53 php.SlackBuild
-rw-r--r-- 1 root root 834 2003-11-16 23:27 slack-desc


My first thought is to pack the whole lot into a bz2 and copy it to my server, which is fine and easy, but now what.
Do I need to unpack the php-4.4.0.tar.bz2 into a suitable directory, make the alterations I need, ie add --with-pgsql=/usr/local/pgsql/ (this is where postgresSQL has been installed to) to the php.SlackBuild and run the php.SlackBuild in the same directory where I unpacked the php-4.4.0.tar.bz2 file?