Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

kernel FATAL: NULL Pss on STACK_OVERFLOW

4 posts in Windows NT Last posting was on 2000-05-03 17:45:19.0Z
M.A.Moraes Posted on 2000-04-28 00:33:17.0Z
From: "M.A.Moraes" <marco.moraes@capes.gov.br>
Subject: kernel FATAL: NULL Pss on STACK_OVERFLOW
Date: Thu, 27 Apr 2000 21:33:17 -0300
Lines: 15
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID: <h6pOHoKs$GA.262@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.nt
NNTP-Posting-Host: 200.252.136.178
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2245
Article PK: 1089677

Hi,

Does anybody knows something about this message (kernel FATAL: NULL Pss on
STACK_OVERFLOW) in errorlog ?
After reboot the server , some time away it sends this new message (kernel
timeslice -500, current process infected ) without the value for %d after
the process infected message.
In the product manuals I don't see anything about this. The server is a
Adaptive Server Enterprise/11.5.1.1/P/NT/OS 4.00/SWR 8916 ESD 5/fbu/Wed Mar
1 17:23:31 PST 2000 and hangs up after this message.

Thanks in advance.


Jean-Pierre CALLANT Posted on 2000-04-28 08:04:56.0Z
Message-ID: <39094628.B2202C1D@csi.com>
Date: Fri, 28 Apr 2000 10:04:56 +0200
From: Jean-Pierre CALLANT <callant@csi.com>
Organization: ACMS
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: fr,en
MIME-Version: 1.0
Subject: Re: kernel FATAL: NULL Pss on STACK_OVERFLOW
References: <h6pOHoKs$GA.262@forums.sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 31
NNTP-Posting-Host: acms-nat.acms.asso.fr 212.11.18.227
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2242
Article PK: 1089673

Hi,

I have seen this message before and in my case this was due to the fact that
the parameters I had set for open objects, open databases, and open indexes
were to low.
I also had to increase to CPU GRACE TIME from the default value of 500 to 1500.

You can check to values for open object using the following stored procedures :

exec sp_countmetadata 'open objects'
exec sp_countmetadata 'open databases'
exec sp_countmetadata 'open indexes'

exec sp_monitorconfig 'open objects'
exec sp_monitorconfig 'open indexes'
exec sp_monitorconfig 'open databases'
exec sp_monitorconfig 'aux scan descriptors'



Jean-Pierre CALLANT

"M.A.Moraes" wrote:

> Hi,
>
> Does anybody knows something about this message (kernel FATAL: NULL Pss on
> STACK_OVERFLOW) in errorlog ?
> After reboot the server , some time away it sends this new message (kernel
> timeslice -500, current process infected ) without the value for %d after
> the process infected message.
> In the product manuals I don't see anything about this. The server is a
> Adaptive Server Enterprise/11.5.1.1/P/NT/OS 4.00/SWR 8916 ESD 5/fbu/Wed Mar
> 1 17:23:31 PST 2000 and hangs up after this message.
>
> Thanks in advance.


Moraes Posted on 2000-05-02 23:00:43.0Z
From: "Moraes" <marcoant@capes.gov.br>
References: <h6pOHoKs$GA.262@forums.sybase.com> <39094628.B2202C1D@csi.com>
Subject: Re: kernel FATAL: NULL Pss on STACK_OVERFLOW
Date: Tue, 2 May 2000 20:00:43 -0300
Lines: 15
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID: <FZEDtrIt$GA.182@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.nt
NNTP-Posting-Host: 200.252.136.178
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2209
Article PK: 1089644

Thanks Callant for your help.
Im my case , the error was in a production dataserver and I spent my weekend
and the labor holliday yesterday to configure and load a new machine with my
databases.This was my option because the log messages of the raid 5 notifies
an access disk error in the same period of the message I've reported.
And in relation of the parameters that you mentioned, the only one that with
default value was the CPU GRACE TIME, because the others I've adjusted it.

But I'm still curious with the ocurrence.

Bye and thank you again.

Moraes


Gerardo A. Posted on 2000-05-03 17:45:19.0Z
From: "Gerardo A." <garroyo@nacion.co.cr>
References: <h6pOHoKs$GA.262@forums.sybase.com> <39094628.B2202C1D@csi.com> <FZEDtrIt$GA.182@forums.sybase.com>
Subject: Re: kernel FATAL: NULL Pss on STACK_OVERFLOW
Date: Wed, 3 May 2000 11:45:19 -0600
Lines: 28
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <L$ZpsgSt$GA.263@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.nt
NNTP-Posting-Host: 196.40.18.21
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2203
Article PK: 1089636

Hi!

Talk with Sybase Support, we report the same case several weeks ago and
there is a bug report (however it is necesary check the stack trace)

"Moraes" <marcoant@capes.gov.br> wrote in message
news:FZEDtrIt$GA.182@forums.sybase.com...
> Thanks Callant for your help.
> Im my case , the error was in a production dataserver and I spent my
weekend
> and the labor holliday yesterday to configure and load a new machine with
my
> databases.This was my option because the log messages of the raid 5
notifies
> an access disk error in the same period of the message I've reported.
> And in relation of the parameters that you mentioned, the only one that
with
> default value was the CPU GRACE TIME, because the others I've adjusted it.
>
> But I'm still curious with the ocurrence.
>
> Bye and thank you again.
>
> Moraes
>
>