Sybase 16.0 DB is not getting setup properly on Docker Desktop for Mac

[veekay98]

Getting this error when trying to login to isql
CT-LIBRARY error:
ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed

[veekay98]

Here is the output of the command docker run -p 5000:5000 --rm datagrip/sybase:latest

STARTING... (about 30 sec)
=============== SYBASE STARTED ==========================
SYBASE_USER: tester
SYBASE_PASSWORD: guest1234
SYBASE_DB: testdb
=============== CREATING LOGIN/PWD ==========================
CT-LIBRARY error:
ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed
=============== CREATING DB ==========================
CT-LIBRARY error:
ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed
=============== CREATING SCHEMA ==========================
CT-LIBRARY error:
ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed

[veekay98]

Can someone please help out here? Thanks.

[tjlee]

It looks like some issues in Sybase ACE and I start to experience the same issue recently. At least it works in Linux

00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  Current process (0x30002) infected with signal 11 (SIGSEGV)
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  Address 0x0x00007f4a24031190 (), siginfo (code, address) = (2, 0x0x00007f4a24031190)
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  **** Saved signal context (0x0x000000014a6474c0): ****
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  uc_flags: 0x7, uc_link: 0x(nil)
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  uc_sigmask: 0x416000 0xb 0x2 0x24031190
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  uc_stack: ss_sp: 0x(nil), ss_size: 0x0, ss_flags: 0x2
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  General Registers (uc_mcontext.gregs):
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  	PC : 0x00007f4a24031190 ()
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel          RAX : 0x00007f4a24031190  RBX : 0x000000014a647dc0
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel          RCX : 0x00007f4a240439a0  RDX : 0x00007f4a24000078
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  	RBP : 0x000000014a647f00  RSP : 0x000000014a647a58
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  	R8  : 0x0000000000000001  R9  : 0x00007f4a24019810
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  	R10 : 0x0000000000000001  R11 : 0x00007f4a38b10620
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  	R12 : 0x00007f4a24031190  R13 : 0x00007f4a24004970
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  	R14 : 0x00007f4a24031080  R15 : 0x00007f4a24030fe8
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  	RDI : (nil)  RSI : (nil)
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  	RIP : 0x00007f4a24031190  CSGSFS : 0x002b000000000033
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  	TRAPNO : 0x000000000000000e  ERR : 0x0000000000000015
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  	EFL : 0x0000000000010206
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  **** end of signal context ****
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  pc: 0x00000000012deabc pcstkwalk+0x46e()
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  pc: 0x00000000012de48f ucstkgentrace+0x20f()
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  pc: 0x00000000012db382 ucbacktrace+0x54()
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  pc: 0x0000000001587225 terminate_process+0xe95()
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  pc: 0x0000000001310144 kisignal+0x31b()
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  pc: 0x00007f4a24031190 ()
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  pc: 0x00000000011fc075 Snap::Validate()+0x35()
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  pc: 0x00000000008ae3d0 SnapValidation+0x82()
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  pc: 0x000000000158331c dsinit+0x25c()
00:0002:00000:00000:2022/02/02 11:18:37.09 kernel  end of stack trace, kernel service process: kpid 196610
00:0001:00000:00000:2022/02/02 11:20:36.94 kernel  Warning: The internal timer is not progressing. If this message is generated multiple times, report to SAP Technical Support and restart the server (alarminterval=0).
00:0001:00000:00000:2022/02/02 11:30:36.26 kernel  Warning: The internal timer is not progressing. If this message is generated multiple times, report to SAP Technical Support and restart the server (alarminterval=0).

[tjlee]

Mainly caused by https://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00729.1500/html/errMessageAdvRes/CACFEEEC.htm
=> so I need to rewrite start and wait in bash

[ConnorDouglasEmpire]

Vasilii Chernov (@tjlee) I'm also looking for a resolution to this issue.
Any chance you can give some direction on what needs to be rewritten? I can take a stab at it locally and respond back if I can get it to work as expected?

I've tried upping the 'wait' that's already configured in the entrypoint.sh script to a bigger value, but the app never seems to init properly/i always get the error that Vignesh Krishnan (@veekay98) mentioned. When i look at the ASE logs, i see the same thing you mention above Vasilii Chernov (@tjlee).

