Re: ABAP Platform Trial 1909 on MBP M1

ansenko · ‎08-08-2023

I did everything as described in the instructions for the link:

https://hub.docker.com/r/sapse/abap-platform-trial

docker ps command it looks good:

CONTAINER ID   IMAGE                            COMMAND                  CREATED       STATUS          PORTS                                                                                                                                                         NAMES
adc92cf3fc9e   sapse/abap-platform-trial:1909   "/usr/local/bin/abap…"   2 hours ago   Up 24 minutes   0.0.0.0:3200->3200/tcp, 0.0.0.0:3300->3300/tcp, 0.0.0.0:8443->8443/tcp, 4237/tcp, 0.0.0.0:30213->30213/tcp, 0.0.0.0:50000-50001->50000-50001/tcp, 30215/tcp   a4h

I also can run rcscc_daemon after that:

docker exec -it a4h bash /usr/local/sbin/rcscc_daemon start
Starting scc_Daemon

scc_Daemon started.

Check that all related processes are running:

/usr/sap/A4H/ASCS01/exe # ps -ef |cat
UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 07:04 ?        00:00:01 /usr/bin/qemu-x86_64 /usr/local/bin/abaptrialinit /usr/local/bin/abaptrialinit -skip-limits-check
root        13     0  0 07:04 pts/0    00:00:00 /usr/bin/qemu-x86_64 /bin/sh /bin/sh
root       159     1  0 07:05 ?        00:00:14 /usr/bin/qemu-x86_64 /usr/sap/hostctrl/exe/saphostexec /usr/sap/hostctrl/exe/saphostexec pf=/usr/sap/hostctrl/exe/host_profile
sapadm     292     1  0 07:05 ?        00:00:47 /usr/bin/qemu-x86_64 /usr/sap/hostctrl/exe/sapstartsrv /usr/sap/hostctrl/exe/sapstartsrv pf=/usr/sap/hostctrl/exe/host_profile -D
root       498     1  0 07:05 ?        00:00:45 /usr/bin/qemu-x86_64 /usr/sap/hostctrl/exe/saposcol /usr/sap/hostctrl/exe/saposcol -l -w60 pf=/usr/sap/hostctrl/exe/host_profile
hdbadm     571     1  0 07:05 ?        00:00:24 /usr/bin/qemu-x86_64 /usr/sap/HDB/HDB02/exe/sapstartsrv /usr/sap/HDB/HDB02/exe/sapstartsrv pf=/usr/sap/HDB/SYS/profile/HDB_HDB02_vhcala4hci -D -u hdbadm
a4hadm    1099     1  0 07:05 ?        00:00:49 /usr/bin/qemu-x86_64 /usr/sap/A4H/D00/exe/sapstartsrv /usr/sap/A4H/D00/exe/sapstartsrv pf=/usr/sap/A4H/SYS/profile/A4H_D00_vhcala4hci -D -u a4hadm
a4hadm    1570     1  0 07:05 ?        00:00:39 /usr/bin/qemu-x86_64 /usr/sap/A4H/ASCS01/exe/sapstartsrv /usr/sap/A4H/ASCS01/exe/sapstartsrv pf=/usr/sap/A4H/SYS/profile/A4H_ASCS01_vhcala4hci -D -u a4hadm
hdbadm    1872     1  0 07:06 ?        00:00:00 /usr/bin/qemu-x86_64 /usr/sap/HDB/HDB02/exe/sapstart sapstart pf=/usr/sap/HDB/SYS/profile/HDB_HDB02_vhcala4hci
hdbadm    1900  1872  0 07:06 ?        00:00:36 /usr/bin/qemu-x86_64 /usr/sap/HDB/HDB02/vhcala4hci/trace/hdb.sapHDB_HDB02 /usr/sap/HDB/HDB02/vhcala4hci/trace/hdb.sapHDB_HDB02 -d -nw -f /usr/sap/HDB/HDB02/vhcala4hci/daemon.ini pf=/usr/sap/HDB/SYS/profile/HDB_HDB02_vhcala4hci
hdbadm    1945  1900  0 07:06 ?        00:00:24 [hdbnameserver] <defunct>
root      4755     0  0 07:25 pts/1    00:00:02 /usr/bin/qemu-x86_64 /usr/bin/bash bash
root     11428  4755  0 08:09 pts/1    00:00:00 /usr/bin/qemu-x86_64 ./sapstart ./sapstart name=TST nr=00 sapdiahost=test
root     11431 11428  0 08:09 ?        00:00:00 [sapstart] <defunct>
root     52810     1  2 12:50 ?        00:00:00 /usr/bin/qemu-x86_64 /usr/bin/su /usr/bin/su - hdbadm -c sapcontrol -nr 02 -function StartWait 3600 2
hdbadm   52819 52810  1 12:50 ?        00:00:00 /usr/bin/qemu-x86_64 /usr/sap/HDB/HDB02/exe/sapcontrol sapcontrol -nr 02 -function StartWait 3600 2
root     53014  4755  0 06:45 ?        00:00:00 ps -ef
root     53016  4755  4 12:50 pts/1    00:00:00 /usr/bin/qemu-x86_64 /usr/bin/cat cat

Check forwarding:

docker port a4h
3200/tcp -> 0.0.0.0:3200
3300/tcp -> 0.0.0.0:3300
8443/tcp -> 0.0.0.0:8443
30213/tcp -> 0.0.0.0:30213
50000/tcp -> 0.0.0.0:50000
50001/tcp -> 0.0.0.0:50001

But nothing work as expected:

1. SAP GUI

2. SAP Cloud Connector

3. Http

I even tried to make it with SOCKS proxy as described here: https://github.com/docker/for-mac/issues/2670

I'd be really grateful for any suggestions on how to sort this out.

