| Newsgroup synchronizing [message #159118] |
Wed, 06 May 2009 17:47  |
wahono
Messages: 10
Registered: April 2009
Karma: 0
|
Junior Member |
|
|
- First cron start from 100 to 200, but I got error on 150rd message.
- I don't know if my cron process got error
- system run next cron at other time, and this second cron process start synchronizing from 100rd message again. So the message is duplicated.
- If I make cron job every 15 minutes and I don't know this error until 3 hours, than messages 100rd to 150rd is duplicate 12 times.
My suggestion, if cron of nntp.php got error, it is safe to ignoring this error message and continue to next step (next message).
I think this is serious problem for newsgroup integration.
Thanks
Wahono
|
|
|
|
|
|
| Re: Newsgroup synchronizing [message #159123 is a reply to message #159119] |
Wed, 06 May 2009 18:24  |
kerryg
Messages: 157
Registered: September 2008
Karma: 0
|
Senior Member |
|
|
How are the attachments encoded? MIME? yEnc? FUD gave me similar problems with that, it can't deal with those kind of attachments yet.
Here's a couple of things you might want to try. First, find your php.ini and raise its memory limits. Try syncing again and see if that solves it.
The "manual" approach that I took involved bypassing a number of problem posts. Shut off your cron, delete all the sync'd posts out of that subforum, compact messages and rebuild your search index. Then sync again, shutting down your cron before you get to the problem post (you may need to adjust the "number of posts per sync")
When you're sure you've identified the problem post, go into your server and find your forum data folder. Find /errors/.nntp/ and inside it will be two files named for the newsgroup you're syncing. Ignore the one that says "lock", open the other one for editing. It contains the post number of the last post sync'd, so increment that number by one and it'll bypass the problem post.
[Updated on: Wed, 06 May 2009 18:25] Report message to a moderator |
|
|
|
|
|
| Re: Newsgroup synchronizing [message #159127 is a reply to message #159125] |
Thu, 07 May 2009 11:05 |
wahono
Messages: 10
Registered: April 2009
Karma: 0
|
Junior Member |
|
|
| naudefj wrote on Wed, 06 May 2009 14:33 | Can you please post the error?
If you want us to try and reproduce the error, please post your NNTP server and newsgroup name.
Best of luck!
Frank
|
The error result is broken text, I can't upload here. And in FUDforum this message is :
| message in fudforum | This is a multi-part message in MIME format.
--------------000408070804020005050104
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Martin Schreiber escribió:
> Julio Jiménez Borreguero wrote:
>
>> I tried the last svn trunk and found a weird issue with tdbstringgrid. I
>> see only the first row is shown (the others are in the screen but not
>> rendered) ie. I have a master detail relation and when I click when a
>> row is supposed to be the detail is shown.
>>
>> If I execute the query again (set tmsesqlquery active after closing the
>> transaction), all is fine. It only happens the first time the
>> tmsesqlquery is active.
>>
> Please send a simple testcase.
Here is the test
Compile and run the program, press the button, you'll see only one row
(left side) but if you click in the tdbstringgrid you'll see how the
ticket in the right side will be shown. (so the rows exists)
if you press the left button (it executes the query again) all is fine.
Thanks
Julio
--------------000408070804020005050104
Content-Type: application/x-bzip;
name="test.tar.bz2"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="test.tar.bz2"
QlpoOTFBWSZTWYeniPMFeNT///////////////////////////////////// ////////5FU4
+ngAWgGihIEXB6K4IAB7xu77B3sADDvds8AAAAHoAEPAAWj6n0cNeGNal26A A+ezaZ8Zyfez
qO31H2Y++zA+19wAHQe+ZMYOs3bbXaTS7Gj7tPYWKo92V6au3p2bLW9g7pg0 oHtjr2rK9b0r
....
....
long binary text==========>
....
....
20zUuNPdWWHv+n7K+f2fW6B9zVy0XJshiUXn9su7q7J2WevPP3fPwx5fLj39 Pa+n9v/Xv+B+
0n6G9B+2WFVasqv1TJ/Cln5EOLPy7oPnaOHoQ/9jDoHgZsYKp9Mtn2zCfmPv XodMPpsRWRFI
sGIxnWDXAes9sWHSIgKWRFSRFT/IBDPFbE//xdyRThQkLEFcA8A=
--------------000408070804020005050104--
|
File attachment doesn't show as attached file but inline message.
You can try with my newsgroup :
server : news.grid-sky.com
user and password =''
group : public.mseide-msegui.talk
message 15130-15134
My PHP conf is like this :
memory_limit 512M 512M
open_basedir no value no value
output_buffering no value no value
output_handler no value no value
post_max_size 80M 80M
precision 12 12
realpath_cache_size 16K 16K
realpath_cache_ttl 120 120
register_argc_argv On On
register_globals On On
register_long_arrays On On
report_memleaks On On
report_zend_debug On On
safe_mode Off Off
safe_mode_exec_dir no value no value
safe_mode_gid Off Off
safe_mode_include_dir no value no value
sendmail_from no value no value
sendmail_path no value no value
serialize_precision 100 100
short_open_tag On On
SMTP localhost localhost
smtp_port 25 25
sql.safe_mode Off Off
track_errors Off Off
unserialize_callback_func no value no value
upload_max_filesize 200M 200M
Thanks in advance
Wahono
[Updated on: Thu, 07 May 2009 11:16] Report message to a moderator |
|
|
|
| Re: Newsgroup synchronizing [message #159128 is a reply to message #159123] |
Thu, 07 May 2009 11:43 |
wahono
Messages: 10
Registered: April 2009
Karma: 0
|
Junior Member |
|
|
| kerryg wrote on Wed, 06 May 2009 14:24 | How are the attachments encoded? MIME? yEnc? FUD gave me similar problems with that, it can't deal with those kind of attachments yet.
|
Yes, MIME.
| kerryg wrote on Wed, 06 May 2009 14:24 | Here's a couple of things you might want to try. First, find your php.ini and raise its memory limits. Try syncing again and see if that solves it.
The "manual" approach that I took involved bypassing a number of problem posts. Shut off your cron, delete all the sync'd posts out of that subforum, compact messages and rebuild your search index. Then sync again, shutting down your cron before you get to the problem post (you may need to adjust the "number of posts per sync")
When you're sure you've identified the problem post, go into your server and find your forum data folder. Find /errors/.nntp/ and inside it will be two files named for the newsgroup you're syncing. Ignore the one that says "lock", open the other one for editing. It contains the post number of the last post sync'd, so increment that number by one and it'll bypass the problem post.
|
My PHP memory limit is 512MB and max upload file is 200MB.
I can do fix syn with your way. But I think that rather than have duplicated messages, it is better to messages that can not be synchronized is ignoring this message.
Thanks
Wahono
|
|
|
|
| Re: Newsgroup synchronizing [message #159132 is a reply to message #159128] |
Thu, 07 May 2009 18:34 |
kerryg
Messages: 157
Registered: September 2008
Karma: 0
|
Senior Member |
|
|
That's consistent with my own symptoms, detailed in this thread - http://fudforum.org/forum/index.php?t=msg&th=118143&start=0& - so I'm pretty sure we've identified the problem anyway.
Basically, as it was the last time I checked, the NNTP script doesn't understand MIME (and yEnc) encoded attachments. It stalls when it hits some; it can also break and go into a loop, endlessly duplicating the last import of messages, when it hits some particular attachments; and if it imports them at all, it does so as a block of text inline with the message.
What version of FUDForum are you running? Some of the looping/duplicating issues were looked at.
It would indeed be better if FUDforum could understand MIME-encoded attachments, but a full fix would involve creating code to permit FUDforum to import them. Frank is aware of the issue, but he has a lot of stuff on his priority list so this may have to wait until a user writes code to support it.
[Updated on: Thu, 07 May 2009 18:39] Report message to a moderator |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]