Syslog Automated Action not run

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: Syslog Automated Action not run

Re:Syslog Automated Action not run

by Guest » Fri Nov 12, 2010 6:23 am


I did it, and it running now!ThanksLeonardo

Re:Syslog Automated Action not run

by Guest » Fri Nov 12, 2010 4:53 am


I never recommend using relative paths in Automated Action scripts.  Change the "./" to a fully-qualified path to which casuser has write access.  Since you are doing an append operation, make sure that file exists.If the AA script still does not run, enable Syslog Analyzer debuggign under RME > Admin > System Preferences > Loglevel Settings, then reproduce the problem, and look at the AnalyzerDebug.log for any errors relating to your AA.

Re:Syslog Automated Action not run

by Guest » Fri Nov 12, 2010 3:46 am


I don't think casuser has a home directory where ./trace.log could be created. How about /tmp that's world writable.#!/usr/bin/shecho "SYSLOG ACTION SUCCESS!" >> /tmp/trace.logCheers,Michel

Re:Syslog Automated Action not run

by Guest » Fri Nov 12, 2010 2:11 am


Hi davistan,I found all messages into syslog_info like that:%SYS-5-CONFIG_I: Configured from console...%SYS-5-RELOAD: Reload requestedI found also messages into RME Report"Syslog Analyzer Configuration Changes Report" and "24 Hour Report".My automatic action script it that:-rwxr-xr-x   1 casuser  casusers      64 Mar 13 12:30 Reload_Router_Switch.sh#!/usr/bin/shecho "SYSLOG ACTION SUCCESS!" >> ./trace.logbut no file trace.log is created.There is no messages filterAny to check?ThanksLeonardo

Re:Syslog Automated Action not run

by Guest » Fri Nov 12, 2010 12:46 am


Hi You need to check the following:Are the devices sending syslog messages to the server managed devices in RME?If so, try the following:Go to the device and enter conf t and then exitThis should generate a config change messageCheck to make sure it hits the syslog_infoWhen it does, wait a few minutes and then go to RME and run a report for that device to see if the message is there.You may also want to turn on Syslog debugs in under RME - Admin - System Preferences - Loglevel Settings before doing the above

Top