You are not logged in. Login Now
 0-24   25-49   50-74   75-99   89-113   114-138   139-163   164-188   189-213 
 214-238   239-263   264-286        
 
Author Message
25 new of 286 responses total.
tpryan
response 114 of 286: Mark Unseen   Aug 14 19:39 UTC 2004

        Any reason for not being able to phone in Friday and early
today, while the system has been up for 26 days?
gelinas
response 115 of 286: Mark Unseen   Aug 16 03:01 UTC 2004

Looks like we had someone using up lots of resources.  A staff member was 
able to visit the Pumpkin and kill off the user's processes.
mary
response 116 of 286: Mark Unseen   Aug 16 10:42 UTC 2004

Thank you, staff, for Grex.
slynne
response 117 of 286: Mark Unseen   Aug 16 12:48 UTC 2004

Yay staff!
jor
response 118 of 286: Mark Unseen   Aug 16 18:43 UTC 2004

        email: negative function?

rcurl
response 119 of 286: Mark Unseen   Aug 17 21:39 UTC 2004

I get the following message when logging in using ssh-1 from Terminal in  Mac
OS 10.3.2

Warning: Server lies about size of server public key: actual size is 767 bits
vs. announced 768.
Warning: This may be due to an old implementation of ssh.

The connection works OK thereafter, so what is the significance of this
warning?
jor
response 120 of 286: Mark Unseen   Aug 17 22:30 UTC 2004

        1 bit
cross
response 121 of 286: Mark Unseen   Aug 18 00:15 UTC 2004

This response has been erased.

tsty
response 122 of 286: Mark Unseen   Aug 18 03:38 UTC 2004

  
   grex is a spammer, it says here:
  
   REALLY need this fixed,   pp ll ee aa ss ee !!
  
*******  See http://spamblock.outblaze.com/216.93.104.34  <<<<<<<
  
from:
  
The original message was received at Tue, 17 Aug 2004 23:12:48 -0400
from YYYyyy@localhost

   ----- The following addresses had delivery problems -----
XXXXXxxxxxx@lycos.com  (unrecoverable error)

   ----- Transcript of session follows -----
... while talking to lycos-com.mr.outblaze.com.:
>>> RCPT To:<XXXXxxxx@lycos.com>
<<< 554 EMail from mailserver at 216.93.104.34 is refused. 

*******  See http://spamblock.outblaze.com/216.93.104.34  <<<<<<<

554 XXXXxxxx@lycos.com... Service unavailable

   ----- Original message follows -----

--XAA22521.1092798775/grex.cyberspace.org
Content-Type: message/rfc822

 /cry
gull
response 123 of 286: Mark Unseen   Aug 19 13:56 UTC 2004

From Outblaze's webpage:

"This listing indicates that the mailserver you are sending our users
mail from is a "Direct Spam Source" - that is, it has been blocked
locally by our administrators as a result of spam coming in from that
server to our users.

"Please have your ISP or systems administrator contact us at
postmaster@outblaze.com regarding this issue."
blaise
response 124 of 286: Mark Unseen   Aug 19 20:11 UTC 2004

The TTY queue is hosed, as is part of spring agora.
davel
response 125 of 286: Mark Unseen   Aug 27 16:13 UTC 2004

/tmp needs to have its permissions corrected.
mcnally
response 126 of 286: Mark Unseen   Aug 27 16:23 UTC 2004

 It sure does..
tpryan
response 127 of 286: Mark Unseen   Aug 27 16:24 UTC 2004

        I tried to get my mail, I got permission denied.  An aftereffect
of catching up on the mail?
like /tmp/Rxa06999: permission denied.
kip
response 128 of 286: Mark Unseen   Aug 27 16:30 UTC 2004

Okay, I believe I have /tmp permissioned correctly now.  I'm still a little
groggy, so holler if that's not it.
gull
response 129 of 286: Mark Unseen   Aug 27 17:06 UTC 2004

