You are not logged in. Login Now
 0-24   25-49   50-71        
 
Author Message
25 new of 71 responses total.
aruba
response 25 of 71: Mark Unseen   Nov 27 17:02 UTC 2005

Over 6 and a half days now.  Looks like it was a memory problem all right,
or at least a problem accessing the memory.
cross
response 26 of 71: Mark Unseen   Nov 27 17:37 UTC 2005

This response has been erased.

keesan
response 27 of 71: Mark Unseen   Nov 27 21:59 UTC 2005

COuld it be that the motherboard would crash no matter which DIMM you put in
the second or third slot?
steve
response 28 of 71: Mark Unseen   Nov 27 22:40 UTC 2005

   Yes.  I don't think the memory per se is bad. I've been thinking along
the lines of Dan's thoughts.  I have a call into Crucial about the best
way to get the memory back to them for testing.  Given the hassles of 
getting to Grex and taking it down for that kind of stuff, if I can get
the memory out to them and back in a week or so, I think we can live 
with that.  With the current usage patterns on Grex 512M works pretty
well.
naftee
response 29 of 71: Mark Unseen   Nov 28 07:07 UTC 2005

hey cross.  they did it without you.
 :( :(
cross
response 30 of 71: Mark Unseen   Nov 28 17:48 UTC 2005

This response has been erased.

tod
response 31 of 71: Mark Unseen   Nov 28 19:34 UTC 2005

Your hips are too wide!
happyboy
response 32 of 71: Mark Unseen   Nov 28 22:56 UTC 2005

a pear-like kim il sung physique?
cross
response 33 of 71: Mark Unseen   Nov 29 01:50 UTC 2005

This response has been erased.

tod
response 34 of 71: Mark Unseen   Nov 29 02:57 UTC 2005

http://media.portland.indymedia.org/images/2004/02/281656.jpg
tsty
response 35 of 71: Mark Unseen   Nov 30 06:14 UTC 2005

geeeeze, tod, where do you find all that shit?
  
=======<<....>>===================
  

#3.13 Rane Curl (rcurl) Thu, Nov 10, 2005 (11:29):
 Just so it is conserved...

#3.14 Jan Wolter (janc) Sat, Nov 19, 2005 (13:58):
 Well, we are up on OpenBSD 3.8.  The process did not live up to my ideals,


nine damn days and not a whisper of what was to happen? mary had to 
send me email (elsewhere) to an hvcn site that *hid* the grex 
situation?
  
i';ll bet there are a whole buncha folks who are pissed as hell at the
nine days and no notice (well maybe there was someting hidden in the
last day or so of motd)
  
point me to the ITEM in agora that discussed the *downtime* anticipated?
  
not everyone reads coop.cf with the same regulatiry as agora.cf.
  
  
item #94 is a post-motrem .. wehre was teh damn PRE-mortem ?????
  
hellz=-bellz ... what a fsckup (and no, i'm not tallking about 
/var/spool/mail - a separate problem).
albaugh
response 36 of 71: Mark Unseen   Nov 30 06:49 UTC 2005

Put the AE unit back in and see if it fails as HAL predicted...
remmers
response 37 of 71: Mark Unseen   Nov 30 13:14 UTC 2005

Re #35:  Well, there was an MOTD announcement, if that counts as a
"whisper".  Unfortunately, the *amount* of downtime was not anticipated,
hence no extensive "pre-mortem".  Hardware problems were discovered
during the upgrade, which prolonged the downtime significantly and
unexpectedly.

The HVCN "Grex status page" has been around for years but could probably
be better publicized.  I'll put a pointer to it in the motd, suggesting
that users bookmark it in their browsers.

http://www.hvcn.org/info/grex/
jep
response 38 of 71: Mark Unseen   Nov 30 15:34 UTC 2005

I've found the HVCN status page is often inaccurate.  I don't even 
bother with it any more.

What's worse is there's no way to find it when it's needed.  How about 
putting the link in the login for the M-Net Grex conference?  (Which is 
where I usually go to find out why Grex is down, when it's down.)
jep
response 39 of 71: Mark Unseen   Nov 30 15:36 UTC 2005

The status page currently says this:

---
Fri Nov 18 21:33:44 EST 2005
Grex is UP!
---

Is there some way to have it updated periodically by an automatic 
process (and the date/time updated as well)?  
keesan
response 40 of 71: Mark Unseen   Nov 30 20:16 UTC 2005

I search on 'grex is down' to find that page.  And when it is wrong (99% of
the time that grex is down the page is not correct) I email staff to fix the
page.  Used to be temporary outages that fixed themselves.
I am delighted that grex is still up and we don't need the page right now.
steve
response 41 of 71: Mark Unseen   Nov 30 20:58 UTC 2005

  So am I. ;-)
remmers
response 42 of 71: Mark Unseen   Nov 30 21:45 UTC 2005

When Grex was crashing a lot, the page was often out of sync with
reality, since it has to be updated manually and there's a lag between
when the system crashes and when someone able to edit the page notices
it.  In recent months I tried to keep it as current as I could, but
there are limits.  If the system crashed at 2:00am the lag was apt to be
many hours.

The real value of a page like that is not posting up to the minute
up/down status (anybody who cares if Grex is up or down is probably able
to figure that out for themselves by trying to log in, DUH), but rather
as a place to post explanatory messages during prolonged downtime. 
True, there's a Grex conference on M-Net for that purpose, but a person
shouldn't have to maintain an account on another system to keep current
on what's happening with Grex.
remmers
response 43 of 71: Mark Unseen   Nov 30 21:55 UTC 2005

The Grex Board of Directors election runs December 1 through December
15, midnight to midnight (EST).  Anybody with a Grex account can vote,
but only the votes of members in good standing will be counted in
determining the outcome.

To vote, or to get more information about the election, type 'vote' at a
Unix shell prompt or '!vote' at most other prompts.  Or on the web, go
to https://grex.org/cgi-bin/pw/voting-booth .

(http and https both work, but the more secure https is recommended,
since you have to authenticate with your Grex id and password.)

If you try to vote outside the December 1-15 timeframe, you'll get a
terse message to the effect that the polls are closed.

It appears that the election is somewhat academic this year, as there
are just as many candidates as open slots, so everyone running is
guaranteed to be elected.  Nonetheless, the bylaws say there shall be an
election, so an election there shall be.  This is also the first
opportunity for me to test the vote program in an OpenBSD environment.
rcurl
response 44 of 71: Mark Unseen   Dec 1 00:46 UTC 2005

No "write ins" allowed?
tsty
response 45 of 71: Mark Unseen   Dec 1 05:56 UTC 2005

is bit-stuffing allowed this year?
bhelliom
response 46 of 71: Mark Unseen   Dec 1 06:05 UTC 2005

Try the cornbread variety.
other
response 47 of 71: Mark Unseen   Dec 1 16:45 UTC 2005

I'd like to suggest that the Grex status page be modified to supply some
history as well as the current status.  It might be useful just for
getting a sense of what the system has been experinecing over time and
in a pretty condensed format.
remmers
response 48 of 71: Mark Unseen   Dec 2 11:29 UTC 2005

In other words, a Grex Status Blog.  Not a bad idea, actually.
bhoward
response 49 of 71: Mark Unseen   Dec 17 00:56 UTC 2005

Weird.  

There is no one else on the system right now.  I don't think that's
ever happened to me before on grex except during one of the system
recoveries after a crash...

;: grex; pwho
User                             Started          Channel
;: grex; f
Login    Name                 Tty  Idle  Login Time   Office     Office Phone
bhoward  Bruce Howard          p0     -     Fri 19:43 Tokyo     
bhoward
;: grex; who
bhoward  ttyp0    Dec 16 19:43   (123.2.111.219.st.bbexcite.jp)
;: grex; 

 0-24   25-49   50-71        
Response Not Possible: You are Not Logged In
 

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