0

Here is my server modules list (modules.conf), its working without any problems, and lighttpd is running correctly while using this list:

server.modules = (
  "mod_access",
#  "mod_alias",
#  "mod_auth",
#  "mod_evasive",
#  "mod_redirect",
#  "mod_rewrite",
#  "mod_setenv",
#  "mod_usertrack",
)

The problem appears, when I want to uncomment the mod_rewrite module:

server.modules = (
  "mod_access",
#  "mod_alias",
#  "mod_auth",
#  "mod_evasive",
#  "mod_redirect",
   "mod_rewrite",
#  "mod_setenv",
#  "mod_usertrack",
)

Then I'm getting the following message, when I want to run my web server:

2012-05-01 15:01:18: (plugin.c.169) dlopen() failed for: /usr/local/lib/lighttpd/mod_indexfile, mod_access.so Cannot open "/usr/local/lib/lighttpd/mod_indexfile, mod_access.so"

2012-05-01 15:01:18: (server.c.656) loading plugins finally failed /usr/local/etc/rc.d/lighttpd: WARNING: failed to start lighttpd

As you can see, it does have some problems with the mod_access module, but its strange a little bit, especially when I comment back the mod_rewrite module then its working.

Where is the problem?

Cyclone
  • 14,839
  • 23
  • 82
  • 114
  • I'm equally confused by what you're reporting here. Can you give a bit more information? `ls -l /usr/local/lib/lighttpd` – David Souther May 01 '12 at 16:20
  • Confused as in it makes no sense why lighttpd would be failing that way, not confused by your description of the problem* – David Souther May 01 '12 at 16:20
  • @DavidSouther Sure, here is the output: http://pastebin.com/raw.php?i=b44myTzG – Cyclone May 01 '12 at 16:27
  • Hm, gee surprise our installs look rather different ;) What version of lighttpd, and what is your host platform? – David Souther May 01 '12 at 16:33
  • `1.4.30` installed using ports , dedicated server running on FreeBSD 8.2. – Cyclone May 01 '12 at 17:38
  • `mod_indexfile` is loaded by default which can be a little confusing. I'm guessing there's another mention of `server.modules` somewhere in your config file(s). Can you post them? – Perry Jun 16 '12 at 20:28

1 Answers1

0

I tried to reproduce this problem with the latest www/lighttpd port (version 1.4.32) and could not... The server starts with the modules.conf as you describe. Try updating to the latest, and if that works for you too, then just chalk it up as a bug of 1.4.30 and move on...

Mikhail T.
  • 3,043
  • 3
  • 29
  • 46