On Thu, Apr 10, 2014 at 3:33 PM, David Benfell <benf...@parts-unknown.org>wrote:
> On Thu, Apr 10, 2014 at 02:14:02PM -0600, Jeff Trawick wrote: > > On Thu, Apr 10, 2014 at 2:05 PM, David Benfell > > <[1]benf...@parts-unknown.org> wrote: > > > > On Thu, Apr 10, 2014 at 01:38:00PM -0600, Eric Covener wrote: > > > On Thu, Apr 10, 2014 at 4:35 AM, David Benfell > > > <[2]benf...@parts-unknown.org> wrote: > > > > apr_crypto_init > > > > > Maybe you built with the up-to-date apr-util (so httpd or some module > > thinks apr_crypto_init() exists) but an older level apr-util > > (system-provided?) is being used when you try to start httpd. > > As a test, try > > export LD_LIBRARY_PATH=/path/to/new/httpd/lib > > (or wherever you installed new apr-util) > > before starting httpd and see if that works. > > > Progress of a sort: There was definitely some cruft lying about from a > previous 2.2 build. I deleted it. I set the environment variable > LD_LIBRARY_PATH=/usr/lib64/apr-util-1 and apachectl start at least > starts the server (I have other problems but I think they're > related to php). > That apr-util-1 subdirectory is only used when loading apr-util extensions, and I thought apr-util could find those on its own once libaprutil-1 was loaded (but I may be wrong there). LD_LIBRARY_PATH generally is updated to point to the directory where libaprutil-1.so resides (when rpath can't help). But I guess that on your platform /usr/lib64 is in the default library search path, so you shouldn't need LD_LIBRARY_PATH at all. Without the old cruft, is your LD_LIBRARY_PATH setting actually necessary? I unfortunately missed your clear, earlier statement that you are using the provided RPM specs which install apr + apr-util as system libraries. IMO that is not a good idea for most people, in case you want to install arbitrary software from your system package repository and have it use the apr + apr-util it is built with and at the same time have your httpd use the apr + apr-util you selected for that particular purpose. I don't use the RPM builds myself, never install into system directories, and don't really know what the considerations are. Sorry. > /etc/init.d/httpd start does not, even when I set the environment > variable in the script right before the line that starts the daemon. > Same error as before, or something different? Can you copy and paste the exact message? I don't think your current LD_LIBRARY_PATH actually changes anything. > > I'm thinking I ought to be able to substitute apachectl for the start > script with a symbolic link. Would this work? Any reason I shouldn't? > Where did you get /etc/init.d/httpd? Is that from an RPM build you did of httpd 2.4? > > Thanks! > -- > David Benfell <benf...@parts-unknown.org> > See https://parts-unknown.org/node/2 if you don't understand the > attachment. > -- Born in Roswell... married an alien... http://emptyhammock.com/ http://edjective.org/
