|
Grex > Helpers > #142: Grex System Problems - Summer 2005 | |
|
| Author |
Message |
| 25 new of 281 responses total. |
tod
|
|
response 225 of 281:
| 
Aug 24 16:21 UTC 2005 |
If you lose your connection during bbs, then it is possible to lose your
history.
When that happens, I type "fix"
Then "read since {date time i'd last read items}"
|
mynxcat
|
|
response 226 of 281:
|
Aug 24 16:35 UTC 2005 |
It happens to me even when I don't lose connection while in BBS. I've quit
BBS and logged out of grex, and the next time I get all brandnew items. It
happened to me THREE times yesterday. Seems to be a problem here.
|
rcurl
|
|
response 227 of 281:
|
Aug 24 16:50 UTC 2005 |
I had one instance of it, yesterday.
|
tod
|
|
response 228 of 281:
|
Aug 24 16:51 UTC 2005 |
This response has been erased.
|
edina
|
|
response 229 of 281:
|
Aug 24 16:51 UTC 2005 |
RE 225 Thanks!
|
mynxcat
|
|
response 230 of 281:
|
Aug 24 16:57 UTC 2005 |
Re 228> Reading mnet gives me a headache. Too much actuivity and very little
relevance
|
scott
|
|
response 231 of 281:
|
Aug 24 16:59 UTC 2005 |
It also can happen when somebody scribbles responses.
|
tod
|
|
response 232 of 281:
|
Aug 24 17:00 UTC 2005 |
re #231
What do you mean?
|
scott
|
|
response 233 of 281:
|
Aug 24 17:02 UTC 2005 |
The item in which a response has been scribbled can show up as unread, though
there are no new responses to display. Annoying when somebody does that
"scribble all my responses in this conf" thing.
|
tod
|
|
response 234 of 281:
|
Aug 24 18:23 UTC 2005 |
Is this a systems problem, Scott?
|
cross
|
|
response 235 of 281:
|
Aug 24 18:45 UTC 2005 |
This response has been erased.
|
keesan
|
|
response 236 of 281:
|
Aug 25 03:42 UTC 2005 |
I think it can also happen if /a fills up and you cannot write to your
participation file and it gets messed up.
|
rcurl
|
|
response 237 of 281:
|
Aug 25 05:34 UTC 2005 |
What's this? Is it a problem?
Date: Wed, 24 Aug 2005 12:58:36 -0700
From: Returned mail <MAILER-DAEMON@cyberspace.org>
To: rcurl@cyberspace.org
Subject: hi
Parts/Attachments:
1 Shown 3 lines Text (charset: ISO-8859-1)
2 81 KB Application
----------------------------------------
Once you have completed the form in the attached file
your account records will not be interrupted and will continue as normal.
[ Part 2, Application/X-COMPRESSED 108KB. ]
[ Cannot display this part. Press "V" then "S" to save in a file. ]
|
keesan
|
|
response 238 of 281:
|
Aug 25 12:34 UTC 2005 |
Looks like a forged From address and someone fishing for your social security
number.
|
rcurl
|
|
response 239 of 281:
|
Aug 25 17:52 UTC 2005 |
That's what I thought. I rarely open attachments to such, but rarely I
take at look to see what the attachment is, expecting the fact that I'm
running Mac OS-X to stop any viruses/worms/etc/.
|
naftee
|
|
response 240 of 281:
|
Aug 25 18:19 UTC 2005 |
/etc/.
|
albaugh
|
|
response 241 of 281:
|
Aug 25 20:14 UTC 2005 |
User "XXX" on grex had the mail program (sending of mail from the command
prompt) hang/crash. Ever since then, on a daily basis or more frequently,
grex keeps sending the user the following notice, even though the recovery
file was deleted. What is doing this, and how can it be turned off.
(e-mailings of this to staff have not met with a response)
From root@cyberspace.org Thu Aug 25 15:45:55 2005
Envelope-to: XXX@cyberspace.org
Delivery-date: Thu, 25 Aug 2005 15:45:55 -0400
X-vi-recover-file: /tmp/mail.RenjUxL20914
X-vi-recover-path: /var/tmp/vi.recover/vi.UHFdq21332
Reply-To: root@cyberspace.org
From: root@cyberspace.org (Nvi recovery program)
To: XXX@cyberspace.org
Subject: Nvi saved the file mail.RenjUxL20914
Precedence: bulk
Date: Thu, 25 Aug 2005 15:45:55 -0400
On Wed Aug 17 14:08:22 2005, the user XXX was editing a file
named /tmp/mail.RenjUxL20914 on the machine
grex.cyberspace.org, when it was saved for recovery. You can
recover most, if not all, of the changes to this file using
the -r option to vi:
vi -r /tmp/mail.RenjUxL20914
|
drew
|
|
response 242 of 281:
|
Aug 26 21:37 UTC 2005 |
When I'm dialed in direct, it is *still* impossible for me to make any
responses or new items; I get some sort of core dump error from the editor.
Is there a more "automatic" way to get a response entered from a pre-written
file? Something like "respond < filename"?
|
drew
|
|
response 243 of 281:
|
Aug 27 05:19 UTC 2005 |
It appears to be something about the gate editor. I am entering this
direct-dialed with vi.
|
albaugh
|
|
response 244 of 281:
|
Aug 29 22:08 UTC 2005 |
While bbs'ing:
/log: write failed, file system is full
|
albaugh
|
|
response 245 of 281:
|
Aug 30 19:11 UTC 2005 |
Re: resp:241 finally the nags are no longer being sent.
|
rksjr
|
|
response 246 of 281:
|
Aug 31 05:46 UTC 2005 |
Re. #183. Regarding crashing, when I was disconnected shortly after
logging on (a little after 8 p.m.), I became curious as to how frequent
the crashes have been recently, which motivated my composing a log of
recent reboots.
Last login data is included to estimate system down time.
For the privacy of users who happened to be the last users logged-in
immediately prior to a reboot, I have replaced their userids with
"userid" in the data below.
reboot ~ Tue Aug 30 20:28 [8:28pm]
userid ttyq1 157.95.31.174 Tue Aug 30 20:13 - crash
(00:15) [approx. time following last login: 28 - 13 = 15 min.]
.... .... .... .... ....
reboot ~ Tue Aug 30 10:37
userid ttyq3 80.51.51.23 Tue Aug 30 10:18 - 10:21
(00:02) [approx. time following last login: 37 - 18 = 19 min.]
.... .... ....
reboot ~ Tue Aug 30 08:47
userid ttyq3 217.21.35.33 Tue Aug 30 06:50 - crash
(01:56)
[approx. time following last login: 8:47 - 6:50 = 1 hr. 57 min.]
.... .... ....
reboot ~ Mon Aug 29 10:02
userid ttyp2 dialup-4.159.214.153.dial1.chicago1.level3.net
Mon Aug 29 09:45 - crash
(00:16) [approx. time following last login: 10:02 - 9:45 = 17 min.]
.... .... .... .... .... .... ....
reboot ~ Mon Aug 29 00:43
userid ttyqe helix.kaist.ac.kr Mon Aug 29 00:27 - crash
(00:16) [approx. time following last login: 43 - 27 = 16 min.]
.... .... .... .... ....
reboot ~ Sun Aug 28 07:32
userid ttyp7 ACD6D4DE.ipt.aol.com Sun Aug 28 07:16 - 07:16
(00:00) [approx. time following last login: 32 - 16 = 16 min.]
.... .... ....
reboot ~ Sat Aug 27 10:34
userid ttypb ip68-13-188-36.om.om.cox.net
Sat Aug 27 02:09 - 02:11
(00:01)
[approx. time following last login: 10:34 - 02:09 = 8 hrs. 25 min.]
.... .... .... .... .... .... .... .... ....
reboot ~ Thu Aug 25 15:46 (3:46pm)
userid ttyp3 netsun.cl.msu.edu Thu Aug 25 15:30 - crash
(00:15) [approx. time following last login: 46 - 30 = 16 min.]
Mode of accessing the above data:
Step 1: Access the shell prompt.
Step 2: Type: "last [pipe symbol] more" (without the quotation marks and
without the square brackets). (The pipe is the uppercase symbol sharing
the same key with the backslash "\". Sometimes typing a pipe into an
editor screen will generate unpredictable results, but the field following
the shell prompt should accept it.)
Step 3: Type: "/" (without the quotation marks).
Step 4: Type "reboot" (without the quotation marks).
Step 5: To view prior reboots: repeat steps 3 and 4 for each prior reboot.
(You may be able to depress the up arrow key in lieu of retyping
"reboot".)
|
remmers
|
|
response 247 of 281:
|
Aug 31 11:37 UTC 2005 |
Re Step 5: Typing "n" instead of "/reboot" will also skip to the next
reboot entry.
Also, if you just want to see a list of recent reboots with other login
information filtered out, you can use the Unix 'grep' utility. Type
this at the shell prompt:
last|grep '^reboot '|more
Using 'awk', you can get a list of reboots, with each reboot followed by
a list of who was logged in at the time of the immediately preceding crash:
last|awk '{if (/^reboot /) print $0; else if (/- crash/) print " "$1}'
|more
(Backtalk wrapped the preceding command; it should be typed all on one
line.)
These reboots are not planned. For a few days now, Grex has been
crashing a couple of times a day, resulting in downtime of 20 minutes or
so while it reboots itself. At this point, cause unknown. Usually the
reboot is successful; when it's not, somebody (usually somebody at our
colo, and on some occasions me) has to push the reset button manually.
I realize the sporadic outages are annoying. Hopefully we'll get the
problem resolved soon.
|
keesan
|
|
response 248 of 281:
|
Aug 31 14:28 UTC 2005 |
I was logged on twice this week when it happened, I think. Lucky me.
I have been emailing gelinas each time - is this appropriate? Should I email
colo instead? Or phone them?
|
remmers
|
|
response 249 of 281:
|
Aug 31 14:46 UTC 2005 |
As a practical matter, I'm online often enough that most of the time I
notice that Grex is down sooner than another staff member is likely to
notice or to check their email. So for this particular problem, I don't
think emailing someone speeds up the process of getting Grex back up
when it doesn't successfully reboot itself.
You shouldn't contact the colo directly. They are just hosting our
server and don't maintain it. They are willing do something simple,
like power-cycle it or hit the reset button, but for security reasons
only on the direct request of a Grex staff member who is known to them.
|