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

# sk180967 - SmartConsole fails to connect to the Management Server with the "Connection timeout" error

| Property | Value |
|----------|-------|
| Solution ID | sk180967 |
| Date Created | 2023-05-11 |
| Last Modified | 2023-05-16 |
| Technical Level | Advanced |
| Products | Security Management Server, Multi-Domain Security Management Server |
| Versions | R81.20, R81.10 (EOS), R81 (EOS), R81 (EOS), R81.10 (EOS), R81.20 |
| OS | Gaia |

## Symptoms

- * SmartConsole fails to connect to the Management Server with the "*Connection timeout*" error.

* The *$FWDIR/log/cpm.elg* file on the Management Server contains these lines:

  `<DATE> <TIME>,<PID> ERROR infrastructure.logging.DefaultExceptionLoggerHandlerImpl [main]: incident [xxx-xxx-xxx-xxx-xxx]:`  
  `
  CpmGeneralException{base='com.checkpoint.management.is.exceptions.CpmGeneralException', errorCode='CP_ERR_UNSPECIFIED', errorFamily='no stored dlesession id found.`  
  `
  HINT: Make sure to propagate dlesession id for this thread', messageForUser='null', message='null'}`  
  `
  at com.checkpoint.management.cpm.commands.Server.checkDeadlockQuery_aroundBody0(Server.java:<N>)`  
  `
  at com.checkpoint.management.cpm.commands.Server$AjcClosure1.run(Server.java:<N>)`  
  `
  at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:<N>)`  
  `
  at com.checkpoint.management.dleserver.coresvc.internal.TransactionRetrySvcImpl.proceed(TransactionRetrySvcImpl.java:<N>)`  
  `
  at com.checkpoint.management.dle.aspects.TransactionRetryAspect.aroundOperation(TransactionRetryAspect.java:<N>)`  
  `
  at com.checkpoint.management.cpm.commands.Server.checkDeadlockQuery(Server.java:<N>)`  
  `
  at com.checkpoint.management.cpm.commands.Server.checkPostgresDeadlock(Server.java:<N>)`  
  `
  at com.checkpoint.management.cpm.commands.Server.run(Server.java:<N>)`  
  `
  at com.checkpoint.management.cpm.Cpm.main(Cpm.java:77)`

## Cause

The CPM process might fail to start because it might fail to check for deadlocks in the PostgreSQL database.

This issue occurs on Management Servers that run:

* R81.20 Jumbo Hotfix Accumulator Take 8 and higher
* R81.10 Jumbo Hotfix Accumulator Take 93 and higher
* R81 Jumbo Hotfix Accumulator Take 82 and higher
* R80.40 Jumbo Hotfix Accumulator Take 196 and higher
* R80.40 with the hotfix "R80_40_jhf_t156_317"

## 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
