Apache Server configuration support - Modules garbled, perhaps not a DSO module

This is Interesting: Free IT Magazines  
Home > Archive > Apache Server configuration support > December 2007 > Modules garbled, perhaps not a DSO module





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Modules garbled, perhaps not a DSO module
Chuck Smith

2007-12-23, 1:26 pm

I have a server that runs apache to host a web site. Recently the server
was upgraded and now the httpd service will not start. A message that the
module being called in the config file might not be a DSO module. Searching
around I get the impression that the modules need to be rebuilt or
recompiled. I don't know how to go about doing this or if the solution is
something else.

Any suggestions or thoughts?

Davide Bianchi

2007-12-23, 1:26 pm

On 2007-12-23, Chuck Smith <smith.chuck48@yahoo.com> wrote:
> I have a server that runs apache to host a web site. Recently the server
> was upgraded and now the httpd service will not start. A message that the
> module being called in the config file might not be a DSO module.


It looks like your upgrade messed up the modules, which module would
that be?

> I don't know how to go about doing this or if the solution is
> something else.


If you can get a pre-compiled, use a precompiled, otherwise you'll have
to rebuild your module.

Davide

--
Reset button? Which reset button? - Linux, the OS that never sleeps.
-- Havlik Denis
Brendan Gillatt

2007-12-23, 1:26 pm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chuck Smith wrote:
> I have a server that runs apache to host a web site. Recently the
> server was upgraded and now the httpd service will not start. A message
> that the module being called in the config file might not be a DSO
> module. Searching around I get the impression that the modules need to
> be rebuilt or recompiled. I don't know how to go about doing this or if
> the solution is something else.
>
> Any suggestions or thoughts?


That may be the result of the core parts of apache being upgraded without
the modules or visa versa. Apache 1.3.x modules will not work with 2.x
versions of apache.

I suggest you find the version of the core of the apache server you're
running (usually in a comment in your httpd.conf file), download the
binary package for that version from apache.org and just extract the
modules into the mod/ directory.

- --
Brendan Gillatt
brendan {at} brendangillatt {dot} co {dot} uk
http://www.brendangillatt.co.uk
PGP Key: http://pgp.mit.edu:11371/pks/lookup...arch=0xBACD7433
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)

iD8DBQFHbpYikA9dCbrNdDMRApsCAKClg7qVQ0GT
fAzONBVLzSwovqEvCACgzFW7
whN6GegMC83mCfHlGm2cVpI=
=JsiT
-----END PGP SIGNATURE-----
HansH

2007-12-23, 7:20 pm

"Chuck Smith" <smith.chuck48@yahoo.com> schreef in bericht
news:ab1bd$476e7ba6$d06639ae$17760@FUSE.NET...
>I have a server that runs apache to host a web site. Recently the server
>was upgraded and now the httpd service will not start. A message that the
>module being called in the config file might not be a DSO module.
>Searching around I get the impression that the modules need to be rebuilt

Without doubt those modules need to be updated too.

For detailed advise you need to provide details like version and
distribution -download link- before and after the upgrade of OS and Apache
and the offending module(s)

HansH


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com