Startup Script

This is a multi-part message in MIME format.

------=_NextPart_000_0003_01C27F8D.12B9ADB0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

Greetings everyone,

I realize this situation has come up before, but none of the suggestions
I have seen have worked for me.

I have created an Apache 1.3.26 / mod_ssl 2.8.10 server. No problems
creating it, and no problems starting from the command line. I am
however, unable to start automatically at boot using a script in the
rc3.d directory. When I try to start it automatically using:

#!/bin/sh
#
# Start SSL-Aware Apache http daemon
#
echo "Start SSL-Aware Apache httpd"
/opt/apache/bin/apachectl startssl


I get the following error:

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

Once the system is booted up the LD_LIBRARY_PATH is
"/lib:/usr/lib:/usr/local/lib:/usr/openwin/lib", and I can run
"/opt/apache/bin/apachectl startssl" just fine. For automation reasons,
I need to boot at startup. Any suggestions?

Regards,

Lawrence

------=_NextPart_000_0003_01C27F8D.12B9ADB0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable



charset=3Dus-ascii">

Re: Startup Script

At 08:52 PM 10/29/02 -0700, Lawrence Cole wrote:
>
>ld.so.1: /opt/apache/bin/httpd: fatal: libexpat.so.0: open failed: No such
>file or directory
>Killed
>/opt/apache/bin/apachectl startssl: httpd could not be started
>Once the system is booted up the LD_LIBRARY_PATH is
>"/lib:/usr/lib:/usr/local/lib:/usr/openwin/lib", and I can run
>"/opt/apache/bin/apachectl startssl" just fine. For automation reasons, I
>need to boot at startup. Any suggestions?
>

When in the startup sequence are you starting Apache? It needs to be very
late in the process. The only thing I do AFTER starting apache in myh
startup scripts is run a process that assigns the ailias IP addresses to
the server.

Without knowing what OS you are using I can't make any suggestions on
exactly how to fix it, but I'm sure it is a matter of starting Apache late
in the process.

Rick


____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

RE: Startup Script

Quick fix is to put in the startup script:

LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib:/usr/openwin/li b

before it tries to start apache..

Better fix is to recompile apache with the additional compile-time
options: "-L/usr/openwin/lib -R/usr/openwin/lib" etc. (one pair for each
lib). This should build the paths to the libs into the binary and then
you don't need LD_LIBRARY_PATH at all.

-----Original Message-----
From: Lawrence Cole [mailto:lmcole@cisco.com]
Sent: Mittwoch, 30. Oktober 2002 04:52
To: modssl-users@modssl.org
Subject: Startup Script


Greetings everyone,

I realize this situation has come up before, but none of the suggestions
I have seen have worked for me.

I have created an Apache 1.3.26 / mod_ssl 2.8.10 server. No problems
creating it, and no problems starting from the command line. I am
however, unable to start automatically at boot using a script in the
rc3.d directory. When I try to start it automatically using:

#!/bin/sh
#
# Start SSL-Aware Apache http daemon
#
echo "Start SSL-Aware Apache httpd"
/opt/apache/bin/apachectl startssl


I get the following error:

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

Once the system is booted up the LD_LIBRARY_PATH is
"/lib:/usr/lib:/usr/local/lib:/usr/openwin/lib", and I can run
"/opt/apache/bin/apachectl startssl" just fine. For automation reasons,
I need to boot at startup. Any suggestions?

Regards,

Lawrence

This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please notify the sender urgently
and then immediately delete the message and any copies of it from your
system. Please also immediately destroy any hardcopies of the message.
You must not, directly or indirectly, use, disclose, distribute, print,
or copy any part of this message if you are not the intended recipient.
The sender's company reserves the right to monitor all e-mail
communications through their networks. Any views expressed in this
message are those of the individual sender, except where the message
states otherwise and the sender is authorised to state them to be the
views of the sender's company.
____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

RE: Startup Script

It's the last script to run in the directory. It's an S99 file. I'm
running Solaris 8 with the latest "patch cluster" from Sun.

-----Original Message-----
From: owner-modssl-users@modssl.org
[mailto:owner-modssl-users@modssl.org] On Behalf Of Rick Widmer
Sent: Tuesday, October 29, 2002 9:16 PM
To: modssl-users@modssl.org; modssl-users@modssl.org
Subject: Re: Startup Script


