Check system start up - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

Alfresco Content Services

Platform
Alfresco
Product
Alfresco Content Services
Release
23.4
License

Use this information to verify that the system started correctly, and to clean up the deployment.

  1. Open a new terminal window.
  2. Change directory to the docker-compose folder that you created in the deployment steps.
  3. Verify that all the services started correctly.
    1. List the images and additional details:
       docker-compose images
      

      You should see a list of the services defined in your docker-compose.yml file (below are the tags used in the latest 23.x release):

       Container                        Repository                                                     Tag                       Image Id       Size
       ------------------------------------------------------------------------------------------------------------------------------------------------
       acs_trial-activemq-1              alfresco/alfresco-activemq                                   5.18-jre11-rockylinux8    c983f8c439f4   645 MB
       acs_trial-alfresco-1              quay.io/alfresco/alfresco-content-repository                 23.2.1                    d543f50c8a7b   1.12 GB
       acs_trial-control-center-1        quay.io/alfresco/alfresco-control-center                     8.4.1                     65e05f14d4a3   43.6 MB
       acs_trial-digital-workspace-1     quay.io/alfresco/alfresco-digital-workspace                  4.4.1                     42bf20815997   47.8 MB
       acs_trial-elasticsearch-1         elasticsearch                                                7.10.1                    558380375f1a   774 MB
       acs_trial-postgres-1              postgres                                                     14.4                      e09e90144645   376 MB
       acs_trial-proxy-1                 alfresco/alfresco-acs-nginx                                  3.4.2                     f9c4519b7920   23.4 MB
       acs_trial-search-1                quay.io/alfresco/alfresco-elasticsearch-live-indexing        4.0.1                     cfd3f6ef7139   596 MB
       acs_trial-search-reindexing-1     quay.io/alfresco/alfresco-elasticsearch-reindexing           4.0.1                     e5eb14f75825   602 MB
       acs_trial-share-1                 quay.io/alfresco/alfresco-share                              23.2.1                    2692e8fa81e3   691 MB
       acs_trial-shared-file-store-1     quay.io/alfresco/alfresco-shared-file-store                  4.1.1                     b0e701edeb6a   540 MB
       acs_trial-sync-service-1          quay.io/alfresco/service-sync                                4.0.1                     cb8e65443e11   719 MB
       acs_trial-transform-core-aio-1    alfresco/alfresco-transform-core-aio                         5.1.1                     ab05c7e4d20a   1.65 GB
       acs_trial-transform-router-1      quay.io/alfresco/alfresco-transform-router                   4.1.1                     fe8db4219e45   564 MB
      
    2. List the running containers:
       docker-compose ps
      

      You should see a list of the services defined in the docker-compose.yml file.

    3. View the log files for each service <service-name>, or container <container-name>:
       docker-compose logs <service-name>
       docker container logs <container-name>
      

      For example, to check the logs for Share, run any of the following commands:

       docker-compose logs share
       docker container logs acs_trial-share-1
      

      You can add an optional parameter --tail=25 before <container-name> to display the last 25 lines of the logs for the selected container.

       docker-compose logs --tail=25 share
       docker container logs --tail=25 acs_trial-share-1
      

      Check for a success message:

       Successfully retrieved license information from Alfresco.
      

      Once you’ve tested the services, you can clean up the deployment by stopping the running services.

  4. Stop the session by using CONTROL+C in the same window as the running services:
     Gracefully stopping... (press Ctrl+C again to force)
     Container acs_trial-transform-router-1   ... Stopped
     Container acs_trial-proxy-1              ... Stopped
     Container acs_trial-transform-core-aio-1 ... Stopped
     Container acs_trial-postgres-1           ... Stopped
     Container acs_trial-alfresco-1           ... Stopped
     Container acs_trial-shared-file-store-1  ... Stopped
     Container acs_trial-share-1              ... Stopped
     Container acs_trial-sync-service-1       ... Stopped
     Container acs_trial-control-center-1     ... Stopped
     Container acs_trial-digital-workspace-1  ... Stopped
     Container acs_trial-activemq-1           ... Stopped
    
  5. Alternatively, you can open a new terminal window, change directory to the docker-compose folder, and run:
     docker-compose down
    

    This stops the running services, as shown in the previous example, and removes them from memory:

     Container acs_trial-transform-core-aio-1 ... Stopping
     Container acs_trial-sync-service-1       ... Stopping
     Container acs_trial-proxy-1              ... Stopping
     Container acs_trial-search-1             ... Stopping
     Container acs_trial-search-reindexing-1  ... Stopping
     Container acs_trial-shared-file-store-1  ... Stopping
     Container acs_trial-transform-router_1   ... Stopping
     Container acs_trial-postgres-1           ... Stopping
     Container acs_trial-activemq-1           ... Stopping
     Container acs_trial-elasticsearch-1      ... Removed
     Container acs_trial-control-center-1     ... Removed
     Container acs_trial-alfresco-1           ... Removed
     Container acs_trial-digital-workspace-1  ... Removed
     Container acs_trial-share-1              ... Removed
     Network acs_trial_default                ... Removed
    
  6. You can use a few more commands to explore the services when they’re running. Change directory to docker-compose before running these:
    1. Stop all the running containers:
       docker-compose stop
      
    2. Restart the containers (after using the stop command):
       docker-compose restart
      
    3. Starts the containers that were started with docker-compose up:
       docker-compose start
      
    4. Stop all running containers, and remove them and the network:
       docker-compose down [--rmi all]
      

      The --rmi all option also removes the images created by docker-compose up, and the images used by any service. You can use this, for example, if any containers fail and you need to remove them:

       docker-compose down --rmi all
      
       Container acs_trial-transform-core-aio-1                           Removed
       Container acs_trial-transform-router-1                             Removed
       Container acs_trial-search-reindexing-1                            Removed
       Container acs_trial-proxy-1                                        Removed
       Container acs_trial-search-1                                       Removed
       Container acs_trial-sync-service-1                                 Removed
       Container acs_trial-postgres-1                                     Removed
       Container acs_trial-elasticsearch-1                                Removed
       Container acs_trial-activemq-1                                     Removed
       Container acs_trial-share-1                                        Removed
       Container acs_trial-digital-workspace-1                            Removed
       Container acs_trial-alfresco-1                                     Removed
       Container acs_trial-control-center-1                               Removed
       Image quay.io/alfresco/service-sync:4.0.1                          Removed
       ...                               
       Image quay.io/alfresco/alfresco-content-repository:23.2.1          Stopping                               
       ...
       Network acs_trial_default                                           Stopping
      
See the Docker documentation for more on using Docker.