Sponsored Content
Full Discussion: help required - stack trace
Top Forums UNIX for Advanced & Expert Users help required - stack trace Post 302084570 by ranj@chn on Friday 11th of August 2006 10:33:56 AM
Old 08-11-2006
Not anywhere

No Jim;

The job is running fine for the past 2 days. We raised the issue with our Sysdamins and they havent got back to us. It looks like they are running 2 similar applications(a new project in Acceptance box) and both have multiple threads running at the same time. Our DBA's advise was that after the testing one App would be switched off and this issue shouldnt occur.

So, what we have determined to do in case of job failure is to check the system status at that moment and the jobs currently running and try to rerun the job after some time when the activity on the system has decreased.

I hope that will help.

Thanks for your help on this. I will get back if we find anything else.
 

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: (0 Replies)
Discussion started by: ciregbu
0 Replies

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++. (2 Replies)
Discussion started by: dmirza
2 Replies

3. Shell Programming and Scripting

Need to capture ERROR msg and stack trace

Hi all, I was hoping someone can point me in the right direction. I'm trying to filter out errors from a web log- any lines with ERROR in it. I know I could simply use the grep command to do this. However, there are times when a stack trace follows the error line. I would like to capture these... (2 Replies)
Discussion started by: gswhoops
2 Replies

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! (4 Replies)
Discussion started by: rydahl
4 Replies

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... (2 Replies)
Discussion started by: rmv
2 Replies

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... (2 Replies)
Discussion started by: Sachin1987
2 Replies

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... (4 Replies)
Discussion started by: steadyonabix
4 Replies

8. 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... (2 Replies)
Discussion started by: rupeshkp728
2 Replies

9. Linux

Server hung, is this a stack trace?

Hi everyone, Our Red Hat server hung yesterday, and I managed to log into the console and see the following message: RIP: 0010: mwait_idle_with_hints+0x66/ 0x67 RSP: 0018:ffffffff80457f40 EFLAGS: 00000046 RAX: 0000000000000010 RBX: ffff810c20075910 RCX: 0000000000000001 RDX:... (6 Replies)
Discussion started by: badoshi
6 Replies

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... (6 Replies)
Discussion started by: chipmunken
6 Replies
queuedefs(4)						     Kernel Interfaces Manual						      queuedefs(4)

NAME
queuedefs - queue description file for at, batch, and crontab SYNOPSIS
DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue. The format of the lines are as follows: [njob[nice[nwait The fields in this line are: q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by (see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined queues. njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed by setting the variable to 1 in the file. nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). The default value is 2. nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's queue, or because more than 100 jobs were running in all the queues (see njob above). EXAMPLES
Consider the following file: The file is interpreted as follows: The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of 1. Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds before trying again to run it (see cron(1M)). The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2. If a job cannot be run because too many other jobs are running, will wait 90 seconds before trying again to run it. All other queues can have up to 100 jobs running simultaneously. They will be run with a value of 2, and if a job cannot be run because too many other jobs are running, will wait 60 seconds before trying again to run it. SEE ALSO
at(1), nice(1), crontab(1), cron(1M), proto(4). STANDARDS CONFORMANCE
queuedefs(4)
All times are GMT -4. The time now is 04:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy