|
Grex > Helpers > #138: Grex System Problems - Winter 2004/2005 |  |
|
| Author |
Message |
| 25 new of 870 responses total. |
bru
|
|
response 461 of 870:
| 
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:
|
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:
|
Jan 20 18:43 UTC 2005 |
This response has been erased.
|
rcurl
|
|
response 464 of 870:
|
Jan 20 19:11 UTC 2005 |
Still very slow.
|
richard
|
|
response 465 of 870:
|
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:
|
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.
|
rksjr
|
|
response 467 of 870:
|
Jan 21 03:07 UTC 2005 |
Re. #463 & #466, postings by cross and gull, referring to "a problem with
an upstream ISP":
Does "a problem with an upstream ISP" mean: unusual use or misuse of the
dsl service by some other customer of the service in such a way as to
limit Grex' normal use of the service?
|
keesan
|
|
response 468 of 870:
|
Jan 21 03:09 UTC 2005 |
What does an upstream ISP have to do with slow dialin, which I just had for
the past 10 minutes (wait 20 sec to see the cursor move)?
If the DSL line is the problem can we cancel wtihout having to pay for the
rest of the contract?
|
cross
|
|
response 469 of 870:
|
Jan 21 03:43 UTC 2005 |
This response has been erased.
|
richard
|
|
response 470 of 870:
|
Jan 21 04:26 UTC 2005 |
#469...so you are saying its just a *coincidence* that these major lag issues
occurred with in days after grex moving to the new server? The timing has
to make you wonder. maybe grex would be better off back on the old server
for the time being. maybe nextgrex can't handle its job
|
cross
|
|
response 471 of 870:
|
Jan 21 05:00 UTC 2005 |
This response has been erased.
|
russ
|
|
response 472 of 870:
|
Jan 21 05:01 UTC 2005 |
Conditions have deteriorated the point that mail delivery seems to
have halted some time Thursday morning. Lag is bad now and I jave
had to drop one connection because it was stuck.
|
keesan
|
|
response 473 of 870:
|
Jan 21 05:02 UTC 2005 |
Dialed in. Load average 028. It just took me three tries to type that number
and I have to wait 10 sec or so to see what I typed appear onscreen.
0.28. Sometimes things go full speed, sometimes a great deal of lag.
No mail came in recently (for a few hours). How would ISP problems affect
dialins?
|
gelinas
|
|
response 474 of 870:
|
Jan 21 06:11 UTC 2005 |
(richard, we've been dealing with network problems since last summer, long
before the move to the new machine.)
|
mcnally
|
|
response 475 of 870:
|
Jan 21 07:00 UTC 2005 |
re #474:
> we've been dealing with network problems since last summer
the recent problems seem qualitatively different than the ongoing outages
that were occurring previously.
re #470:
> maybe grex would be better off back on the old server for the time being.
That would take a major amount of work to move back to the old server
and then another major amount of work when the new server was judged
to be ready for prime time. Worse, one might complete all that work
only to find that the source of the problem lay elsewhere, as seems to
be the current prevailing opinion among staff.
|
richard
|
|
response 476 of 870:
|
Jan 21 07:17 UTC 2005 |
#474...gelinas, what mcnally said...the problems have clearly gotten worse,
much worse, since the switch to the new server. I understand the work that
would be involved in going back to the old server, but how else can the new
server's role in the current problems be conclusively proven?
|
rksjr
|
|
response 477 of 870:
|
Jan 21 07:41 UTC 2005 |
Regarding the particular variety of intermittent screen freezing (if there
are different kinds) that we have been observing recently, when I'm logged
onto Grex and my screen happens to be frozen, are all the other screens of
other logged on Grex users also frozen <<at that moment>>, or at any given
time are some Grex screens frozen and some not frozen?
|
mary
|
|
response 478 of 870:
|
Jan 21 11:43 UTC 2005 |
Please have some patience, folks. Please. There are multiple
reasons for the problems Grex is having and staff is as anxious to
get them under control as everyone else.
It's my undertanding the machine is moving to co-lo this weekend, if
at all possible. Some of the lag will be helped when robocop is up
and working and Jan is working on that. And the setting are still
being fine-tuned but doing so under the current lag makes that all
the more difficult. Staff is not ignoring Grex right now, really,
they're not. Let's try to be supportive - especially now, when they
have so much to do.
I suppose we could go to our DSL folks and insist it's their fault
and consider not paying the bill, but first we'd have to be sure
it's their problem, entirely. I'd rather we simply work on a
solution and get Grex working right.
|
russ
|
|
response 479 of 870:
|
Jan 21 13:36 UTC 2005 |
Re #477: Some are frozen and some are ot frozen. (Speaking from
experience here.)
|
russ
|
|
response 480 of 870:
|
Jan 21 13:38 UTC 2005 |
In other news, there appears to have been no mail all of
yesterday afternoon, evening and last night.
|
keesan
|
|
response 481 of 870:
|
Jan 21 15:13 UTC 2005 |
And this morning.
|
keesan
|
|
response 482 of 870:
|
Jan 21 15:21 UTC 2005 |
The problem before was frequent sudden freezeups for mayb 30 seconds while
telnetted. Right now (I am dialed in) things are okay for a minute or so then
I will type something and wait 5 sec for half a line to appear, then after
5 sec another chunk appears A 5-10 character string will appear, then in 5
sec a few more characters, and then suddenly it all works okay again. This
is entirely different from before. Is there some way to hook up any other
grex-type setup to the same DSL modem and phone line to see if the problem
carries over? (An httpd server? Telnetd server? Do I have the terms
right?). At this point nobody would be terribly inconvenienced (more than
currently) if grex were off the air for an hour or two to do such a test.
Can some other computer (say a laptop) be plugged into the serial port via
a serial cable to see if it can telnet to grex? Or work as a dumb terminal?
(I even had this working on my little linux setup once, both ways).
|
naftee
|
|
response 483 of 870:
|
Jan 21 16:23 UTC 2005 |
It's funny how m-net's bbs is getting more activity.
|
cross
|
|
response 484 of 870:
|
Jan 21 19:14 UTC 2005 |
This response has been erased.
|
rksjr
|
|
response 485 of 870:
|
Jan 21 22:05 UTC 2005 |
Re. #479 in which russ wrote:
Re #477: Some are frozen and some are ot frozen. (Speaking
from experience here.)
If not all screens are frozen at the same time, then would it be possible
for an online user whose screen is <<not>> frozen to run a Unix script
that would unfreeze the screen of another online user whose screen <<is>>
frozen?
|