You try to start HANA DB from the command line with 'HDB Start' and an error returns 'FAIL: process hdbdaemon HDB Daemon not running

 You try to start HANA DB from the command line with 'HDB Start' and an error returns 'FAIL: process hdbdaemon HDB Daemon not running'.

Possible Reason:

1. The nameserver.ini file is corrupt 

2. The nameserver.ini file is missing, the error messages in the nameserver trace files:
Daemon.cpp(00693) :  runlevel 0 completely started

[32184]{-1}[-1/-1] 2026-04-20 17:49:37.980370 i Daemon  Program.cpp(00173) : line up of program group mdcdispatcher to instances <none>.

[32184]{-1}[-1/-1] 2026-04-20 17:49:37.980372 i Daemon Program.cpp(00173) : line up of program group nameserver to instances 0.

[32184]{-1}[-1/-1] 2026-04-20 17:49:37.980405 i Daemon  TrexDaemon.cpp(02338) : starting program at '/usr/sap/NDB/HDB00/exe/hdbnameserver' with args ''

[32184]{-1}[-1/-1] 2026-04-20 17:49:37.983897 w Environment   NetworkListener.cpp(01153) : Child process deletes daemon port

[32184]{-1}[-1/-1] 2026-04-20 17:49:37.983999 w Environment  Environment.cpp(00422) : Changing environment set TREXDAEMON_PORT==

[32184]{-1}[-1/-1] 2026-04-20 17:49:37.985158 i Daemon RunningInstance.cpp(00192) : start 'hdbnameserver' as process 32200

[32184]{-1}[-1/-1] 2026-04-20 17:49:39.651341 i Daemon  SignalsUNIX.cpp(00699) : signo 2 SIGINT from user errno 0 code 0

sender pid 32200 real user id 1001 executable '/hana/shared/NDB/exe/linuxx86_64/HDB_1.00.122.22.1543461992_5253312/hdbnameserver'

[32184]{-1}[-1/-1] 2026-04-20 17:49:39.651469 i Daemon           TrexDaemon.cpp(04101) : got shutdown event (quit)

 “[32184]{-1}[-1/-1] 2026-04-20 17:49:39.651495 i Daemon           Daemon.cpp(00779) : comment file contains: nameserver: [landscape]/master is missing in nameserver.ini. did someone delete SYS/global/hdb/custom/config/nameserver.ini ?”

 [32184]{-1}[-1/-1] 2026-04-20 17:49:39.651885 i Daemon           RunningInstance.cpp(00215) : stop process hdbnameserver with pid 32200

[32184]{-1}[-1/-1] 2026-04-20 17:49:39.651986 i Daemon           TrexDaemon.cpp(02958) : stopped child with pid 32200 (32200)


Solution :

1. Log in to the HANA System and Check Trace Files

  • Connect to the HANA server.
  • Switch to the HANA system administrator user:

su – ndbadm

·       Navigate to the HANA trace directory:

ndbadm@SAPHANA:/usr/sap/NDB/HDB00>cdtrace

ndbadm@SAPHANA:/usr/sap/NDB/HDB00/_<IP_ADDRESS>./trace> ls -ltr

search for daemon_<IP_ADDRESS>.30000.002.trc with pen the latest trace file and verify the error messages related to the landscape or nameserver issues.

 2. Verify and configure nameserver.ini

Path to configuration file: /hana/shared/NDB/global/hdb/custom/config

Navigate to the directory: cd /hana/shared/NDB/global/hdb/custom/config

·       Open or create the nameserver.ini file: vi nameserver.ini

3.  Add or update the  following configuration (modify values as per your system):

ü  [landscape]

ü  id = <LANDSCAPE_ID>

ü  master = <SERVER_IP>:30001

ü  worker = <SERVER_IP>:30001

ü  active_master = <SERVER_IP>:30001

ü  workergroups_<SERVER_IP> = default

ü  failovergroup_<SERVER_IP> = default

ü  roles_<SERVER_IP> = worker

4.  Retrieve the Landscape ID

The landscape ID is required in nameserver.ini.

  1. Locate the landscape.id file:

            /hana/data/NDB/mnt00001/hdb00001/landscape.id

2.     Display the ID:

cat /hana/data/NDB/mnt00001/hdb00001/landscape.id

Show more lines

  1. Copy the value and paste it into the id = field in nameserver.ini.

4. Save and Validate

  • Save the nameserver.ini file.
  • start HANA and services, check the HANA is started. 


Note: The HANA configuration file files (nameserver.ini, indexserver.ini, xsengine.ini, etc.) are not backed up as part of a database backup.


Comments

Post a Comment

Popular posts from this blog

SAP B1SiteUser Password Reset || SAP Business One

Image
  Account is disabled, contact your administrator –Error 1. How to reset B1SiteUser password  2.  Log in to the Linux server as the root user 3 .  Navigate to the folder  /        <Installation Folder>/SAPBusinessOne/Common/keycloak/conf. Ø   4.  Open the env.conf file and add the following two parameters.     5. add the following two parameters   KEYCLOAK_ADMIN=B1admin KEYCLOAK_ADMIN_PASSWORD=Welcome1# 2.       6.    Restart the SAP Business One Server Tools Authentication Service by performing the following commands: systemctl restart sapb1servertools-authentication.service. 7. Login to KEYCLOAK using above credentials à Navigate to Users à click on B1Admin à Enable and save   3.       8 . click on B1Admin à Enable and save   4.      9.    Click on Credentials 5.        10...
Read more

Service pack migration SLES 15 SP1 to SLES 15 SP5 x86_64

Image
Service pack migration SUSE Linux Enterprise Server 15 SP1 to SUSE Linux Enterprise Server 15 SP5  x86_64   Note: we can’t directly upgrade to SUSE Linux Enterprise Server 15 SP5 , so first we will upgaring to SLE 15 SP4 then   SLE 15 SP4 to SLE 15 SP5 will be upgraded. 1.        Verify the server current patch  # cat /etc/os-release a.        Take the snapshot backup of server   2.        Register server or VM in SUSE customer centre # SUSEConnect -r {Regi CODE} -e   {your email Id} 3.         Make sure that your server is registered in suse center # SUSEConnect -s 4.        Disable   multiversion.(once the upgrade is completed you need to roll back same as it’ s) # cat -n /etc/zypp/zypp.conf | grep -i multiversion Make sure multi version disabled . 5.   ...
Read more

SAP HANA Server (SUSE) – Service Restart Procedure || Server Maintance

Image
1. Login to the SAP HANA Server Log in to the SUSE (HANA) server using  root  access. Verify which user you are logged in as: # who am i Note: As a best practice, take a full backup of all databases before starting the following activity. 2. Stop All HANA Services Run the following commands to stop all SAP HANA-related services: systemctl stop sapb1servertools-authentication.service systemctl stop authentication.service systemctl stop sapb1edfbackend.service systemctl stop b1s.service systemctl stop sapb1servertools.service 3. Verify That Services Are Stopped Check the status of each service: # systemctl status...
Read more