I'm running on a Windows host, but I've also tried in a Linux VM and get the same result, even when upping the wait to 75s.

Any guidance is appreciated.

Thanks! :)

[djauregui76]

I would be interested as well on the timeout. @tljee any updates?

[doresome]

Hi, I was just searching for a solution to this very problem and found your question, and a little bit later the answer here.

https://answers.sap.com/questions/13286419/ase-16-signal-11-stack-trace-snapvalidate-kba-3018.html

In your docker RUN script add this -T11889 flag which switches off the Snap Validation routine causing the problem. It is working fine now for me. This only seemed to affect Sybase when run in Docker 20.x.y engine, docker 19.x.y seemed to work fine which is another workaround :).

root@28e4eac8ad0a install]# pwd
/opt/sybase/ASE-16_0/install
[root@28e4eac8ad0a install]# cat RUN_MYSYBASE
#!/bin/sh
..
/opt/sybase/ASE-16_0/bin/dataserver
-d/opt/sybase/data/master.dat
-e/opt/sybase/ASE-16_0/install/MYSYBASE.log
-c/opt/sybase/ASE-16_0/MYSYBASE.cfg
-M/opt/sybase/ASE-16_0
-N/opt/sybase/ASE-16_0/sysam/MYSYBASE.properties
-i/opt/sybase
-sMYSYBASE
-T11889 \

[iambearman]

Hi, I was just searching for a solution to this very problem and found your question, and a little bit later the answer here.

https://answers.sap.com/questions/13286419/ase-16-signal-11-stack-trace-snapvalidate-kba-3018.html

In your docker RUN script add this -T11889 flag which switches off the Snap Validation routine causing the problem. It is working fine now for me. This only seemed to affect Sybase when run in Docker 20.x.y engine, docker 19.x.y seemed to work fine which is another workaround :).

root@28e4eac8ad0a install]# pwd /opt/sybase/ASE-16_0/install [root@28e4eac8ad0a install]# cat RUN_MYSYBASE #!/bin/sh .. /opt/sybase/ASE-16_0/bin/dataserver -d/opt/sybase/data/master.dat -e/opt/sybase/ASE-16_0/install/MYSYBASE.log -c/opt/sybase/ASE-16_0/MYSYBASE.cfg -M/opt/sybase/ASE-16_0 -N/opt/sybase/ASE-16_0/sysam/MYSYBASE.properties -i/opt/sybase -sMYSYBASE -T11889 \

Using Docker Engine version 24.0.1, can confirm -T11889 fixed the problem! Thank you so much!

[Mustaphabns]

Hi, i'am face to the same problem i'am using the last version of docker engine, i didn't inderstand where we should add -T11889, can you give me an exemple of this ?

I used this command : docker run -p 5000:5000 --rm datagrip/sybase:latest -T11889

# Interfaces file directory: /opt/sybase
# SAP Adaptive Server Enterprise name: MYSYBASE
#
/opt/sybase/ASE-16_0/bin/dataserver \ -d/opt/sybase/data/master.dat \ -e/opt/sybase/ASE-16_0/install/MYSYBASE.log \ -c/opt/sybase/ASE-16_0/MYSYBASE.cfg \ -M/opt/sybase/ASE-16_0 \ -N/opt/sybase/ASE-16_0/sysam/MYSYBASE.properties \ -i/opt/sybase \ -sMYSYBASE \
Thnx

[iambearman]

First of all, I am sorry for your poor soul that you have to use Sybase (or you actually like it?), I have no choice but to use Sybase because that's what my company had.

Second, follow these steps

1. run command docker run -p 5000:5000 --name sybase -v sybase-data:/opt/sybase datagrip/sybase:16.0
2. wait for it until it stop at

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
=============== WAITING FOR master.dat SPACE ALLOCATION ==========================
=============== WAITING FOR INITIALIZATION ==========================
=============== SYBASE STARTED ==========================
SYBASE_USER: tester
SYBASE_PASSWORD: guest1234
SYBASE_DB: testdb
=============== CREATING LOGIN/PWD ==========================
CT-LIBRARY error:
	ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed
=============== CREATING DB ==========================
CT-LIBRARY error:
	ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed
