You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   200-224 
 225-249   250-274   275-299   300-324   325-349   350-374   375-399   400-424   417-441 
 442-466   467-491   492-516   517-541   542-566   567-591   592-616   617-641   642-666 
 667-691   692-716   717-741   742-766   767-791   792-816   817-841   842-866   867-870 
 
Author Message
25 new of 870 responses total.
cross
response 442 of 870: Mark Unseen   Jan 19 00:48 UTC 2005

This response has been erased.

russ
response 443 of 870: Mark Unseen   Jan 19 01:15 UTC 2005

Then why doesn't retry fix the problem with the hung connection?  I
can type things and see echo packets all the while.
cross
response 444 of 870: Mark Unseen   Jan 19 02:06 UTC 2005

This response has been erased.

gelinas
response 445 of 870: Mark Unseen   Jan 19 04:03 UTC 2005

Dan, what do you do on gryps?  Anything other than ssh on to grex?

I've not been doing anything strenuous on groupie, but it does seem responsive
when grex is not.

Sometimes, I've been able to open a new connection to grex while the old one
is hung.  Sometimes, I've seen one connection hang and another not.

I'm not convinced it's a problem affecting all machines on our network; 
I've insufficient evidence.

To those complaining: yes, staff is aware of the problem and is trying to
figure it out.  We simply don't have anything else to report. :(
keesan
response 446 of 870: Mark Unseen   Jan 19 04:41 UTC 2005

I am telnetted and grex is usable at the moment (for bbs, anyway).
keesan
response 447 of 870: Mark Unseen   Jan 19 04:50 UTC 2005

I just got my first mail in about two days here so perhaps things are fixed.
(I hope my answer got sent okay). There was about a 20 sec freezeup while I
was answering it but otherwise just the usual telnet lag.  (I have to slow
down my typing speed to about 2/3 usual).  
keesan
response 448 of 870: Mark Unseen   Jan 19 04:51 UTC 2005

Another mail just arrived
gelinas
response 449 of 870: Mark Unseen   Jan 19 04:51 UTC 2005

Re 426:  the "Do Not Delete" message is an artifact of Pine.  If you don't
use Pine, delete it.  If you do use Pine, you won't see it.
keesan
response 450 of 870: Mark Unseen   Jan 19 05:28 UTC 2005

Three more mails arrived - is grex cured?  I could also send mails out.
keesan
response 451 of 870: Mark Unseen   Jan 19 05:33 UTC 2005

Pine works and I think I replied to a mail, but a mail forwarded from here
elsewhere did not arrive.  I can now ssh elsewhere too.  (I am dialed in).
If someone fixed grex, thanks.  If not, let's hope it stays fixed for two more
weeks.
naftee
response 452 of 870: Mark Unseen   Jan 19 08:12 UTC 2005

GreX is fast and then locks.

That is all.
tsty
response 453 of 870: Mark Unseen   Jan 19 09:42 UTC 2005

grex is fast and fine as of this entry ... whatever was done - thankxx!
russ
response 454 of 870: Mark Unseen   Jan 19 12:21 UTC 2005

Yup, enough of the problem has been fixed to allow mail to flow again.
tsty
response 455 of 870: Mark Unseen   Jan 19 15:37 UTC 2005

oh, did i type too fast in #453 ....  bogged & idleded & disconnected
about 3 minutes later ... 
gull
response 456 of 870: Mark Unseen   Jan 19 23:11 UTC 2005

It seemed suspiciously like a path MTU discovery problem of some sort. 
Pings and such worked, but anything that used larger packets failed.
jor
response 457 of 870: Mark Unseen   Jan 19 23:12 UTC 2005

        
        right. number of bytes.
gull
response 458 of 870: Mark Unseen   Jan 19 23:50 UTC 2005

Yeah.  Initially I thought I was having a rerun of an MTU problem I used
to have on my own connection, but then I noticed every site I tried
except Grex was working fine.
russ
response 459 of 870: Mark Unseen   Jan 20 01:21 UTC 2005

The lag problem and the mail-delivery problem appear to have been
fixed completely.
naftee
response 460 of 870: Mark Unseen   Jan 20 03:38 UTC 2005

Whoa.
bru
response 461 of 870: Mark Unseen   Jan 20 06:28 UTC 2005

wanna bet?  took nearly 30 seconds to establish the telnet connection over
my eathernet from work.
jep
response 462 of 870: Mark Unseen   Jan 20 15:59 UTC 2005

The system is deadly slow again, both via putty and Backtalk.  I assume
someone is aware there is a problem, but there's very little information,
it5 seems, about what is being done about it, or if anything is being
done.  Any idea abuot what is causing the problem?
cross
response 463 of 870: Mark Unseen   Jan 20 18:43 UTC 2005

This response has been erased.

rcurl
response 464 of 870: Mark Unseen   Jan 20 19:11 UTC 2005

Still very slow.
richard
response 465 of 870: Mark Unseen   Jan 20 22:37 UTC 2005

BAcktalk is barely responding at all.  Half the time the pages don't load and
when they do it takes five minutes or more.  I couldn't even get to the agora
screen, I had to telnet in finally just to post this
gull
response 466 of 870: Mark Unseen   Jan 21 01:05 UTC 2005

How long will it be before we move to colo?  Is it really not worth even
trying to get the upstream problem resolved in the mean time?

Right now I'm even getting intermittent lag on the *dialin*.  This morning
dialin was giving me a 1-2 second delay for each character.
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   200-224 
 225-249   250-274   275-299   300-324   325-349   350-374   375-399   400-424   417-441 
 442-466   467-491   492-516   517-541   542-566   567-591   592-616   617-641   642-666 
 667-691   692-716   717-741   742-766   767-791   792-816   817-841   842-866   867-870 
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss