Hi All,
I'm deffently not a Unix specialist so be Gentel.
I need to parse a Log file that looks like that:
2006-06-12 01:00:00,463 ERROR {cleanLoggersFiles} General Error
comverse.compas.shared.exceptions.SystemParametersException: Error in reading parameter FileLocation
at... (4 Replies)
Hi Experts,
Im a new bee for scripting,
I would ned to do the following via linux shell scripting, I have an application which throws a log file, on each action of a particular work with the application, as sson as the action is done, the log file would vanish or stops updating there, the... (2 Replies)
I need help in parsing the following log files.
10 Apr 2009 0:16:16 * name: Tuna Belly Format: Well done, Price: 999 only
10 Apr 2009 0:16:16 * name: Roast Beef Format: Raw, Price: 55 c
10 Apr 2009 0:16:16 * name: Pasta Format: Dry, Price: 88.43 only
etcetc
I need to parse this... (8 Replies)
Hello members,
I have some doubts on how to write a script that can reports success / failure of a batch job ?
1. Run a batch job:
2. Wait and search for a particular string in the Log file:
tail -f log01*.txt | egrep -v "^SUCCESSFUL"
echo "continue with the other tasks"
... (1 Reply)
Hi All,
In vim, when we press ^G, the file name is displayed at the bottom of the screen and as soon as we enter into some other mode (say e.g. Insert), the file name is replaced by the words "Insert". I was just wondering whether it is possible to continuously show the file name no matter which... (3 Replies)
Working on a script that inputs an IP, parses and outputs to another file.
A Sample of the log is as follows:
I need the script to be able to input IP and print the data in an output file in the following format or something similar:
Thanks for any help you can give me! (8 Replies)
Hello all,
I am new to scripting and I have written a script that performs an Rsync on my NAS and then moves on to send me an email with the status etc. The problem is that I think Rsync is taking to long to complete and the IF statement is timing out, as it doesn't appear to move on.
Here... (1 Reply)
Hi,
I am a newbie to scripting.
I have multiple log files (saved as .gz) in a directory that looks like this
01-01-2013 10:00 pn: 123
01-01-2013 10:00 sn: 987
01-01-2013 10:00 Test1
01-01-2013 10:00 Result: Pass
01-01-2013 10:00 Time: 5:00
01-01-2013 10:00 Test2
01-01-2013 10:00... (3 Replies)
Hi,
I have a log file that looks like below and I am wanting to know if there is a better way of parsing it from how I am doing it right now.
I am looking for when an application service is OFFLINE and ONLINE. This log file is getting written into every 30 minutes
... (1 Reply)
Hi
I have written below log monitoring script to egrep multiple words and redirect the output to a text file and its working fine but I want to add some more below given functionality to it, which is very advance and im not very good in it, so please help if you can :)
I am egrepping all the... (1 Reply)
Discussion started by: scazed
1 Replies
LEARN ABOUT CENTOS
xfs_logprint
xfs_logprint(8) System Manager's Manual xfs_logprint(8)NAME
xfs_logprint - print the log of an XFS filesystem
SYNOPSIS
xfs_logprint [ options ] device
DESCRIPTION
xfs_logprint prints the log of an XFS filesystem (see xfs(5)). The device argument is the pathname of the partition or logical volume con-
taining the filesystem. The device can be a regular file if the -f option is used. The contents of the filesystem remain undisturbed.
There are two major modes of operation in xfs_logprint.
One mode is better for filesystem operation debugging. It is called the transactional view and is enabled through the -t option. The
transactional view prints only the portion of the log that pertains to recovery. In other words, it prints out complete transactions
between the tail and the head. This view tries to display each transaction without regard to how they are split across log records.
The second mode starts printing out information from the beginning of the log. Some error blocks might print out in the beginning because
the last log record usually overlaps the oldest log record. A message is printed when the physical end of the log is reached and when the
logical end of the log is reached. A log record view is displayed one record at a time. Transactions that span log records may not be
decoded fully.
OPTIONS -b Extract and print buffer information. Only used in transactional view.
-c Attempt to continue when an error is detected.
-C filename
Copy the log from the filesystem to the file filename. The log itself is not printed.
-d Dump the log from front to end, printing where each log record is located on disk.
-D Do not decode anything; just print data.
-e Exit when an error is found in the log. Normally, xfs_logprint tries to continue and unwind from bad logs. However, sometimes it
just dies in bad ways. Using this option prevents core dumps.
-f Specifies that the filesystem image to be processed is stored in a regular file at device (see the mkfs.xfs(8)-d file option).
This might happen if an image copy of a filesystem has been made into an ordinary file with xfs_copy(8).
-l logdev
External log device. Only for those filesystems which use an external log.
-i Extract and print inode information. Only used in transactional view.
-q Extract and print quota information. Only used in transactional view.
-n Do not try and interpret log data; just interpret log header information.
-o Also print buffer data in hex. Normally, buffer data is just decoded, so better information can be printed.
-s start-block
Override any notion of where to start printing.
-t Print out the transactional view.
-v Print "overwrite" data.
-V Prints the version number and exits.
SEE ALSO mkfs.xfs(8), mount(8).
xfs_logprint(8)