I crashed Backtalk just now by hiting the 'Next Conf' button.  I didn't
copy the whole error (I assume it's logged somewhere) but here's the
first part.  Looks like there's a permission problem.

ERROR: Could not open item file /bbs/agora49/_49 - Permission denied
executing "conf_new" on line 63 of pistachio/confhome.bt

Version: Backtalk version 1.2.24

Stack:
(<HTML><HEAD>\n<BASE HREF=")
(http://www.cyberspace.org/cgi-bin/pw/backtalk)
(/)
(pistachio/)
(confhome">\n)
MARK[0]
janc
response 130 of 286: Mark Unseen   Aug 27 17:20 UTC 2004

Yeah, there were some problems restoring agora49 (the previous agora to this
one).  A lot of it's files are munged.
albaugh
response 131 of 286: Mark Unseen   Aug 27 17:26 UTC 2004

I realize that grex has just gotten back "on the air".  But could someone give
us the Reader's Digest version of what happened to grex?  What was done to
fix it?  Why was it so hard?  Is this likely to repeat?  Whether or not the
same thing could happen on Next Grex?
albaugh
response 132 of 286: Mark Unseen   Aug 27 17:27 UTC 2004

With the problems that grex experienced, would there have been any way to
display some terse "system down because X" + auto-logout during connection
via telnet or dialup?
gregb
response 133 of 286: Mark Unseen   Aug 27 18:08 UTC 2004

Re. 131:  Would U like fries with that order?  B-)
albaugh
response 134 of 286: Mark Unseen   Aug 27 18:10 UTC 2004

Onion rings & a chocolate shake, please!  :-)
dpc
response 135 of 286: Mark Unseen   Aug 27 18:29 UTC 2004

I'd also like to know what happened.  This "disk disaster" ranks with
the accidental destruction of the password file (and its hand-rebuilding
by Marcus) several years ago.
janc
response 136 of 286: Mark Unseen   Aug 27 18:37 UTC 2004

Here's what I know:

  Grex's disk drive zero died.  This disk is used to boot the system, and
  contains most of the operating system (root, /usr, /usr/local) and the
  bbs data (/bbs).  It was still partially working, but not enough to
  boot the system.

  Our last tape backup was many months old.  I forgot how many, but way too
  many.

  STeve and Kip did nearly all the work restoring things.  I was on vacation
  when this started and didn't get involved till late and then only in
  limited ways.

  STeve and Kip's initial problem was that you can't build a new disk on
  a machine that you can't boot.  So they're plan was to take Grex's tape
  drive to one of the machines at Kip's workplace, and build a new boot
  disk for Grex from the backup tape there.  However, they didn't have
  the latest backup tape, which (appropriately) was not stored on site.
  So they got the tape drive hooked up, and discovered that they couldn't
  read the much older tape backups that they had brought from the pumpkin.

  Later, Joe passed the latest backup tape to STeve.

  I came home from vacation, and spent a little time in the pumpkin.  Since
  I did much of the original building of the current Grex system, I
  remembered that we had a CD-drive for Grex (standard ones won't work
  with SunOS) and a 4.1.4 distribution CD which can be booted.  I hooked
  this up and figured out how to boot from the CDrom and documented this.
  Booting from the CDrom gives you an extremely limited set of tools. It
  looked to me to be too limited to actually do anything useful, plus I
  had neither the tape drive, nor the backup tape, so I left things at that.

  Kip and STeve again got together, with tape drive and backup tape.  They
  actually managed to figure out how to do a restore when booted from the
  CDrom.  (I'd still like to know how they did that.)  However, they
  discovered that most of the spare disk drives in the pumpkin were
  unusuable.  Some are differential drives.  Some are too small.  The
  only viable candidates were four 4Gig Conner drives.  They tried two
  of these and found that both were defective.  (I had tried using one
  of these years ago and found it didn't work, but they didn't know that).

  When I saw their emailed report the next day, I went and searched my
  house for some other disk drives.  When we had started putting together
  the new Grex, but didn't have drives yet, I had borrowed some drives from
  the pumpkin that I thought I could use temporarily.  These were 4Gig
  Seagate drives, which had previously been used on a development system
  that we ran for a while called "grease".  I never ended up using them on
  the NextGrex project, and couldn't really remember what I'd done with them.
  I found them in my garage and returned them to the pumpkin.

  STeve and Kip did another late night session, restoring the backups of
  root, /usr, and /usr/local onto one of the Seagate disks.  Years ago,
  STeve had set up a cron process that backed up the /etc/passwd file and
  related files to various other disks periodically, so they had a current
  copy of that.  However, he had not backed up /etc/group or the system
  mail aliases, so new versions of those have to be built.  There is
  probably more work to do updating things that had changed since the last
  backup, but not that much has.

  I believe the got /bbs by reading off the dead drive.  Mostly the /bbs
  partition of the old drive was still readable, but there seems to have been
  some damage.  Items 19 through 58 in oldagora (agora49) where trashed.
  I think someone said they had an offsite backup of this though, so we may
  be able to restore those.

  Overall, we took way too long to get this job done.  We repeatedly allowed
  ourselves to fall into resource deadlocks - first STeve and Kip couldn't
  do much because Joe had the backup tape, then I couldn't do much because
  STeve and Kip had the backup tape and tape drive respectively, then STeve
  and Kip couldn't do much because I had the only good disk drives.  Each
  time STeve and Kip's work got blocked, it took them some time to be able
  to get together again - they both have very busy schedules.

  I think that part of the problem is that knowledge of these old Sun systems
  is thinly scattered.  STeve and Kip are experienced system administrators,
  but I doubt either has done much SunOS work for years.  I'm not a system
  administrator at all, and my knowledge about this stuff is very spotty, but
  I did do a lot of the "recent" work on Grex, so I know more about what
  CD drives and disk drives and bootable CD's we have.  I don't think any
  one of us knows enough to be able to readily do this kind of job on our
  own.  This means that we have to work together on jobs like this, and
  that slows things down, as it is hard to coordinate among us.  Hopefully
  this will be less of an issue with the new machine and operating system
  which are better known to more people.
albaugh
response 137 of 286: Mark Unseen   Aug 27 18:51 UTC 2004

Thanks very much to everyone who helped with the restoration, in any way!

It sounds like this is the first time this has happened to grex.  It probably
shouldn't happen again.  It shouldn't happen any more frequently on Next Grex,
hopefully much less.  And if it did, Next Grex should be easier to recover
from.  Is this a correct assessment?
mary
response 138 of 286: Mark Unseen   Aug 27 22:10 UTC 2004

A huge thank you to Kip, STeve and Jan.  While the rest of us
were missing Grex you folks were spending hours of your time 
thrashing though problem after problem.  You are our heroes.
 0-24   25-49   50-74   75-99   89-113   114-138   139-163   164-188   189-213 
 214-238   239-263   264-286        
Response Not Possible: You are Not Logged In
 

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