> Source: [sk177467](https://support.checkpoint.com/results/sk/sk177467)

# sk177467 - CPM fails to start on an Endpoint Management Server

| Property | Value |
|----------|-------|
| Solution ID | sk177467 |
| Date Created | 2022-01-19 |
| Last Modified | 2022-01-26 |
| Technical Level | Advanced |
| Products | Endpoint Security |
| Versions | R81 (EOS) |
| OS | Gaia |
| Platform | Open Server |

## Symptoms

- * Admin is unable to log into SmartConsole or SmartEndpoint.
* When Running: watch API status, CPM shows:  
  `CPM Stopped 1024 Check Point Security Management Server failed to start`
* server_messages.log shows: `
  [2022-01-14T09:04:17,382] ERROR SYNC UPDATE QUEUE-0 - Failed to notify about UEPM DB changes.`  

  `

  error:com.checkpoint.uepm.api.epsbackend.is.EpsBackendException:`  

  `

  [2022-01-14T09:04:17,386] WARN SYNC UPDATE QUEUE-0 - Interceptor for `  
  `{ws:com.checkpoint.gsoap.uepmha_service}uepmha_service#{ws:com.checkpoint.gsoap.uepmha_service}notifyOfUEPMChangeDB has thrown exception, unwinding
  now (PhaseInterceptorChain)`  

  `

  org.apache.cxf.interceptor.Fault: Could not send Message.`  

* The cpm.elg file shows:   

  `
  13/01/22 22:46:39,863 ERROR transport.http_jetty.JettyHTTPServerEngine [main]: Could not start Jetty server on port 19,009: Address already in use

  13/01/22 22:46:39,999 ERROR cpm.commands.Server [main]: CPM failed to start`  

  `

  13/01/22 22:46:40,000 ERROR utils.runtime.CpAssert$DefaultAssertionErrorHandler [main]: AssertionError has been caught: Uncaught exception org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'wsPublisher' defined in class path resource `  
  `[com/checkpoint/management/web_services/internal/ws-internal-config.xml]: Invocation of init method failed; nested exception is org.apache.cxf.interceptor.Fault: Could not start Jetty server on port 19,009: Address already in use in thread Thread[main,5,main]
  `  

  `
  Caused by: org.apache.cxf.interceptor.Fault: Could not start Jetty server on port 19,009: Address already in use`

## Cause

1. The Jetty server could not be started because some other process is holding the connection to the port the jetty server needs to run in, and in this case, it is port 19009. This web server is needed for our processes to function properly and gain access to our server.
2. The process holding the port was not killed properly.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content
