--- Michael Stauber <bq (at mark) solarspeed.net> wrote:
> Hi Dan,
>
> > Any idea what services to restart, short of doing a reboot?
> >
> > Apr 14 17:31:11 admin sshd[22769]: Invalid user eaguilar from
> > 203.197.82.242
> > Apr 14 22:31:11 admin sshd[22772]: input_userauth_request: invalid user
> > eaguilar
> > Apr 14 17:31:12 admin sshd[22773]: Invalid user eaguilar from
> > 203.197.82.242
> > Apr 14 22:31:12 admin sshd[22776]: input_userauth_request: invalid user
> > eaguilar
> > Apr 14 17:31:35 admin sshd[22769]: Failed password for invalid user
> > eaguilar from 203.197.82.242 port 39381 ssh2
> > Apr 14 22:31:35 admin sshd[22772]: Connection closed by 203.197.82.242
> > Apr 14 17:31:36 admin sshd[22773]: Failed password for invalid user
> > eaguilar from 203.197.82.242 port 36154 ssh2
> > Apr 14 22:31:36 admin sshd[22776]: Connection closed by 203.197.82.242
> >
> > I had previously restarted sshd to no effect.
>
> While this by itself does no harm: Yeah, it sure doesn't look nice in the
>
> logs. :o)
>
> To "unclutter" the logs after such a spectacular time drift it may be
> necessary restart pretty much all daemons - including Syslogd itself. To
> be
> honest: I'd rather do a reboot as it's less hassle than restarting all
> the
> required services manually.
>
> To prevent this from happening again, consider specifying a NTP server
> under "System Settings" / "Time" / "NTP Server Address".
>
What's strange is, I have had such a setting since before the last reboot
of the server.
--
Dan Kriwitsky
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