At 08:52 PM 10/29/02 -0700, Lawrence Cole wrote:
>
>ld.so.1: /opt/apache/bin/httpd: fatal: libexpat.so.0: open failed: No
>such
>file or directory
>Killed
>/opt/apache/bin/apachectl startssl: httpd could not be started
>Once the system is booted up the LD_LIBRARY_PATH is
>"/lib:/usr/lib:/usr/local/lib:/usr/openwin/lib", and I can run
>"/opt/apache/bin/apachectl startssl" just fine. For automation
reasons, I
>need to boot at startup. Any suggestions?
>

When in the startup sequence are you starting Apache? It needs to be
very
late in the process. The only thing I do AFTER starting apache in myh
startup scripts is run a process that assigns the ailias IP addresses to

the server.

Without knowing what OS you are using I can't make any suggestions on
exactly how to fix it, but I'm sure it is a matter of starting Apache
late
in the process.

Rick


____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

RE: Startup Script

Boyle,

Thank you for your suggestions.

Adding "LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib:/usr/openwin/l ib"
to the startup script does not help.

Sourcing root's .profile before running the "apachectl startssl" command
does not help. The LD_LIBRARY_PATH is set in the .profile.

So the last thing to try are the -R and -L compile-time option pairs for
each library. I have a rookie question to ask. Where do I use these?
I can't use them with the .configure or make commands. Do I need to
edit the Makefile? Can you give me an example?

Regards,

Lawrence


-----Original Message-----
From: owner-modssl-users@modssl.org
[mailto:owner-modssl-users@modssl.org] On Behalf Of Boyle Owen
Sent: Wednesday, October 30, 2002 2:21 AM
To: modssl-users@modssl.org
Subject: RE: Startup Script


Quick fix is to put in the startup script:

LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib:/usr/openwin/li b

before it tries to start apache..

Better fix is to recompile apache with the additional compile-time
options: "-L/usr/openwin/lib -R/usr/openwin/lib" etc. (one pair for each
lib). This should build the paths to the libs into the binary and then
you don't need LD_LIBRARY_PATH at all.

-----Original Message-----
From: Lawrence Cole [mailto:lmcole@cisco.com]
Sent: Mittwoch, 30. Oktober 2002 04:52
To: modssl-users@modssl.org
Subject: Startup Script


Greetings everyone,

I realize this situation has come up before, but none of the suggestions
I have seen have worked for me.

I have created an Apache 1.3.26 / mod_ssl 2.8.10 server. No problems
creating it, and no problems starting from the command line. I am
however, unable to start automatically at boot using a script in the
rc3.d directory. When I try to start it automatically using:

#!/bin/sh
#
# Start SSL-Aware Apache http daemon
#
echo "Start SSL-Aware Apache httpd"
/opt/apache/bin/apachectl startssl


I get the following error:

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

Once the system is booted up the LD_LIBRARY_PATH is
"/lib:/usr/lib:/usr/local/lib:/usr/openwin/lib", and I can run
"/opt/apache/bin/apachectl startssl" just fine. For automation reasons,
I need to boot at startup. Any suggestions?

Regards,

Lawrence

This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please notify the sender urgently
and then immediately delete the message and any copies of it from your
system. Please also immediately destroy any hardcopies of the message.
You must not, directly or indirectly, use, disclose, distribute, print,
or copy any part of this message if you are not the intended recipient.
The sender's company reserves the right to monitor all e-mail
communications through their networks. Any views expressed in this
message are those of the individual sender, except where the message
states otherwise and the sender is authorised to state them to be the
views of the sender's company.
____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

RE: Startup Script

your problem might be the ldconfig settings, for your system, they might
not be locating the libs prperly for the server to find them and function.
try updating ldso with a call to ldconfig, if thats the proper solaris way
of doing things, with the lib paths required, something like a ldconfig -R
-v (paths) which is the bsdish way. It's been awhile since I admined a
sun system and my sun box is bsd'ed, so I can't check at present for the
proper syntax and params for you, but this should give you a clue...

Thanks,

Ron DuFresne


On Wed, 30 Oct 2002, Lawrence Cole wrote:

