Some very very strange behaviors
[1/15] from: luca::truffarelli::it at: 24-Sep-2004 19:10
Hi all!
I got some VERY strange behaviors with Rebol on my WindowsXP.
First of all, the computer is a box that I use at work so it is installed
by someone else other than me. This mean that I know what is installed in
but I can't not be sure of it.
Second, the problems are rised with any kinf of connection to internet I
use. I tryed thru the proxy, thru a dial-up, thru my ADSL, .... So the
problems are not caused by some network problems.
The is some of the problems, be prepared to hear things that no men have
ever heard:
1) I can't download every rebol plugin applications. Someone load but
other don't.
Eg.:
http://www.rebol.net/plugin/demos/ LOAD
while
http://www.rebol.net/plugin/demos/rebtris.html DON'T LOAD
But this is just the last, and less significant, problem.
2) I open a rebol console (/core /view 1.2.1-1.2.47-1.2.48 is the same)
and write aa: read http://www.yahoo.com it read the page. Them if I write
it again it read the page again, and again and again and again and again
and again and again and again and again and STOP. After 9 hopes it doesn't
read the page no more. I can reproduce the problem how many time I want. I
jyst need to close the console and open it again. :-)
3) This is a bit complicated, but in few words I wrote a client/server
application. Every x minutes the server send a PING to the client to
verify it is there. After a random period of time the server send the PING
but if the client is on my computer is doesn't receive it. I traced it
thru tcpdump and I saw the the packet arrives but the 'wait doens't wake
up. This happen only if in the 'wait there is a 'time data type. It's
funny, do you agree?
I think it is enough. :-)
So I quite sure the problem is between my computer (or the TCP stack of my
computer) and Rebol (or Rebol like style to access the net). But want
could be the problem? Where can I investigate? It is too strange for me.
:-)
Please, write me something, a "Don't worry be happy" is enough. :-)
Thank you
[2/15] from: AJMartin::orcon::net::nz at: 25-Sep-2004 8:39
Hi, Luca.
You wrote:
> 2) I open a rebol console (/core /view 1.2.1-1.2.47-1.2.48 is the same)
> and write aa: read http://www.yahoo.com it read the page. Them if I write
> it again it read the page again, and again and again and again and again
> and again and again and again and again and STOP. After 9 hopes it doesn't
> read the page no more. I can reproduce the problem how many time I want. I
> jyst need to close the console and open it again. :-)
I tried it:
>> write %Yahoo.html read http://www.yahoo.com
>> write %Yahoo.html read http://www.yahoo.com
>> write %Yahoo.html read http://www.yahoo.com
>> Rebol/version
== 1.2.8.3.1
....and got no problems with three attempts. Perhaps www.yahoo.com is
blocking your access because you've read it so many times?
I can't help with your other points.
--
Andrew J Martin
ICQ: 26227169
http://www.rebol.it/Valley/
http://valley.orcon.net.nz/
http://valley.150m.com/
[3/15] from: luca::truffarelli::it at: 25-Sep-2004 15:06
> Hi, Luca.
> You wrote:
<<quoted lines omitted: 15>>
> ...and got no problems with three attempts. Perhaps www.yahoo.com is
> blocking your access because you've read it so many times?
I think not, because I have the same result reading other addresses.
[4/15] from: amicom::sonic::net at: 26-Sep-2004 23:00
Try reinstalling the TCP stack on your XP machine. Sounds like weirdness
I've encountered before that can only be fixed by doing this.
Bohdan "Bo" Lechnowsky
Lechnowsky Technical Consulting
At 03:06 PM 9/25/04 +0200, you wrote:
[5/15] from: luca::truffarelli::it at: 27-Sep-2004 14:59
Thank you Bo for you answer.
I tryed the
netsh int ip reset c:\ipreset.log
because the TCP/IP under Xp could not be uninstalled.
It does a lot of work but I got no results. After 10 or 12 attempt to read
a web page the 'read always timeout. :-(
[6/15] from: amicom::sonic::net at: 27-Sep-2004 22:07
Luca,
If you have a router on your local network, check to make sure that it is
not stopping multiple requests. Also, some anti-virus software like McAfee
and Norton Antivirus have settings set by default to block what appear to
be malicious scripts. Also, your ISP may also be performing some kind of
filtering or blocking. I would check all of these.
If you cannot reinstall your TCP stack on XP, you may need to log in as
administrator or a user with administrator rights. If you restart your
machine in safe mode (by pressing F8 before you get to the Windows XP
splash screen during boot up), you can log in as administrator there,
although I've never tried to reinstall the TCP stack in safe mode (it may
not be allowed, even as administrator).
Good luck!
Bohdan "Bo" Lechnowsky
Lechnowsky Technical Consulting
At 02:59 PM 9/27/04 +0200, you wrote:
[7/15] from: lmecir::mbox::vol::cz at: 28-Sep-2004 8:08
Hi Rebols, I am back from Collaboration Conference and excited
Luca Truffarelli napsal(a):
>while
>http://www.rebol.net/plugin/demos/rebtris.html DON'T LOAD
>
what is meant by "don't load" in this case? READ works pretty well, and
it is a HTML page.
>2) I open a rebol console (/core /view 1.2.1-1.2.47-1.2.48 is the same)
>and write aa: read http://www.yahoo.com it read the page. Them if I write
<<quoted lines omitted: 4>>
>I
>jyst need to close the console and open it again. :-)
this is unbelievable, it simply works for me here without any glitches
(I didn't look at the PING issue yet...)
-L
[8/15] from: luca:truffarelli:it at: 28-Sep-2004 10:00
> If you have a router on your local network, check to make sure that it is
> not stopping multiple requests. Also, some anti-virus software like
> McAfee
> and Norton Antivirus have settings set by default to block what appear to
> be malicious scripts. Also, your ISP may also be performing some kind of
> filtering or blocking. I would check all of these.
I have the same problem connecting thru my company Proxy, thru ADSL, thru
dialup.
Then I also tryed to disable the local firewall and the Antivirus programms.
> If you cannot reinstall your TCP stack on XP, you may need to log in as
> administrator or a user with administrator rights. If you restart your
> machine in safe mode (by pressing F8 before you get to the Windows XP
> splash screen during boot up), you can log in as administrator there,
> although I've never tried to reinstall the TCP stack in safe mode (it may
> not be allowed, even as administrator).
I read that in XP the TCP could not be reinstalled because it is core
component.
Anyway I just discovered I trick that let it work... but it only
complicate the problem:
If I set "trace/net true" before starting the 'read it never stop with a
timeout. 8-|
While if I reproduce the problem (executing the 'read 10 times without the
trace/net) and then set "trace/net true" it stops there:
>> aa: read http://www.yahoo.com
URL Parse: none none www.yahoo.com none none none
Net-log: ["Opening" "tcp" "for" "HTTP"]
connecting to: www.yahoo.com
Aaaaaaaaaaaaaaaah! ...ehm ehm... excuse me :-)
[9/15] from: luca::truffarelli::it at: 28-Sep-2004 10:36
> Hi Rebols, I am back from Collaboration Conference and excited
I heard that it was a real success, I hope to see some videos soon!
>>while
>>http://www.rebol.net/plugin/demos/rebtris.html DON'T LOAD
>>
>>
> what is meant by "don't load" in this case? READ works pretty well, and
> it is a HTML page.
This problem is solved, it was a proxy problem, I think a known problem.
>>2) I open a rebol console (/core /view 1.2.1-1.2.47-1.2.48 is the same)
>>and write aa: read http://www.yahoo.com it read the page. Them if I write
<<quoted lines omitted: 9>>
>>
> this is unbelievable, it simply works for me here without any glitches
Yes "unbelievable" is the right term. :-)
Since when I use Rebol I have never had this kind of problems, but
recently I changed my computer I think the problem is it.
But today I discovered that setting "trace/net true" the 'read works well
throwing no timeouts. I alread explained it in another mail.
Excuse me for these "strange" questions but I assure you that I managed a
lot before write here.
[10/15] from: antonr::lexicon::net at: 29-Sep-2004 21:58
Hi Luca,
Sounds like you found a workaround to the problem
(using trace/net on).
But did you determine what the problem was exactly ?
Was the proxy on your machine or at your isp ?
Anton.
[11/15] from: luca:truffarelli:it at: 29-Sep-2004 18:50
> Hi Luca,
>
> Sounds like you found a workaround to the problem
> (using trace/net on).
It is not a workaround, I can't keep the switch trace on in each
application. :-)
> But did you determine what the problem was exactly ?
No. :-(
> Was the proxy on your machine or at your isp ?
The problem is something between Rebol and that computer.
If I connect from home thru my home computer I get the same problem but if
I try to read from the home computer it read with no problems.
So it is not a network related problem, but something in the TCP stack of
my thinkpad that Rebol doesn't like. I disabled all the firewall,
antivirus, proxy client, ... It is only Windows (or something I don't
discovered yet) and Rebol. :-(
[12/15] from: antonr:lexicon at: 30-Sep-2004 17:11
It can be made into a workaround :)
if you wrap your read like this:
-----------------------------
rebol/options/quiet: on
trace/net on
orig-print: :print
orig-prin: :prin
print: none
prin: none
read http://www.yahoo.com
print: :orig-print
prin: :orig-prin
trace/net off
-----------------------------
net-utils/net-log is the one which produces all the output
to the console, and it uses PRIN and PRINT (via PROBE).
(mold get in net-utils 'net-log) ; <- have a look.
I'd like to know if you get any more strangeness using
this technique.
Anton.
[13/15] from: luca:truffarelli:it at: 30-Sep-2004 10:20
It is really interesting and I learned something more. :-)
Unfortunatly I discovered that the "trace/net workaround" just move the
number of success 'read from 10 to 80, and at the end it return a timeout,
so there is still something wrong.
Then, I really like to understand the real reason.
*** Thru tcpdump I saw that the packets arrive but Rebol is not notified
of them. Anyone have an idea to try to understand who prevent them to
reach Rebol, or what in Rebol stops them?
[14/15] from: antonr:lexicon at: 30-Sep-2004 19:00
Mmm... worth a try.
Perhaps playing around with:
system/schemes/http/cache-size
might help.
Try setting it to 0, and see if it affects
the results.
Anton.
[15/15] from: luca::truffarelli::it at: 30-Sep-2004 11:16
> Mmm... worth a try.
I tryed it, but it moved the number of success 'read from 10 to 80. :-(
> Perhaps playing around with:
>
> system/schemes/http/cache-size
>
> might help.
> Try setting it to 0, and see if it affects
> the results.
Tryed, no result.
I think it is something at a lower level. In my opinion the client/server
problem, I wrote about, is related to this one.
There, a port opened in /no-wait stops receiving the packets. The 'wait
doesn't wake-up.
The missing packets are sent from the server and received from the box, I
saw them thru tcpdump, but Rebol is not notified.
It is similar to the 'read problem. The request is sent and the answer
arrive but Rebol is not notified and after a few it return a timeout.
Notes
- Quoted lines have been omitted from some messages.
View the message alone to see the lines that have been omitted