You are not logged in. Login Now
 0-16   17-41   42-66   67-91   92-116   117-141   142-166   167-191   192-216 
 217-223          
 
Author Message
cfadm
Grex System Problems - Fall 2015/Winter 2016 Mark Unseen   Dec 31 16:42 UTC 2015

This item is for system problems.  If something on Grex isn't working
right (weird behavior from a program, etc.), this is the place to
announce it.  Except for security holes.  If you find a hole in system
security, mail information about it directly to "staff".
223 responses total.
walkman
response 1 of 223: Mark Unseen   Jan 28 12:40 UTC 2016

My browser is telling me grex is unsafe. I told it that slynne and zulu
are  gone but it insisted that I proceed with caution. 
cross
response 2 of 223: Mark Unseen   Jan 28 13:10 UTC 2016

Oh. We need to renew the certificate, probably.
telnetuserid
response 3 of 223: Mark Unseen   Feb 22 01:52 UTC 2016

Hi there.
It seems that grex is still using OpenBSD 5.0. That's
too old.
It would be nice to have latest OpenBSD running on
grex, maybe the next 5.9 version.
commodorejohn
response 4 of 223: Mark Unseen   Feb 22 02:36 UTC 2016

What exactly are the criteria for "too old?" Seems to be working perfectly
fine...
kentn
response 5 of 223: Mark Unseen   Feb 22 12:55 UTC 2016

We've talked about this repeatedly for the last several years.  Our goal
is to migrate to FreeBSD.  That requires more time than staff currently
have to devote. So we are in a holding pattern and leaving what works
alone.  Just updating OpenBSD to a newer version would require more
staff time than we have right now (local applications would likely need
updating).  If we were to do anything we'd rather put that time toward
FreeBSD.
telnetuserid
response 6 of 223: Mark Unseen   Feb 23 11:40 UTC 2016

Ok. No problem here. Moving to FreeBSD is also
acceptable, because of simpler incremental binary
upgrades.
As long as the system is running just fine, I think
it doesnt matter how old the os.
Maybe it would be simpler to stick to the old Unix
"if it isn't broken, don't fix it"
cross
response 7 of 223: Mark Unseen   Feb 23 20:03 UTC 2016

The thing is, OpenBSD sucks and actually is kind of broken.
The system panics every now and again because of it.
tod
response 8 of 223: Mark Unseen   Feb 27 05:21 UTC 2016

Damnit Chewie
walkman
response 9 of 223: Mark Unseen   Feb 29 18:57 UTC 2016

*RAAAARRRRR*
kentn
response 10 of 223: Mark Unseen   Mar 1 01:16 UTC 2016

Grex was inaccessible for at least a day or so (or so it seemed)
due to a UPS failure causing the server Grex exists on to reboot
and then die.  This lead to the dreaded "no route to host"
message when trying to connect.  The issue should be fixed now.

Thank you, Tony!
kentn
response 11 of 223: Mark Unseen   Mar 20 23:20 UTC 2016

Grex was up and down a couple times starting with last Friday and into
Sunday evening.  Both times it was the bug in the OpenBSD system that
caused it although it is not clear if anyone has found a way to make it
happen sooner.  The load average was over 150 on Saturday before I lost
my connection.  It was not clear what was causing that sort of load and
top showed a lot of 0% cpu processes.  

Thanks to Tony for coming to the rescue on these issues several
times this weekend!
kentn
response 12 of 223: Mark Unseen   Mar 31 23:15 UTC 2016

Grex went comatose again this afternoon/evening.  Thanks to Tony for
the reboot! 
walkman
response 13 of 223: Mark Unseen   Apr 2 20:05 UTC 2016

Is a reboot like a smelling salt?
tod
response 14 of 223: Mark Unseen   Apr 6 08:16 UTC 2016

It's like a smack to Otis the Drunk when Andy is having a bad hairday
kentn
response 15 of 223: Mark Unseen   Apr 8 23:19 UTC 2016

What happened was we lost our network connection for a while, so Grex
itself was still alive, but a reboot got it connected again after the
box that was handling the network was rebooted.  
glitch
response 16 of 223: Mark Unseen   Apr 12 14:21 UTC 2016

(not dead yet, just *very* busy!)

Can someone set up the reverse DNS for grex? Right now it's just the dynamic
address that SBC is handing out. Probably seems kinda nit picky, but it really
helps in e.g. IRC to see @grex.org (or @cyberspace.org, or whatever) when a
user connects.

I can set it up if staff doesn't have time and would like help.
 0-16   17-41   42-66   67-91   92-116   117-141   142-166   167-191   192-216 
 217-223          
Response Not Possible: You are Not Logged In
 

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