FUDforum: How To » importing messages breaks forum

Home » FUDforum » How To » importing messages breaks forum

Show: Today's Messages :: Polls :: Message Navigator

importing messages breaks forum [message #22312]

Thu, 27 January 2005 01:07

arakune

Messages: 10
Registered: April 2004

Karma: 0

Junior Member

I've got a number of mailing list archives (~14000 messages all told) which I'm trying to import into a fresh FUDforum install. Invariably, after a certain point (though NOT triggered by the same message each time), maillist.php will fail, and at that point I am no longer able to import any more messags, nor am I able to access FUDforum itself.

The error from maillist.php looks like this:

-------------------------------------------------------------
(/u2/afs/home/sites/lainlist.net/fud_data/include/theme/default/db.inc:123 
/u2/afs/home/sites/lainlist.net/fud_data/include/theme/default/db.inc:185 
/u2/afs/home/sites/lainlist.net/fud_data/include/theme/default/imsg_edt.inc :369 
/u2/afs/home/sites/lainlist.net/fud_data/scripts/maillist.php:484 
) 1016: Can't open file: 'fud26_thread_view.MYD'. (errno: 145) 
Query: SELECT page FROM fud26_thread_view WHERE forum_id=2 AND thread_id=171 
Server Version: 3.23.36 
---------------------------------------------------------------

and the error from index.php (when browsed) is this:

--------------------------------------------------------------
Warning: error_log(/u2/afs/home/sites/lainlist.net/fud_data/errors/sql_errors) [function.error-log]: failed to create stream: Permission denied in /u2/afs/home/sites/lainlist.net/chatter/index.php on line 51
UNABLE TO WRITE TO SQL LOG FILE
(/u2/afs/home/sites/lainlist.net/chatter/index.php:125
/u2/afs/home/sites/lainlist.net/chatter/theme/default/thread.php:508
/u2/afs/home/sites/lainlist.net/chatter/index.php:1174
) 1016: Can't open file: 'fud26_thread_view.MYD'. (errno: 145)
Query: SELECT m.attach_cnt, m.poll_id, m.subject, m.icon, m.post_stamp, u.alias, u.id, u2.id, u2.alias, m2.id, m2.post_stamp, f.id, f.name, t.id, t.moved_to, t.root_msg_id, t.replies, t.rating, t.thread_opt, t.views, r.last_view FROM fud26_thread_view tv INNER JOIN fud26_thread t ON tv.thread_id=t.id INNER JOIN fud26_msg m ON t.root_msg_id=m.id INNER JOIN fud26_msg m2 ON m2.id=t.last_post_id LEFT JOIN fud26_users u ON u.id=m.poster_id LEFT JOIN fud26_users u2 ON u2.id=m2.poster_id LEFT JOIN fud26_forum f ON f.id=t.moved_to LEFT JOIN fud26_read r ON t.id=r.thread_id AND r.user_id=2 WHERE tv.forum_id=2 AND tv.page=1 ORDER BY tv.pos ASC
_GET: t=thread&frm_id=2&rid=2&S=abe974fd290fcd8b7a19da7d700408de&
Server Version: 3.23.36
[Referring Page] http://chatter.lainlist.net/index.php?t=i&rid=2&S=abe974fd290fcd8b7 a19da7d700408de
--------------------------------------------------------------

Errors are logged to to errors/sql_errors, but its gibberish (I'm not sure if this file is supposed to be human readable or not). The permissions on the file are -rw-rw-r-- for the user running maillist.php (i.e., I'm not sure where permission denied is coming from).

This happens in the middle of running

for i in * ; do
cat $i | php /afs/home/sites/lainlist.net/fud_data/scripts/maillist.php 1
sleep 1
done

but as I mentioned, isn't being triggered by any particular message. This time around, it was triggered by the 810th message in my maildir. In previous tries, its made it passed that particular message, and choke elsewhere.

I haven't been able to figure out how to recover from this (other than re-install and start over). I wondered if anyone had any suggestions on what to look at. This is starting to look like a show-stopper, which is a shame, because otherwise FUDforums is quite perfect for what I want. I've tried the fudbox.php and popfud.php hacks provided elsewhere in the forums, as a potential workaround, but unfortunately have run into other errors with them Sad

Thanks in advance for any suggestions!

Edit: of course, the permissions issue for sql_errors is because its the web server, not my local account, who is attempting to write to the file. I've opened up permissions on it, and now just get the remainder of the original error (i.e., everything after the can't write to sql_errors).

