Server hung, is this a stack trace? Post: 302894354

10 More Discussions You Might Find Interesting

1. Programming

Core file without a readable stack trace

I am using gdb to examine a core file but the output contains only the method addresses in hex. Is there anyway to translate these addresses to a human-readable form? :confused:

2. Programming

printing a stack trace with backtrace

I am trying to print a stack trace programatically using backtrace and backtrace_symbols. The problem is that the stack being printed in a mangled format. Is there a way to get the output in more of a human readable form? I am using Red Hat and the program is written in c++.

3. UNIX for Advanced & Expert Users

help required - stack trace

Hi all, One of our programs written in Java, produced this logfile. This job runs 48 threads and only one thread failed with this error. The code is a blackbox(external product), so cant look at the source code. From what I can infer from the log, the job was trying to write the log messages into...

4. Filesystems, Disks and Memory

get stack trace from C program on Solaris 8

I'm on solaris 8. I need to check the stack trace inside my C program. I don't have printstack or walkstack. I tested getcontext and it works. But how do I get the symbols from "stack_t" ? Help please. Many thanks!

5. Solaris

Need to retrieve stack trace from core using mdb

Hello , I use Solaris 5.10 . I have huge core file , 48 GB , resulted from an application that was running and got crashed with SIGSEGV. On my system only mdb works. Please help me to retrieve the stack trace from this core file. I am novice to mdb and its nuaunces. Please help me with...

6. AIX

How to get the stack trace using kdb?

Hi All, I am trying to debug my core file using kdb. When I try to get the stack trace I am facing this error. core mapped from @ 700000000000000 to @ 70000000306fc04 Preserving 1680415 bytes of symbol table Dump does not start with valid magic number WARNING: Possibly truncated or...

7. Shell Programming and Scripting

Stack Trace

Hi All Thought it would be kind of fun to implement a stack trace for a shell script that calls functions within a sub shell. This is for bash under Linux and probably not portable - #! /bin/bash error_exit() { echo "=======================" echo $1 echo...

8. UNIX for Dummies Questions & Answers

View User Mode Call Stack of Hung Process

I have a multithreaded usermode program(actually a daemon) which is in hanged state. To debug it I tried attaching the process to gdb, but the gdb hangs. gstack also gets hanged. I peeped into the proc file system and saw the process to be in sleeping state. /proc/sysrq-trigger I guess...

9. Programming

View Stack Trace of different cores

I have a C program which is running as daemon and has some threads. The program is running on dual core cpu and it may happen that different threads may run on different cpu core. The problem is sometimes it crashes with some heap memory corruption probably between threads. GDB command(t a a...

10. Shell Programming and Scripting

Java stack trace parser in awk

I want the developers to get a mail with Java stack traces on a daily bases. When something is flaged as known issue and will get a fix but mean while this does not need to get sent each dayl. This is what I got so far. It's a bash script that runs some AWK in it. To get the files that needs to...

LEARN ABOUT CENTOS

redhat-upgrade-tool-cli

REDHAT-UPGRADE-TOOL(8)					  redhat-upgrade-tool User Manual				    REDHAT-UPGRADE-TOOL(8)

NAME

       redhat-upgrade-tool - Red Hat Upgrade tool

SYNOPSIS

       redhat-upgrade-tool [OPTIONS] SOURCE

DESCRIPTION

       redhat-upgrade-tool is the Red Hat Upgrade tool.

       The redhat-upgrade-tool client runs on the system to be upgraded. It determines what packages are needed for upgrade and gathers them from
       the source(s) given. It also fetches and sets up the boot images needed to run the upgrade and sets up the system to perform the upgrade at
       next boot.

       The actual upgrade takes place when the system is rebooted, using the boot images set up by redhat-upgrade-tool. The upgrade initrd starts
       the existing system (mostly) as normal, lets it mount all the local filesystems, then starts the upgrade.

       When the upgrade finishes, it reboots the system into the newly-upgraded OS.

OPTIONS

   Optional arguments
       -h, --help
	   Show a help message and exit.

       -v, --verbose
	   Print more info.

       -d, --debug
	   Print lots of debugging info.

       --debuglog DEBUGLOG
	   Write debugging output to the given file. Defaults to /var/log/redhat-upgrade-tool.log.

       --reboot
	   Automatically reboot to start the upgrade when ready.

   SOURCE
       These options tell redhat-upgrade-tool where to look for the packages and boot images needed to run the upgrade. At least one of these
       options is required.

       --device [DEV]
	   Device or mountpoint of mounted install media. If DEV is omitted, redhat-upgrade-tool will scan all currently-mounted removable devices
	   (USB disks, optical media, etc.)

       --iso ISO
	   Installation image file.

       --network VERSION
	   Online repos matching VERSION (a number or "rawhide")

       Multiple sources may be used, if desired.

   Additional options for --network
       --enablerepo REPOID
	   Enable one or more repos (wildcards allowed).

       --disablerepo REPOID
	   Disable one or more repos (wildcards allowed).

       --addrepo REPOID=[@]URL
	   Add the repo at URL. Prefix URL with @ to indicate that the URL is a mirrorlist.

       --instrepo REPOID
	   Get upgrader boot images from the repo named REPOID. The repo must contain a valid .treeinfo file which points to the location of
	   usable kernel and upgrade images.

   Cleanup commands
       --resetbootloader
	   Remove any modifications made to bootloader configuration.

       --clean
	   Clean up everything written by redhat-upgrade-tool.

EXAMPLES

       redhat-upgrade-tool --network 7.0 --instrepo <repo URL>

       Upgrade to RHEL 7.0 by downloading all needed packages and data from the specified repository.

       redhat-upgrade-tool --device --network 7.0

       Upgrade to RHEL 7.0 using install media mounted somewhere on the system, fetching updates from the network if needed.

EXIT STATUS

       0
	   Success.

       1
	   Cancelled by user, failure writing files to disk, or other unknown error

       2
	   Failed to download/copy files from the given SOURCE

       3
	   RPM upgrade transaction test failed

BUGS

       The --iso image must be on a filesystem listed in /etc/fstab.

AUTHORS

       Will Woods <wwoods@redhat.com>

redhat-upgrade-tool						    11/08/2013						    REDHAT-UPGRADE-TOOL(8)