SCIENTIFIC-LINUX-USERS Archives

December 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Fri, 30 Dec 2011 05:15:27 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (52 lines)
On 2011/12/30 00:06, MT Julianto wrote:
>
> On 27 December 2011 15:11, MT Julianto <[log in to unmask]
> <mailto:[log in to unmask]>> wrote:
>
>
>     On 27 December 2011 08:57, zxq9 <[log in to unmask] <mailto:[log in to unmask]>> wrote:
>
>         On 12/27/2011 04:12 PM, MT Julianto wrote:
>
>             The machine looks (sometimes) sleep, although it is always on, idle, no
>             screensavers is running, and no network changes surroundings.  That's
>             never happened before migrated, and never happened when connecting or
>             neighbor machines in the office.
>
>
>         I haven't had this issue myself at all, but power settings is the first
>         place I would start looking. Another place to check might be the sshd
>         settings (but again, this would be strange since others haven't reported
>         the same issue).
>
>
>     What settings of sshd might related to the problem?  I used fresh
>     installation of SL61, did small change to /etc/ssh/sshd_config:
>     "PermitRootLogin no" and always use ssh with authentication key.
>
>         It could also be routing in the office. But I'd check the above two
>         things before I start wondering if routers don't like to remember my
>         system's MAC or DHCP address or something (though its possible if your
>         office needs some setting for DHCP leases to last the right amount of
>         time or whatever).
>
>
>     The machine got IP (public IP) via dhcp with fixed-address
>
>     I'll watch the dhcp lease further whenever the problem occurs again later,
>
>
> Thanks for your replies :-)
>
> All possibilities are negative: not power mode issue, not dhcp issue (see
> below), not iptables issue (see below), not hacking issue (/var/log/secure is
> clear (no attack) at that fail time).

What happens if you ping the host before trying ssh?

Can you check if the ssh daemon is running or if it's setup to use xinetd?
(Normally it runs as a daemon. I'm hypothesizing that it is running off an
inet daemon and taking too long to load or something.)

{^_^}

ATOM RSS1 RSS2