[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ale] Long lag for command line

Subject: [ale] Long lag for command line
From: cluon at geeklabs.com (Mike Harrison)
Date: Sat, 29 Jun 2013 11:41:12 +0000 (UTC)
In-reply-to: <[email protected]>
References: <[email protected]> <CAMdBqcNTgc0pVn_1OXYie4__K8d9XiNgaQW8de+nZDo8UDQkBg@mail.gmail.com> <CAHWNiXz_j+nPojzA65f-sK=+w7kD5Baikuaxn-UVjCRu3DY1rQ@mail.gmail.com> <CAMdBqcNn0bOQjrAvhhO66psNY+ResX-eARmkx6m=6esb_BUHPQ@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]>

On Sat, 29 Jun 2013, Alex Carver wrote:
> didn't crop up until recently (maybe four or five days ago) but the machine 
> had been running continuously without issue for about 50 days (would have

I'd start with dmesg - I've seen weird HD or other I/O errors cause 
similar issues and they showed up in 'dmesg'

And stupid things: If this system is remote, run MTR/traceroute
to it, it might not be a machine issue, but a connection to it issue.

Follow-Ups:
- [ale] Long lag for command line
  - From: agcarver+ale at acarver.net (Alex Carver)

References:
- [ale] Long lag for command line
  - From: agcarver+ale at acarver.net (Alex Carver)
- [ale] Long lag for command line
  - From: pete.hardie at gmail.com (Pete Hardie)
- [ale] Long lag for command line
  - From: dustin.h.strickland at gmail.com (Dustin Strickland)
- [ale] Long lag for command line
  - From: pete.hardie at gmail.com (Pete Hardie)
- [ale] Long lag for command line
  - From: agcarver+ale at acarver.net (Alex Carver)
- [ale] Long lag for command line
  - From: atllinuxenthinfo at techstarship.com (Ron Frazier (ALE))
- [ale] Long lag for command line
  - From: agcarver+ale at acarver.net (Alex Carver)

Prev by Date: [ale] Long lag for command line
Next by Date: [ale] OT fyi interesting historical info on memory management
Previous by thread: [ale] Long lag for command line
Next by thread: [ale] Long lag for command line
Index(es):
- Date
- Thread