Page 1 of 1
Re: SIGSEGV, SIGBUS
Posted: Thu Dec 01, 2005 9:02 am
by Ultramundane
Usually bad code that caused a segmentation fault. It could also be failing hardware. Did anything get logged by the error daemon?
Posted: Thu Dec 01, 2005 3:37 pm
by ray.wurlod
The UNIX command
man signal will inform you about signals. Here are the most common ones. An asterisk indicates that a core image is dumped.
Code: Select all
Value Description
1 (SIGHUP) hangup
2 (SIGINT) interrupt
3* (SIGQUIT) quit
4* (SIGILL) illegal instruction
5* (SIGTRAP) trace trap
6* (SIGIOT) IOT instruction
7* (SIGEMT) EMT instruction
8* (SIGFPE) floating-point exception
9 (SIGKILL) kill (cannot be caught or ignored)
10* (SIGBUS) bus error
11* (SIGSEGV) segmentation violation
12* (SIGSYS) bad argument to system call
13 (SIGPIPE) write on a pipe with no one to read it
14 (SIGALRM) alarm clock
15 (SIGTERM) software termination signal
16 (SIGURG) urgent condition present on socket
17 (SIGSTOP) stop (cannot be caught or ignored)
18 (SIGTSTP) stop signal generated from keyboard
19 (SIGCONT) continue after stop
20 (SIGCHLD) child status has changed
21 (SIGTTIN) background read attempted from control terminal
22 (SIGTTOU) background write attempted to control terminal
23 (SIGIO) I/O is possible on a descriptor
24 (SIGXCPU) CPU time limit exceeded
25 (SIGXFSZ) file size limit exceeded
26 (SIGVTALRM) virtual time alarm
27 (SIGPROF) profiling timer alarm
Posted: Sat Dec 03, 2005 6:31 am
by kumar_s
HI,
I guess this would be an intermintent issue.
Pls let know what happens if you reset and resun if no load in the server.
-Kumar
Posted: Sat Dec 24, 2005 4:52 am
by kumar_s
I guess you might have approached australian support for this.
We too got the same resolution
IBM did develop a patch, which fixed these problems
You received any patch for this
I wish java code for jobmon could be upgraded.
-Kumar
Posted: Tue Dec 27, 2005 12:39 pm
by rhys.jones@target.com
Sorry, good ol' USA support engineers.
Yes we did receive a patch, and it resolved the SIGBUS/SIGSEGV errors that were coming from this bug. We now have been able to reenable time-based monitoring. Check with your support engineer for the patch under ecase e74035. We received a patch for both AIX and Sun.
Posted: Tue Dec 27, 2005 8:15 pm
by kumar_s
Hi,
Is the patch doing somthing more than, truning off the job mon, and converting time base monitoring to size base monitoring???
I guess i cannot directly go ahead and access this case no right?
-Kumar
Posted: Mon Jan 02, 2006 11:32 am
by bmadhav
U could be having a memory leak when you're job is running and the operating system is issuing a hard kill when all the memory is chewed up by the datastage process. U shd monitor memory usage when ur job starts up.
As the others suggested, u shd contact IBM tech support and send them the job log.