| Grex > Helpers > #132: Grex System Problems - Spring 2004 |  |
| response 50 of 405: | 
Apr 12 16:52 UTC 2004 |
Hopefully grex backups don't suffer this kind of crash: http://www.ucomics.com/foxtrot/2004/04/09/ :-)
| response 51 of 405: |
Apr 12 16:53 UTC 2004 |
This response has been erased.
| response 52 of 405: |
Apr 12 16:57 UTC 2004 |
Busy staffers probably need a break from cleaning up messes made by guys like you, and so can use some humor once in a while.
| response 53 of 405: |
Apr 12 17:40 UTC 2004 |
This response has been erased.
| response 54 of 405: |
Apr 12 21:11 UTC 2004 |
Re #50: Cute. Thanks, Kevin.
| response 55 of 405: |
Apr 12 22:16 UTC 2004 |
I'll try this again: #53 of 54: by Jackoffski (soup) on Mon, Apr 12, 2004 (13:40): /d is full
| response 56 of 405: |
Apr 12 22:38 UTC 2004 |
I( wonder how that happened. 'Twas at or about 50% last time I checked it. Ah well. No time to deal with it now.
| response 57 of 405: |
Apr 15 22:11 UTC 2004 |
2nd cnnnection in 4 minutes. so far this has lasted ..... first connection (according to grex anyway ... ) was 17:27 - 17:50 (00:22) grex is incorrect ... connecti0n lasted a little more than a minute. as gelinas said in #43 (and i posted:) these last 3 hops 15 216.93.15.210 36ms 36ms TTL: 0 (rback0.flnt.mi.voyager.net ok) 16 No Response * * * 17 216.93.104.34 60ms 218ms TTL:241 (grex.cyberspace.org ok) any help for diagnosis here?
| response 58 of 405: |
Apr 15 23:52 UTC 2004 |
I tried power-cycling the DSL modem(?) today; it doesn't seem to have helped. I'll try to call our ISP tomorrow.
| response 59 of 405: |
Apr 15 23:53 UTC 2004 |
This response has been erased.
| response 60 of 405: |
Apr 16 01:08 UTC 2004 |
This response has been erased.
| response 61 of 405: |
Apr 16 01:30 UTC 2004 |
This response has been erased.
| response 62 of 405: |
Apr 16 01:59 UTC 2004 |
I have not had any lockups today so maybe it did help.
| response 63 of 405: |
Apr 16 02:44 UTC 2004 |
This response has been erased.
| response 64 of 405: |
Apr 16 05:57 UTC 2004 |
This early morning's connection has barely been useable, with lag often going 30-60 seconds and up. \
| response 65 of 405: |
Apr 16 11:54 UTC 2004 |
This response has been erased.
| response 66 of 405: |
Apr 16 15:28 UTC 2004 |
I was locked up twice this morning (once while trying to respond to this item) and had the connection time out once after a lockup.
| response 67 of 405: |
Apr 16 15:28 UTC 2004 |
This response has been erased.
| response 68 of 405: |
Apr 16 17:57 UTC 2004 |
This response has been erased.
| response 69 of 405: |
Apr 16 18:12 UTC 2004 |
This response has been erased.
| response 70 of 405: |
Apr 16 19:37 UTC 2004 |
At this moment, grex system performance (at least bbs) is pretty poor. I suspect that may be why there are so few new reponses...
| response 71 of 405: |
Apr 16 20:13 UTC 2004 |
This response has been erased.
| response 72 of 405: |
Apr 18 19:33 UTC 2004 |
Judging by the flood of new spam I received in the past day or two, is it plausible that increased mail server load may be saturating the DSL bandwidth and also bogging down the cpu?
| response 73 of 405: |
Apr 20 03:46 UTC 2004 |
I was unable to ssh in all day - the connection always timed out. Likewise with telnet.
| response 74 of 405: |
Apr 20 03:48 UTC 2004 |
Looks like there was a problem with the Ethernet connection on grex. I power-cycled the machine because I could not log in from the console.