Announcement

Collapse
No announcement yet.

Event Log does not behave as expected

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Event Log does not behave as expected

    Hi all..

    I have Monitoring -> Event Log -> All Logs (under "Event Logs") being populated with no problem. But I can only view for current day. When I change the period other than "Today", it still shows "Today"'s logs.
    How can I solve this.

    Moreover.. the logs in "Advance Logs" is not automatically being populated. I have to manually run "parsing_log.pl -a" (under /usr/local/oreon/cron) to populate it. How can I make it run automatically?

    Hope somebody can help me..

    thanks
    ARaman.

  • #2
    Hi Araman,

    "Event Logs" are the nagios parsed log files, so it takes long time and it's a bit crapy.

    "Advanced Log" are stored in "Oreon Data Storage" (ODS) database. If you run multiple times the "parsing_log.pl -a" script you will have duplicated infos in the base.
    However you can run it without option. It will parse the actual "nagios.log" file that is named in the configuration table in ODS datatable.

    To automatize the process, the install of oreon creates a cron file "/etc/cron.d/oreon". You can also create this entry manualy in your crontab file:
    Code:
    * * * * * nagios /usr/local/oreon/cron/parsing_log.pl >> /usr/local/oreon/log/ods_parsing_log 2>> /usr/local/oreon/log/ods_parsing_log
    And restart your cron service.

    It will automaticaly feed the database.
    ..()_() .("who | grep -i blonde | date; cd ~; unzip;")
    =(o_0)=
    *(() () Nicolas Verriest, France

    Comment


    • #3
      Thanks for replying NoS

      That's weird...
      All that you've mentioned is already there.. yet, it doesn't populate it.
      I did try to restart the cron "/etc/init.d/crond restart"..
      Still the same.. No population happening..
      Is there anything that I missed out?

      THanks
      Rgds

      Comment


      • #4
        Try it manualy with the good user.

        I suspect that this user can't create "/usr/local/oreon/log/ods_parsing_log" and the file doesn't exists.

        If so, touch it with the good rights
        ..()_() .("who | grep -i blonde | date; cd ~; unzip;")
        =(o_0)=
        *(() () Nicolas Verriest, France

        Comment


        • #5
          Thanks NoS.. but still

          You are right.. I didn't have the file ods_parsing_log.
          Just created it. But still no progress.
          Is there a log on seeing the ods_parsing_log being written upon?
          Or is ods_parsing_log is the log?

          Rgds
          Araman

          Comment


          • #6
            Hi Araman,

            is the file, you've created, writable by the user that runs this command ?

            Because by default you've created one that should be only readable, the folder needs to be executable at least.

            Maybie try to chmod this folder to 777 to debug it.
            ..()_() .("who | grep -i blonde | date; cd ~; unzip;")
            =(o_0)=
            *(() () Nicolas Verriest, France

            Comment

            Working...
            X