Reading page oddity

[whobutdrew]

OK, so my install is, for many intents and purposes, functional. I got postfix sending email, I am working around other issues. I have everything imported and friends added.

If I go to http://mysite.com, log in as anyone, and click on Reading Page, I get

Oops!

If you've gotten this error, it means that something is currently (and, with luck, temporarily) broken. Please wait five minutes and try again.

The person's journal loads correctly, friends' pages work correctly, going to profiles (own or others) works correctly. As far as I can tell, only other.

If it is relevant, instead of using journal-name.mysite.com, I'm using mysite.com/users/journal-name. Any logs or configs will be made available upon request.

Though, as has been the case with many of my supposed issues, I've been linked to one patch and it solves everything, so tell me which one I'm missing! :P

Comments

[exor674]

What are the last few messages in your error log?

[whobutdrew]

Assuming Apache log is what you meant:


[Sun Jan 24 18:18:19 2010] [error] [client 1.2.3.4] Invalid type 'Q' in pack at /home/dw/cgi-bin/DW/User/Edges/WatchTrust/Loader.pm line 276.\n, referer: http://mysite.com

[sophie]

Ah, that'll be because you're running on a 32-bit Perl.

If you're on the latest code, you should be able to uncomment the $ARCH32 = "1"; line in your config-private.pl file, or add it if you don't have it. If that doesn't help, you'll want to update so that the changes made in bug #1632 are applied. (Don't patch it yourself as Mark made some more changes.)

That should fix that error, and hopefully the problem with the reading page.

[whobutdrew]

That Arch32 var is set, I made sure to do it when I saw it, as it was new. Are the quotes necessary?

I'm not clear what you mean by 'don't patch it myself.' Does that mean I should not run "patch -p0" on the attachment that's on there? If not, what should I do?

(Its pre-6am here and I'm on my way to work, hence my sub-par lack of understanding/ability to read the comment threads!)

[pauamma]

Quoting from http://changelog.dreamwidth.org/517277.html:

--- a/doc/config-private.pl.txt Sat Jan 09 00:43:59 2010 +0000
+++ b/doc/config-private.pl.txt Sat Jan 09 01:10:00 2010 +0000
@@ -50,6 +50,14 @@
pass => 'password', # CHANGETHIS
},
);
+
+ # 32 vs 64 bit arch. By default everything goes to a 64 bit arch. Uncomment
+ # to enable 32 bit arch support.
+ #
+ # WARNING: This must be set prior to setting up your site. If you change it
+ # later on a running site, things may go badly for you.
+ #
+ #$ARCH32 = "1";

but "I made sure to do it when I saw it" sounds like you changed it after setting up your site.

[whobutdrew]

I made the change right after downloading the code, when I was changing the other config files. I hadn't configured Apache yet, or populated any databases yet, either.

[pauamma]

OK.

[pauamma]

I think that by "don't patch it yourself", sophie meant "don't just apply patches attached to that ticket, but synchronize your source code to the current version" (since mark may have made changes not attached to the bug).

[whobutdrew]

I should have the latest code already, or at least since the last week or two. I downloaded really recently. I'll re-sync if needed, though.

[pauamma]

OK, there are still a few places that should honor that setting but don't (yet). *wanders off to the ticket*

[whobutdrew]

I updated the code (using the steps outlined in the wiki) and while a few changes did appear to get pulled down, it didn't fix my reading page issue.

[pauamma]

Yeah, I know. See my comment on the bug ticket.

[whobutdrew]

OK, switching back to my 64bit server might be the path I have to take. Is there a way to migrate all of the work I've done from one machine to the other? Or would flipping that 32bit switch now that the site had been configured do more harm than good?

[pauamma]

Flipping in either direction with live data will likely cause a number of problems, sorry. Your best way is probably to fix the code (if you're in a hurry) or to wait until the additional patch if you can afford to. (Fixing it isn't very hard. Just check how it's been done in other patches on that ticket and do the same for that file.)

[whobutdrew]

Don't go too crazy trying to address this. I found out today that I'm going to be traveling for work as soon as this weekend, so I'm just going to leave it alone until I get back. At which point I'll probably just switch back to my 64bit environment and call it good.