Professional Web Applications Themes

System logging not working. - Linux Setup, Configuration & Administration

Hi, On my Redhat 9 machine, I recently noticed that during bootup the "Starting system loggin" says FAILED. I have looked at /var/log/messages and I see that not messages older than about 3 days are in the log. I cannot recall anything specific I did to cause the logging to stop working. I have not touched etc/syslog.conf. Can anyone suggest on how to get this working again ? Regards Anton Erasmus...

  1. #1

    Default System logging not working.

    Hi,

    On my Redhat 9 machine, I recently noticed that during bootup the
    "Starting system loggin" says FAILED. I have looked at
    /var/log/messages and I see that not messages older than about 3 days
    are in the log. I cannot recall anything specific I did to cause the
    logging to stop working.
    I have not touched etc/syslog.conf. Can anyone suggest on how to
    get this working again ?

    Regards
    Anton Erasmus

    Anton Guest

  2. #2

    Default Re: System logging not working.

    Anton Erasmus <net> wrote: 

    Start syslogd manually and look for error messages.
    Davide
    Davide Guest

  3. #3

    Default Re: System logging not working.

    On 24 Sep 2003 18:30:20 GMT, Davide Bianchi
    <net> wrote:
     
    >
    >Start syslogd manually and look for error messages.
    >Davide[/ref]

    It says syslogd already running.
    At startup it still says FAIL as the result for "Starting Syslog".
    Nothing is being added to /var/log/messages.
    Anyway, at least together with man syslogd, I have some direction
    in which to search for the problem and solution.

    Thanks
    Anton Erasmus

    Anton Guest

  4. #4

    Default Re: System logging not working.

    Anton Erasmus <net> wrote: 

    If you use ps -ef | grep syslog do you see it working? What if you
    try to kill it and then restart it?

    Davide
    Davide Guest

  5. #5

    Default Re: System logging not working.

    On 25 Sep 2003 18:06:38 GMT, Davide Bianchi
    <net> wrote:
     
    >
    >If you use ps -ef | grep syslog do you see it working? What if you
    >try to kill it and then restart it?
    >
    >Davide[/ref]

    Logged in as root on tty2 I get:
    3130 tty2 S 0:00 grep syslog HOSTNAME=duzi.antera.net
    PVM_RSH=/usr/bin

    If I do:
    kill 3130
    I get:
    No such process

    If I do:
    kill -SIGHUP 'cat /var/run/syslogd.pid'
    as suggested by the syslogd man file to
    restart syslogd
    I get:
    cat /var/run/syslogd.pid: no such pid.
    If I do:
    cat /var/run/syslogd.pid
    I get 2061
    If I do:
    kill -SIGHUP 2061
    I get just the normal prompt.
    If I then look in /var/log/messages I actually
    get a line indicating that syslogd has been restarted.

    Regards
    Anton Erasmus





    Anton Guest

  6. #6

    Default Re: System logging not working.

    Anton Erasmus <net> wrote: 

    And if you ps -ef | grep 2061 (or whatever PID is in the /var/run/syslog.pid)
    what you see?
     

    So it looks like is started and running, but is not logging anything.
    Maybe is a problem in the syslog.conf file. Have you checked it?

    Davide
    Davide Guest

  7. #7

    Default Re: System logging not working.

    On 27 Sep 2003 18:25:35 GMT, Davide Bianchi
    <net> wrote:
     
    >
    >And if you ps -ef | grep 2061 (or whatever PID is in the /var/run/syslog.pid)
    >what you see?

    >
    >So it looks like is started and running, but is not logging anything.
    >Maybe is a problem in the syslog.conf file. Have you checked it?
    >[/ref]

    Below is a transcript of what I get.

    [antonduzi anton]$ tail /var/log/messages
    Sep 28 12:30:35 duzi syslogd 1.3-0: restart.
    [rootduzi anton]# cat /var/run/syslogd.pid
    2061
    [rootduzi anton]# ps -ef | grep 2061
    root 2061 1 0 19:32 ? 00:00:00 syslogd -m 0
    root 3065 3032 0 20:34 pts/1 00:00:00 grep 2061
    [rootduzi anton]# tail /var/log/messages
    Sep 28 12:30:35 duzi syslogd 1.3-0: restart.
    [rootduzi anton]# kill -SIGHUP 2061
    [rootduzi anton]# tail /var/log/messages
    Sep 28 12:30:35 duzi syslogd 1.3-0: restart.
    Sep 30 20:34:46 duzi syslogd 1.3-0: restart.

    I have not touched the syslog.conf file. It should be as originally
    installed. I have another RH9 box, where the syslog works as
    it should. I will copy it's syslog.conf file to the box that is giving
    problems.

    Regards
    Anton Erasmus

    Anton Guest

  8. #8

    Default Re: System logging not working.

    Anton Erasmus <net> wrote: 

    It looks like it's working, the -m disable the insertion of a "mark"
    message every x minutes, the default it's 20 minutes, setting it to
    0 disable it.
     

    If you didn't changed it, maybe someone else did. I'd test for
    rootkit on that machine.

    Davide
    Davide Guest

  9. #9

    Default Re: System logging not working.

    On 30 Sep 2003 18:44:15 GMT, Davide Bianchi
    <net> wrote:
     
    >
    >It looks like it's working, the -m disable the insertion of a "mark"
    >message every x minutes, the default it's 20 minutes, setting it to
    >0 disable it.[/ref]

    The problem is that it is not logging anything. At startup the syslog
    process startup is reported as FAILED. It works fine after
    I do the kill -SIGHUP pid command. (Until the next reboot)
    I switch this machine off every time after I have used it, hence
    a working syslogd directly after startup would be nice.
    Anything else failing normally writes to the log file. With the actual
    logging not starting up, where does one look ?
    the kernel log seems to start up correctly. Might the reason for
    the syslogd failing at startup be logged here ?
     
    >
    >If you didn't changed it, maybe someone else did. I'd test for
    >rootkit on that machine.[/ref]

    I am the only person with access to this machine. I am as close to
    100% sure as can be that no-one except myself have ever used
    the machine. I had been playing with some source and binary rpm's
    for various utilities. Can a install via rpm cause such problems ?

    Regards
    Anton Erasmus
     




    Anton Guest

  10. #10

    Default Re: System logging not working.

    Anton Erasmus <net> wrote: 

    Check in /etc/rc.d/initd which script start syslogd and (eventually)
    add there the SIGHUP command, I admit that isn't a really good
    solution, but if it works...
     

    COuld be, check.
     

    It shouldn't...

    Davide
    Davide Guest

Similar Threads

  1. Working with Adobe InDesign CS 2 , Xinetand Dalim Twist Workflow System
    By Michele T Nelson in forum Adobe Indesign Macintosh
    Replies: 0
    Last Post: July 2nd, 07:18 AM
  2. Replies: 3
    Last Post: January 18th, 10:55 AM
  3. Replies: 2
    Last Post: July 24th, 06:17 PM
  4. Replies: 1
    Last Post: July 18th, 08:48 PM
  5. Replies: 1
    Last Post: July 9th, 07:46 AM

Bookmarks

Posting Permissions

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

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139