Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: a better way to grep until end of error message, although most seem to be 1 or 2 line
Top Forums Shell Programming and Scripting a better way to grep until end of error message, although most seem to be 1 or 2 line Post 302314090 by durden_tyler on Thursday 7th of May 2009 10:54:44 AM
Old 05-07-2009
Quote:
Originally Posted by VGR
...
Basically I want to capture the description of the error along with the error and count how many times it occurred.
...
[blank line] <-all the information upto this blank line and then how many times it appears in the file
Here's one way to do it:

Code:
$
$ cat input.txt
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
 
SQL0204N "ITUAM.VW_TT_VALUES" is an undefined name. 
SQLSTATE=42704
blah blah blah....
 
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
 
SQL0204N "ITUAM.VW_TT_VALUES_2" is an undefined name. 
SQLSTATE=42705
blah blah blah....
 
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
 
SQL0204N "ITUAM.VW_TT_VALUES_3" is an undefined name. 
SQLSTATE=42706
blah blah blah....
 
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned: success
$
$ perl -ne '{$n++ if /SQL\d{4}[A-Z].*/s}END{print "The error occurred $n times.\n"}' input.txt
The error occurred 3 times.
$
$

HTH,
tyler_durden
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

grep error message

hi, I get this error message after I pipe a lot of output into grep. Does anyone know what his means? grep: writing output: Invalid argument thanks, gammaman (3 Replies)
Discussion started by: gammaman
3 Replies

2. Solaris

syntax error at line 59: `end of file' unexpected

Hello... I'm trying to run the sshd script, but I keep geting the Syntax errot message . Here's the last few lines on the script. set nu in vi shows 58 lines, but I keep getting error referring to line 59. Any help is appreciated. Thanks, Remi else echo... (4 Replies)
Discussion started by: Remi
4 Replies

3. UNIX for Advanced & Expert Users

Is there a better way to grep until end of error message?

My file creates an output log after which includes a few sql queries. I segregate them into warnings and errors and then get a total count. The errors' and warnings' lines always start with SQL{4} followed by the details of the error. This is what im doing as o now... errors=`grep -A 1 -E... (1 Reply)
Discussion started by: VGR
1 Replies

4. Shell Programming and Scripting

Grep from a starting line till the end of the file

Hi Folks, I got to know from this forums on how to grep from a particular line say line 6 awk 'NR==6 {print;exit}' But how do i grep from line 6 till the end of the file or command output. Thanks, (3 Replies)
Discussion started by: Mr. Zer0
3 Replies

5. Shell Programming and Scripting

AWK-grep from line number to the end of file

Does anyone know how to use awk to act like grep from a particular line number to the end of file? I am using Solaris 10 and I don't have any GNU products installed. Say I want to print all occurrences of red starting at line 3 to the end of file. EXAMPLE FILE: red green red red... (1 Reply)
Discussion started by: thibodc
1 Replies

6. Homework & Coursework Questions

end of line error

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: #/bin/sh -xv #Author: Lauren Buecker #Date: September 28 2012 #Class COP3353 #Assignment: Assignment 4... (7 Replies)
Discussion started by: swimmerbhs
7 Replies

7. UNIX for Dummies Questions & Answers

Grep lines with numbers greater than 2 digits at the end of the line

I'm trying to grep lines where the digits at the end of each line are greater than digits. Tried this but it will only allow me to specify 2 digits. Any ideas would greatly be appreciated. grep -i '\<\{3,4,5\}\>' file ---------- Post updated at 05:58 PM ---------- Previous update was at 05:41... (1 Reply)
Discussion started by: jimmyf
1 Replies

8. Shell Programming and Scripting

Grep start and end line of each segments in a file

Cat file1 -------- ---------- SCHEMA.TABLE1 insert------- update----- ------------- ---------- SCHEMA.TABLE2 insert------- update----- ----------- ------------ SCHEMA.TABLE3 insert------- update----- ------------ grep -n SCHEMA > header_file2.txt (2 Replies)
Discussion started by: Veera_V
2 Replies

9. SCO

Grep to ignore suffix & find end of line

In COBOL, a hyphen can be used in a field name and in a specific program some field names would be identical to others except a suffix was added--sometimes a suffix to a suffix was used. For example, assume I am looking for AAA, AAA-BBB, and AAA-BBB-CCC and don't want to look at AAA-BBB-CCC... (7 Replies)
Discussion started by: wbport
7 Replies

10. Shell Programming and Scripting

Grep after - til the end of the line

Hi, i need to cat a file after # till the end of the file usually ill do cat /etc/somthing | grep -A999999 # but its not that professional thanks edit by bakunin: please use CODE-tags (or ICODE-tags) for code and data. Thank you. (9 Replies)
Discussion started by: batchenr
9 Replies

LEARN ABOUT REDHAT

podchecker

PODCHECKER(1)						 Perl Programmers Reference Guide					     PODCHECKER(1)

NAME

       podchecker - check the syntax of POD format documentation files

SYNOPSIS

       podchecker [-help] [-man] [-(no)warnings] [file ...]

OPTIONS AND ARGUMENTS

       -help   Print a brief help message and exit.

       -man    Print the manual page and exit.

       -warnings -nowarnings
	       Turn on/off printing of warnings. Repeating -warnings increases the warning level, i.e. more warnings are printed. Currently
	       increasing to level two causes flagging of unescaped "<,>" characters.

       file    The pathname of a POD file to syntax-check (defaults to standard input).

DESCRIPTION

       podchecker will read the given input files looking for POD syntax errors in the POD documentation and will print any errors it find to
       STDERR. At the end, it will print a status message indicating the number of errors found.

       Directories are ignored, an appropriate warning message is printed.

       podchecker invokes the podchecker() function exported by Pod::Checker Please see "podchecker()" in Pod::Checker for more details.

RETURN VALUE

       podchecker returns a 0 (zero) exit status if all specified POD files are ok.

ERRORS

       podchecker returns the exit status 1 if at least one of the given POD files has syntax errors.

       The status 2 indicates that at least one of the specified files does not contain any POD commands.

       Status 1 overrides status 2. If you want unambigouus results, call podchecker with one single argument only.

SEE ALSO

       Pod::Parser and Pod::Checker

AUTHORS

       Brad Appleton <bradapp@enteract.com>, Marek Rouchal <marek@saftsack.fs.uni-bayreuth.de>

       Based on code for Pod::Text::pod2text(1) written by Tom Christiansen <tchrist@mox.perl.com>

perl v5.8.0							    2003-02-18							     PODCHECKER(1)
All times are GMT -4. The time now is 12:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy