Find the answer to your Linux question:
Results 1 to 4 of 4
hi, when i take a log from tail -f /var/log/messages, below messages are their and still continue. message is Mar 5 05:13:49 fcore last message repeated 5 times Mar 5 ...
  1. #1
    Just Joined!
    Join Date
    Mar 2009
    Posts
    3

    last message repeated 6 times

    hi,
    when i take a log from tail -f /var/log/messages, below messages are their and still continue. message is
    Mar 5 05:13:49 fcore last message repeated 5 times
    Mar 5 05:14:55 fcore last message repeated 6 times
    Mar 5 05:15:50 fcore last message repeated 5 times
    Mar 5 05:16:57 fcore last message repeated 6 times
    Mar 5 05:17:52 fcore last message repeated 5 times
    Mar 5 05:18:58 fcore last message repeated 6 times
    Mar 5 05:19:53 fcore last message repeated 5 times
    Mar 5 05:20:59 fcore last message repeated 6 times
    Mar 5 05:21:55 fcore last message repeated 5 times
    Mar 5 05:22:50 fcore last message repeated 5 times

    fcore is my machine name. what is happening with my server, and whats going on!!!!!!!!!!!!

  2. #2
    Linux Newbie
    Join Date
    Feb 2009
    Location
    Third ring of Pergatory
    Posts
    199
    try vi /var/log/messages
    Your server is trying to tell you something, did root get an email from a demon?

  3. #3
    Just Joined!
    Join Date
    Mar 2009
    Posts
    3
    no, root user have not receive any email when this message come, and this message "Mar 6 14:15:36 fcore last message repeated 5 times" every minute.

  4. #4
    Linux Newbie
    Join Date
    Feb 2009
    Location
    Third ring of Pergatory
    Posts
    199
    Quote Originally Posted by masimiqbal View Post
    Mar 6 14:15:36 fcore last message repeated 5 times" every minute.
    That's all that's in dmesg? Or that's all you caught with the tail command?
    You can slice and dice dmesg with grep to shorten the amount of reading. Try
    dmesg |grep fail
    dmesg | grep FAIL
    and see what pops out.
    If that's all that's in dmesg, reboot the machine. Dmesg might have a limited quota, if it's posting every minute you've probably blown it up. Once it gets to a certain size it drops off the older entries so lets put the diagnostic init runs at startup at the front of the file.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...