[skalie]

I was trying to configure the Apache webserver to enable .htaccess.

That was to change the "AllowOverride" from "None" to "All" using the sudo pico method in the terminal.

It didn't work so I turned off the webserver at the sharing tab from the system preferences. Turning it back on again and I get "Webserver starting up........" , but it doesn't.

Anyone have any idea what I have managed to mess up here?

[Simon Mundy]

Originally posted by skalie:
I was trying to configure the Apache webserver to enable .htaccess.

That was to change the "AllowOverride" from "None" to "All" using the sudo pico method in the terminal.

It didn't work so I turned off the webserver at the sharing tab from the system preferences. Turning it back on again and I get "Webserver starting up........" , but it doesn't.

Anyone have any idea what I have managed to mess up here?

Probably something a bit nasty in the httpd.conf file. Go to the terminal and type 'sudo apachectl configtest'. It will explain what's wrong (although you may have to do a bit of leg work to pin down the EXACT cause).

Keep testing with the 'apachectl configtest' until it reports everything as OK, then do a 'sudo apachectl graceful' to get things started again.

The system control panel is a bit useless with the 'start' web serving - if there's a problem, it doesn't tell you and it just appears to hang.

Cheers

[skalie]

Thanks for the post Simon, unfortunately apachectl configtest yields....

dyld: /usr/sbin/httpd can't open library: /usr/lib/libiodbc.2.1.6.dylib (No such file or directory, errno = 2)

....I've been all over the web looking for a solution for this one, I have come to the conclusion that it has to do with adjustments I performed after setting the server up the first time.

Everything was still working after I adjusted the httpd config file, this time, the problems arose after I turned the webserver off.

So maybe the option is to start from scratch again, delete Apache completely and re-install?

[Simon Mundy]

Originally posted by skalie:
Thanks for the post Simon, unfortunately apachectl configtest yields....



....I've been all over the web looking for a solution for this one, I have come to the conclusion that it has to do with adjustments I performed after setting the server up the first time.

Everything was still working after I adjusted the httpd config file, this time, the problems arose after I turned the webserver off.

So maybe the option is to start from scratch again, delete Apache completely and re-install?

Heh, yeah it is an option but always the worst one!

I've just checked my own /usr/lib/ directory and I've got that installed (10.2.3 with 'factory' installed Apache), so somehow the contents of your library have been hosed...

Could you do a post of the contents of your /usr/lib/ directory just to double-check?

[skalie]

bundle1.o libc.dylib libobjc.dylib
crt1.o libcom_err.dylib libpcap.A.dylib
dyld libcrypto.0.9.dylib libpcap.dylib
dylib1.o libcrypto.dylib libpthread.dylib
gcrt1.o libcurses.dylib libssl.0.9.dylib
java libdes524.dylib libssl.dylib
libDHCPServer.A.dylib libgssapi_krb5.dylib libtcl.dylib
libDHCPServer.dylib libinfo.dylib libtcl8.3.dylib
libIOKit.A.dylib libk5crypto.dylib libz.1.1.3.dylib
libIOKit.dylib libkrb4.dylib libz.1.dylib
libSystem.B.dylib libkrb5.dylib libz.dylib
libSystem.dylib libkvm.dylib php
libalias.A.dylib libm.dylib
libalias.dylib libobjc.A.dylib

The "libiodbc.2.1.6.dylib" file is indeed not present . Googling that file name draws a blank, well it does show up in someone's who's running Mandrakes list of file names for /usr/lib.

It may or may not be pertinent to mention that I am running Mac OSX 10.1.

I have this unesay feeling that I will have had to learn Unix by the time I get this one sorted.

[skalie]

Found some documentation (finally) at Apple.....

http://discussions.info.apple.com/We...14@.3bbd1f5d/6

...seems that it has something to do with OS X 10.1 after all, not having the file.

My version....Server version: Apache/1.3.20 (Darwin)

None of the solutions have worked so far, and it's quite possible that I've foobarred a combination of configuration problems by now.

I did download a more recent version of Apache at some stage for better session management, maybe that has thickened the plot.

If only I hadn't turned off the webserver.

So how does one completely remove Apache then?

***Edit*** ......taken that question to the OS X forum....

http://forums.macnn.com/showthread.p...hreadid=138346