mod_perl brains

[naienko]

I'm so close I can smell it. Apache directives are set, db is populated, files are in the right folders ...

*insert swearing here* So everything else works - I'm just getting a DirectoryIndex instead of it loading index.bml properly. When I load index.bml directly it shows the code. There's gotta be something I'm missing here, something key.

site throws 500 internal error, error.log says:

/home/crantz3/.htaccess: Can't locate modperl_subs.pl in @INC (@INC contains: CODE(0x10e3870) /cgi-bin /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl . /dh/apache2/apache2-ps23029) at /home/crantz3/dw/cgi-bin/modperl.pl line 60.
Compilation failed in require at (eval 2) line 1.

Now, I know the LJHOME variable is set, I've run

env

. I know modperl_subs.pl exists, I'm looking at it. I know it's in the cgi-bin.

I've even gone in and force-set the location of modperl_subs.pl, at which point it says fine, Can't locate LJ/Config.pm in @INC etcetc.

What's set wrong here?

It's taunting me.

/home/crantz3/.htaccess: Can't run '$s->add_config' after server startup at /home/crantz3/dw/cgi-bin/modperl_subs.pl line 205.

/facepalm

Comments

[mark]

Weird, you have an .htaccess file? And can you show your Apache configuration?

I'd argue that $LJHOME is somehow not getting set, since your @INC contains "/cgi-bin" which should probably have been "$LJHOME/cgi-bin" with whatever your LJHOMe is.

[naienko]

Dreamhost virtual servers are a bit funky, but Linux obeys my commands -- perl doesn't >< . I got LJHOME set properly (moved it out of the area in the httpd.conf), and dumped the PerlRequire into the .htaccess because it worked there and don't change what works. So now I have the taunting error, where it looks like the modperl_subs.pl code is trying to modify or create another httpd.conf?

[sophie]

Right, it tries to tell the server what it needs as extra configuration, that's what it does. You'll need to move the PerlRequire out of your .htaccess; it needs to be in the httpd.conf since .htaccess files are only read after the server has already started, when someone tries to access the directory.

Could you pastebin your Apache config at http://pastebin.ca/ or similar? It might help us to see it.

[naienko]

Here is the httpd.conf, slightly obfuscated because I'm paranoid: http://pastebin.ca/1846869

I've shifted all the Perl Directives to that file and removed the .htaccess; I tried putting some of the Directives from modperl_subs into the httpd.conf and that didn't work (although I can get a blank page, i.e. the server received headers but no other code); I tried putting that same code into an .htaccess and got the same results.

I've added four lines to the original httpd.conf. All of them are to do with perl. Beyond that, I am stuck.

[exor674]

You need to have:

PerlSetEnv LJHOME /home/[username]/dw
SetEnv LJHOME /home/[username]/dw
PerlPassEnv LJHOME

PerlRequire /home/[username]/dw/cgi-bin/modperl.pl

down in the <VirtualHost 69.163.149.178:80> section
However note that the Dreamwidth code isn't known to play well with VirtualHost directives -- SHOULD be fine if it's the only mod_perl site, though.

Also, you are missing the apreq module.

If you still, can't get it working, try a config file closer to:
http://pastie.org/private/euszmiymtz57x7fbz4liq

[naienko]

As soon as I move

PerlSetEnv LJHOME /home/[username]/dw
SetEnv LJHOME /home/[username]/dw
PerlPassEnv LJHOME

PerlRequire /home/[username]/dw/cgi-bin/modperl.pl

into the section, the apache server fails to start.

[sophie]

Hmm. You really don't want to be running DW on a webserver with other sites on it, I think; ideally a Dreamwidth installation should live on its own server, without using VirtualHosts. As such, it's very hard to know what precisely is going on. (Also, watch out for any weirdnesses on your other virtual hosts...)

That said, you could try the following:

* moving the Perl lines into the hamsterjournal.com VirtualHost section, rather than in the main section.
* Removing the DirectoryIndex line from the hamsterjournal.com VirtualHost; DW provides its own to Apache when it initialises.

All in all, those might bring some luck. But I have no clue how well the DW code will perform in a VirtualHost; particularly, as your configuration is currently set up, you won't be able to use user subdomains.

If you can, I'd advise you set up a totally new Apache instance with its own config and no VirtualHosts; you might have more luck with that.

[denise]

Not to mention that the DW code is kind of a hog. I wouldn't want to run anything other than a dev site on 512MB of RAM, for instance....

[catness]

Hi there. I had exactly the same problem yesterday (everything works except for bml-parsing) and managed to solve it by copying the bml handling bit from modperl_subs.pl

<Files ~ "\.bml$">
SetHandler perl-script
PerlResponseHandler Apache::BML
</Files>

to one of the default apache config settings (00_default_settings.conf on my platform but I use Gentoo)

[naienko]

oh god, that made it work! You helped me make it work. YAY!

[catness]

Hooray! glad it helped! :D