RDBMS - CAST Storage Service - CAST Storage Service 3 - Service did not start or stopped abruptly

This page will help you to troubleshoot CAST Storage Service 3 Service issues.  

1. Make sure that you are following the minimum system configuration requirements to run the CAST Storage Service: CAST AIP for Dashboards
2. Check whether the available disk space on the drive where the CAST Storage Service is installed is higher than 0 MB.
3. Go to CAST Storage Service 3 Installation folder.
4. Go to the db_data folder.
5. If the CAST Storage Service 3 service is not running, check if Postmaster.pid file exists.
   
   1. Go to your CAST Installation folder
   2. Right click on the folder and select properties
   3. In the security tab, check whether your Group (usually Administrator group) or User group has all the access to write, read and modify all the folders:
      
   4. If the user has all the rights, in the Services window, start CAST storage service 3.
1. If the file exists, it is corrupted and locked:
   1. Rename the Postmaster.pid into SAV_Postmaster.pid
   2. Open the Services window.
   3. Restart CAST Storage Service 3 service.
2. If the Postmaster.pid is not there, check whether your Windows user account has the right to modify the CAST Storage Service 3 installation folder :
6. If the service fails to start, go to the <Cast Storage Service 3 Installation folder>/db_data/pg_log and open the last log file:
   1. Check the timestamp corresponding to the time you have run the service
   2. Check if there is an error that prevents the service to start:

      1. If there is an error like :

         LOG:  could not bind IPv4 socket: Address already in use
         HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
         FATAL:  could not create TCP/IP listen socket 

          You tried to start another server on the same port where one is already running. You must reinstall the CAST Storage Service 3 on another port.

      2. 
         

         If there is an error like this (a similar error can also be seen in Event viewer):

         FATAL:  could not create shared memory segment: Invalid argument
         DETAIL:  Failed system call was shmget(key=5440001, size=4011376640, 03600). 

          This could mean that you do not have enough free memory for CSS 3 to start or that that the SHARED_MEMORY parameter that is defined in the file PostgreSQL.conf is too high:

         1. 1. Make sure that you have enough memory available for CSS 3 to start
            2. For changing the parameter for Shared memory:
               1. Open the file PostgreSQL.conf that is in <Your CAST Storage Service 3 Installation folder>\db_data folder 
               2. Change the parameter SHARED_MEMORY to a lower value. You can divide it by two. This will impact the performance of your Server.
7. If the service fails to start go to the <Cast Storage Service Installation folder>/db_data/pg_log and open the last log file.   You will observe the below message -  [2-1] PANIC: replication checkpoint has wrong magic 0 instead of 307747550

   Error Stack - 

   2021-09-22 15:09:16 CEST [14640]: [3-1] LOG:  starting PostgreSQL 13.0, compiled by Visual C++ build 1914, 64-bit
   2021-09-22 15:09:16 CEST [14640]: [4-1] LOG:  listening on IPv6 address "::", port 2284
   2021-09-22 15:09:16 CEST [14640]: [5-1] LOG:  listening on IPv4 address "0.0.0.0", port 2284
   2021-09-22 15:09:17 CEST [232]: [1-1] LOG:  database system was interrupted; last known up at 2021-09-22 09:29:16 CEST
   2021-09-22 15:09:17 CEST [232]: [2-1] PANIC:  replication checkpoint has wrong magic 0 instead of 307747550
   2021-09-22 15:09:19 CEST [14640]: [6-1] LOG:  startup process (PID 232) was terminated by exception 0xC0000409
   2021-09-22 15:09:19 CEST [14640]: [7-1] HINT:  See C include file "ntstatus.h" for a description of the hexadecimal value.
   2021-09-22 15:09:19 CEST [14640]: [8-1] LOG:  aborting startup due to startup process failure
   2021-09-22 15:09:19 CEST [14640]: [9-1] LOG:  database system is shut down

               The issue occurs when the Postgres DB has crashed and when trying to restart the service.

               To solve the issue you need to move the existing replorigin_checkpoint file from pg_logical folder elsewhere and restart the CSS service. 

8. When the service does not start and the event viewer shows the message - 

          You need to remove the postmaster.pid file from the db_data folder inside the CSS Installation folder or the db_data folder, if configured outside the CSS Installation folder.

       9. If the above points do not help you to solve the issue, Contact CAST Technical Support and provide the relevant input.