> Boyle,
>
> Thank you for your suggestions.
>
> Adding "LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib:/usr/openwin/l ib"
> to the startup script does not help.
>
> Sourcing root's .profile before running the "apachectl startssl" command
> does not help. The LD_LIBRARY_PATH is set in the .profile.
>
> So the last thing to try are the -R and -L compile-time option pairs for
> each library. I have a rookie question to ask. Where do I use these?
> I can't use them with the .configure or make commands. Do I need to
> edit the Makefile? Can you give me an example?
>
> Regards,
>
> Lawrence
>
>
> -----Original Message-----
> From: owner-modssl-users@modssl.org
> [mailto:owner-modssl-users@modssl.org] On Behalf Of Boyle Owen
> Sent: Wednesday, October 30, 2002 2:21 AM
> To: modssl-users@modssl.org
> Subject: RE: Startup Script
>
>
> Quick fix is to put in the startup script:
>
> LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib:/usr/openwin/li b
>
> before it tries to start apache..
>
> Better fix is to recompile apache with the additional compile-time
> options: "-L/usr/openwin/lib -R/usr/openwin/lib" etc. (one pair for each
> lib). This should build the paths to the libs into the binary and then
> you don't need LD_LIBRARY_PATH at all.
>
> -----Original Message-----
> From: Lawrence Cole [mailto:lmcole@cisco.com]
> Sent: Mittwoch, 30. Oktober 2002 04:52
> To: modssl-users@modssl.org
> Subject: Startup Script
>
>
> Greetings everyone,
>
> I realize this situation has come up before, but none of the suggestions
> I have seen have worked for me.
>
> I have created an Apache 1.3.26 / mod_ssl 2.8.10 server. No problems
> creating it, and no problems starting from the command line. I am
> however, unable to start automatically at boot using a script in the
> rc3.d directory. When I try to start it automatically using:
>
> #!/bin/sh
> #
> # Start SSL-Aware Apache http daemon
> #
> echo "Start SSL-Aware Apache httpd"
> /opt/apache/bin/apachectl startssl
>
>
> I get the following error:
>
> ld.so.1: /opt/apache/bin/httpd: fatal: libexpat.so.0: open failed: No
> such file or directory Killed /opt/apache/bin/apachectl startssl: httpd
> could not be started
>
> Once the system is booted up the LD_LIBRARY_PATH is
> "/lib:/usr/lib:/usr/local/lib:/usr/openwin/lib", and I can run
> "/opt/apache/bin/apachectl startssl" just fine. For automation reasons,
> I need to boot at startup. Any suggestions?
>
> Regards,
>
> Lawrence
>
> This message is for the named person's use only. It may contain
> confidential, proprietary or legally privileged information. No
> confidentiality or privilege is waived or lost by any mistransmission.
> If you receive this message in error, please notify the sender urgently
> and then immediately delete the message and any copies of it from your
> system. Please also immediately destroy any hardcopies of the message.
> You must not, directly or indirectly, use, disclose, distribute, print,
> or copy any part of this message if you are not the intended recipient.
> The sender's company reserves the right to monitor all e-mail
> communications through their networks. Any views expressed in this
> message are those of the individual sender, except where the message
> states otherwise and the sender is authorised to state them to be the
> views of the sender's company.
> ____________________________________________________________ __________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List modssl-users@modssl.org
> Automated List Manager majordomo@modssl.org
>
> ____________________________________________________________ __________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List modssl-users@modssl.org
> Automated List Manager majordomo@modssl.org
>

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
admin & senior security consultant: sysinfo.com
http://sysinfo.com

"Cutting the space budget really restores my faith in humanity. It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation."
-- Johnny Hart

testing, only testing, and damn good at it too!

____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

RE: Startup Script

To expand a little on my previous post:

When you run a shell-script, it forks a new shell which doesn't usually
inherit environment variables from the calling shell. So you have to set
any envs in the script. To do this under the standard shell (i.e.
/bin/sh) you need two lines:

LD_LIBRARY_PATH="/lib:/usr/lib:/usr/local/lib:/usr/openwin/l ib"
export LD_LIBRARY_PATH

Under the tcsh, you'd only need one:

setenv LD_LIBRARY_PATH
/lib:/usr/lib:/usr/local/lib:/usr/openwin/lib

So that's how to get LD_LIBRARY_PATH to work.

However, the use of LD_LIBRARY_PATH is generally discouraged for several
reasons - it breaks encapsulation by making the execution of a binary
dependent on the shell (hence your problem), it invites namespace
problems if two libraries in different lib directories have the same
name (the binary will load the first it finds on the path), on large
projects with lots of development libs, the path can become unfeasibly
large, etc. etc.

A much cleaner solution is to define the paths when compiling. Thus the
binary carries with it the paths to just those directories it needs. To
do this, define the "CFLAGS" environment variable in the shell in which
you configure apache, i.e.

CFLAGS="-L/lib -R/lib -L/usr/lib -R/usr/lib -L/usr/openwin/lib
-R/usr/openwin/lib"
export CFLAGS
./configure

