|
Grex > Helpers > #123: Grex System Problems - Fall 2003 |  |
|
| Author |
Message |
| 25 new of 291 responses total. |
goose
|
|
response 125 of 291:
| 
Nov 9 18:52 UTC 2003 |
I'm not complaining about the volunteer staff, but sheesh, what is taking
NextGrex so long to put together?
|
jep
|
|
response 126 of 291:
|
Nov 9 20:08 UTC 2003 |
I asked that question in the coop conference on October 17. That led
to cross (who's on the staff) speculating the staff should set a goal
of 3 months. He seems to be assuming they have set such a goal, from
which I gather they've discussed it, and I hope they've even got
consensus on it. There has been no announcement, or discussion other
than what cross has said, as far as I've discerned. I lack confidence
that cross represents the staff and their commitment to the project.
|
davel
|
|
response 127 of 291:
|
Nov 9 20:20 UTC 2003 |
I saw the same behavior keesan reported in #114 - modem connected and then
just sat there. Mine also was on 5041. I can't telnet in, so I tried 3000,
and it let me in. Since there was no "this will take a few seconds" message,
I suspect the termserver port.
|
tpryan
|
|
response 128 of 291:
|
Nov 9 22:41 UTC 2003 |
ditto
|
tpryan
|
|
response 129 of 291:
|
Nov 9 22:45 UTC 2003 |
I think the question I wanted to ask was:
"Is NextGrex coming together at such a pace, that all voluneteers
are needed simultaniously to put it together?".
It is only being put together when the committee can all
be present to work on it?
|
remmers
|
|
response 130 of 291:
|
Nov 9 23:22 UTC 2003 |
The hardware is all assembled and working, and has been for some time.
The machine is on the internet. Staff can log in remotely and work
individually.
There's been extensive discussion of NextGrex in the Coop conference.
Read Item 11 if you're curious about the status. It's a long item --
recent discussion starts at resp:434.
|
cross
|
|
response 131 of 291:
|
Nov 10 00:19 UTC 2003 |
This response has been erased.
|
keesan
|
|
response 132 of 291:
|
Nov 10 01:08 UTC 2003 |
Thanks davel, I will try 3000 next time. I had assumed the trunk hunt would
at least work.
|
goose
|
|
response 133 of 291:
|
Nov 10 01:53 UTC 2003 |
Wow...the hardware was purchased in May and is not yet "Grex"? At this pace
it will be outdated before any of us mortals use it. I'll look at the current
discussion in Coop, thanks John.
For a computer group, Grex moves r-e-a-l-l-y s--l--o--w.....
|
gelinas
|
|
response 134 of 291:
|
Nov 10 02:32 UTC 2003 |
I stopped by the Pumpkin, but then realised I didn't have enough
information. I could, and did, at least disable the unworking modem,
so 5041 will currently ring open. I'll get the information I need and
stop back by the Pumpkin later this evening.
|
gelinas
|
|
response 135 of 291:
|
Nov 10 04:19 UTC 2003 |
I've now put a different modem (and thus terminal port) on 5041.
Please report here if problems continue.
FWIW, there is a note in the Pumpkin indicating the hunt order as of
12 Aug 1997. The numbers from that list that are still active, in order
of appearance, are:
761-3000
761-3411
761-3451
761-5041
|
aruba
|
|
response 136 of 291:
|
Nov 10 04:32 UTC 2003 |
The order they hunt in now should be 3000, 5041, 3411, 3451.
|
aruba
|
|
response 137 of 291:
|
Nov 10 15:19 UTC 2003 |
The load average was up around 50 a few minutes ago. Haven't seen Grex that
slow in a while.
|
keesan
|
|
response 138 of 291:
|
Nov 10 16:20 UTC 2003 |
I just dialed in on 3000. First try did not connect, had to redial.
I would be willing to wait a bit longer for the next grex if it could
including more reliable modems.
|
bhoward
|
|
response 139 of 291:
|
Nov 10 23:03 UTC 2003 |
Not me. Perhaps it is just the times-of-day when I sign into grex but
regularly encounter spikes of "slowness" that bring my conference buffer
editing sessions to a crawl.
I'm willing to queue up to get into the system but once in, I'd like to be
able to interact and respond at some approximation of normal typing speed.
|
pvn
|
|
response 140 of 291:
|
Nov 11 08:33 UTC 2003 |
Yo, bro! #3 son is headed to Iraq as the 25th Infantry is headed there
and he's part of the 'round out' from the NG. Call mom on account she's
pissed as she thought he'd only been on alert for N. Korea. You guys
don't call enough, and what, you never heard of email or what?
Hmm, May was it. Dual motherboard with SATA is pretty common now.
Are we suggesting that 'new' hardware is obsolete and more expensive
before it was even deployed?
|
tsty
|
|
response 141 of 291:
|
Nov 11 09:30 UTC 2003 |
/emote salutes son #3!
good luck and godspeed!
|
naftee
|
|
response 142 of 291:
|
Nov 11 16:54 UTC 2003 |
/d is full
/dev/sd7g 1971009 1773872 37 100% /d
|
gelinas
|
|
response 143 of 291:
|
Nov 11 21:12 UTC 2003 |
Thanks for the report; I'm working on it.
|
tod
|
|
response 144 of 291:
|
Nov 11 21:22 UTC 2003 |
This response has been erased.
|
gelinas
|
|
response 145 of 291:
|
Nov 11 21:28 UTC 2003 |
I made some progress, but I have to stop now. /d is at about 98%.
|
gull
|
|
response 146 of 291:
|
Nov 11 21:31 UTC 2003 |
Minor nagging problem: The logo for the Co-op conference home page in
Backtalk has been broken for a while now.
|
naftee
|
|
response 147 of 291:
|
Nov 11 22:44 UTC 2003 |
re 145 Thanks!
|
russ
|
|
response 148 of 291:
|
Nov 16 16:38 UTC 2003 |
Despite the fact that a number of good, full-speed-capable
modems were just freed up, at least one of the modems near
the top of the trunk hunt is stuck at the miserable transfer
speed of perhaps 610 bytes/sec when Grex can do at least 1300.
|
keesan
|
|
response 149 of 291:
|
Nov 16 16:46 UTC 2003 |
I got disconnected when I dialed 5041, but that happens often, especially when
writing emails with Pine. At this point I would choose faster and more
reliable modems over getting newgrex online sooner.
|