Re: [freenet-support] 5032 FIW 0.07 - FEC Encoding problem?
this is a FIW issue which is known for some time now but has never been fixed FIW sets the socket timeout for FCP connections to 5 minutes. if a FCP connection is more than 5 minutes in use, FIW closes it therefore and throws an SocketTimepoutException (well, java itself does it, but nevertheless the connection gets closed and an exception is raised) so any action which uses more than 5 minutes to complete is unable to succeed! as FEC encoding may take up to half an hour or more depending on your machine power and the size of your splitfile, you are unable to upload the file as FIW fucks up with its default settings you might consider changing the tuning.sotimeout=30 parameter in fiw.conf to something higher (30 milliseconds = 5*60*1000 ms = 5 minutes), or to 0 to disable the timeout HTH When I'm trying to upload a site containing a large file (~ 150 Mb) with FIW 0.07, I get the following error message in FIW when generating FEC check chunks: [Error] unexpected error while building check chunks! This gets written to FIW log: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at java.io.FilterInputStream.read(Unknown Source) at fiw.fcp.FCPUtil.readLine(FCPUtil.java:859) at fiw.fcp.FECUtil.makeFECData(FECUtil.java:245) at fiw.fcp.FECUtil.makeFECData(FECUtil.java:182) at fiw.core.jobs.FECBuilderJob.run(FECBuilderJob.java:83) at fiw.core.jobs.Job.run0(Job.java:132) at fiw.core.jobs.PooledThreadProducer$PooledThread.run(PooledThreadProducer.jav a:97) The following is spewed on the Freenet java console window: java.io.IOException: Sent 0 bytes (27 of packet in notifyDone at freenet.node.states.FCP.NewFECEncodeSegment.sendChunk(NewFECEncodeSeg ment.java:293) at freenet.node.states.FCP.NewFECEncodeSegment.sendDataChunks(NewFECEnco deSegment.java:276) at freenet.node.states.FCP.NewFECEncodeSegment.received(NewFECEncodeSegm ent.java:95) at freenet.node.StateChain.received(StateChain.java:192) at freenet.node.StateChain.received(StateChain.java:68) at freenet.node.StandardMessageHandler$Ticket.run(StandardMessageHandler .java:235) at freenet.node.StandardMessageHandler$Ticket.received(StandardMessageHa ndler.java:173) at freenet.node.StandardMessageHandler$Ticket.access$100(StandardMessage Handler.java:125) at freenet.node.StandardMessageHandler.handle(StandardMessageHandler.jav a:73) at freenet.Ticker$Event.run(Ticker.java:323) at freenet.thread.QThreadFactory$QThread.run(QThreadFactory.java:235) I can't find anything relevant in freenet.log when set to Normal logging level - I can try Debug if this will help, but it eats valuable HDD space _really_ quickly :-(, so I'm not sure if it will be able to log enough information before I'll have to start rotating log files. I can't verify at the moment if this is only relevant for build 5032, or any previous new stable builds are affected as well. If any additional information would help - I'll be happy to provide it. Is this a bug with FIW/Freenet or am I doing something stupid? Regards, Victor Denisov. ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] 5032 FIW 0.07 - FEC Encoding problem?
Hmmm. Strange. This was the first thing I've thought, so I've tried setting it to 30 minutes (actual FEC encoding takes ~ 12 mins on this machine) - no luck, the error still happens. Regards, Victor Denisov. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, November 20, 2003 2:34 PM Subject: Re: [freenet-support] 5032 FIW 0.07 - FEC Encoding problem? this is a FIW issue which is known for some time now but has never been fixed FIW sets the socket timeout for FCP connections to 5 minutes. if a FCP connection is more than 5 minutes in use, FIW closes it therefore and throws an SocketTimepoutException (well, java itself does it, but nevertheless the connection gets closed and an exception is raised) so any action which uses more than 5 minutes to complete is unable to succeed! as FEC encoding may take up to half an hour or more depending on your machine power and the size of your splitfile, you are unable to upload the file as FIW fucks up with its default settings you might consider changing the tuning.sotimeout=30 parameter in fiw.conf to something higher (30 milliseconds = 5*60*1000 ms = 5 minutes), or to 0 to disable the timeout HTH When I'm trying to upload a site containing a large file (~ 150 Mb) with FIW 0.07, I get the following error message in FIW when generating FEC check chunks: [Error] unexpected error while building check chunks! This gets written to FIW log: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at java.io.FilterInputStream.read(Unknown Source) at fiw.fcp.FCPUtil.readLine(FCPUtil.java:859) at fiw.fcp.FECUtil.makeFECData(FECUtil.java:245) at fiw.fcp.FECUtil.makeFECData(FECUtil.java:182) at fiw.core.jobs.FECBuilderJob.run(FECBuilderJob.java:83) at fiw.core.jobs.Job.run0(Job.java:132) at fiw.core.jobs.PooledThreadProducer$PooledThread.run(PooledThreadProducer.ja v a:97) The following is spewed on the Freenet java console window: java.io.IOException: Sent 0 bytes (27 of packet in notifyDone at freenet.node.states.FCP.NewFECEncodeSegment.sendChunk(NewFECEncodeSeg ment.java:293) at freenet.node.states.FCP.NewFECEncodeSegment.sendDataChunks(NewFECEnco deSegment.java:276) at freenet.node.states.FCP.NewFECEncodeSegment.received(NewFECEncodeSegm ent.java:95) at freenet.node.StateChain.received(StateChain.java:192) at freenet.node.StateChain.received(StateChain.java:68) at freenet.node.StandardMessageHandler$Ticket.run(StandardMessageHandler .java:235) at freenet.node.StandardMessageHandler$Ticket.received(StandardMessageHa ndler.java:173) at freenet.node.StandardMessageHandler$Ticket.access$100(StandardMessage Handler.java:125) at freenet.node.StandardMessageHandler.handle(StandardMessageHandler.jav a:73) at freenet.Ticker$Event.run(Ticker.java:323) at freenet.thread.QThreadFactory$QThread.run(QThreadFactory.java:235) I can't find anything relevant in freenet.log when set to Normal logging level - I can try Debug if this will help, but it eats valuable HDD space _really_ quickly :-(, so I'm not sure if it will be able to log enough information before I'll have to start rotating log files. I can't verify at the moment if this is only relevant for build 5032, or any previous new stable builds are affected as well. If any additional information would help - I'll be happy to provide it. Is this a bug with FIW/Freenet or am I doing something stupid? Regards, Victor Denisov. ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] 5032 FIW 0.07 - FEC Encoding problem?
the last time i've uploaded a splitfile is some months ago using fiw version 0.07.
the only occurence where setSoTimeout() is called is in fcp.FCPUtil.makeSocket():
public static Socket makeSocket() throws IOException {
Socket s = makeSocket0();
int soTimeout = Integer.parseInt
(Settings.inst.getProperty(tuning.sotimeout));
if (s != null soTimeout != 0) {
s.setSoTimeout(soTimeout);
}
return s;
}
reading the code i'd suggest the settings are read and if!=0 set, otherwise no socket
timeout should be set.
the default is set in core.option.GlobalOptions:
new Option(Socket Timeout (ms),
tuning.sotimeout,30,1, new IntOptionType(0)),
i'm currently short on time, so perhaps you should have a glimpse on the source
yourself or contact mihi to track this one down
Hmmm. Strange. This was the first thing I've thought, so I've tried setting
it to 30 minutes (actual FEC encoding takes ~ 12 mins on this machine) - no
luck, the error still happens.
Regards,
Victor Denisov.
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, November 20, 2003 2:34 PM
Subject: Re: [freenet-support] 5032 FIW 0.07 - FEC Encoding problem?
this is a FIW issue which is known for some time now but has never been
fixed
FIW sets the socket timeout for FCP connections to 5 minutes.
if a FCP connection is more than 5 minutes in use, FIW closes it therefore
and throws an SocketTimepoutException (well, java itself does it, but
nevertheless the connection gets closed and an exception is raised)
so any action which uses more than 5 minutes to complete is unable to
succeed!
as FEC encoding may take up to half an hour or more depending on your
machine power and the size of your splitfile, you are unable to upload the
file as FIW fucks up with its default settings
you might consider changing the
tuning.sotimeout=30
parameter in fiw.conf to something higher (30 milliseconds = 5*60*1000
ms = 5 minutes), or to 0 to disable the timeout
HTH
When I'm trying to upload a site containing a large file (~ 150 Mb) with
FIW
0.07, I get the following error message in FIW when generating FEC check
chunks:
[Error] unexpected error while building check chunks!
This gets written to FIW log:
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at java.io.FilterInputStream.read(Unknown Source)
at fiw.fcp.FCPUtil.readLine(FCPUtil.java:859)
at fiw.fcp.FECUtil.makeFECData(FECUtil.java:245)
at fiw.fcp.FECUtil.makeFECData(FECUtil.java:182)
at fiw.core.jobs.FECBuilderJob.run(FECBuilderJob.java:83)
at fiw.core.jobs.Job.run0(Job.java:132)
at
fiw.core.jobs.PooledThreadProducer$PooledThread.run(PooledThreadProducer.ja
v
a:97)
The following is spewed on the Freenet java console window:
java.io.IOException: Sent 0 bytes (27 of packet in notifyDone
at
freenet.node.states.FCP.NewFECEncodeSegment.sendChunk(NewFECEncodeSeg
ment.java:293)
at
freenet.node.states.FCP.NewFECEncodeSegment.sendDataChunks(NewFECEnco
deSegment.java:276)
at
freenet.node.states.FCP.NewFECEncodeSegment.received(NewFECEncodeSegm
ent.java:95)
at freenet.node.StateChain.received(StateChain.java:192)
at freenet.node.StateChain.received(StateChain.java:68)
at
freenet.node.StandardMessageHandler$Ticket.run(StandardMessageHandler
.java:235)
at
freenet.node.StandardMessageHandler$Ticket.received(StandardMessageHa
ndler.java:173)
at
freenet.node.StandardMessageHandler$Ticket.access$100(StandardMessage
Handler.java:125)
at
freenet.node.StandardMessageHandler.handle(StandardMessageHandler.jav
a:73)
at freenet.Ticker$Event.run(Ticker.java:323)
at
freenet.thread.QThreadFactory$QThread.run(QThreadFactory.java:235)
I can't find anything relevant in freenet.log when set to Normal
logging
level - I can try Debug if this will help, but it eats valuable HDD
space
_really_ quickly :-(, so I'm not sure if it will be able to log enough
information before I'll have to start rotating log files.
I can't verify at the moment if this is only relevant for build 5032, or
any
previous new stable builds are affected as well. If any additional
information would help - I'll be happy to provide it.
Is this a bug with FIW/Freenet or am I doing something stupid?
Regards,
Victor Denisov.
___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] 5032 FIW 0.07 - FEC Encoding problem?
I don't have a fix, but as a work around, try using another program like Fuqid or the Freenet browser interface to insert the large files, then copy the keys into the parse file for your site. The syntax for doing this is listed in FIW itself. Hmmm. Strange. This was the first thing I've thought, so I've tried setting it to 30 minutes (actual FEC encoding takes ~ 12 mins on this machine) - no luck, the error still happens. Regards, Victor Denisov. ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
[freenet-support] 5032 FIW 0.07 - FEC Encoding problem?
When I'm trying to upload a site containing a large file (~ 150 Mb) with FIW 0.07, I get the following error message in FIW when generating FEC check chunks: [Error] unexpected error while building check chunks! This gets written to FIW log: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at java.io.FilterInputStream.read(Unknown Source) at fiw.fcp.FCPUtil.readLine(FCPUtil.java:859) at fiw.fcp.FECUtil.makeFECData(FECUtil.java:245) at fiw.fcp.FECUtil.makeFECData(FECUtil.java:182) at fiw.core.jobs.FECBuilderJob.run(FECBuilderJob.java:83) at fiw.core.jobs.Job.run0(Job.java:132) at fiw.core.jobs.PooledThreadProducer$PooledThread.run(PooledThreadProducer.jav a:97) The following is spewed on the Freenet java console window: java.io.IOException: Sent 0 bytes (27 of packet in notifyDone at freenet.node.states.FCP.NewFECEncodeSegment.sendChunk(NewFECEncodeSeg ment.java:293) at freenet.node.states.FCP.NewFECEncodeSegment.sendDataChunks(NewFECEnco deSegment.java:276) at freenet.node.states.FCP.NewFECEncodeSegment.received(NewFECEncodeSegm ent.java:95) at freenet.node.StateChain.received(StateChain.java:192) at freenet.node.StateChain.received(StateChain.java:68) at freenet.node.StandardMessageHandler$Ticket.run(StandardMessageHandler .java:235) at freenet.node.StandardMessageHandler$Ticket.received(StandardMessageHa ndler.java:173) at freenet.node.StandardMessageHandler$Ticket.access$100(StandardMessage Handler.java:125) at freenet.node.StandardMessageHandler.handle(StandardMessageHandler.jav a:73) at freenet.Ticker$Event.run(Ticker.java:323) at freenet.thread.QThreadFactory$QThread.run(QThreadFactory.java:235) I can't find anything relevant in freenet.log when set to Normal logging level - I can try Debug if this will help, but it eats valuable HDD space _really_ quickly :-(, so I'm not sure if it will be able to log enough information before I'll have to start rotating log files. I can't verify at the moment if this is only relevant for build 5032, or any previous new stable builds are affected as well. If any additional information would help - I'll be happy to provide it. Is this a bug with FIW/Freenet or am I doing something stupid? Regards, Victor Denisov. ___ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
