KFAA91102-E


      
         An error occurred during HADB server start processing.

         
            
               aa....aa: 

               
                  Message ID

               

            
            
               S: 

               
                  Terminates processing.

               

            
            
               Action:

               
                  The start processing error message (the message corresponding to the message ID output as aa....aa) has been output to a message log file. Take corrective action as indicated for that error message.

                  If an error occurs before the area for communication between the adbstart process and the server process is prepared, and the message ID cannot be acquired, 00000 is output for aa....aa. In that case, check the message that was output immediately prior to this message, since the cause of the error is sometimes output to the message log.

                  If no message is output, the file might have failed to open because there are not enough file descriptors. In this case, reduce the number of file descriptors used in the system as a whole, and then retry the operation.

                  00000 is also output for information even when the server process is terminated due to one of the following errors prior to completion of server process startup.

                  
                     
                        When the server process is terminated by the OS's kill command

                     

                     
                        When the server process is forcibly terminated by OOM Killer because sufficient memory could not be allocated by the OS

                     

                     
                        When the multi-node function is used and the adbstart command is executed without waiting for
                           the HA Monitor server to stop

                     

                  

                  In these cases, the cause of the error is output to syslog. Check syslog, eliminate the cause of the error, and then retry the operation.