P.S. This question raised after discussion under this blog: https://blogs.sap.com/2023/07/31/now-available-abap-platform-trial/

ansenko · ‎08-08-2023

Okay, looks like some processes are missed:

hdbnameserver

hdbpreprocessor

hdbcompileserver

hdbindexserver

hdbstatisticsserver

and /usr/sap/HDB/HDB02/vhcala4hci/trace/nameserver_alert_vhcala4hci.trc not looks good.

exception type information:
 - 0: public ltt::exception@0x4028ea1960
[1949]{-1}[-1/-1] 2023-08-08 16:14:58.046897 f topology         Topology.cpp(00415) : assign failed with persistence startup error. exception  1: no.2000009  (Basis/IO/FileAccess/impl/LocalFileCompletionThread.cpp:513) TID: 1949
    Error calling io_setup, rc=38: Function not implemented
exception throw location:
 1: 0x000000402847c7cd in FileAccess::LocalFileFactory::init(Configuration::ConfigurationHandler&)+0x9b9 at LocalFileCompletionThread.cpp:513 (libhdbbasis.so)
 2: 0x00000040284a53b3 in FileAccess::FileFactory::createInstance(Configuration::ConfigurationHandler&, FileAccess::FileFactory::Type, ltt::basic_string<char, ltt::char_traits<char>, ltt::integral_constant<int, 64> > const&, int, int, FileAccess::FileFactory::Usage)+0x290 at FileFactory.cpp:415 (libhdbbasis.so)
 3: 0x0000004023135af3 in PersistenceLayer::PersistenceFactory::initPersistence(PersistenceLayer::PERSISTENCE_MODE, DataAccess::TransactionCallback*, NameServer::ServiceStartInfo&, ltt::refcounted_handle<TransactionManager::TransactionControlBlockFactory>&, bool, ltt::smartptr_handle<DataAccess::DisasterRecoverySecondaryCallback>&, bool)+0x270 at PersistenceFactory.cpp:417 (libhdbpersistence.so)
 4: 0x0000004005e1d4eb in PersistenceController::startup(PersistenceLayer::PERSISTENCE_MODE, NameServer::ServiceStartInfo*, bool, DataAccess::TablePreloadWriteCallback*, DataAccess::TablePreloadReadCallback*, Backup::RecoverCbc_Federation*)+0x1407 at PersistenceController.cpp:560 (libhdblogger.so)
 5: 0x000000400307a37a in NameServer::Topology::initPersistence(NameServer::ServiceStartInfo&, bool, bool, TREX_ERROR::TRexError*, bool, ltt_adp::basic_string<char, ltt::char_traits<char>, ltt::integral_constant<bool, true> >, NameServer::ServiceStartInfo::RequestAction)+0x406 at Topology.cpp:392 (libhdbns.so)
 6: 0x0000004002f110d6 in NameServer::TREXNameServer::loadTopology(NameServer::LoadTopologyMode, NameServer::ServiceStartInfo&, Backup::Backup_ExtendedRecoveryInformation*, bool)+0x722 at TREXNameServer.cpp:11160 (libhdbns.so)
 7: 0x0000004002f6c435 in NameServer::TREXNameServer::assign(NameServer::ServiceStartInfo&)+0xe41 at TREXNameServer.cpp:1804 (libhdbns.so)
 8: 0x000000400015ca4c in TRexAPI::TREXIndexServer::assign(NameServer::ServiceStartInfo&, bool, TREX_ERROR::TRexError&)+0x108 at TREXIndexServer.cpp:1077 (hdbnameserver)
 9: 0x0000004000164749 in TRexAPI::AssignThread::run(void*)+0x35 at TREXIndexServer.cpp:533 (hdbnameserver)
10: 0x0000004023cb1d8b in TrexThreads::PoolThread::run()+0x787 at PoolThread.cpp:462 (libhdbbasement.so)
11: 0x0000004023cb4850 in TrexThreads::PoolThread::run(void*&)+0x10 at PoolThread.cpp:143 (libhdbbasement.so)
12: 0x00000040284c34e8 in Execution::Thread::staticMainImp(Execution::Thread*)+0x534 at Thread.cpp:529 (libhdbbasis.so)
13: 0x00000040284b2798 in Execution::pthreadFunctionWrapper(Execution::Thread*)+0x164 at ThreadInterposition.cpp:633 (libhdbbasis.so)
14: 0x0000004028db56ea in start_thread+0xd8 (libpthread.so.0)
15: 0x000000402a08b94f in __GI___clone+0x3b (libc.so.6)
exception type information:
 - 0: public ltt::exception@0x4028ea1960
 stopping service...
[1949]{-1}[-1/-1] 2023-08-08 16:14:58.051654 f NameServer       TREXNameServer.cpp(03714) : persistence initialization failed -> stopping instance ...
[1949]{-1}[-1/-1] 2023-08-08 16:14:58.052503 f NameServer       TREXNameServer.cpp(03727) :  stopping topology thread
[1949]{-1}[-1/-1] 2023-08-08 16:14:58.052567 f NameServer       TREXNameServer.cpp(03729) :  got shutdown scope
[1949]{-1}[-1/-1] 2023-08-08 16:14:58.052667 f NameServer       TREXNameServer.cpp(03733) :  stopped topology thread
[1949]{-1}[-1/-1] 2023-08-08 16:14:58.052770 e Basis            TREXNameServer.cpp(03743) : Process exited due to an error via explicit exit call with exit code 1 , no crash dump will be written

m_kubis · ‎11-16-2023

With the new Docker Desktop Version 4.25.1 the HDB will start up und everthing is running on Apple Silicon! They updated Rosetta.

ansenko · ‎11-16-2023

Thank you Michael, I'll check.