When you run make, you will find that the CFLAGS above will appear on
the compile line and the resulting binary will find its libraries from
these internal symbols.

Compiling is a bit of a black art at times and I don't really understand
all of it myself - the advices in this note are just some distillations
of my own experiences and things I found when trawling the web..

Rgds,

Owen Boyle

-----Original Message-----
From: Lawrence Cole [mailto:lmcole@cisco.com]
Sent: Mittwoch, 30. Oktober 2002 21:05
To: modssl-users@modssl.org
Subject: RE: Startup Script


Boyle,

Thank you for your suggestions.

Adding "LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib:/usr/openwin/l ib"
to the startup script does not help.

Sourcing root's .profile before running the "apachectl startssl" command
does not help. The LD_LIBRARY_PATH is set in the .profile.

So the last thing to try are the -R and -L compile-time option pairs for
each library. I have a rookie question to ask. Where do I use these?
I can't use them with the .configure or make commands. Do I need to
edit the Makefile? Can you give me an example?

Regards,

Lawrence


-----Original Message-----
From: owner-modssl-users@modssl.org
[mailto:owner-modssl-users@modssl.org] On Behalf Of Boyle Owen
Sent: Wednesday, October 30, 2002 2:21 AM
To: modssl-users@modssl.org
Subject: RE: Startup Script


Quick fix is to put in the startup script:

LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib:/usr/openwin/li b

before it tries to start apache..

Better fix is to recompile apache with the additional compile-time
options: "-L/usr/openwin/lib -R/usr/openwin/lib" etc. (one pair for each
lib). This should build the paths to the libs into the binary and then
you don't need LD_LIBRARY_PATH at all.

-----Original Message-----
From: Lawrence Cole [mailto:lmcole@cisco.com]
Sent: Mittwoch, 30. Oktober 2002 04:52
To: modssl-users@modssl.org
Subject: Startup Script


Greetings everyone,

I realize this situation has come up before, but none of the suggestions
I have seen have worked for me.

I have created an Apache 1.3.26 / mod_ssl 2.8.10 server. No problems
creating it, and no problems starting from the command line. I am
however, unable to start automatically at boot using a script in the
rc3.d directory. When I try to start it automatically using:

#!/bin/sh
#
# Start SSL-Aware Apache http daemon
#
echo "Start SSL-Aware Apache httpd"
/opt/apache/bin/apachectl startssl


I get the following error:

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

Once the system is booted up the LD_LIBRARY_PATH is
"/lib:/usr/lib:/usr/local/lib:/usr/openwin/lib", and I can run
"/opt/apache/bin/apachectl startssl" just fine. For automation reasons,
I need to boot at startup. Any suggestions?

Regards,

Lawrence

This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please notify the sender urgently
and then immediately delete the message and any copies of it from your
system. Please also immediately destroy any hardcopies of the message.
You must not, directly or indirectly, use, disclose, distribute, print,
or copy any part of this message if you are not the intended recipient.
The sender's company reserves the right to monitor all e-mail
communications through their networks. Any views expressed in this
message are those of the individual sender, except where the message
states otherwise and the sender is authorised to state them to be the
views of the sender's company.
____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please notify the sender urgently
and then immediately delete the message and any copies of it from your
system. Please also immediately destroy any hardcopies of the message.
You must not, directly or indirectly, use, disclose, distribute, print,
or copy any part of this message if you are not the intended recipient.
The sender's company reserves the right to monitor all e-mail
communications through their networks. Any views expressed in this
message are those of the individual sender, except where the message
states otherwise and the sender is authorised to state them to be the
views of the sender's company.
____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

RE: Startup Script

Owen,

Both solutions work. Thank you very much for your time and patience.


Regards,

-Lawrence



-----Original Message-----
From: owner-modssl-users@modssl.org
[mailto:owner-modssl-users@modssl.org] On Behalf Of Boyle Owen
Sent: Thursday, October 31, 2002 1:04 AM
To: modssl-users@modssl.org
Subject: RE: Startup Script


To expand a little on my previous post:

When you run a shell-script, it forks a new shell which doesn't usually
inherit environment variables from the calling shell. So you have to set
any envs in the script. To do this under the standard shell (i.e.
/bin/sh) you need two lines:

LD_LIBRARY_PATH="/lib:/usr/lib:/usr/local/lib:/usr/openwin/l ib"
export LD_LIBRARY_PATH

Under the tcsh, you'd only need one:

