dw_dev | Errors on new DreamWidth installation using Ubuntu 9.10 Server

Entry tags:

install issues

Errors on new DreamWidth installation using Ubuntu 9.10 Server

Just setup a new instance of DreamWidth and I am getting blank screens when I hit certain portions of the site. For example when I hit http://www.librejournal.org/users/kyle/ I get the following errors in my Apache error log (which I've upped to debug):


[Wed Dec 09 15:17:29 2009] [info] [client 198.247.174.231] Module bug?  Request filename is missing for URI /users/kyle/
[Wed Dec 09 15:17:29 2009] [notice] child pid 1570 exit signal Segmentation fault (11)

Anyone have any suggestions on how to troubleshoot? It seems related to any user related pages, so maybe the patch used for dw-free installations had an issue w/ User.pm?

As noted in the subject I'm also on Ubuntu 9.10 Server, don't know how common that install is.

Flat | Top-Level Comments Only

Well - actually one thing divided into two parts:
Off the top of my head, I'm thinking this might be an Apache (or DW) subdomain thing.
Is your DW installation configured to use subdomains for user accounts (as in: grimsniffer.dreamwidth.org rather than www.dreamwidth.org/users/grimsniffer/)? It's a variable in one of the config files. If it is, do you manage to access journals when typing in the URL like that? If it isn't, try enabling it, restarting the server and see if you can access user-pages (both in a subdomain form and in the form you used above).

Second: Is your Apache server configured to use subdomains? As in: does your httpd.conf file have something along these lines?: http://www.howtoforge.com/forums/showthread.php?t=23
I'm not near my installation at the moment, so I can't check these parameters exactly and tell you what they should read - so I have to revert to Google.

I don't know about Ubuntu 9.10 and DW. I'm running it on Debian Lenny and it works fine (at least the parts you're having trouble with).

This is odd, I've never seen this error message before.

I'm afraid that we're not running on 9.10 (yet), but I've been meaning to. I'll be upgrading my development environment in a week or two, how much is this impacting you? I.e., is this a "my site is down, on fire, help!" issue or are you just working on setting things up?

Heh, can't it be both? I'm working on a new site and it's down! :P

I'm leaning towards it being a problem w/ some new perl module version in 9.10 or something Apache related.

Is there a hard 64-bit requirement for DW? I have another machine running ESX but I can only provision 32-bit VMs on it. I could put up a 9.10 server for you to test on.

64 bit isn't a hard requirement... there's a patch? A bug? The DeadJournal guys are working on 32 bit support because they want to be able to run the DW code.

And yeah, I assume it's some incompatibility with new versions of things, but it has to be tracked down. I haven't upgraded to 9.10 yet so I can't help you much. I intend to soon -- but it probably won't happen until after the holidays, as I'm going to be pretty busy until January.

Some more troubleshooting with

exor644 and

sophie on IRC and we found that if I comment out line 40 from update.bml which reads:


    my $remote = LJ::get_remote();

it no longer seg faults. I can't update anything but the segfault does disappear.

Loading a test.bml with:


$test = LJ::get_remote();

works.

Ignore last entry, it was just failing because it didn't have a valid declaration for $remote anymore. After more research I can now get update.bml to allow an entry w/o a segfault if I comment out line 209. Something it doesn't like about auth_as_remote.


        my $entry = {
            'mode' => "update",
#            'auth_as_remote' => $auth_as_remote,
            'subject' => $subject,
            'event' => $event,
            'prop_taglist' => $tags,
            'datetime' => "$year-$mon-$mday $hour:$min",
            'usejournal' => LJ::canonical_username($POST{'usejournal'} || $GET{'usejournal'}),
            'auth' => $auth,
            'remote' => $remote,
            'spellcheck_html' => $spellcheck_html,
            'clientversion' => "WebUpdate/2.0.0",
            'richtext' => LJ::is_enabled('richtext'),
            'richtext_default' => $remote ? $remote->new_entry_editor eq 'rich' ? 1 : 0  # User setting
                                          : $LJ::DEFAULT_EDITOR       eq 'rich' ? 1 : 0, # Site default
            'include_insert_object' => $GET{'insobj'},
            'prop_qotdid' => $qid,
            'altlogin' => $GET{altlogin} ? 1 : 0,
            'prop_opt_preformatted' => $opt_preformatted ? 1 : 0,

            %xpost_vals,
        };