Sybase instance doesn't start on Linux

[f4ll3nl0rd]

Hello,
I'm trying to run docker container but on Linux. Unfortunatelly without succes.
Build process is successfull and container can be started without errors.

After initial start I'm doing the same hostname "adjustment" in /etc/hosts and /etc/hostname

After startsap ALL instance is trying to start but at some point it dies. Traces shows following issue

C    Last SYBASE DBSL patchcomment SAP Support Package Stack Kernel 7.53 Patch Level 400 (2752112)
C  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 6164]
C  (30294) [HY000] [SAP][ASE ODBC Driver]There is no server listening at vhcalnplci:4901
C  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 6164]

Indeed Sybase DB is listening only on 4902 as per netstat

vhcalnplci:npladm 21> netstat -an | grep 49
tcp        0      0 172.17.0.2:4902         0.0.0.0:*               LISTEN      
udp        0      0 127.0.0.1:35785         127.0.0.1:64996         ESTABLISHED 
udp        0      0 127.0.0.1:36904         127.0.0.1:64998         ESTABLISHED 
udp        0      0 127.0.0.1:58794         127.0.0.1:64997         ESTABLISHED 
udp        0      0 127.0.0.1:42522         127.0.0.1:64999         ESTABLISHED 

However port in DEFAULT.PFL is configured with different value:

vhcalnplci:npladm 25> less DEFAULT.PFL | grep dbs
dbs/syb/schema = SAPSR3
dbs/syb/server = vhcalnplci
dbs/syb/dbname = NPL
dbs/syb/port = 4901
dbs/syb/cache_size = 300

Also in /sybase/NPL/interfaces we have

NPL
        master tcp ether 5c044ae0c72d 4901
        query tcp ether 5c044ae0c72d 4901
NPL_BS
        master tcp ether 5c044ae0c72d 4902
        query tcp ether 5c044ae0c72d 4902
NPL_JSAGENT
        master tcp ether 5c044ae0c72d 4903
        query tcp ether 5c044ae0c72d 4903

Why Sybase is not starting on port 4901 then?

[tobiashofmann]

Not sure why Sybase is not listening on 4901. First thing that comes to my mind: do you have valid license? The Sybase license that is included in the NW download expired march 31st. You'll have to update it manually.