setenv LD_LIBRARY_PATH
/lib:/usr/lib:/usr/local/lib:/usr/openwin/lib

So that's how to get LD_LIBRARY_PATH to work.

However, the use of LD_LIBRARY_PATH is generally discouraged for several
reasons - it breaks encapsulation by making the execution of a binary
dependent on the shell (hence your problem), it invites namespace
problems if two libraries in different lib directories have the same
name (the binary will load the first it finds on the path), on large
projects with lots of development libs, the path can become unfeasibly
large, etc. etc.

A much cleaner solution is to define the paths when compiling. Thus the
binary carries with it the paths to just those directories it needs. To
do this, define the "CFLAGS" environment variable in the shell in which
you configure apache, i.e.

CFLAGS="-L/lib -R/lib -L/usr/lib -R/usr/lib -L/usr/openwin/lib
-R/usr/openwin/lib"
export CFLAGS
./configure

When you run make, you will find that the CFLAGS above will appear on
the compile line and the resulting binary will find its libraries from
these internal symbols.

Compiling is a bit of a black art at times and I don't really understand
all of it myself - the advices in this note are just some distillations
of my own experiences and things I found when trawling the web..

Rgds,

Owen Boyle

-----Original Message-----
From: Lawrence Cole [mailto:lmcole@cisco.com]
Sent: Mittwoch, 30. Oktober 2002 21:05
To: modssl-users@modssl.org
Subject: RE: Startup Script


Boyle,

Thank you for your suggestions.

Adding "LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib:/usr/openwin/l ib"
to the startup script does not help.

Sourcing root's .profile before running the "apachectl startssl" command
does not help. The LD_LIBRARY_PATH is set in the .profile.

So the last thing to try are the -R and -L compile-time option pairs for
each library. I have a rookie question to ask. Where do I use these? I
can't use them with the .configure or make commands. Do I need to edit
the Makefile? Can you give me an example?

Regards,

Lawrence


-----Original Message-----
From: owner-modssl-users@modssl.org
[mailto:owner-modssl-users@modssl.org] On Behalf Of Boyle Owen
Sent: Wednesday, October 30, 2002 2:21 AM
To: modssl-users@modssl.org
Subject: RE: Startup Script


Quick fix is to put in the startup script:

LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib:/usr/openwin/li b

before it tries to start apache..

Better fix is to recompile apache with the additional compile-time
options: "-L/usr/openwin/lib -R/usr/openwin/lib" etc. (one pair for each
lib). This should build the paths to the libs into the binary and then
you don't need LD_LIBRARY_PATH at all.

-----Original Message-----
From: Lawrence Cole [mailto:lmcole@cisco.com]
Sent: Mittwoch, 30. Oktober 2002 04:52
To: modssl-users@modssl.org
Subject: Startup Script


Greetings everyone,

I realize this situation has come up before, but none of the suggestions
I have seen have worked for me.

I have created an Apache 1.3.26 / mod_ssl 2.8.10 server. No problems
creating it, and no problems starting from the command line. I am
however, unable to start automatically at boot using a script in the
rc3.d directory. When I try to start it automatically using:

#!/bin/sh
#
# Start SSL-Aware Apache http daemon
#
echo "Start SSL-Aware Apache httpd"
/opt/apache/bin/apachectl startssl


I get the following error:

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

Once the system is booted up the LD_LIBRARY_PATH is
"/lib:/usr/lib:/usr/local/lib:/usr/openwin/lib", and I can run
"/opt/apache/bin/apachectl startssl" just fine. For automation reasons,
I need to boot at startup. Any suggestions?

Regards,

Lawrence

This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please notify the sender urgently
and then immediately delete the message and any copies of it from your
system. Please also immediately destroy any hardcopies of the message.
You must not, directly or indirectly, use, disclose, distribute, print,
or copy any part of this message if you are not the intended recipient.
The sender's company reserves the right to monitor all e-mail
communications through their networks. Any views expressed in this
message are those of the individual sender, except where the message
states otherwise and the sender is authorised to state them to be the
views of the sender's company.
____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please notify the sender urgently
and then immediately delete the message and any copies of it from your
system. Please also immediately destroy any hardcopies of the message.
You must not, directly or indirectly, use, disclose, distribute, print,
or copy any part of this message if you are not the intended recipient.
The sender's company reserves the right to monitor all e-mail
communications through their networks. Any views expressed in this
message are those of the individual sender, except where the message
states otherwise and the sender is authorised to state them to be the
views of the sender's company.
____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org