Sponsored Content
Full Discussion: AIX system dump analysis
Operating Systems AIX AIX system dump analysis Post 303034729 by vbe on Friday 3rd of May 2019 12:28:25 PM
Old 05-03-2019
I am a bit puzzled, and at home with no AIX box to check, I am surprised by the thread itself, if I were to deal with a machine suspicious reboot, I would start by having a look at the error reports:
Code:
errpt  -a

then after finding the cause or possible cause, and the diag in the report ( permanent /software etc...) I would start to scratch my head and search for more clues if needed, because truly from the core dump its hard work if you have no idea for what you are after..
So what did you find in the error report?
This User Gave Thanks to vbe For This Post:
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to do core dump analysis

Hi All, I am new to unix environment. Please tell me how to do coredump analysis. Please explain clearly with example. What are the details are available in the core. Thanks in advance (5 Replies)
Discussion started by: sip
5 Replies

2. UNIX for Advanced & Expert Users

Core Dump Analysis Using PStack and PMAP

Hello, I'm new to the group and this is my first post. I'm hoping someone can help me out. I have a core dump that I need to analyze from a Unix box and I've never done this sort of thing before. I was told to run a pmap and pstack on the core file which provided two different output files. ... (3 Replies)
Discussion started by: kimblebee
3 Replies

3. Solaris

use sunexplorer and vmcore analysis result instead of vmcore dump file itself.

in solaris 8 environment,frequently os panic happened and someone advise me check vmcore.:( for crash dump facility can we use SUNEXPLORER data collector package including with analyse result of vmcore like ? It may provides panic message included program counter address, perhaps ... (3 Replies)
Discussion started by: mahadib
3 Replies

4. AIX

How to do core dump analysis in AIX?

Please tell me some methods to analyse core dump in AIX.:) (2 Replies)
Discussion started by: Mythili
2 Replies

5. Red Hat

core dump analysis : __kernel_vsyscall ()

We have just enabled core dump on our RHEL5.7 OS. the java process is terminating very often so we enable core dump to analysis the issue and find below in core dump file. Core was generated by `/usr/java/jdk1.6.0_06//bin/java -server -Xms1536m -Xmx1536m -Xmn576m -XX:+Aggre'. Program... (0 Replies)
Discussion started by: pawankkamboj
0 Replies

6. UNIX for Dummies Questions & Answers

Learn Linux Core Dump Analysis

Can any body provide me some good link to learn to create and analyze linux user mode application / kernel module core dumps? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
IO::Async::Timer::Periodic(3pm) 			User Contributed Perl Documentation			   IO::Async::Timer::Periodic(3pm)

NAME
"IO::Async::Timer::Periodic" - event callback at regular intervals SYNOPSIS
use IO::Async::Timer::Periodic; use IO::Async::Loop; my $loop = IO::Async::Loop->new; my $timer = IO::Async::Timer::Periodic->new( interval => 60, on_tick => sub { print "You've had a minute "; }, ); $timer->start; $loop->add( $timer ); $loop->run; DESCRIPTION
This subclass of IO::Async::Timer implements repeating events at regular clock intervals. The timing may or may not be subject to how long it takes the callback to execute. Iterations may be rescheduled runs at fixed regular intervals beginning at the time the timer was started, or by a fixed delay after the previous code has finished executing. For a "Timer" object that only runs a callback once, after a given delay, see instead IO::Async::Timer::Countdown. A Countdown timer can also be used to create repeating events that fire at a fixed delay after the previous event has finished processing. See als the examples in "IO::Async::Timer::Countdown". EVENTS
The following events are invoked, either using subclass methods or CODE references in parameters: on_tick Invoked on each interval of the timer. PARAMETERS
The following named parameters may be passed to "new" or "configure": on_tick => CODE CODE reference for the "on_tick" event. interval => NUM The interval in seconds between invocations of the callback or method. Cannot be changed if the timer is running. first_interval => NUM Optional. If defined, the interval in seconds after calling the "start" method before the first invocation of the callback or method. Thereafter, the regular "interval" will be used. If not supplied, the first interval will be the same as the others. Even if this value is zero, the first invocation will be made asynchronously, by the containing "Loop" object, and not synchronously by the "start" method itself. reschedule => STRING Optional. Must be one of "hard", "skip" or "drift". Defines the algorithm used to reschedule the next invocation. "hard" schedules each iteration at the fixed interval from the previous iteration's schedule time, ensuring a regular repeating event. "skip" schedules similarly to "hard", but skips over times that have already passed. This matters if the duration is particularly short and there's a possibility that times may be missed, or if the entire process is stopped and resumed by "SIGSTOP" or similar. "drift" schedules each iteration at the fixed interval from the time that the previous iteration's event handler returns. This allows it to slowly drift over time and become desynchronised with other events of the same interval or multiples/fractions of it. Once constructed, the timer object will need to be added to the "Loop" before it will work. It will also need to be started by the "start" method. AUTHOR
Paul Evans <leonerd@leonerd.org.uk> perl v5.14.2 2012-10-24 IO::Async::Timer::Periodic(3pm)
All times are GMT -4. The time now is 11:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy