Searching exception keyword in all logs in last 5 minutes


 
Thread Tools Search this Thread
Top Forums UNIX for Beginners Questions & Answers Searching exception keyword in all logs in last 5 minutes
# 8  
Old 01-21-2019
Note that punpun26262626 says that he or she is running commands on a UNIX system through putty. Since, date -d is a GNU date extension, there is a good chance that none of the above suggestions will work.

Hello punpun26262626,
When starting a new thread on unix.com, please always tell us what operating system and shell you're using. Saying you're using UNIX is roughly equivalent to saying that you're driving a vehicle when someone asks you what model of car, truck, or motorcycle you drive. Asking questions about handling strings containing dates is one of the topics where knowing exactly what versions of operating system you're using and which shell you're using are crucial to getting help that will work in your environment.

Please help us help you.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to extract logs between the current time and the last 15 minutes ?

I want to extract the logs between the current time stamp and 15 minutes before and sent an email to the people configured. I developed the below script but it's not working properly; can someone help me?? I have a log file containing this pattern: Constructor QuartzJob ... (3 Replies)
Discussion started by: puneetkhullar
3 Replies

2. Shell Programming and Scripting

Need help in getting the Last 30 minutes logs from the Log File

I have a log file with the below contents : log_file_updated.txt : Jul 5 03:33:06 rsyslogd: was Jul 5 03:33:09 adcsdb1 rhsmd: This system is registered. Sep 2 02:45:48 adcsdb1 UDSAgent: 2015-07-05 04:24:48.959 INFO Worker_Thread_4032813936 Accepted connection from host <unknown>... (3 Replies)
Discussion started by: rahul2662
3 Replies

3. Shell Programming and Scripting

Searching Error Message from a log life between timestamp of every 10 minutes

HI Everyone, My task is to search error messages last 10 minutes everytime from a log file. My script, date1=`date -d '10 minutes ago' "+%H:%M:%S"` date2=`date "+%H:%M:%S"` awk -v d1="${date1}" -v d2="${date2}" '$0~d1{p=1} $0~d2{p=0} p' filename No error getting in... (3 Replies)
Discussion started by: ctscbe
3 Replies

4. Shell Programming and Scripting

Catching the exception in multiple logs

Hi folks, I have logs folder in which different type of logs are generated , I am monitoring them by the below command tail -f *.log but I want that if exception come in any of the logs then it should be catch so what i should prefix with tail -f *.log so that it imeediatley catches and... (3 Replies)
Discussion started by: punpun66
3 Replies

5. Shell Programming and Scripting

Line numbers and exception to be caught in logs

Hi Folks, I have just basic queries is that suppose I have to monitor the logs then there is a command , suppose I have to monitor the abc.log which is updating dynamically within seconds so the command will be after going to that directory is .. tail -f abc.log Now please advise what about... (1 Reply)
Discussion started by: punpun66
1 Replies

6. Shell Programming and Scripting

Monitor logs for exception and if exception come then sent an email

Hi Folks, please advise , I have logs generated on unix machine at location /ops/opt/aaa/bvg.log , now sometimes there come exception in these logs also, so I want to write such a script such that it should continuously monitor these logs and whenever any exception comes that is it try to find... (3 Replies)
Discussion started by: tuntun27272727
3 Replies

7. Shell Programming and Scripting

Searching set of string from Live Running Logs

Hey just need one simple syntax to search for the string from the Live Running Logs. The strings are placed in a $infile & everytime the script should pull each string from $infile and should provide as an input for grepping from Live running logs on a rotational basis. So here are the Contents... (14 Replies)
Discussion started by: raghunsi
14 Replies

8. OS X (Apple)

Keyword Searching

Hi all, I am in the process of building a shell script as part of a auditing utility. It will search a specified directory for keywords and output results of the file path, and line number that the word was found on. I built a test script (shown below) that does just this, but egrep apparently... (0 Replies)
Discussion started by: tmcmurtr
0 Replies

9. Shell Programming and Scripting

Searching *.gz logs

I have been trying to search for a string from close to 200 *.gz file, But i get a error. Can someone suggest a bulletproof solution Please. zgrep 20/Aug/2008:13:50:23 request.log.*.gz -bash: /usr/bin/zgrep: /bin/sh: bad interpreter: Argument list too long also zgrep 20/Aug/2008:13:50:23... (9 Replies)
Discussion started by: openspark
9 Replies

10. OS X (Apple)

keyword searching of documents

Unix based fix-it needed? Platform and feature: search programs on Apple computers (Leopard or Tiger; 10.4 and above; Spotlight) Problem: the document search feature of these programs produce hits when keyword(s) used appear anywhere in the document's content. Change required: we need to... (1 Reply)
Discussion started by: Miles
1 Replies
Login or Register to Ask a Question
autofs(4)																 autofs(4)

NAME
autofs - file containing parameter values for automountd daemon and automount command SYNOPSIS
/etc/default/autofs The autofs file resides in directory /etc/default and supplies default parameters for the automountd(1M) daemon and the automount(1M) com- mand. The autofs file format is ASCII; comment lines begin with the crosshatch (#) character. Parameters consist of a keyword followed by an equal sign followed by the parameter value, of the form: keyword=value As shipped, the parameters in the autofs file are commented out. As root, you must uncomment a keyword-value line to make the value for that parameter take effect. Administrators can make changes to the startup parameters for automountd by logging in as root and editing the autofs file. Changes made to autofs values on an automount or automountd command line override values in /etc/default/autofs. The /etc/default/autofs file is preserved across operating system upgrades. The following parameters are currently supported in the autofs file: AUTOMOUNT_TIMEOUT=<num> Specifies a duration, in seconds, that a file system is to remain mounted when not in use. The default value is 600 (10 minutes). Equivalent to the -t option in automount. AUTOMOUNT_VERBOSE=TRUE | FALSE Verbose mode. Causes you to be notified of non-critical events, suchs as autofs mounts and unmounts. The default value is FALSE. Equiv- alent to the -v option in automount. AUTOMOUNTD_VERBOSE=TRUE | FALSE Verbose mode. Causes status messages to be logged to /var/svc/log/system-filesystem-autofs:default.log. (See smf(5).) The default value is FALSE. Equivalent to the -v option in automountd. AUTOMOUNTD_NOBROWSE=<num> Turn on or off browsing for all autofs mount points. The default value is FALSE. Equivalent to the -n option in automountd. AUTOMOUNTD_TRACE=<num> Expands each RPC call and logs it to /var/svc/log/system-filesystem-autofs:default.log. (See smf(5).) The default value, 0, turns off such tracing. Starting with 1, with each higher value, the verbosity of trace output increases. AUTOMOUNTD_ENV=<name>=<value> Environment variables. Each environment variable-value pairing must be on its own line. You can specify multiple such pairings. There are no environment variable settings supplied. For example: AUTOMOUNTD_ENV=DAY=TUES automount(1M), automountd(1M), smf(5) 2 Aug 2005 autofs(4)