|
Grex > Helpers > #130: Grex System Problems - Winter 2003/2004 |  |
|
| Author |
Message |
| 25 new of 384 responses total. |
kip
|
|
response 178 of 384:
| 
Jan 18 19:22 UTC 2004 |
re 174 /var/log/messages doesn't contain information that would say who killed
a login process. Or at least it doesn't to my eyes. I'll defer to other
staff with more experience.
|
ryan
|
|
response 179 of 384:
|
Jan 18 19:49 UTC 2004 |
This response has been erased.
|
mcnally
|
|
response 180 of 384:
|
Jan 18 20:19 UTC 2004 |
re #174: I recently had an evening where I kept getting logged
out abruptly, several times while in party. Did you just leap
to the conclusion that you were being persecuted by a vengeful
root user? My assumption was that it was likely that network
problems were causing my session to drop out.. I'm not sure how
you'd differentiate between the two scenarios in a typical login
session, so perhaps you should at least consider other causes..
|
twenex
|
|
response 181 of 384:
|
Jan 18 20:24 UTC 2004 |
I've been having this, too - after a while, if i don't type anything, my
session just gets dropped. Is that the problem you've ben having, Mike?
|
ryan
|
|
response 182 of 384:
|
Jan 18 20:35 UTC 2004 |
This response has been erased.
|
willcome
|
|
response 183 of 384:
|
Jan 18 20:39 UTC 2004 |
I already have an item about this in coop. maybe oldcoop.
|
kip
|
|
response 184 of 384:
|
Jan 18 20:41 UTC 2004 |
re 179 actually that would be /var/log/sulog.
|
gull
|
|
response 185 of 384:
|
Jan 18 22:21 UTC 2004 |
I get Pine sessions killed with various signals from time to time. I
don't know why. I'd been assuming some hardware glitch.
|
goose
|
|
response 186 of 384:
|
Jan 19 03:54 UTC 2004 |
I for one am glad that the messages file is closed to all but roots.
|
naftee
|
|
response 187 of 384:
|
Jan 19 04:02 UTC 2004 |
re 177 All the crappy e-mail bombers are written with Italian instructions.
re 180 Both ryan and jimj were in party at the same time; it's more than
enough to get worried.
re 184 It is /var/log/messages on FreeBSD, maybe it's different on SunOS.
re 186 I'm glad you're just a silly old goose.
|
kip
|
|
response 188 of 384:
|
Jan 19 04:12 UTC 2004 |
It is different here. Use of the su command is logged in /var/log/sulog, not
/var/log/messages
|
jiffer
|
|
response 189 of 384:
|
Jan 19 04:18 UTC 2004 |
Naftee you are paranoid.
And now for my paranoid issue. I logged in to find that I supposedly sent
junk crap mail to people and it was bounced back. I find this more than just
strange but odd since I never send mail on grex anymore and all my mail from
grex should be forwarding which is forwarding again. so... there, and who
ever the unethical jerk who did this, f- you! f- you and your large a-hole!
|
naftee
|
|
response 190 of 384:
|
Jan 19 04:40 UTC 2004 |
Jiffer quit being mean.
|
gelinas
|
|
response 191 of 384:
|
Jan 19 04:54 UTC 2004 |
It's probably a virus, choosing an e-mail address from the infected machine's
address book.
|
bhoward
|
|
response 192 of 384:
|
Jan 19 05:06 UTC 2004 |
Occasionally, if I am disconnected from grex for being idle to long
but log in just after having been disconnected, I will get forcibly
signed-off again. Unfortunately, I don't have enough debugging
evidence to really nail down the cause but I assume there may be
a bug in the idle login killer or robocop that causes it to mistake
my fresh loging for a valid target process to kill.
|
bhoward
|
|
response 193 of 384:
|
Jan 19 05:07 UTC 2004 |
s/loging/login session
|
goose
|
|
response 194 of 384:
|
Jan 19 16:08 UTC 2004 |
RE#189 -- Yep, your address was harvested from someone elses machine that has
been infected with a virus. It looks like you sent mail, but you really
didn't. It's a huge pain in the ass, but there is nothing you can do about
it.
|
jiffer
|
|
response 195 of 384:
|
Jan 19 16:49 UTC 2004 |
Drats, that is a bit embarressing.
Naftee I am always mean.
|
remmers
|
|
response 196 of 384:
|
Jan 19 17:27 UTC 2004 |
I frequently get spam with the "From:" address forged to look like
it came from somebody I know. As Chris says, the most likely
explanation is that both addresses were lifted by a virus from the
address book on some third party's infected (Windows) machine.
|
albaugh
|
|
response 197 of 384:
|
Jan 19 18:14 UTC 2004 |
Is this the proper item in which to report an e-mail "difficulty"?
|
gelinas
|
|
response 198 of 384:
|
Jan 19 18:19 UTC 2004 |
Probably as good as any. What's up?
|
albaugh
|
|
response 199 of 384:
|
Jan 19 18:40 UTC 2004 |
For I'm not sure how long now an e-quaintance who receives my grex e-mail OK
cannot get mail delivered [back] to grex. After a few days, he gets a bounce
message that looks like this:
From: "Mail Delivery System" <MAILER-DAEMON@out1.mx.nwbl.wi.voyager.net>
To: <auser@voyager.net>
Sent: Monday, December 29, 2003 11:34 AM
Subject: Undelivered Mail Returned to Sender
This is the Postfix program at host out1.mx.nwbl.wi.voyager.net.
I'm sorry to have to inform you that the message returned
below could not be delivered to one or more destinations.
For further assistance, please send mail to <postmaster>
If you do so, please include this problem report.
You can delete your own text from the message returned below.
The Postfix program
<auser@cyberspace.org>: connect to
grex.cyberspace.org[216.93.104.34]: read timeout
I guess I should contact the voyager.net postmaster (my e-quaintance isn't
computer savvy), but before I do, does the grex "side" have anything to
comment on about this?
|
gelinas
|
|
response 200 of 384:
|
Jan 19 19:00 UTC 2004 |
My _guess_ is that they've set a too-short timeout on the voyager end.
Hmm...
Jan 18 02:08:37 grex sendmail[19179]: NOQUEUE: SYSERR: putoutmsg
(out0.mx.nwbl.wi.voyager.net): error on output channel
sending "220 ESMTP spoken here": Connection refused by
out0.mx.nwbl.wi.voyager.net
The connection is supposed to be something like:
} telnet grex.cyberspace.org 25
} Trying 216.93.104.34...
} Connected to grex.cyberspace.org.
} Escape character is '^]'.
} 220-grex.cyberspace.org Sendmail 8.6.13/8.6.12 ready at Mon, 19 Jan 2004
13:57:13 -0500
} 220 ESMTP spoken here
Apparently, that second line never gets back to out?.mx.nwbl.wi.voyager.net,
and then things time-out/break.
|
albaugh
|
|
response 201 of 384:
|
Jan 19 19:05 UTC 2004 |
Does that mean that the grex side is "failing" in some way, or is it still
something on the voyager.net side. BTW, I'm very sure that my e-quaintance
would have mentioned if this problem ocurred with other systems he tries to
send e-mail to...
|
gelinas
|
|
response 202 of 384:
|
Jan 19 19:21 UTC 2004 |
I think it's on the voyager side: grex is trying to send something, but
voyager doesn't accept it.
|