Server crashed with Signal 10 error..
Emanuel Marciniak
The environment is SQL v. 11.0.3.3 (EBF 7936) on Alpha OpenVms v.7.1.
The server crashed today with Signal 10 error. Trace is included below.
The server is
up and running without the problem now (and so far). Any idea what cause
this crash..??
Thank you in advance for any hint..
Emanuel Marciniak
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
00:1999/06/18 10:57:15.25 kernel nast_writeprep: invalid send count 0
02:1999/06/18 10:57:15.27 server Process id 118 killed by Hostname ,
Host process id 25202555.
00:1999/06/18 10:57:15.36 kernel %SYSTEM-F-ACCVIO, access violation,
reason mask=00, virtual address=000000000001C548, PC=0000000000295CEC,
PS=0000001B
00:1999/06/18 10:57:15.42 kernel current process (0x50005) infected
with Signal 10
00:1999/06/18 10:57:15.54 kernel kechkfault: engine 0: scheduler
infected with signal 10
00:1999/06/18 10:57:15.63 kernel os_backtrace - pc 0x1e70fc / pd
00:1999/06/18 10:57:15.67 kernel r02 = 0x23e08, r03 = 0x50005, r04 =
0x1
00:1999/06/18 10:57:15.73 kernel r05 = 0x14, r06 = 0x4d0850, r07 =
0x4d0850
00:1999/06/18 10:57:15.77 kernel r08 = 0x7f9e060, r09 = 0x4ebf00, r29 =
0x69f2e0
00:1999/06/18 10:57:15.82 kernel r30 = 0x69f2e0
00:1999/06/18 10:57:15.94 kernel -----
00:1999/06/18 10:57:16.00 kernel ucbacktrace - pc 0x162dd0 / pd
00:1999/06/18 10:57:16.06 kernel r02 = 0x17280, r03 = 0x50005, r04 =
0x1
00:1999/06/18 10:57:16.14 kernel r05 = 0x7ea3860, r29 = 0x69f340, r30 =
0x69f340
00:1999/06/18 10:57:16.18 kernel -----
00:1999/06/18 10:57:16.23 kernel keipanic - pc 0x16491c / pd
00:1999/06/18 10:57:16.29 kernel r02 = 0x175c0, r03 = 0x69f388, r04 =
0xc378
00:1999/06/18 10:57:16.35 kernel r29 = 0x69f380, r30 = 0x69f380
00:1999/06/18 10:57:16.44 kernel -----
00:1999/06/18 10:57:16.51 kernel kechkfault - pc 0x12d27c / pd
00:1999/06/18 10:57:16.57 kernel r29 = 0x69f5f0, r30 = 0x69f5f0
00:1999/06/18 10:57:16.61 kernel -----
00:1999/06/18 10:57:16.66 kernel kisignal_vms - pc 0x170100 / pd
00:1999/06/18 10:57:16.74 kernel r02 = 0x192c0, r29 = 0x69f610, r30 =
0x69f610
00:1999/06/18 10:57:16.78 kernel -----
00:1999/06/18 10:57:16.85 kernel **EXTERNAL** - pc 0xa620659c /
00:1999/06/18 10:57:16.92 kernel r29 = 0x69f650, r30 = 0x69f640
00:1999/06/18 10:57:16.97 kernel -----
00:1999/06/18 10:57:17.02 kernel tcp_nwrite - pc 0x295cec / pd
00:1999/06/18 10:57:17.14 kernel r02 = 0x39548, r03 = 0x7f9fba0, r04 =
0x8e9b7b4
00:1999/06/18 10:57:17.21 kernel r05 = 0x7f40a80, r06 = 0x1c540, r07 =
0x0
00:1999/06/18 10:57:17.25 kernel r29 = 0x69f928, r30 = 0x69f8f8
00:1999/06/18 10:57:17.32 kernel -----
00:1999/06/18 10:57:17.35 kernel ksrequest_spost - pc 0x17ad1c / pd
00:1999/06/18 10:57:17.39 kernel r02 = 0x1a318, r03 = 0x7f9fba0, r04 =
0x7fcc5bc
00:1999/06/18 10:57:17.45 kernel r05 = 0x7f40a80, r06 = 0x5faa24, r07 =
0x0
00:1999/06/18 10:57:17.51 kernel r08 = 0x7f9e060, r09 = 0x4ebf00, r10 =
0x0
00:1999/06/18 10:57:17.59 kernel r29 = 0x69f978, r30 = 0x69f978
00:1999/06/18 10:57:17.63 kernel -----
00:1999/06/18 10:57:17.70 kernel nast_writepost - pc 0x17b1c4 / pd
00:1999/06/18 10:57:17.75 kernel r02 = 0x1a2f0, r03 = 0x7f4c780, r04 =
0x94cbf
00:1999/06/18 10:57:17.81 kernel r05 = 0x7fa0b60, r06 = 0x5dc100, r07 =
0x8e962b8
00:1999/06/18 10:57:17.94 kernel r29 = 0x69f9d8, r30 = 0x69f9d8
00:1999/06/18 10:57:17.97 kernel -----
00:1999/06/18 10:57:18.03 kernel ksrequest_spost - pc 0x17ad4c / pd
00:1999/06/18 10:57:18.08 kernel r02 = 0x1a318, r03 = 0x7fa0b60, r04 =
0x8e962b8
00:1999/06/18 10:57:18.13 kernel r05 = 0x7f4c780, r06 = 0x5fa9c0, r07 =
0x5dc100
00:1999/06/18 10:57:18.17 kernel r08 = 0x7f9dfe0, r09 = 0x4ebf00, r10 =
0x0
00:1999/06/18 10:57:18.31 kernel r29 = 0x69fa28, r30 = 0x69fa28
00:1999/06/18 10:57:18.36 kernel -----
00:1999/06/18 10:57:18.41 kernel nast_writepost - pc 0x17b1c4 / pd
00:1999/06/18 10:57:18.47 kernel r02 = 0x1a2f0, r03 = 0x7f64a80, r04 =
0x94cbf
00:1999/06/18 10:57:18.53 kernel r05 = 0x7f9f080, r06 = 0x5dc100, r07 =
0x8e9b760
00:1999/06/18 10:57:18.59 kernel r29 = 0x69fa88, r30 = 0x69fa88
00:1999/06/18 10:57:18.71 kernel -----
00:1999/06/18 10:57:18.80 kernel tcp_nwrite_defer - pc 0x295f30 / pd
00:1999/06/18 10:57:18.86 kernel r02 = 0x394e8, r03 = 0x7f9f080, r04 =
0x7f64a80
00:1999/06/18 10:57:18.91 kernel r05 = 0x2000001, r06 = 0x1, r07 =
0x200
00:1999/06/18 10:57:19.01 kernel r29 = 0x69fad8, r30 = 0x69fad8
00:1999/06/18 10:57:19.14 kernel -----
00:1999/06/18 10:57:19.19 kernel kadodeferred - pc 0x161d68 / pd
00:1999/06/18 10:57:19.25 kernel r02 = 0x5e6a00, r29 = 0x69fb28, r30 =
0x69fb28
00:1999/06/18 10:57:19.32 kernel -----
00:1999/06/18 10:57:19.37 kernel kpsched - pc 0x176a48 / pd
00:1999/06/18 10:57:19.44 kernel r02 = 0x19b70, r03 = 0x4e76f0, r04 =
0x5e6a00
00:1999/06/18 10:57:19.48 kernel r05 = 0xeb720, r06 = 0x0, r07 =
0x4ebf00
00:1999/06/18 10:57:19.52 kernel r08 = 0x4ebf10, r09 = 0x4e77b0, r10 =
0x4e9b80
00:1999/06/18 10:57:19.57 kernel r11 = 0x7f0f060, r12 = 0x0, r13 =
0x4e9b90
00:1999/06/18 10:57:19.62 kernel r14 = 0x0, r15 = 0xf58e0, r29 =
0x69fb48
00:1999/06/18 10:57:19.68 kernel r30 = 0x69fb48
00:1999/06/18 10:57:19.74 kernel -----
00:1999/06/18 10:57:19.91 kernel kistartup - pc 0x1774ec / pd
00:1999/06/18 10:57:20.00 kernel r02 = 0x19b70, r03 = 0x1765e8, r04 =
0x0
00:1999/06/18 10:57:20.05 kernel r05 = 0x0, r06 = 0x0, r07 = 0x0, r08 =
0x0
00:1999/06/18 10:57:20.09 kernel r09 = 0x0, r10 = 0x0, r11 = 0x0, r12 =
0x0
00:1999/06/18 10:57:20.17 kernel r13 = 0x0, r14 = 0x0, r15 = 0x0, r29 =
0x7ae49e90
00:1999/06/18 10:57:20.20 kernel r30 = 0x69fbd8
00:1999/06/18 10:57:20.26 kernel -----
00:1999/06/18 10:57:20.32 kernel mainvms - pc 0x120b54 / pd
00:1999/06/18 10:57:20.35 kernel r02 = 0x102a0, r03 = 0x0, r04 = 0x0,
r05 = 0x0
00:1999/06/18 10:57:20.42 kernel r06 = 0x1, r07 = 0x4ec020, r08 = 0x0
00:1999/06/18 10:57:20.64 kernel r09 = 0x57c72c, r10 = 0x0, r29 =
0x7ae4b200
00:1999/06/18 10:57:20.69 kernel r30 = 0x7ae4b200
00:1999/06/18 10:57:20.74 kernel -----
00:1999/06/18 10:57:20.80 kernel **EXTERNAL** - pc 0x7af48294 /
00:1999/06/18 10:57:20.89 kernel r02 = 0x7af024a0, r03 = 0x102a0, r15 =
0x7ae4b950
00:1999/06/18 10:57:20.94 kernel r29 = 0x7ae4b7b0, r30 = 0x7ae4b7b0
00:1999/06/18 10:57:20.99 kernel -----
00:1999/06/18 10:57:21.04 kernel **EXTERNAL** - pc 0x80046cc0 /
00:1999/06/18 10:57:21.11 kernel r02 = 0x10048, r03 = 0x57c028, r04 =
0x7ffcf818
00:1999/06/18 10:57:21.24 kernel r05 = 0x7ffcf938, r06 = 0x0, r07 = 0x1
00:1999/06/18 10:57:21.29 kernel r08 = 0x7ffac208, r09 = 0x7ae4b950
00:1999/06/18 10:57:21.35 kernel r10 = 0x7ffad238, r11 = 0x7ffce3e0,
r12 = 0x0
00:1999/06/18 10:57:21.40 kernel r13 = 0x7af08cf8, r29 = 0x7ae4b7f0
00:1999/06/18 10:57:21.45 kernel r30 = 0x7ae4b7e0
00:1999/06/18 10:57:21.52 kernel -----
00:1999/06/18 10:57:21.59 kernel **EXTERNAL** - pc 0x80046cc0 /
00:1999/06/18 10:57:21.67 kernel r02 = 0x10048, r03 = 0x57c028, r04 =
0x7ffcf818
00:1999/06/18 10:57:21.74 kernel r05 = 0x7ffcf938, r06 = 0x0, r07 = 0x1
00:1999/06/18 10:57:21.84 kernel r08 = 0x7ffac208, r09 = 0x7ffac410
00:1999/06/18 10:57:21.92 kernel r10 = 0x7ffad238, r11 = 0x7ffce3e0
00:1999/06/18 10:57:22.04 kernel r13 = 0x7af08ab0, r29 = 0x7ae4b8b0
00:1999/06/18 10:57:22.10 kernel r30 = 0x7ae4b890
00:1999/06/18 10:57:22.20 kernel -----
00:1999/06/18 10:57:22.27 kernel **EXTERNAL** - pc 0x4b0de4 / pd
00:1999/06/18 10:57:22.44 kernel r29 = 0x7ae4b940, r30 = 0x7ae4b940
00:1999/06/18 10:57:22.54 kernel -----
00:1999/06/18 10:57:22.60 kernel end of stack trace, kernel service
process: kpid 327685
00:1999/06/18 10:57:22.64 kernel ueshutdown: exiting
weed...@my-deja.com
I am not sure how Unix signals map to VMS, but signal 10 is a bus error
(in Unix). I think that the most important part for you is the line
before
00:1999/06/18 10:57:15.36 kernel %SYSTEM-F-ACCVIO, access violation,
reason mask=00, virtual address=000000000001C548, PC=0000000000295CEC,
PS=0000001B
The "%SYSTEM-F-ACCVIO" is telling you that you suffered a *fatal*
access violation. Just about the only thing that you can do with this
is to open a case with Sybase.
dowen
In article <376A6E28...@berniann.com>,
--
David Owen 7, Stradbrooke Rise SW, Calgary, AB, Canada
dowen@<spam-me-not>cadvision.com
You needn't be well to wealthy, but you gotta be whole to be holy.
Greg Lake, Works Vol 1
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
cro...@ptahsoft.ch
It seems that the scheduler within your server got an ACCVIO
(Segmentation Violation, or Signal 11 on UNIX):
> 00:1999/06/18 10:57:15.54 kernel kechkfault: engine 0: scheduler
infected with signal 10
That's why your entire server crashed (and not only a connection)
Is it possible that you are useing RPC's to other servers, which the
scheduler has to dispatch or terminate initiated IO on the net.
Do you use DECnet as well as TCP/IP ?
Make sure that your server use TCP/IP as primary master listener, which
means put the line "master tcp " in front of "master decnet", same on
the remote server.
Second, check if you don't have dedundant servers is sysservers, which
means different remote server names for one and the same physical
remote server.
Quota ?? Possibly not, but doublecheck anyway ASTLM and TQLM (and maybe
FILLM, not related, but which is in a lot of cases too low).
If you need more help, you should call Tech Support, maybe they ask you
to set up CSMD to perform a Triggered Shared Memory Dump in case this
reoccurs, which they can analyze in detail.
Hope this helps
/Anton
In article <376A6E28...@berniann.com>,
Emanuel Marciniak <ema...@berniann.com> wrote: