Apache 1.3.27 Problems on Solaris 8

This is a discussion on Apache 1.3.27 Problems on Solaris 8 within the Linux Web Servers forums, part of the Web Server and Related Forums category; Attempting to start apache via /usr/local/apache/bin/apachectl start. Receive error message as follows: ld.so.1: /usr/...


Go Back   Usenet Forums > Web Server and Related Forums > Linux Web Servers

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 01-05-2004
Fernando
 
Posts: n/a
Default Apache 1.3.27 Problems on Solaris 8

Attempting to start apache via /usr/local/apache/bin/apachectl start.
Receive error message as follows:

ld.so.1: /usr/local/apache/bin/httpd: fatal: libexpat.so.0: open
failed: No such file or directory
Killed
/usr/local/apache/bin/apachectl start: http could not be started

In addition, I have verified that the error log via the httpd.conf
file should be written to the default location,
/usr/local/apache/logs/ but there is no error_log.

Any help would be greatly appreciated. Thanks in advance!
  #2 (permalink)  
Old 01-06-2004
 
Posts: n/a
Default Re: Apache 1.3.27 Problems on Solaris 8

In article <bd99e632.0401051536.24fa2e00@posting.google.com >,
forjuela@netscape.net (Fernando) writes:
> Attempting to start apache via /usr/local/apache/bin/apachectl start.
> Receive error message as follows:
>
> ld.so.1: /usr/local/apache/bin/httpd: fatal: libexpat.so.0: open
> failed: No such file or directory


See what:
ldd /usr/local/apache/bin/httpd
reveals. My setup is somewhat different but you should see something like:
libaprutil-0.so.0 => /opt/apache2/lib/libaprutil-0.so.0
libexpat.so.0 => /opt/apache2/lib/libexpat.so.0
libapr-0.so.0 => /opt/apache2/lib/libapr-0.so.0
etc.
You'll probably see "file not found" messages. That means the app
wasnt compiled correctly but you can employ workarounds found in
"man ld.so.1" or "man crle"
It better to set LD_RUN_PATH before you compile the source or
add appropriate -L -R flags at your ./configure run

pre packaged apache 1.3.28 is available from www.blastwave.org

> In addition, I have verified that the error log via the httpd.conf
> file should be written to the default location,
> /usr/local/apache/logs/ but there is no error_log.


Fix the loading problem first..
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 07:47 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0