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

# sk182112 - AWS CloudGuard Security Gateway boot into 'Sh-4.4' shell after in-place upgrade to R81.20 with Jumbo HFA Takes 38-53

| Property | Value |
|----------|-------|
| Solution ID | sk182112 |
| Date Created | 2024-03-20 |
| Last Modified | 2026-04-19 |
| Technical Level | General |
| Products | Cloud Firewall |
| Versions | R81 (EOS), R81.10 (EOS), R81.20 |
| OS | Gaia |
| Platform | AWS |

## Symptoms

- * An R81.20 Security Gateway/ClusterXL in AWS boot up to 'sh-4.4' shell after installing an in-place upgrade package from [sk177714](https://support.checkpoint.com/results/sk/sk177714) and then installing Jumbo HFA with Takes 38-53.

* You see this output in the serial console during the Security Gateway boot:

      
      Starting aaa_os_pre_udev_cloud:  [  OK  ]
      Telling INIT to go to single user mode.
      INIT: Going single user
      INIT: Sending processes the TERM signal
      INIT: Sending processes the KILL signal
      Error: 'Couldn't connect to /tmp/xgets:  No such file or directory
      '.
      sh-4.4#

* You see these logs in the */var/log/messages* file:

  ```
  
  [DATE][TIME] r8040-cluster-member-b CKP: failed to execute `taskset -c 0 insmod -f -o simmod_0 /etc/ppk.boot/boot/modules/sim_kern_64_3_10_64.o
  sim_kversion=3 sim_kpatchlevel=10 sim_ksublevel=0 sim_kextraversion=1160 sim_fast_xmit=0 fwha_unicast_only=1 sim_sxl_dev_id_modglob=0 sim_num_of_instances=1
  kiss_usermode_enabled=1 kiss_sxl_usermode_enabled=0 sim_is_scalable_platform=0'
  ```

* The issue does not occur when you deploy the Security Gateway with version R81.20 that already includes Jumbo HFA Takes 38-53.

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 54

If you choose not to upgrade, and you have a snapshot of the Security Gateway, based on [sk180259](https://support.checkpoint.com/results/sk/sk180259), you can use it to revert back to a working state.   
As an alternative, redeploy the Security Gateway in AWS. For deployment information, refer to the AWS documentation for your solution on the [Check Point CloudGuard Network](https://support.checkpoint.com/product/456) page.

---

# 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