In my logs, I get this:

KC91Mi9hZnMvaG9tZS9zaXRlcy9sYWlubGlzdC5uZXQvY2hhdHRlci9pbmRleC5waHA6MTI1P
GJyIC8+Ci91Mi9hZnMvaG9tZS9zaXRlcy9sYWlubGlzdC5uZXQvY2hhdHRlci90aGVtZS9kZWZh dWx0L3RocmVhZC5waHA6NTA4PGJy
IC8+Ci91Mi9hZnMvaG9tZS9zaXRlcy9sYWlubGlzdC5uZXQvY2hhdHRlci9pbmRleC5waHA6MTE 3NDxiciAvPgopIDEwMTY6IENhbid
0IG9wZW4gZmlsZTogJ2Z1ZDI2X3RocmVhZF92aWV3Lk1ZRCcuIChlcnJubzogMTQ1KTxiciAvPg pRdWVyeTogU0VMRUNUCgkJbS5hdH
RhY2hfY250LCBtLnBvbGxfaWQsIG0uc3ViamVjdCwgbS5pY29uLCBtLnBvc3Rfc3RhbXAsCgkJd S5hbGlhcywgdS5pZCwKCQl1Mi5pZ
CwgdTIuYWxpYXMsCgkJbTIuaWQsIG0yLnBvc3Rfc3RhbXAsCgkJZi5pZCwgZi5uYW1lLAoJCXQu aWQsIHQubW92ZWRfdG8sIHQucm9v
dF9tc2dfaWQsIHQucmVwbGllcywgdC5yYXRpbmcsIHQudGhyZWFkX29wdCwgdC52aWV3cywKCQl yLmxhc3RfdmlldwoJCUZST00gZnV
kMjZfdGhyZWFkX3ZpZXcgdHYKCQkJSU5ORVIgSk9JTiBmdWQyNl90aHJlYWQJdAlPTiB0di50aH JlYWRfaWQ9dC5pZAoJCQlJTk5FUi
BKT0lOIGZ1ZDI2X21zZwltCU9OIHQucm9vdF9tc2dfaWQ9bS5pZAoJCQlJTk5FUiBKT0lOIGZ1Z DI2X21zZwltMglPTiBtMi5pZD10L
mxhc3RfcG9zdF9pZAoJCQlMRUZUIEpPSU4gZnVkMjZfdXNlcnMJdQlPTiB1LmlkPW0ucG9zdGVy X2lkCgkJCUxFRlQgSk9JTiBmdWQy
Nl91c2Vycwl1MglPTiB1Mi5pZD1tMi5wb3N0ZXJfaWQKCQkJTEVGVCBKT0lOIGZ1ZDI2X2ZvcnV tCWYJT04gZi5pZD10Lm1vdmVkX3R
vCgkJCUxFRlQgSk9JTiBmdWQyNl9yZWFkIAlyCU9OIHQuaWQ9ci50aHJlYWRfaWQgQU5EIHIudX Nlcl9pZD0yCgkJCVdIRVJFIHR2Lm
ZvcnVtX2lkPTIgQU5EIHR2LnBhZ2U9MSBPUkRFUiBCWSB0di5wb3MgQVNDPGJyIC8+Cl9HRVQ6I HQ9dGhyZWFkJmZybV9pZD0yJnJpZ
D0yJlM9YWJlOTc0ZmQyOTBmY2Q4YjdhMTlkYTdkNzAwNDA4ZGUmPGJyIC8+ClNlcnZlciBWZXJz aW9uOiAzLjIzLjM2PGJyIC8+CltS
ZWZlcnJpbmcgUGFnZV0gaHR0cDovL2NoYXR0ZXIubGFpbmxpc3QubmV0L2luZGV4LnBocD90PWk mcmlkPTImUz1hYmU5NzRmZDI5MGZ
jZDhiN2ExOWRhN2Q3MDA0MDhkZTxiciAvPgo=

[Updated on: Thu, 27 January 2005 01:15]

Report message to a moderator