=============== SYBASE INITIALIZED ==========================

3. If you are familiar with Unix/Linux shell operation, you may continue to step 4-9, else just do 3.1 and ignore step 4-9
   3.1. run command: docker exec -it sybase bash -c "sed -i '$ s/$/-T11889 \\\\/' /opt/sybase/ASE-16_0/install/RUN_MYSYBASE && echo '' >> /opt/sybase/ASE-16_0/install/RUN_MYSYBASE"
4. open another shell, and run command docker exec -it sybase bash to get inside the container
5. inside container shell, run command cd /opt/sybase/ASE-16_0/install
6. inside container shell, run command vi RUN_MYSYBASE
7. add -T11889 \ to the last line such that it should looks something like this (keep one more empty line as the last line), save and exit the file

#!/bin/sh
#
# SAP ASE page size (KB):       16k
# Master device path:   /opt/sybase/data/master.dat
# Error log path:       /opt/sybase/ASE-16_0/install/MYSYBASE.log
# Configuration file path:      /opt/sybase/ASE-16_0/MYSYBASE.cfg
# Directory for shared memory files:    /opt/sybase/ASE-16_0
# License properties file:      /opt/sybase/ASE-16_0/sysam/MYSYBASE.properties
# Interfaces file directory:    /opt/sybase
# SAP Adaptive Server Enterprise name:  MYSYBASE
#
/opt/sybase/ASE-16_0/bin/dataserver \
-d/opt/sybase/data/master.dat \
-e/opt/sybase/ASE-16_0/install/MYSYBASE.log \
-c/opt/sybase/ASE-16_0/MYSYBASE.cfg \
-M/opt/sybase/ASE-16_0 \
-N/opt/sybase/ASE-16_0/sysam/MYSYBASE.properties \
-i/opt/sybase \
-sMYSYBASE \
-T11889 \
<<<empty line here>>>

9. close the container shell
10. open another shell and run command docker stop sybase to stop the Sybase container
11. the first shell that has Sybase container running should now have exited the container
12. run command docker start sybase to start Sybase container again
13. wait for a good 5 minutes to let Sybase correctly setup
14. use your tools/program to login with

• username: tester
• password: guest1234
  or
• username: sa
• password: myPassword

15. when you are done using the Sybase container, run command docker stop sybase to stop it
16. next time you wanna use the container again, just run command docker start sybase, all of the previously stored data are still there because of the docker volume.

[Mustaphabns]

Thank's for your quick response, it's not my choice, it's consumer choice :/ .

I still have the same issue when tring to connect to database with ISQL:

/opt/sybase/OCS-16_0/bin/isql -Usa -PmyPassword -SMYSYBASE CT-LIBRARY error: ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed

[Mustaphabns]

start your docker, exec an interactive bash, make your RUN file look like this below by adding a line to the last by one line. Restart your docker, it should then work.

-T11889 \

$ sudo docker start syb syb $ sudo docker exec --interactive --tty syb bash --login [root@1911757ee96f /]# cat /opt/sybase/ASE-16_0/install/RUN_MYSYBASE #!/bin/sh

SAP ASE page size (KB): 16k

Master device path: /opt/sybase/data/master.dat

Error log path: /opt/sybase/ASE-16_0/install/MYSYBASE.log

Configuration file path: /opt/sybase/ASE-16_0/MYSYBASE.cfg

Directory for shared memory files: /opt/sybase/ASE-16_0

License properties file: /opt/sybase/ASE-16_0/sysam/MYSYBASE.properties

Interfaces file directory: /opt/sybase

SAP Adaptive Server Enterprise name: MYSYBASE

/opt/sybase/ASE-16_0/bin/dataserver -d/opt/sybase/data/master.dat -e/opt/sybase/ASE-16_0/install/MYSYBASE.log -c/opt/sybase/ASE-16_0/MYSYBASE.cfg -M/opt/sybase/ASE-16_0 -N/opt/sybase/ASE-16_0/sysam/MYSYBASE.properties -i/opt/sybase -sMYSYBASE -T11889 \

i still have the same issue when restarting container or try to connect directly by ISQL

[iambearman]

I don't have isql with me, would you mind share your isql interface file content for reference?