cancel
Showing results for 
Search instead for 
Did you mean: 

ASE 16 - signal 11 / stack trace - Snap::Validate() [KBA 3018138 ?]

Mark_A_Parsons
Contributor

Trying to get ASE 16 up and running on a new Ubuntu host but generating a signal 11 stack trace during initial build/startup of the instance.

The stack trace looks (to me) like the same one mentioned in KBA 3018138:

- stack trace commences right after 'kernel bucket manager consolidator online'

- stack trace includes the same function calls, including Snap::Validate() and SnapValidation

- dataserver process hangs with the same final message in the errorlog 'The internal timer is not progressing. If this message is generated multiple times, report to SAP Technical Support and restart the server (alarminterval=0).'

I don't currently have access to the support/firewall so was curious if anyone might know the resolution to this issue?

Thanks,

Mark

-----------------------

Details:

  • Ubuntu 20.04.1 LTS (running as a client/VM under VMware Workstation; host is Windows 10 Pro)
  • Adaptive Server Enterprise/16.0 SP03 PL07/EBF 28773 SMP/P/x86_64/SLES 11.1/ase160sp03pl07x/3595/64-bit/FBO/Wed May 22 02:09:02 2019
  • ASE errorlog: errorlog.txt

Accepted Solutions (1)

Accepted Solutions (1)

former_member188958
Active Contributor
0 Kudos

Hi Mark,

The issue hasn't been seen on 15.7, as far as I know.

Maybe it would work to temporarily alias dataserver to 'dataserver -T11889' to run srvbuildres?

Otherwise the upgrade from 15.7 approach should work.

I should also mention: while this traceflag is active, DO NOT turn on "enable simplified native access plans" with sp_configure. I'm not sure exactly what will happen, but it won't be good.

Cheers,
-bret

Answers (2)

Answers (2)

former_member188958
Active Contributor

Hi Mark,

The underlying CR 824104 isn't fixed yet ("The message, "Current process infected with signal 11 (SIGSEGV)", with a stack trace which includes the modules 'Snap::Validate' and 'SnapValidation' is reported in the SAP ASE error log when the 'simplified native access plan' fails to initialize at boot time even if it is not enabled.")

A workaround is listed as starting ASE with Traceflag -T11889 in the RUN_SERVER file.
This traceflag "Turns off SNAP struct validation mechanism at server boot time".

Cheers,
-bret

stevendawe
Explorer
0 Kudos
0 seconds ago

" workaround is listed as starting ASE with Traceflag -T11889 in the RUN_SERVER file."

This worked for me after spending 2 months scratching my head why my docker engine (version 20 only, 19 still worked) with every Sybase instance failed with this error on startup. My team are going to be happy now we can use the new Docker 20 features.

Thanks a lot!

Steve

dan_thrall
Participant
0 Kudos

Hi Mark,

The Simplified Native Access Plan is present in 16.0 and not on 15.7. Because of this, there's no need to use this trace flag in 15.7.

Best Regards

Dan